Re: StreamDevice not parsing STREAM_PROTOCOL_PATH

[Mark Rivers via Tech-talk <tech-talk@aps.anl.gov>]

> BTW: Is there some place where implemented protocols for StreamDevice are
> being collected? I guess there must be solutions for many different
> devices already existing out there...

One place is the synApps "ip" module.  This name is historical, but it is basically a repository for various devices that communicate with strings and are not the types of devices in dedicated repositories like "motor", "vac", etc.

These are the protocols currently in "ip":

corvette:ip/ipApp/Db>ls -l *pro*
-rw-rw-r-- 1 epics domain users 1495 Dec 10  2017 ADAM_4018.proto
-rw-rw-r-- 1 epics domain users  263 Nov 21  2015 Alcatel_ACS1000.protocol
-rw-rw-r-- 1 epics domain users  178 Nov 21  2015 Alcatel_ACS2000.protocol
-rw-rw-r-- 1 epics domain users 1468 Nov 21  2015 BK9130.proto
-rw-rw-r-- 1 epics domain users 1499 Oct  5  2018 BK9173B.proto
-rw-rw-r-- 1 epics domain users  886 Nov 21  2015 CPSyringe.proto
-rw-rw-r-- 1 epics domain users  716 Nov 21  2015 Encoder_AD4.proto
-rw-rw-r-- 1 epics domain users  669 Jan  4 09:18 HG-100.proto
-rw-rw-r-- 1 epics domain users  474 Nov 21  2015 JenaNV40.proto
-rw-rw-r-- 1 epics domain users 3039 Nov 21  2015 LakeShore335.proto
-rw-rw-r-- 1 epics domain users 3482 Nov 21  2015 LakeShore336.proto
-rw-rw-r-- 1 epics domain users 1236 Aug 31  2017 MKS651C.proto
-rw-rw-r-- 1 epics domain users  912 Nov 21  2015 NCD_R2X.proto
-rw-rw-r-- 1 epics domain users  448 Nov 21  2015 NeslabEX.proto
-rw-rw-r-- 1 epics domain users 3264 Nov 21  2015 Omega_DP41.proto
-rw-rw-r-- 1 epics domain users 1092 Nov 21  2015 PACE5000.proto
-rw-r--r-- 1 epics domain users  860 Jan 21  2017 PHD2000.proto
-rw-rw-r-- 1 epics domain users 1390 Nov 21  2015 SR630.proto
-rw-rw-r-- 1 epics domain users  843 Nov 21  2015 SR830.proto
-rw-rw-r-- 1 epics domain users  951 Nov 21  2015 Tabor8024.proto
-rw-rw-r-- 1 epics domain users  763 Nov 21  2015 USdigital_T7.proto
-rw-rw-r-- 1 epics domain users  153 Nov 21  2015 USdigital_X3.proto
-rw-rw-r-- 1 epics domain users  591 Nov 21  2015 iSeries.proto

It would be great if others would contribute here.

Mark


________________________________
From: Tech-talk <tech-talk-bounces@aps.anl.gov> on behalf of Gerrit Kühn via Tech-talk <tech-talk@aps.anl.gov>
Sent: Tuesday, January 21, 2020 7:32 AM
To: Ralph Lange via Tech-talk; Ralph Lange
Subject: Re: StreamDevice not parsing STREAM_PROTOCOL_PATH

Am Tue, 21 Jan 2020 09:45:10 +0100
schrieb Ralph Lange via Tech-talk <tech-talk@aps.anl.gov>:

> > No error messages to be seen during the build,
> > though. What do I have to check to find out where this is not being
> > picked up properly?

> You will have to set CALC to an absolute path pointing to your
> installation of the calc module in your application's configure/RELEASE
> file (don't use the environment), and as well add the dbd snippet that
> calc generates ( calcSupport.dbd, including the definition for the
> scalcout record type) as the name of the library that calc generates
> (calc, containing the code for the scalcout record type) to the
> appropriate definitions in your application's Makefile (where the IOC
> binary is created).

Thanks for the detailed explanation! Turns out I was simply missing the
inclusion of the calc.dbd file. Having added that, everything is happily
compiling now. The created dbd file looks ok, and libcalc is linked
against the binary as it should.

BTW: Is there some place where implemented protocols for StreamDevice are
being collected? I guess there must be solutions for many different
devices already existing out there...