Ok, so I was very happy to see the new firmware..

Upgraded both the rfx9400 and the tsu9400....

All seems to work fine, and I'm a happy boy again (as I can start to use prontosqueeze again :0) )

Anyway, hopes were a bit smashed she my 8 year old daughter tells me that the remote is broken!

Anyway, I come over and it seems to work fine for me... Under further investigation that evening I think I've worked out what is happening.

I've got the remote setup so that the screen does NOT come on when I press the hard keys (to save battery).... It seems if the remote has been sitting there for a little while (ie, in between ad breaks), the remote screen times out.... If I then press a hard key, the command fails.... If I first 'wake up' the remote by lifting it, then the command works...

Anybody else experiencing this?


I'm using fixed IP on both the RFS and the TSU..... Have selected single channel WPA on the pep...

Im guessing its going to be a WPA nogotiation that it heeds to do when it wakes up.

Try setting the wifi timeout to 24 hours.

WPA seems to be alot better, but I would try to set RFX's to DHCP, both in pep and in RFX setup, maybe reserve its MAC address in the router to a specific IP if you find it necessary.

Since the RFX's are logged on all the time you dont need them on static to improve speed, they are not called via IP address anyway.

As mentioned before in this thread, this is likely due to WPA handshake problems. (To verify this, you could try setting the access point to WEP or no encryption instead)

Could you please indicate which access point and access point firmware you are using ?

Some access points allow you to configure some settings related to WPA handshaking (though mostly on enterprise-grade devices, most consumer-grade have these statically set in their firmware).

Try adjusting the following access point settings to their maximum values:

EAPOL-Key Timeout
EAPOL-Key handshake retries
EAP-Request timeout
EAP-Request handshake retries

Also, some access points will blacklist a client if there are too many WPA handshake failures. If possible, disable this feature on the access point.

Thanks All.

I'll change back to DHCP to see if that fixes it... Don't want to really leave on WEP to see if that works, but will revert back ultimately to WPA for the extra security.

I'm using a Billion BiPAC 7800N.... on basic looking, it doesn't have EAPOL timeout etc, so I'll do some googling and see if I can change any values.

Just got a very quick reply from Billion (only logged the ticket 10 minutes ago!) that they don't support any changing of the EAP/EAPOL commands :-(

Does anyone know if the command failed fix requires new firmware for the TSU, RFX or both units? I've done the update on one of my TSU9600's and re-downloaded my same config to it using the new PEP2. It is working better, but I am still seeing failures. I have not had a chance to update the firmware in the RFX9600 yet and am wondering if anything was done there to help with the problem.

The software and firmware are released in sets so, yes you have to update all the pronto's and RFX's :)