I had two TSU 9600 with 2 wirless extenders and 1 serial extender all of which i bought 2 years back and programed them my self and they were working fine.

I have programed IR mouse and keyboard for my WINDOWS PC/MEDIA CENTRE thru wirless extender on the TSU 9600 with up-down-left-right cursor keys inside the rotary wheel to move the mouse.

Recently aquired a 3rd new TSU 9600 (the only diffrence the rotary wheel is more updated less round shape flatter) and uploaded the same file as being used in old TSU 9600.

Both the old TSU work fine but the new one is very erratic, it gives command failed error and does not respond, specailly when i use the cursor keys to control mouse it does not repsond says "COMMANS FAILED" and the other TSU 9600 unit also stop responding....with error "SYSTEM IN USE BY ANOHER USER"

I never faced this problme betwene my old TSU except when both were being used at same time, which is hardly ever, i checked IP all 3 have diffrent ips and no ip clash.

Does anyone know if the new TSU 9600 with new design rotary wheel is diffrent on respnse do i have to change in program file ? does rotary wheel have more functionatlity or is change only for asthetics.

I am useing Pronto profesional ver 1.1.20 and did not update is as new looks very diffiuclt and i am use to teh old editor.
Do i have to program the new TSU with new editor versions ?

Pls. help as 3rd pronto i bought for my bed room and now cant use it.

would like to add

i am useing on TSU 9600 7.2.22 on all 3 TSU 9600 v2.2 but boot loader is differnt 2 old TSU 9600 have bootloader 1.2.8 where as new one has BFU1.6.17

philips pls. help....sad i was so happy with TSU 9600 for past 2 years nad buy a 3rd one and now i am frustarted.

Philips does not respond to questions in this forum except under very rare occasions.

What, if any, entries are in the diagnostics log?
What versions of firmware are on all your extenders?
What versions of firmware (not bootloader version but application version) are in your remotes?
How many remotes are accessing the extender when this problem occurs?

If you plan to use the new PEPv2, you need to be on the latest version fo the firmware in both extenders and remotes.

If you are running latest version of firmware in extenders you will want to be running latest versions of firmware in the remote otherwise, you will get quite a few errors in your diagnostic log and some may manifest themselves as Command Failed.

Command Failed can occur for many reasons. Check the diagnostic log. Also did you try a search for Command Failed in this forum?

Here's another thread that may offer some insight.

[Link: remotecentral.com]

This "Command Failed" message is driving me nuts. If I use WPA, this happens continuously. Press a button, get "Command Failed", wait about 10 seconds, it connects and you can try the button (command) again and it works. If you then wait a few minutes and the remote has shut off the display, the problem reappears.

If I switch to WEP security, the problem never occurs. I hate WEP!

Hi Jon
what Access point are you using?

Here's some additional info:
TSU9600 Firmware 7.2.22
RFX9600 Firmware 1.4.5
PEP Version 2.4.18.0

For access points, I've used both a Linksys WRT54GL w/ Tomato software and a Westell Ultraline Series 3 (aka Verizon 9100EM) using VZ's customized Jungo OpenRG software.

I am having an identical problem, only I have WEP on my wireless access point.

Lift a sleeping TSU9600. Hit a button that uses either a RFX9400 or RFX9600. Get a "Command Failed" message. Wait a few seconds. Hit the same button. Works every time.

When I check the log, it is littered with 0450 error messages "Extender xx.xx.xx.xx didn't reply."

It definitely seems to be a problem related to waking up. I have all the latest software. Everything has a fixed IP address. My wireless timeout is set at 2 hours, and this problem happens much more frequently than that.

Would you be using DHCP on you pronto by any chance? if you are try fixing the IP address on the Pronto and the RFX :)

I have the same errors in the log and I also use static IP addresses on everything. I set my timeout to 24 hours and it didn't change anything.

Can you do a test for me? Leave the TSU9600 in the docking cradle and see if the problem is lessened. It is for me (doesn't go away, but greatly lessened).

I've got some other ideas I may test tonight. I have two different 9600's, and I have multiple access points so I can test differences side by side.

Doesn't seem to be purely a WEP/WPA issue as I've had the problem multiple times tonight using WEP. I am using a fixed channel and a 128 bit key. I'll continue trying different combinations to see if I can find something that works reliably.

These problems all started with the firmware updates for the TSU9600/RFX9600 that added the WPA support. Everything was rock solid before that.

Edit... more info

The problem seems to be limited only to the TSU9600 side of the equation. There is no delay or problems talking to the RFX9600 from the simulator while the remote itself is showing "command failed". I also have some control screens for my home automation that use TCPIP and first use fails on those as well. After the 10 second wait, the "command failed" goes away and communication with my home automation is restored.

I guess you run extenders in static IP setting, switch to DHCP for the extenders.
We have had several issues like this with the current software where it seems like the extender, which suppose to be connected all the time, act as the did not wake up properly on the first try, second try works fine.
After much tweaking, setting my extenders in DHCP mode did the trick.
(BTW i run all my gear in WEP, so this is not likely a WPA issue)
This has been reported to the Prontoteam as well.

" The problem seems to be limited only to the TSU9600 side of the equation. There is no delay or problems talking to the RFX9600 from the simulator while the remote itself is showing "command failed". I also have some control screens for my home automation that use TCPIP and first use fails on those as well. After the 10 second wait, the "command failed" goes away and communication with my home automation is restored."

Are there any extender in that macro as well?, IF so, please see my previous answer.

If by macro, you mean my code for talking to my home automation system, then no, there is no extender communication there. If you do pure TCPIP comms to another IP device from the remote, the extenders aren't involved at all. Also, as stated, if I run my XCF file in the simulator, I can communicate to the RFX9600 and it will never fail. The only failures are on the TSU9600.

I had "command failed" issues during the last 6 months. If I remember well since the WPA fuction has been enabled. I tried everything in order to solve the problem, I even replaced my D-LINK WAP with a Linksys, which didn't resolved the issue. So I read your post and you tell us to change the extender from static IP (which was my setup) to DHCP. I wasn't too much confident if that could solve the problem. So I changed from static to DHCP for the extender, and left my Pronto in Static IP as it was before an updated the system.
Since then I haven't got one single "command failed" message, and it works again like a charm. No more double press on the buttons from now on. Cheers mate you rock :). THX for that post!!!!