RE: Comms issue with New Focus 8752 motor driver

[Mark Rivers <rivers@cars.uchicago.edu>]

I don't think this is the problem.  The driver can change the eos before and after each command it sends.

#define PROMPT_EOS      ">"

...

    if (eos)
      // Temporary Change to End-of-string
      pasynOctetSyncIO->setInputEos(cntrl->pasynUser,eos,strlen(eos));


    /* Perform atomic write/read operation  */
    status = pasynOctetSyncIO->writeRead(cntrl->pasynUser, send_com, size,
                                         recv_com, BUFF_SIZE-1,
                                         PMNC_TIMEOUT, &nwrite, &nread, &eomReason);
    if (eos)
      // Reset EOS to default
      pasynOctetSyncIO->setInputEos(cntrl->pasynUser,PROMPT_EOS,strlen(PROMPT_EOS));


Mark


-----Original Message-----
From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Kevin Peterson
Sent: Tuesday, August 20, 2013 2:03 PM
To: tim.hayton@stfc.ac.uk
Cc: tech-talk@aps.anl.gov
Subject: Re: Comms issue with New Focus 8752 motor driver

On 8/20/13 1:13 PM, tim.hayton@stfc.ac.uk wrote:
> send_recv_mess(): message = VER
> 2013/08/20 17:37:57.736 192.168.42.31:23 write 4
> VER\r
> 2013/08/20 17:37:57.742 192.168.42.31:23 read 16
> Version 1.6.0\r\n>
> send_recv_mess(): recv message = "Version 1.6.0
> "

It looks like the input terminator may not be set correctly.  If the
asynOctetSetInputEos really set the input terminator to ">", there
shouldn't be any ">" characters in the responses that are received.

What is the response to the following command?

asynOctetGetInputEos("serial1", 0)

Kevin