Pronto TSU9600 and RFX9400 do not appear to be communicating despite being set to "stand alone" mode. This system has been working for the past 2 years, however last week the TSU9600 started displaying "Command Failed" and the remote no longer controls any of my devices. I reinstalled the firmware for both the RFX9400 (v1.4.8) as well as the TSU 9600 (v7.4.22). I also changed the extender ID from 0 to 3 but still no joy. The lights on the RFX 9400 show no obvious signs of a problem (WiFi light is solid green), however the 2 units aren't working together. Anyone have an idea of how to troubleshoot from here?

Thanks for your help!

Ron,

What are the network settings in ProntoEdit? Can you post a screen print uploaded to some site? If you changed extender ID from 0 to 3, you made a change there and would like to see what they are. And if RFX is in standalone mode, is it using DHCP or fixed IP address? Can you possibly share a screen print of the RFX setup screen as well?

Thanks,
Lyndel

If both the remote (per the configuration file downloaded) and RFX9400 (hard switch on the back) are set to Stand Alone mode a wireless ad-hoc network is established between the two automatically. There are no user configurable options in this case aside from setting each to Stand Alone mode. That being said, there is nothing you can do that I know of short of performing a full firmware update for the remote which perhaps you haven't done and reflashing the firmware for the extender. Instructions for performing a full firmware update can be found here.

LowPro,

I had something weird happen a while back. Extender was set to non-DHCP and IP addy was not in the correct subnet and for some reason, would not connnect. When reset to be DHCP, everything started working.

Lyndel

Thanks for the responses. I finally figured out that the issue really wasn't communication related. When troubleshooting I decided to go ahead and take the remote out of wireless and use IR. My hunch was right and somehow the unit "forgot" it's programming. Not sure how to account for this as I hadn't done a firmware upgrade recently or any changes in over 3 months. Nevertheless, I tweaked the programming and downloaded it to the remote. IR worked right away as did the RF in standalone mode. Weird, but fixed.

Thanks!

Ron

Well, trouble in paradise again... Wife informed me that the remote wasn't working again and it appears to be a communication problem between the TSU 9600 and the RFX 9400. I checked and everything is still set for stand alone mode on the back of the extender. Switch is set to "stand alone", Extender ID arrow is pointing to "0" and the configuration switch is set to "1". I tried the above trick taking the extender out of the program in order to test IR and indeed the remote performed fine while in IR mode. I added the extender back in with the Extender ID set properly and I continuously get the "Command Failed" message. Not sure what else to try here... nothing seems to get these two guys communicating again.

Anyone have some ideas?

Thanks!

Ron Carmichael

Hi , i think you may be getting interferance from another device , can you down load a copy of inSSider and do a scan of the wirless networks around you and send me the screen shot

Hi. I'm wondering if this thread has been resolved, as I'm experiencing this exact issue and have tried unsuccessfully to get the TSU9600 and RFX9400 communicating again. I've updated both units to the newest available firmware and have gone over whatever config combinations I could. When I originally had the problem in standalone mode, the RF Symbol on the TSU9600 had no bars. I noticed that the Pronto_Network_1 ad hoc network shows on a WiFi scan only when the TSU9600 is on, but not if only the RFX9400 is on - is this normal? I have tried setting both units to communicate over the home network, giving them static IP addresses and being careful they are on the same subnet with the same gateway... still get a "Command Failed" message whenever a command is trying to use the extender. I am suspecting this could end up being a RFX9400 hardware issue, and good luck to me finding a fairly-priced replacement now...

Hi have you also had any new devices in your home Cordless phones baby monitors, new Access points etc?

Reinstall the firmware in the RFX9400 and then reboot it.

Thanks for your replies, but still no luck

gopronto, yes - the problem originally occurred sometime after a new access point was installed in the house, so I've tested with the AP switched off to make sure there was no interference, plus I've narrowed its band, switched its channel to the other end away from the Pronto's. The only thing consistent is the TSU and RFX not connecting. That was another reason I went for network

Lyndel, I've reinstalled both units' firmware multiple times, rebooted, and the problem remains. I tested with a different TSU9600, every attempt to connect with the RFX9400 = "Command Failed"

I'll note also that the last time the unit actually worked (probably 3 weeks ago) was after a simple reboot of the RFX9400 - but it only worked for about a day. Since then, nothing I have tried has given me even a sporadic connection.

If I had access to another RFX9400 I'd be able to pinpoint whether this is a hardware issue, which is what my intuition tells me.

I understand there are users on the forum who may have "hoarded" Pronto units a few years back - if any have lost their love affair with the line, I may be interested in taking one off their hands (for, well what is a reasonable price?), or possibly trading for a TSU9600 or TSU9400...

I had the exact same issue recently. My remote/extender had been working flawlessly for almost 2 years and then suddenly would not communicate with one another. Turns out that my recent HTPC build had caused some interference with my extender. I simply relocated the extender and we're back in business.

We'll, after a couple of years working fine, the rfx 9400 is going flaky..once per day I look.over at it and all three red leds are lit.

No new wireless devices recent enough that I can even remember.

Sounds like your extender may have a fixed IP and maybe you switched routers and the DHCP address range is conflicting?