1 / 12

PC Application Development Environment

PC Application Development Environment. PC Based EPICS Application Development Generic PC vxWorks targets. PC Based Application Development. Databases record / device / driver support code development Visual Basic and others can be used to call CA Client API CA server tool development

shafferm
Download Presentation

PC Application Development Environment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PC Application Development Environment • PC Based EPICS Application Development • Generic PC vxWorks targets

  2. PC Based Application Development • Databases • record / device / driver support code development • Visual Basic and others can be used to call CA Client API • CA server tool development • CA DDE server

  3. For IOC Application Development You Will Need • EPICS base version 3.13 binaries • GNU make • PERL • vxWorks

  4. 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?

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

  6. 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

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

  8. vxWorks 5.3.1 Bare Minimum Component Set Required by EPICS IOC core

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

  10. Generic PC vxWorks targets (vxWorks pc486 BSP) • We 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 package

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

  12. Conclusion • EPICS 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 problems

More Related