There should be someone on pager duty if you really have to get it fixed today, but first…

?

RMC may be stuck in bootloader. If you have access to a DM frame, try connecting it to a DM output and doing REPORTDMNET in text console on the matrix and see if (and how) it reports.

?

If you don’t have access to a DM matrix, do the same thing from the transmitter.

?

If you see it report, usually the easiest thing is to run PUF tool pointed at the non-RMC side of the equation, and PUF tool should pick up the RMC even in bootloader and either automatically select it or allow you to manually select it to push firmware.

?

If it is reporting, but PUF tool isn’t playing nice you may have to go the more circuitous approach of extracting the specific firmware from the PUF, setting up an indirect connection in Toolbox, and manually updating the firmware.

?

If it doesn’t report at all, it may be time for an RMA

?

?

?

Hi everyone,

?

Understand TB is closed today, I am wondering if any of you can shed some light on issue connecting to RMCs.

?

I have 11 RMC's ?- Tx pair in which each RMC is connected to a network switch with DHCP server on. Originally, I was able to see all 11 RMC's but when I performed puf?update via script manager, 5 out of 11 failed (during scripting upgrade, I was connected to the switch and only updated RMC's together).?

?

I was like no biggey as it's not the first time an update has failed so I tried to connect to each directly without any tx attached. Currently, I can't connect to any of this 5 RMC's. I tried resetting, setting them to static IP. ?Even after setting them to static IP, I can't discover them or ping them at the default IP (my pc ip?was set to 192.168.1.200 and pinging to .221).

?

Weird part is that If i attach tra nsmitter to each of the receivers and tie the lan?of rmc?to switch with dhcp, i can see all the transmitters and able to batch upgrade them without a problem but can't seem to connect to any RMC.

?

Any thoughts?

?

?