| 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 2025 | 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 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | RE: ASYN command string with null character |
| From: | "Bruins, Stefan" <[email protected]> |
| To: | "'Marty Kraimer'" <[email protected]>, "'[email protected]'" <[email protected]> |
| Date: | Tue, 29 Nov 2005 14:47:21 +0100 |
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
Aan: '[email protected]'
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