Re^2: Expect.pm CTRL Characters not being recognised by remote device

All good points. I tried using the send_slow capability of expect to add a 1 sec delay between each character - didnt make a difference. Within my script the syntax does conform to the same as in the doc. With debug(3) discovered the following :-


Sending '\020\004\024' to spawn id(4)
Expect::print('Expect=GLOB(0xd67aac)','\x{10}\x{4}\x{14}') called at S
+DU/CommandIteratorSDU.pm line 1076
[download]

In the unix nutshell book i have:-


character  octal hex
ctrl p     020   10
ctrl d     004   04
ctrl t     024   14
[download]

So its sending the sequences as hex and the conversion looks good. Time to sniff the packets

Comment on Re^2: Expect.pm CTRL Characters not being recognised by remote device Select or Download Code

Replies are listed 'Best First'.
Re^3: Expect.pm CTRL Characters not being recognised by remote device by set_uk (Pilgrim) on Apr 11, 2007 at 21:41 UTC
Managed to sort it by sniffing the packets. Wasnt the perl script it was the mode that telnet was running in - needed to be character mode - not line mode. Thanks for all your help	[reply]