And many thanks to you Mark for diving in the deep end, getting the snags sorted and reporting the results back to the rest of us! It certainly does increase my confidence when considering moving our beamlines on to EPICS7.
Cheers,
Ulrik
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Mark Rivers
Sent: 04 October 2018 13:39
To: [email protected]
Subject: Using EPICS 7 on our production beamlines
Folks,
I decided that the only way to really find problems with EPICS 7 was to put it in production on our 4 beamlines at the APS. This includes 7 VME/vxWorks IOCs and roughly 70 IOCs running on Linux and Windows, including ~30 areaDetectors.
I'm happy to say that it is working. There were a few issues that we have encountered so far and that have now been fixed.
1) There was a bug in the soft motor device support that was exposed when switching to EPICS 7. This is fixed on the master branch of motor.
2) There was a bug in the mbbi and mbbo records in EPICS 7 that prevented the *VL fields from being modified at run-time. This is fixed in the 7.0 branch of epics-base.
3) There was a problem with autosave that was exposed with a change in dbAccess.c::dbGet() in EPICS 7. dbGet() was changed so that it now returns the current length of long string fields, rather than the maximum length. This caused problems for autosave with PVs that are long strings and whose value is empty ("") . Rather than an empty string being written to the autosave file, the string "0" was written. This caused serious problems with the calculation fields in the transform record, for example, where there is an important difference between an empty string and the string "0". This is fixed in the master branch of autosave.
This is a pretty short list, and I want to thank the EPICS 7 developers for all the effort they have put into this project!
Mark
--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
- References:
- Using EPICS 7 on our production beamlines Mark Rivers
- Navigate by Date:
- Prev:
Using EPICS 7 on our production beamlines Mark Rivers
- Next:
measComp R2-2 released Mark Rivers
- 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:
Using EPICS 7 on our production beamlines Mark Rivers
- Next:
measComp R2-2 released Mark Rivers
- 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
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·