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  2021  2022  2023  2024  2025  <2026>  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  <2026> 
<== Date ==> <== Thread ==>

Subject: Re: Oxford Cryostream 1000 IOC questions
From: Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>
To: "James P. Withrow" <jwithrow at cornell.edu>, tech-talk <tech-talk at aps.anl.gov>
Date: Fri, 14 Aug 2026 21:05:27 +0000
Hi James,

That looks to me like the Oxford rejected the connection attempt for the second socket.

Here are a couple of ways to diagnose:


asynReport 1

That will show the status of all asyn port drivers, including whether they are connected.


telnet 164.54.212.121 10304
Does it let you connect, or does it reject the connection attempt?  If it rejects then it would seem the Oxford is only allowing one socket client at a time on that port.  That is not consistent with the original database and startup script design.  Perhaps there is a configuration setting on the Oxford to allow more than one socket connection?

Mark




From: James P. Withrow <jwithrow at cornell.edu>
Sent: Thursday, August 13, 2026 6:34 PM
To: Mark Rivers <rivers at cars.uchicago.edu>; tech-talk <tech-talk at aps.anl.gov>
Subject: Re: Oxford Cryostream 1000 IOC questions

Hello Mark -

Below is the relevant excerpt from the IOC when both the status and command sockets are set to the same IP and port as in the repository.

# CS1000 uses TCP for Status Packets or Commands # Status Packets drvAsynIPPortConfigure("L0", "164.54.212.121:10304 TCP", 0, 0, 0) # Commands drvAsynIPPortConfigure("OC_CMD", "164.54.212.121:10304 TCP", 0, 0, 0) # Status Packet and Commands on a Single Port dbLoadRecords("db/MDO.db", "P=OXCRYO:,Q=CS1000,PORT=L0,R=MDO:,L=0,A=0,PORTCMD=OC_CMD") #var mySubDebug 1 #var streamError 1 #var streamDebug 1 #If are interested in saving logs, it can produce a few GBs of logs, use with caution #streamSetLogfile("logfile.txt") cd "/opt/epics/iocs/cryostream-1000-EPICS-IOC/OXCS1000/iocBoot/ioccryo1" iocInit Starting iocInit ############################################################################ ## EPICS R7.0.9 ## Rev. 2026-01-14T12:49-0600 ## Rev. Date build date/time: ############################################################################ 2026/08/13 18:20:47.498515 _main_ OXCRYO:CS1000:TURBOCMD lockRequest: port OC_CMD not connected
-Jim

Jim Withrow, Research Support Specialist - jwithrow at cornell.edu
NE-CAT, Cornell University - https://necat.chem.cornell.edu
Advanced Photon Source, Sector 24
9700 S. Cass Avenue, Building 436 E001
Lemont, IL 60439

From: Mark Rivers <rivers at cars.uchicago.edu>
Sent: Thursday, August 13, 2026 5:07 PM
To: tech-talk <tech-talk at aps.anl.gov>; James P. Withrow <jwithrow at cornell.edu>
Subject: Re: Oxford Cryostream 1000 IOC questions
 
Hi Jim,

I think the database was probably intentionally designed to open 2 separate sockets to the device, so that the long status reply and short commands were independent.

Can you send the error message you got when using 2 separate asyn ports?

Mark


From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of James P. Withrow via Tech-talk <tech-talk at aps.anl.gov>
Sent: Thursday, August 13, 2026 4:02 PM
To: tech-talk <tech-talk at aps.anl.gov>
Subject: Oxford Cryostream 1000 IOC questions
 
Good afternoon, all - 

I have an Oxford Cryostream 1000 and I am attempting to use the IOC located at 


I have it working well; I am able to both control and monitor the cryostream. However, my IOC console fills up with the following messages at 1-second intervals:

2026/08/13 15:55:18.027546 L0 OXCRYO:CS1000:STATUS: device L0 0 disconnected
2026/08/13 15:55:19.179502 L0 OXCRYO:CS1000:STATUS: device L0 0 disconnected
2026/08/13 15:55:20.331536 L0 OXCRYO:CS1000:STATUS: device L0 0 disconnected
2026/08/13 15:55:21.483524 L0 OXCRYO:CS1000:STATUS: device L0 0 disconnected
2026/08/13 15:55:22.635480 L0 OXCRYO:CS1000:STATUS: device L0 0 disconnected

Have I configured something incorrectly? Is this something to be concerned with? I did change the following line in st.cmd:

dbLoadRecords("db/MDO.db", "P=OXCRYO:,Q=CS1000,PORT=L0,R=MDO:,L=0,A=0,PORTCMD=L0")

I changed PORTCMD from "OC_CMD" to "LO" as both the drvAsynIPPortConfigure lines referenced the same IP and port, and the IOC complained about not being able to get a lock for the second port.

Thank you, 
-Jim Withrow


Jim Withrow, Research Support Specialist - jwithrow at cornell.edu
NE-CAT, Cornell University - https://necat.chem.cornell.edu
Advanced Photon Source, Sector 24
9700 S. Cass Avenue, Building 436 E001
Lemont, IL 60439

Replies:
Re: Oxford Cryostream 1000 IOC questions James P. Withrow via Tech-talk
References:
Oxford Cryostream 1000 IOC questions James P. Withrow via Tech-talk
Re: Oxford Cryostream 1000 IOC questions Mark Rivers via Tech-talk
Re: Oxford Cryostream 1000 IOC questions James P. Withrow via Tech-talk

Navigate by Date:
Prev: Re: Modbus and SScan acquisition synchronisation and timestamp query Mark Rivers via Tech-talk
Next: Re: [EXTERNAL] Modbus and SScan acquisition synchronisation and timestamp query Ralph Lange 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  2025  <2026> 
Navigate by Thread:
Prev: Re: Oxford Cryostream 1000 IOC questions James P. Withrow via Tech-talk
Next: Re: Oxford Cryostream 1000 IOC questions James P. Withrow 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  2025  <2026> 
ANJ, 17 Aug 2026 · Home · News · About · Talk · Base · Modules · Extensions ·
· Distributions · Download · Documents · Links · Licensing ·