but wouldn't that reversal return
SET MDI ACK\n\r
instead of what i'm getting:
\rSET MDI ACK\n
? it seems like i'm getting the ACK string *between* the cr and lf instead
of having them reversed at the end.
thanks!
On Sat, Jun 12, 2010 at 10:29 PM, Eric H. Johnson
ejohn...@camalytics.com
I am basing what I said on looking at the code, I have not had a chance to
try it. Are you seeing that through your code? Can you reproduce it through
other means, such as directly through telnet?
Regards,
Eric
but wouldn't that reversal return
SET MDI ACK\n\r
instead of what i'm getting:
I don't see the same behavior over telnet, although I can't examine
the raw strings that way and I'm not trying to store and work with the
strings it's sending back like I am with my client. But given what I
see over telnet it appears to work fine.
I found a way to deal with it on my end. I
To: Enhanced Machine Controller (EMC)
Subject: Re: [Emc-users] unexpected output from emcrsh
I don't see the same behavior over telnet, although I can't examine
the raw strings that way and I'm not trying to store and work with the
strings it's sending back like I am with my client. But given
I've been working on a client that talks to emcrsh. I've figured out
that I'm getting unexpected output over the socket. Unexpected
because the format of the returned strings vary. The variance is in
the escape characters so I will write my strings as raw strings below.
For example, if I send:
It looks to me like there is a case in using the 'set' command that the
termination cr lf gets reversed. IOW it is terminated as lf cr. If you
swallow the cr lf, regardless of order, you should be ok. When I get a
chance, I will update it to always return cr lf in that order.
Regards,
Eric
