PDA

View Full Version : How to connect to TCP/IP Plugin?



Ron
October 13th, 2002, 12:55 PM
bodziak,

Did you enable the tcp/ip plugin ?

Does the green light in Girder light up?

If not enable the plugins :)

-Ron

Ron
October 13th, 2002, 12:55 PM
The Helpfile says :)

TCP/IP Server:
This plugin allows you to control girder from anywhere on the (inter)network. To be able to control Girder you must know the password and the port specified in the settings dialog of the Plugin. Be sure to add the IP address of the computer from where you want to control Girder. You can use the TCP/IP action plugin to control it, a simple terminal emulator or the commandline tool tcpclient.exe in the girder directory.

When you use a telnet client the first thing you should type is “pass <youpass>” girder should than
Respond with “
“2: execute <string> = execute a command in girder”
“Close = close connection”

When you want to make girder do something on a TCP event, press the learn IR button and send a IR string via the telnet session. Eg “execute teststring” Girder should now have learned the “teststring” into your command.
The next time you execute teststring girder should run the command you learned.

Mind! There is no echo of the text that you type, so maybe you can turn on the local echo function of your terminal emulator.

Regards,
Ron

Ron
October 13th, 2002, 12:55 PM
Hi,

Can you try the tcpclient.exe for me ?

Cause if netstat shows the listening
socket it should work.... "should" :)

Ron

bodziak
October 13th, 2002, 12:55 PM
I try to connect using telnet on default port 1024 but it do not connect me? . It doesn't mater if the allowed IP list is empty or it is my IP or 127.0.0.1. What is wrong ?

bodziak
October 13th, 2002, 12:55 PM
I check everything. The TCP/IP server is in listening state (tested using "netstat -a"). Telnet do not work. It seems that server do not Accept connection. Maybe it is Win2000 problem ?

Addtionaly - i can't delete IP from allowed list. Only ADD works as expexced - still in WIN2000

bodziak
October 13th, 2002, 12:55 PM
OK id did it. It due tu mu strange configuration (2 IP for one netcard). I can connect to first IP only but not to loopback address 127.0.0.1 :-).

zakrzep
October 13th, 2002, 12:55 PM
Is there documentation for the TCP/IP plugin anywhere? How does it work?

uivic
October 13th, 2002, 12:55 PM
Help! I can't get girder 3.0 to work at all. I suceeded to get girder 2.1 using the generic plugins, and then learning the command, and then binding the button. However can't find any plugins for 3.0. Tried to go to the export page and could not download the files I wanted,ie (ATI TV). Could you give me a step by step list of commands to do to make my remote work properly. ie 1. find plugins, or make plugins. 2. bind keys 3. choose commands 4. choose buttons 5.learn 6. bind. I have already tried to execute notepad like you said and don't have a clue how to do anything. Please make it really siple to understand from start to finish for girder 3.0. Please e-mail me direct at uivic@home.com

stefan
October 13th, 2002, 12:55 PM
I have a problem with the TCP/IP plugin and the newest version of Girder. :???:
I also think to have found a little bug:

Bug: The file "tcpclient2.exe" says the
usage should be "console ..." . I
think this is only a mistake in the
usage message.

Problem:
when typing:
"tcpclient [host] [port] [event]"
the return is:
" Could not connect socket "

I enabled the TCP/IP server and the client
and want to communicate this way using a PC under WIN 2000. Maybe someone knows how I can turn my plugin into action?

Regards, Stefan

umbrella133
October 31st, 2005, 12:16 AM
Hi,

Okay if you say so. :D

umbrella133
October 31st, 2005, 12:17 AM
:o) Well thats exactly what i thought.:lol::lol:

umbrella133
October 31st, 2005, 12:17 AM
Is there documentation for the TCP/IP plugin anywhere? How does it work?

I have no idea of what is going on? :o)

umbrella133
October 31st, 2005, 12:18 AM
Could some one explain that to me.. xx(

umbrella133
October 31st, 2005, 12:19 AM
OK id did it. It due tu mu strange configuration (2 IP for one netcard). I can connect to first IP only but not to loopback address 127.0.0.1

:wink: But is that not a bit risky?

umbrella133
October 31st, 2005, 12:20 AM
OK id did it. It due tu mu strange configuration (2 IP for one netcard). I can connect to first IP only but not to loopback address 127.0.0.1

V Oh please I do not think so.