Difference between revisions of "LVDCOM"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
* [http://epics.isis.stfc.ac.uk/downloads/lvDCOM/1.0/lvDCOM-1_0-win32-x86-static.zip Source plus win32-x86 statically linked IOC binary (EPICS BASE 3.14.12.2, AUTOSAVE 5-0, ASYN 4-18)] | * [http://epics.isis.stfc.ac.uk/downloads/lvDCOM/1.0/lvDCOM-1_0-win32-x86-static.zip Source plus win32-x86 statically linked IOC binary (EPICS BASE 3.14.12.2, AUTOSAVE 5-0, ASYN 4-18)] | ||
** Binary download provides '''bin/win32-x86/example.exe''' which can be used with '''iocboot/iocexample/st.cmd''' as the basis for further IOCs | ** Binary download provides '''bin/win32-x86/example.exe''' which can be used with '''iocboot/iocexample/st.cmd''' as the basis for further IOCs | ||
| − | * [http://epics.isis.stfc.ac.uk/doxygen/lvDCOM/ | + | * [http://epics.isis.stfc.ac.uk/doxygen/lvDCOM/ Documentation] |
Revision as of 20:31, 12 July 2015
An EPICS support module to access items on the front panel of the National Instruments LabVIEW software package and expose them as EPICS process variables. It uses Microsoft Windows DCOM technology and thus both the EPICS IOC and LabVIEW software must be running on Microsoft Windows. For an alternative option that additionally works on Linux, you could create network shared variables within LabVIEW and then use the NETSHRVAR package.
lvDCOM 1.0 Download
- Source only
- Source plus win32-x86 statically linked IOC binary (EPICS BASE 3.14.12.2, AUTOSAVE 5-0, ASYN 4-18)
- Binary download provides bin/win32-x86/example.exe which can be used with iocboot/iocexample/st.cmd as the basis for further IOCs
- Documentation