PC Application Development Environment PC Based EPICS Application DevelopmentPC Based EPICS Application Development Generic PC vxWorks targetsGeneric PC vxWorks targets

PC Based Application Development DatabasesDatabases record / device / driver support code developmentrecord / device / driver support code development Visual Basic and others can be used to call CA Client APIVisual Basic and others can be used to call CA Client API CA server tool developmentCA server tool development CA DDE serverCA DDE server

For IOC Application Development You Will Need EPICS base version 3.13 binariesEPICS base version 3.13 binaries GNU makeGNU make PERLPERL vxWorksvxWorks

Install FTP Server NT4.0 WS includes FTP server in Microsoft Peer Web Services package Install with start | control panel | network | services | add (as administrator) rumor: after installing Microsoft Peer Web Server you must reinstall NT service pack 3?

Configure FTP Server allow non anonymous login add a NT user with password use this user and password in your target boot configuration

FTP Server - Tornado Configuration Subtleties set the FTP home to the directory where the vxWorks file resides and supply no path with the vxWorks file name when configuring the target boot OR use the “tgtsvr -c” to set the location of the vxWorks image for the Tornado target server

Other Tornado Subtleties When calling “dbLoadRecords()” from the host based shell you may be required to use xxxx” instead of “cd xxxx” I have had some trouble with the host/target symbol table synchronization (needs further investigation)

vxWorks Bare Minimum Component Set Required by EPICS IOC core

Create Application Development Tree Mostly identical in operation to UNIX application development treeMostly identical in operation to UNIX application development tree To create an example application tree from a dos shell typeTo create an example application tree from a dos shell type perl f:\epics\bin\win32\makeBaseApp.pl -e -b f:\\epicsperl f:\epics\bin\win32\makeBaseApp.pl -e -b f:\\epics

Generic PC vxWorks targets (vxWorks pc486 BSP) We boot to DOS/W95 first followed by vxWorksWe boot to DOS/W95 first followed by vxWorks –most PC IO card vendors supply DOS or W95 based configuration utilities We transfer the vxWorks boot image over NCSA DOS FTP packageWe transfer the vxWorks boot image over NCSA DOS FTP package

Generic PC BSP Configuration Boot change is volatile in this BSPBoot change is volatile in this BSP –All boot parameters are compiled into the boot image Select Ethernet card type, IO address, and interrupt levelSelect Ethernet card type, IO address, and interrupt level

Conclusion EPICS IOC application development environment is nearly identical under UNIX and WindowsEPICS IOC application development environment is nearly identical under UNIX and Windows Generic PCs have been operational at LANL for several months now with no major problemsGeneric PCs have been operational at LANL for several months now with no major problems