Re^3: Telnet.pm and IAC

Actually the problem is not with the Watlow but with the Digi CM-32. The Watlow is communicating to the Digi CM-32 in Modbus RTU which has no issues with \xff characters.

See if there is some option you can set in the Digi CM-32 to allow "raw" data mode or some such. If not, you may need to implement your ethernet communication with raw TCP sockets using IO::Socket::INET, which is what Net::Telnet uses under the hood.

Comment on Re^3: Telnet.pm and IAC

Replies are listed 'Best First'.
Re^4: Telnet.pm and IAC by PaulNg (Novice) on Feb 25, 2012 at 04:32 UTC
Hi thudergnat, I agree, but now I'm not sure if it's the CM-32's busybox OS is the one interpreting the IAC or is it Telnet.pm on my PC that's doing it. I'm actually leaning more towards Telnet.pm causing the problem. I tried Khen's fix earlier it didn't work. The output did not change at all. TCP protocol isn't recommended because there are other scripts that require the CM-32 to be in Telnet mode rather than RawTCP. Any suggestions? Thanks!	[reply]

Replies are listed 'Best First'.

Re^4: Telnet.pm and IAC
by PaulNg (Novice) on Feb 25, 2012 at 04:32 UTC

Hi thudergnat,

I agree, but now I'm not sure if it's the CM-32's busybox OS is the one interpreting the IAC or is it Telnet.pm on my PC that's doing it. I'm actually leaning more towards Telnet.pm causing the problem. I tried Khen's fix earlier it didn't work. The output did not change at all. TCP protocol isn't recommended because there are other scripts that require the CM-32 to be in Telnet mode rather than RawTCP. Any suggestions? Thanks!

[reply]