EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <2005>  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <2005>  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>
Subject: FW: ASYN command string with null character
From: "Bruins, Stefan" <[email protected]>
To: "'[email protected]'" <[email protected]>
Date: Tue, 29 Nov 2005 15:36:32 +0100
 
One thing I did not made clear in the previous email: the idea is that the device has to respond to the message.
 
My first idea was to use the GBIBREAD operation for that, but this type has only got a conversion routine for the reply. I had taken a look to the GPIBCVTIO type, but this is not a query->response construction.
 
Is the only possibility to handle this creating a seperate "write" parameter table to create the request without waiting for the response and using a dummy "read" parameter table which is not sending any request but only waits for the reply. Or is there a more "elegant solution". 
 
-----Oorspronkelijk bericht-----
Van: Eric Norum [mailto:[email protected]]
Verzonden: dinsdag 29 november 2005 15:22
Aan: Bruins, Stefan
CC: 'Marty Kraimer'; '[email protected]'
Onderwerp: Re: ASYN command string with null character

If you're using the devGpib ASYN support you can create such messages merely by providing a custom 'convert' routine.  The tutorial at
shows how to do this.  If your convert routine returns a non-zero value the devSupportGpib.c code will use that value as the length of the message to send. 


On Nov 29, 2005, at 7:47 AM, Bruins, Stefan wrote:

I presume this change has to be made in the "devSupportGpib.c" file of the
asyn driver in the function "writeIt"? Will a make of the ASYN module be
sufficient or must I run the makeSupport command a second time (this may be
a stupid question but I'm pretty new to EPICS/ASYN etc...)

-----Oorspronkelijk bericht-----
Van: Marty Kraimer [mailto:[email protected]]
Verzonden: dinsdag 29 november 2005 14:27
Onderwerp: Re: ASYN command string with null character


Bruins, Stefan wrote:

For the building of device support through the ASYN driver I have to sent a
message with a null character inside. The problem is that the driver
terminates the string at this null character according to the C++ standard.
My question is, how am I able to overcome this problem?

Stefan Bruins



You have to call  pasynOctet->writeRaw instead of pasynOctet->write.

Marty Kraimer

-- 

Eric Norum <[email protected]>

Advanced Photon Source

Argonne National Laboratory

(630) 252-4793



Navigate by Date:
Prev: Re: ASYN command string with null character Eric Norum
Next: FW: ASYN command string with null character Bruins, Stefan
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <2005>  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: ASYN command string with null character Eric Norum
Next: FW: ASYN command string with null character Bruins, Stefan
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  <2005>  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·