ip client and server issues are still a problem

[Ron]

1. I am working on the input thread of Girder in Girder 3.2 I never said Girder 3.1 fixed the problem of dropped events. So please stop filing bugs for this.
2. I never heard of " eclient "
3. Post an exact description step by step how I can recreate the payload corruption to appear.

[Ron]

Rick,

Could you please give exact step by step description how I can recreate the payload corruption, I do not see it here ( which does not mean it is not there ).

Thanks

[rickd]

Ron I have switched back to the standard 3.12 of Girder and I still have issues with the ip client and server I am losing events the logger see the connection but the eventstring is not passed in this case screendown.

The machine that recieves it has my slink-e attached and I want it to simply pull my screen down when it receives this. Also I have had several crashes with the error eclient has caused girder to crash.

[edit: removed lotsa output]

The payload bug is still there after a reboot it reappeared.

See log above how the event bracket is missing.

Much later more testing
My Event seems to work fine when I send it on it's own so I suspect it's getting out of a loop to early...I am damned if I can find it.

I can send the groups if it helps.

Rick

[rickd]

Sorry Ron :oops:

I did not mean to go over old ground I am not dropping events for everything else only a new command I added which is simple and does not make sense. I need to do some more work to figure this out because the group works fine executed on its own.

It basically disables a group (on serial even so it does not create another event to jump out of this group) sends an input serial command to the projector then sends an event via ip client to another machine which then sends an ir command to pull the screen down via the slink-e attached to the other machine. It works if the group is executed by it self.

It fails when it is triggered by an On serial Event group.....this group is trigged by the processor (receiver) anytime you do an input change. Everytime you do something it returns it status creating a serial event.

It checks the change by the data received back via rs232 then based on the input then sends a serial command to the projector to change it to the appropriate input. (note I disable the receive event group first so that it does not jump out of this group based on receiving another serial command) The group that has the input change command also has the internet event client
sending a command "down" to the machine with the slink-e. This group is working but and the input is changing on the projector so it's getting to that group but the internet client is not getting though.

I am wondering if puting a wait in may help? I will try that.

I have made some changes and the crashing has stopped so don't know what was causing that. It was definitely the client crashing grider.

I will do more testing to determine what is different or the situation that causes this to occur. I think I need to put counters in to insure it's not jumping through to many loops and creating to many events on itself.

As for the payload corruption. I reloaded Girder 3.12e added an internet client event then saved. Grider crashed, then rebooted my machine to be safe and the payload issue was back. I run on ME.

Thanks Rick

[rickd]

Sorry Ron it is really weird it's gone again....I am making progress though this is occurring cause my system is trying to send too many internet events at one time......and some are being dropped (as we know) limiting the exchange of data seems to eliminate the issue.

It is also crashing Girder with Ieventc.dll error closing Girder. I also have to restart Girder on the other machine for them to handshake again.

Cheers Rick

[rickd]

Ok I have it working reliably now .....it seems having a disable group command before the internet client event was causing the crash every time so it was repeatable changing the order fixed it. Not sure why.

So it is all good now.....