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: Syncronising triggred data acquisition for Modbus "I/O Intr" records and sscan records
From: Kuldeep Joshi via Tech-talk <tech-talk at aps.anl.gov>
To: tech-talk at aps.anl.gov
Date: Fri, 16 Jul 2021 16:37:24 +0000
Hello,
I am having a Modbus interface, I have disabled polling and I am using MODBUS_READ as a trigger. An ai record  "myData" (with SCAN as "I/O Intr" which holds the data received over Modbus.

sseq is used to give start of conversion and check for EOC and send MODBUS_READ and wait for myData to be processed (by checking busy record). In short I am using the sseq record in sscan as a detector trigger.

I am using a sscan along with sseq records for triggering and acquiring the data over Modbus. To synchronise the detectors MODBUS_READ command (I am using busy record) and on processing of myData record (I am using myData.FLNK to trigger a bo record to reset the busy record). the sseq record is waiting on this busy before sscan record acquires the detector data.

I am always getting N-1th sample instead of the Nth sample. However if I give sufficiently long detector delay time ie of 1-2 sec I am receiving proper data. I am not happy with this workaround
What am I doing wrong?

Thank you in advance

Regards,
Kuldeep
Replies:
RE: Syncronising triggred data acquisition for Modbus "I/O Intr" records and sscan records Mark Rivers via Tech-talk
Navigate by Date:
Prev: Attocube AMC300 driver? Leicester, Pete (DLSLtd, RAL, LSCI) via Tech-talk
Next: RE: Syncronising triggred data acquisition for Modbus "I/O Intr" records and sscan records Mark Rivers via Tech-talk
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: Attocube AMC300 driver? Kevin Peterson via Tech-talk
Next: RE: Syncronising triggred data acquisition for Modbus "I/O Intr" records and sscan records Mark Rivers via Tech-talk
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, 20 Jul 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·