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: | Base R7.0.2.2 VME_IO Parsing |
From: | Graham Cox - UKRI STFC via Tech-talk <[email protected]> |
To: | "[email protected]" <[email protected]> |
Date: | Mon, 23 Sep 2019 09:48:29 +0000 |
Hello All, I have discovered during the upgrade process from Base v3.14.x to v7 (specifically 7.0.2.2) that certain support modules do not work correctly. I am experiencing issues with the parsing of VME_IO INP/OUT specifications (“#Cn Sn @parameter” format) during dbLoadRecords. For example, the mrfioc2 support module defines a record as: record(bo, "CLA-C16-TIM-EVG-01:ResetMxc-Cmd") { field( DTYP, "EVG") field( DESC, "EVG Reset MXC") field( OUT, "#C S @EVG-01") field( PINI, "YES") field( VAL, "1") field( UDF, "0") } The OUT field of this record is acceptable to 3.14.12.5 but 7.0.2.2 kicks this out on dbLoadRecords due to the missing card and signal numbers. A v7 ‘fix’ to this is to replace all “#C S” instances with “#C0 S0”. Another support module defines a record as: record(ao,"CLA-C16-IOC-CS-01:CENTRAL-SMONCONF40") { field(DESC, "sys_mon config") field(DTYP, "ifc1210") field(OUT , "#C S0x40 @SMON") field(VAL , "0") field(PINI, "YES") field(PRIO, "LOW") field(FLNK, "CLA-C16-IOC-CS-01:CENTRAL-CORETEMP") } Again, this is acceptable to 3.14.12.5 but 7.0.2.2 kicks this out on dbLoadRecords due to the use of a hexadecimal format signal identifier. A v7 ‘fix’ is to replace all hex specifiers with decimal. Is this behaviour an intentional change from Base 3.14->7 ? Or am I missing something here? Thanks, Graham |