TCP/IP : only "TCPIP_connect" gets through

[Ron]

So you are using 2 plugins, the server and the action plugin. I think you have to put the server into 'compatiblity mode' or something similar before this works. The new version is a little different from the original.

[Ron]

What you can do is, take the old tcpip.dll and put that in the hardware directory of the new girder install. That should fix your problems to and have the new girder.

[Ron]

I've updated the tcpip client plugin, download it from the download page. Let me know if it worked for you.

[Ron]

When does that access violation happen ?

And the plugin is rewritten from scratch in C++ while it was previously written in Delphi, so that is where the smaller size comes from.
This is also the reason that it cannot use the old settings. Please upgrade Girder to make
sure the plugin works correctly.

-Ron

[Ron]

Nothing to be embarraced about, if 2.0.23 works for you perfect. Did you get it to work again after a reinstall ?

[Caffiend]

Let's see if I'm still registered :wink:

So I think the original problem you had with "TCP_Connect" being the learned event is that you weren't supposed to learn the event. Change the box next to the Learn Event button from All to TCP/IP Server. Then when you click Learn Event you should get a pop-up dialog asking you to enter a string. That's what you'd pass from the client to trigger the event.

-will

[Harald]

I want to control Girder on PC2 by another Girder on PC1. Connect from Girder on PC1 to PC2 works. But whatever I try, the captured "IR code" on PC2 after "Learn event" is always "TCPIP_connect". I don't get the string that I entered in the "setting" of the given command on PC1.
Thus whatever command I give on PC1 that have different settings, always "TCPIP_connect" is put through.

My next try on PC1 was the usage of tcpclient: I tried different strings in command, but I only see on PC2 the string "TCPIP_connect".

I suspect that I am misunderstanding a great deal of the concept of the TCP Plugin. E.g. should "command" in tcpclient be the name in the tree (what's initially "new")

I've installed the latest versions of Girder and the TCP Plugin (older versions make no difference).

Cheers,

-Harald

[Harald]

Ron, your answer shows me that not all my actions seem faulty.

Sure I've tried the compatibility option: no change. I have configured both Girders in the same way: TCP/IP Hardware & Software Plugins activated, Keyboard disabled (like how described in the new TCP Plugin). Both Plugin settings contain the IP addressees of both PC's.

Cheers,

-Harald

[Harald]

I solved my problem by installing the "old" version 3.019. All works as expected.

This means that there are some problems with the new TCP/IP plugin in combination with newer Girder versions.

Cheers,

-Harald

[Harald]

I have implemented your updated TCPIP client that appears as "TCP Client 2" in the action plugins.

Unfortunately there is an access violation:

Exception EAccess Violation in modul TCPIP.DLL at 00001124
Access violation at address 019B1124 in TCPIP.DLL. Write address FF5CA120

This occurs in version 3022 which I had to install since 3019 suddenly quit working. Very weird: password was suddenly wrong. When I checked the client setting, password was reset to blank and port to 0 instead of 1024. The "apply" with the proper values were accepted but not really entered in the registry - the values were just ignored in the settings.

With 3022 and the old tcpip.dll all seem to be working now. What's remarkable with the new tcpip.dll: it's only half as long as the old one with 25K ! Normally updated programs become longer :wink:

[Harald]

Will,

thanks for the hint: I did that and even disabled the keyboard plugin. But I'm rather happy with version 3.022.

-Harald

[Harald]

I uninstalled the version 3.022 and tried 3.023. I copied your tcpip.dll to pluginsoftware (replaced the old one).

I had to fill in again IP numbers, password and port in the client setting.

When I tried to execute a client command that just sends a string to the Girder on the other PC, I got the access violation, this time in slightly different addresses.

When I tried to inspect the settings for this command, I got :
invalid page in tcpip.dll at 017f:019b1bb3
and Girder finished.

To make the test complete, I copied girder.exe from 3.24pre in to the girder directory - the error did not change.

I really appreciate your efforts!

Thanks,

-Harald

[Harald]

Ron, I'm a little embarrassed and am sorry for the traffic I caused.

I installed now 3.023 (without your new dll) and astonishingly all my previous problems are gone (especially the "TCPIP_Connect" problem).

The problem starts again when I copy the new tcp/ip plugin from http://www.guerette.net. Once used, even replacing tcpip.dll with the original module doesn't help anymore: the installation is ruined (incompatibilities in the registry settings?).

[Harald]

No more problems any more - they were just made for me to better understand Girder. Thanks.