craig_blizard
Member
Hey Marsupilami,
Thanks for the tips. you are correct, i should be able to get this to work but something strange is definitely going on.
In answer to your questions:
1) there is no telnet port however using ssh and netcat i can definately connect to the device through the port i have configured in my citect setup.
2) yes i ran the computer setup wizard
it is all pretty much standard, this pc is an ioserver as far as i can tell
3) i am not running multiprocess
4) i am running citect version 7.1
5) using wireshark i am not seeing any traffic coming from citect only what is expected from the PLC end.
6) looking into the kernal i wasn't able to use the TCPIP debug character for some reason. Not really sure how do use it but i will read up on that next.
7) both sides have TCP for the port that i am talking but the PLC also has a seperate dedicated UDP port used for broadcasting distributed messages. This has no effect on the port i am interested in.
8) no messages in the kernal that point to anything wrong.
THIS IS SO STRANGE .. It's a very simple implementation.
I will comment on the current setup next.
Thanks for the tips. you are correct, i should be able to get this to work but something strange is definitely going on.
In answer to your questions:
1) there is no telnet port however using ssh and netcat i can definately connect to the device through the port i have configured in my citect setup.
2) yes i ran the computer setup wizard
it is all pretty much standard, this pc is an ioserver as far as i can tell
3) i am not running multiprocess
4) i am running citect version 7.1
5) using wireshark i am not seeing any traffic coming from citect only what is expected from the PLC end.
6) looking into the kernal i wasn't able to use the TCPIP debug character for some reason. Not really sure how do use it but i will read up on that next.
7) both sides have TCP for the port that i am talking but the PLC also has a seperate dedicated UDP port used for broadcasting distributed messages. This has no effect on the port i am interested in.
8) no messages in the kernal that point to anything wrong.
THIS IS SO STRANGE .. It's a very simple implementation.
I will comment on the current setup next.