Thanks for testing, that's really helpfull.

If you go to the middle of the pagescript and change:
widget("_PS_DEBUG_").visible = false;

to:
//widget("_PS_DEBUG_").visible = false;

Does it give any error in the debug panel? You may have to make the panel bigger to fully read the error.

There are some error messages that are repeated:

line #68 GUI widget "PNLMODE"
pronto script error: type error GUI.widget PNLMODE

sometimes simply:

pronto script error: failed

sometimes:

offending line #5
pronto script error: type error GUI.widget PNLMODE

In general, if one hits a button VERY briefly, one gets less lock ups but if one hits a button longer than half a second or so, it nearly always locks up.

While the PNLMODE problem is interesting and I've changed it for 1.40 (unsure if the change helps because the problem is non existing on DVD3910), it shouldn't be the cause of the lockup. That's in the receiving part and something seems to kill the sending part. Could you change:
GUI.widget("PNLMODE").label = DenonPlayer1.Answer.Mode;
to:
//GUI.widget("PNLMODE").label = DenonPlayer1.Answer.Mode;

and see if there's another error?

And one more question about the PNLMODE problem, do you get it with all disctype (cd, dvd and bd) or only with blurays?

With this script-change there's this error displayed:

Pronto Script Error: Failed
Offending protected library script: Tag: "DenonPlayer (the rest is not readable)
Offending line #5

after that, it's locked

And if you increase the poll delay to 400? (This probably won't help, but I do need to know if it does, then I don't have to look at the timing)

Edit: This probably could help. If I lower the polldelay to 50 I get lockouts aswell.

If it does work I'll enable the dynamic timings, which is a feature that was actually ment for 2.0.

With poll delay 400 the same message appears, but only after one has pressed about 10 or more buttons. It seems the locking appears less often.

And with a general delay of 300, poll delay of 400 and only using play stop and pause, does it still lock out?

With this setting I can't get it to lock out, with ALL keys.

Does Audio and Sub +/- work?

1.40 Will have a different way of execution, something between dynamic and static. It also will not lockout instead it will display an error and keep running. Also the debugging will tell how high the error rate per minute is (Should be lower then 7, I'm getting 1 - 2). So you can check if your delays are doing you any good.
Also BD IP will be dropped from 1.40 and postponed until RS232 on BD players runs as great as on DVD and when Í have managed to get a Denon player with IP for testing. It takes way to much time without a player here.

1.40 send out. If you didn't receive it please email or PM me.

Locking problems should be gone, however there is no way to test for me.

First of all: Thanks for the new version!

I get the message

Communication Timeout Possible Player powered off
Dealys too low.

I have increased general delay to 300 and poll delay to 400 - without success

Edit:
Sorry, my fault, the port number was wrong - now the module runs very well, with out any lock-ups!

No problem, nice to know what mistake you made, I'll add that cause to the errorbox.

1) Does audio+, audio-, sub+ and sub- work on a BD player?
2) Does it run without issues on the default delays?
3) Could you run the 9600 version in the simulator and tell me if you like the homescreen?

1) So far, these buttons never worked, I will test again this evening. However, I doubt they ever will, because the 2500BT has a different interface: first one has to open the on-screen menu for audio, then one can select an audio track. The same with the subtitles.

2) No it doesn't with the default delays, I still got lock-ups. Now I use 300 general delay and 400 poll delay and that works without problems, except that sometimes I still get the error message above, but without apparent reason, because the module at that moment has done and still does all it should and doesn't lock up.

In this context I should maybe mention that my RFX9600 isn't directly connected to the router via ethernet but via a WLAN bridge, which probably causes delays(?).

3) I really like your homescreen for the 9600. In fact I have made one for the 9400 and for my devices that looks quite similar!

1) Is that only for Bluray or also for DVD? Do you know if it's the same for the other BD players?

2) Every wireless hop causes a delay and will lower the transferspeed. The transferspeed is not an issue because the ammount of traffic from and to a remote is very low, the delay is a bigger issue. Also the ammount of devices using the accessPoint cause bigger delays and lower transferspeed. I'm using extremely quick networkequipment and use a fast (330MHz) router stictly as a accesspoint for the TSU and it doesn't have to do DNS and DHCP. Could you ping your remote and extender? And tell me the longest and average ping time? (Go to the settings on your remote and remember the IP. Go to your pc and open a command box and run ping [remote's ip]) Here's my ping (PC->main switch->ap->remote)

C:\>ping 192.168.1.8

Pingen naar 192.168.1.8 met 32 bytes aan gegevens:
Antwoord van 192.168.1.8: bytes=32 tijd=4 ms TTL=64
Antwoord van 192.168.1.8: bytes=32 tijd=3 ms TTL=64
Antwoord van 192.168.1.8: bytes=32 tijd=6 ms TTL=64
Antwoord van 192.168.1.8: bytes=32 tijd=6 ms TTL=64

Ping-statistieken voor 192.168.1.8:
    Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
    (0% verlies).

De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
    Minimum = 3ms, Maximum = 6ms, Gemiddelde = 4ms

And the ping to my extender (PC->Main Switch->Switch2->Extender):

C:\>ping 192.168.1.250

Pingen naar 192.168.1.250 met 32 bytes aan gegevens:
Antwoord van 192.168.1.250: bytes=32 tijd<1 ms TTL=64
Antwoord van 192.168.1.250: bytes=32 tijd<1 ms TTL=64
Antwoord van 192.168.1.250: bytes=32 tijd<1 ms TTL=64
Antwoord van 192.168.1.250: bytes=32 tijd<1 ms TTL=64

Ping-statistieken voor 192.168.1.250:
    Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
    (0% verlies).

De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
    Minimum = 0ms, Maximum = 0ms, Gemiddelde = 0ms

This roughly means my average time from remote to extender is 4 + 0 = 4ms and my max is at 6 + 0 = 6ms (When doing this longer I see an average of 6 and a max of 7ms) Even better for you would be opening two command prompts and do a ping -t [ip] for both at the sametime. Also you player might be slower then mine. I'll re-enable the logging of the time to send and receive in the next version. Another thing you could check is enabling the errorrate in the parameters, when it's to high (the rednumber on the top >7) this will cause delays aswell.

3) Ok, I'll do the rest of my ideas for the home screen aswell.

And thanks for the feedback, you're one of the few who actually tests and reports.

The pings deliver inconstant values for the remote (three typical examples):


C:\>ping 192.168.2.116

Ping wird ausgeführt für 192.168.2.116 mit 32 Bytes Daten:
Antwort von 192.168.2.116: Bytes=32 Zeit=21ms TTL=64
Antwort von 192.168.2.116: Bytes=32 Zeit=9ms TTL=64
Antwort von 192.168.2.116: Bytes=32 Zeit=7ms TTL=64
Antwort von 192.168.2.116: Bytes=32 Zeit=7ms TTL=64

Ping-Statistik für 192.168.2.116:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 7ms, Maximum = 21ms, Mittelwert = 11ms

C:\>ping 192.168.2.116

Ping wird ausgeführt für 192.168.2.116 mit 32 Bytes Daten:
Antwort von 192.168.2.116: Bytes=32 Zeit=18ms TTL=64
Antwort von 192.168.2.116: Bytes=32 Zeit=6ms TTL=64
Antwort von 192.168.2.116: Bytes=32 Zeit=5ms TTL=64
Antwort von 192.168.2.116: Bytes=32 Zeit=4ms TTL=64

Ping-Statistik für 192.168.2.116:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 4ms, Maximum = 18ms, Mittelwert = 8ms

C:\>ping 192.168.2.116

Ping wird ausgeführt für 192.168.2.116 mit 32 Bytes Daten:
Antwort von 192.168.2.116: Bytes=32 Zeit=11ms TTL=64
Antwort von 192.168.2.116: Bytes=32 Zeit=8ms TTL=64
Antwort von 192.168.2.116: Bytes=32 Zeit=9ms TTL=64
Antwort von 192.168.2.116: Bytes=32 Zeit=7ms TTL=64

Ping-Statistik für 192.168.2.116:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 7ms, Maximum = 11ms, Mittelwert = 8ms


and this the RFX9600 (with constant values):

C:\>ping 192.168.2.115

Ping wird ausgeführt für 192.168.2.115 mit 32 Bytes
Antwort von 192.168.2.115: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.2.115: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.2.115: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.2.115: Bytes=32 Zeit=3ms TTL=64

Ping-Statistik für 192.168.2.115:
Pakete: Gesendet = 4, Empfangen = 4, Verloren =
Ca. Zeitangaben in Millisek.:
Minimum = 3ms, Maximum = 3ms, Mittelwert = 3ms