Interesting....
can the XML file (Labview variable to asyn variable) be generated automatically (or semi automatically)?
> From:
[email protected]> To:
[email protected]> Subject: lvDCOM (LabVIEW -> EPICS PVs on Windows)
> Date: Thu, 3 Oct 2013 18:46:31 +0000
>
> lvDCOM is an EPICS support module that can export front panel variables from National Instruments LabVIEW software applications as EPICS process variables on computers running the Microsoft Windows operating system. The program allows you to rapidly "EPICS enable" existing LabVIEW applications as it is not necessary to modify Virtual Instrument (VI) internals, so it could be used to conveniently wrap e.g. manufacturer supplied applications. As the program uses DCOM for communication, this (ActiveX) needs to be selected in the "VI Server" options of LabVIEW, but this is the only required change to a VI.
>
> Features of lvDCOM include:
> * Able to communicate with either native LabVIEW VIs or compiled LabVIEW applications (.EXE)
> * Can (optionally) automatically start and/or stop VIs on IOC startup/shutdown
> * Can communicate with remote Windows PCs using standard DCOM authentication or a supplied username + password
> * Can handle some additional front panel logic e.g. automatically push a front panel button either before doing a read from, of after doing a write to, another front panel variable
>
> For more information on lvDCOM see http://epics.isis.stfc.ac.uk/
>
> Regards,
>
> Freddie Akeroyd
> --
> Scanned by iCritical.
>