Copy that.
Is the tech support number pretty much for end users only?

I seem to recall calling them about 6 months ago about RFX9400 'bleeding' signals from IR ports 1 into 2 ( and others) when I had 2 identical Denon AVRs connected, and tech support was worthless than as well.

I recently joined this club. But have some additional info.

As stated in this topic:www.remotecentral.com/cgi-bin/mboard/prontopro/thread.cgi I have encountered the problem of the RFX busy LED. At first I thought it was ht extender that was not ok. Then I started some testing.

All the FW's are the latest. I use an XCF file I used before (and it worked flawlessly), with no changes, just a new RFX, router/AP and TSU9800. Network is with or without encription, works the same way. All fixed IP.

I started getting:
0450 Extender _ IP_ didn't reply.
0404 Extender 0 didn't acknowledge command

Then I reloaded the XCF on our "default" TSU9800 whit which I make all of the configs (yes I do it all on this, then just transfer to the client's). And ... everything worked flawlessly. Not one extender error in the Diagnostics.log.

I currently have 5 TSU9800 here and tried all of them. I had 3 different behaviors:

My (the working one), worked flawlessly and has a serial number:
PL1B .... v2.2 TSU9800

The 2x PL1C...  (v2.2 TSU9800) had the greatest number of failures

The 2x PL1D... (v2.2 TSU9800 - the one with the wall-mount already in the box) had a small number of failures (at the end I hardly got any).

So it seems that the newer revisions have these problems, maybe they changed something, maybe not.  The reproducing of the errors is quite random. I noticed one more thing, all of the bad TSU9800's have a warmer top (above the pronto logo) than the working (old) one.

I also noticed that this persists for some time on the TSU, during this time there is no communication with the RFX (even not all of the failed presses are logged as communication faliures with the RFX), then after some time has passed everything starts working again.

Please can you all check the SN's  of your devices, if they match the ones I provided.

Or maybe the problem really is in the extenders.

What aree the serial numbers of the TSU9800,

Oh I might have written it a bit unclear.

When you turn it to the back you see the bar code. The bar code starts with PL1B..., PL1C .... or PL1D...

sorry i ment the serial number of the Pronto on the diagnostic page? i think the number on the back may only be a date and batch number..

I'll take a look tomorrow. I know that 2 are around 300, the outher 2 are around 1700.

Yes seems B, C, D are batches, I hope philips didn't change any hardware (like different brand WiFi IC) or had any other radical revisions of the hardware.

I doubt there has been any changes, thats why i asked for the Serial Number if they are close there is less likely to be any differances even in Component batches.

I used to be in High volume manufacturing so i know what its like :)

The working one is:
PL1B ... S/N: 262

The other 4, that have problems:
PL1C ... S/N: 368
PL1C ... S/N: 1725

PL1D ... S/N: 3141
PL1D ... S/N: 3643

The ones that I have from the PL1C batch emit a click (like button_mono.wav in pep) when I turn them off, the others don't.

The S/N to me are odd, maybe they start with the serial 0 with each batch?

I finally got a reply to an email I sent off on 20th June...


Thank you for contacting the pronto team, and sorry for the late reply.
About your problem, I can confirm that a new update will be available within a few days..
If you are in our database you must receive the newsletter, otherwise check our website regular.
Hope this is a solution to your problem?
Think more this is a network problem? What kind of security did you used? WEP or WPA?

Good news if a new firmware is coming out that will fix this... I asked to be on the beta program, but they didn't offer to put me on :-)

I have the latest firmware on my TSU9400 and my RFX9400 and this evening I have had no end of command failures!!!!!!!!!!!

Hi Richard

How is your pronto network set up?
and what encryption are you using?

"It just don't work" ain't gonna cut it for this one. We need more information, such as Network configuration, etc, please.

I'm still getting the same intermittent "command not found" error after upgrading to the latest firmware. The error message in the log is "0450 Extender 192.168.*.* didn't reply".

Network configuration:
- Extender connected hard-wired to network
- Pronto connects via Linksys WAP54G wireless access point
- Encryption WEP (WPA had too many failures and delays

Thanks,

Mark

So are we all, I think. Its certainly always been the case for me. But, as I always flash up the error message on the screen when it happens, it is not too much of an irritation in practice (I just press the button again).

My Network config is

- Extender connected hard-wired to network
- Pronto connects via BT wireless router
- Encryption WPA