Hello,

I recently procured a second TSU9400 and would like to have both talking to my centrally located RFX9400. I loaded the same xcf I run on my existing remote onto the new one and expected things to just work. Unfortunately, my codes are not being sent. Both remotes are configured to connect wirelessly in stand alone mode. When I look at diagnostics on the new remote, every remote code is throwing a 450 extender didn't reply error. The settings screen indicates that it is connecting to the RFX9400 and getting an IP address. What am I missing?

Both remotes should work with the same configuration, as long as you use DHCP for the remotes.
Have you checked the firmware of the TSU9400?

I did have to upgrade the firmware version on the new remote to bring it up to the current one (7.2.22/4.0.20). The only difference between the two is the bootloader.

I reflashed the firmware on the RFX to 1.4.5 (current version), put Philip's demo xcf on the new remote, reflashed firmware, put my xcf back on and still have the same problem. Defective remote?

If you turn off the remote that is working and then put that file onto the other remote, does it connet then?

what are the IP addresses of Prontos and RFX?

gopronto: interesting experiment, unfortunately same result - 450. I also tried turning the defective remote off and back on while the working one was off, still no go.

pthornhill:
defective TSU: 169.254.172.72
working TSU: 169.254.52.198

What is the best way to check the RFX? I can take it out of stand alone so I can connect to it, but I'm assuming that changes its IP.

Thanks for the replies.

The subnet also likely applies has well. Depending on what the subnet mask is, the 2 TSU's are in different subnet.

See Barry's post discussing subnet here.

[Link: remotecentral.com]

Hi Lyndel, thanks for the reply. I did notice that, but how do I control the IP in stand alone mode? I assume the remote is getting an IP via DHCP from the RFX, so why is it giving out IPs in different subnets?

Perhaps I need to go advanced and connect to a router? I've tried that before, integrating into my existing wireless network, but didn't have great results and went back to stand alone. One of the big problems was a delay for the TSU to connect when woken up. Are most people running a dedicated network? I've also got Sonos and a Vudu that I'd like to ProntoScript, so I guess that is an argument to have the Philips gear on my main network if I can figure out the delay.

re my comment
If the file that works in one remote does not work in the other , it may be faulty and i would take it back to the Installer / supplier.

If you wanna talk 2 sonos, you will need network mode. With regard to wifi delay, why the delay? Is it because you are using WPA vs WEP?

I am running a WPA protected network. I know a lot has been said on RC about getting these things to work with WPA since support was added, but I haven't found the time to do the reading to find the optimal settings. Sonos ProntoScripting was what tempted me to try it the first time.

This might be encouragement to try again, but I still don't see why it doesn't connect in stand alone, unless gopronto hit the mark and the remote is defective. If that is the case, I will probably be equally unsuccessful in getting the new remote to connect in network mode.

Turn off working remote, put known, good configuration into non-working remote. If it does not work then remote likely needs to be serviced.

Just to wrap this up, I upgraded to the new firmware for the TSUs and the RFX and was able to get the new remote connected. I still had spotty connectivity and and slow reconnects. I found a post by Recordable in this thread [Link: remotecentral.com] that indicated that my Dlink DIR-655 might be the problem. Too bad, because I really liked that router, but it was a good excuse to get a dual band Airport Extreme.

Anyway, it appears to be up and running much more smoothly - now it is time to start working on Sonos and Vudu ProntoScripts...

Thanks everyone for your help.