First, thanks to Matt Newville and Mark Rivers for your help in getting my XSPRESS3 IOC running. (I'll post later it it actually fixes our original problem.)
I have two questions related to the IOC:
On IOC start-up I get 48 messages (6 channels x 8 SCAs) of this type:
devAsynFloat64Array::initCommon, XSPRESS3:C1SCA1:TSArrayValue connectDevice failed asynManager:connectDevice port XSP3.C1SCA_TS not found
devAsynFloat64Array::initCommon, XSPRESS3:C1SCA2:TSArrayValue connectDevice failed asynManager:connectDevice port XSP3.C1SCA_TS not found
devAsynFloat64Array::initCommon, XSPRESS3:C1SCA3:TSArrayValue connectDevice failed asynManager:connectDevice port XSP3.C1SCA_TS not found
.
.
.
I don't see those messages, but they look familiar: This seems like it might be related to changes that were made for TimeSeries around AD3.5 or AD3.6.
I'm using the "iocGSECARS-4Channel" boot directory, which needs the more recent versions of AD. It may be that the other iocBoot directories are still using TimeSeries syntax that
are based on AD2 (I think it might be "up to AD3.5"), which are subtly different than for AD 3.6 and higher. Does that seem it might be the culprit? If so, we should update all the iocBoot directories to be consistent with the latest version of AD3.
Plus this message:
2020/01/28 12:57:33.650 asynNDArrayDriver:readNDAttributesFile: unknown attribute type = INT for attribute CHAN1DTCFLAGS
Oh, yes I do see that. The XSP3.xml NDAttributesFile has
<Attribute addr="0" datatype="DOUBLE" description="Chan 1 DTC Flags" name="CHAN1DTCFLAGS" source="XSP3_CHAN_DTC_FLAGS" type="INT"/>
which should probably be
<Attribute addr="0" datatype="DOUBLE" description="Chan 1 DTC Flags" name="CHAN1DTCFLAGS" source="XSP3_CHAN_DTC_FLAGS" type="PARAM"/>
We should fix that in master.