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: | sequencer problem |
From: | Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Wed, 10 May 2023 22:06:58 +0000 |
Folks, I am seeing behavior I don’t understand with the sequencer. I am using base 7.0.6.1 and sequencer 2.2.9 (latest). I have a VxWorks IOC running a number of motors. All of the motor records are loaded, but currently one of the motor controllers is not available, so that motor record
is not functional. I am running an SNL program on a Linux IOC, and it connects to the motors on the VxWorks system, including the currently non-functional motor. The SNL program puts monitors
several of the motor record fields. I see the following messages after iocInit when the SNL program starts: seq BM13_Energy, "E=13BMA:E, MONO=13BMA:m17, EXPTAB_Z=13BMD:m22, YXTAL=13BMA:MON:, ZXTAL=13BMA:m14" sevr=info Sequencer release 2.2.9, compiled Wed May 10 16:25:47 2023 sevr=info Spawning sequencer program "BM13_Energy", thread 0x2c304a0: "BM13_Energy" sevr=minor BM13_Energy[0](after 0 sec): assigned=26, connected=26, monitored=24, got monitor=21 sevr=minor BM13_Energy[0](after 0 sec): assigned=26, connected=26, monitored=24, got monitor=21 sevr=minor BM13_Energy[0](after 0 sec): assigned=26, connected=26, monitored=24, got monitor=21 sevr=minor BM13_Energy[0](after 0 sec): assigned=26, connected=26, monitored=24, got monitor=21 sevr=minor BM13_Energy[0](after 0 sec): assigned=26, connected=26, monitored=24, got monitor=21 The SNL program has monitors on 3 record fields for the non-functional motor. I think that is why there are 24 channels monitored, but only 21 monitors have been received? The above seems like it might be normal. However, after about 30 seconds I get this error on the Linux IOC: CA.Client.Exception............................................... Warning: "Virtual circuit unresponsive" Context: "ioc13bma.cars.aps.anl.gov:5064" Source File: ../tcpiiu.cpp line 926 Current Time: Wed May 10 2023 16:53:37.844955871 At the same time I get this error on the VxWorks IOC: DB CA Link Exception: "Virtual circuit disconnect", context "corvette:38399" After the exceptions I then get the following messages on the Linux IOC. Note that it spontaneously dropped 24 of the 26 connections, and “got monitor” changed to -1. .................................................................. sevr=minor BM13_Energy[0](after 0 sec): assigned=26, connected=2, monitored=24, got monitor=-1 sevr=minor BM13_Energy[0](after 0 sec): assigned=26, connected=2, monitored=24, got monitor=-1 sevr=minor BM13_Energy[0](after 0 sec): assigned=26, connected=2, monitored=24, got monitor=-1 Is this behavior expected? Thanks, Mark |