Experimental Physics and
Industrial Control System

One of the changes in the new release was to replace .dll in all call library nodes with .*  as this will use .so on Linux and .dll on WIN32 systems.

lvInitialized is looking for lvPortDriver.dll if you’re using the old version.  I expect you’ll have this same problem with all of the other call library nodes in the LabVIEW code.

If you don’t want to move to 2016 or newer LabVIEW, then you’ll need to modify the code.  (If you have access to LabVIEW 2016, you might be able to save the library for 2015 instead), there shouldn’t be anything that requires the newer LabVIEW (although I’m already encountering cRIO modules that require LabVIEW 2017).

One other difference you’ll find is that the original release did not allow one to write to arrays without wiring the status control (newer version assumes NO_ALARM status if the control is not wired).

Either way I’d recommend using the latest version of the c++ code, it fixes some bugs with arrays, and with using more than one port.

 

As far as the build process, I usually put the LabVIEW headers in a different include directory (as if they’re a separate shared App), but as long as it’s working.

The lvInitialized function is there to make sure that the LabVIEW program started and initialized the ports before the IOC is started.  This would only be an issue for systems where the IOC is started independently of the LabVIEW program (if done properly this would work on all systems except LinuxRT).

Even without that call you’ll be able to run the IOC, you just won’t be able to use lvPortDriver (driver initialization will return an error).

 

Also, note that one you have this up a running, it will be normal to lose connection the first time you deploy code from the debugger if the IOC had previously been run.  I have not found a way to properly run down all of the asyn tasks when the IOC exits, and if I properly delete all items, then  the tasks continue to try to access them.

--

Correspondence

-------

Scott Baily

AOT-IC, MS H820

Los Alamos National Laboratory

Los Alamos, NM 87545

ph: (505) 606-2260

 

 

From: Baily, Scott A

Date: 2018-03-24 00:39

To: [email protected]; tech-talk

Subject: RE: How to start EPICS IOC via LabVIEW on cRIO

lvPortDriver.dbd should be located in lvPortDriverApp/src,

and when that directory builds, it should be installed into the dbd folder

for your system that would be: /usr/local/EPICS/synapp/support/lvPortDriver-master/dbd/

perhaps somethings going wrong the build or install from lvPortDriverApp/src  (like no permission to create the directory, or a case mismatch in the filename)

 

From: [email protected] <[email protected]>
Sent: Friday, March 23, 2018 7:49 AM
To: tech-talk <[email protected]>; Baily, Scott A <[email protected]>
Subject: RE: How to start EPICS IOC via LabVIEW on cRIO

 

Dear Dr. Baily,

 

Thank you very much for giving me these instructions about "lvPortDriver"! But I'm still unable to build it successfully. 

 

I built the EPICS base 3.14.12.7, asyn4-30, and put the LabVIEW header(my version is LabVIEW-2015 32-bit for windows) 

and the newer released version of lvPortDriver to my cRIO-9030.

Then I set the ./configure/RELEASE file like (annotations in the file are omitted ):

 

EPICS_RELEASE = R3.14.12.7

SUPPORT=/usr/local/EPICS/synapp/support

ASYN=/usr/local/EPICS/synapp/support/asyn4-30

LINUX_GPIB=NO

LABVIEW=/usr/local/EPICS/synapp/support/labview

EPICS_BASE= /usr/local/EPICS/base-3.14.12.7

 

Next I typed "make" in this configure directory, "cd ../",and "make" in the lvPortDriver directory.

But errors occur:

 

make[3]: Entering directory '/usr/local/EPICS/synapp/support/lvPortDriver-master/lvtestApp/src/O.linux-x86_64'
perl /usr/local/EPICS/base-3.14.12.7/bin/linux-x86_64/makeIncludeDbd.pl base.dbd lvPortDriver.dbd asyn.dbd lvtestInclude.dbd
echo "../O.Common/lvtestInclude.dbd : ../Makefile" >> lvtest.dbd.d
Expanding dbd
Can't open include file "lvPortDriver.dbd"
Error at or before ""lvPortDriver.dbd"" in file "../O.Common/lvtestInclude.dbd" line 2
dbExpand: Input errors, no output generated
/usr/local/EPICS/base-3.14.12.7/configure/RULES.Db:265: recipe for target '../O.Common/lvtest.dbd' failed
make[3]: *** [../O.Common/lvtest.dbd] Error 1
make[3]: Leaving directory '/usr/local/EPICS/synapp/support/lvPortDriver-master/lvtestApp/src/O.linux-x86_64'
/usr/local/EPICS/base-3.14.12.7/configure/RULES_ARCHS:61: recipe for target 'install.linux-x86_64' failed
make[2]: *** [install.linux-x86_64] Error 2

 

I tried to uninstall and rebuild it several times, but the result didn't changed.

What should I do to correct the error? Look forward to your guidance. 

 

Best Regards,

Zefeng Zhao