EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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  <20212022  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  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: Syncronising triggred data acquisition for Modbus "I/O Intr" records and sscan records
From: Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>
To: 'Kuldeep Joshi' <kuldeep.joshi at gmail.com>
Cc: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Fri, 16 Jul 2021 17:48:25 +0000

Hi Kuldeep,

 

What you are doing should work without the long detector delay time, but it depends on using the correct type of database links.

 

Can you send your database, perhaps simplified to just illustrate the problem?  Also send the output of camonitor for all of the interesting PVs in the chain.

 

Mark

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Kuldeep Joshi via Tech-talk
Sent: Friday, July 16, 2021 11:37 AM
To: tech-talk at aps.anl.gov
Subject: Syncronising triggred data acquisition for Modbus "I/O Intr" records and sscan records

 

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


References:
Syncronising triggred data acquisition for Modbus "I/O Intr" records and sscan records Kuldeep Joshi via Tech-talk

Navigate by Date:
Prev: Syncronising triggred data acquisition for Modbus "I/O Intr" records and sscan records Kuldeep Joshi via Tech-talk
Next: linking in IOC makefile for RTEMS Siddons, David 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  <20212022  2023  2024 
Navigate by Thread:
Prev: Syncronising triggred data acquisition for Modbus "I/O Intr" records and sscan records Kuldeep Joshi via Tech-talk
Next: linking in IOC makefile for RTEMS Siddons, David 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  <20212022  2023  2024 
ANJ, 16 Jul 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·