Modify the application startup script

The iocBoot/iocAB300/st.cmd application startup script created by the makeBaseApp.pl script needs a few changes to get the application working properly.

1. Ensure that the application database records are loaded. Remove the # and give a reasonable value to the 'user' macro:

   dbLoadRecords("../../db/AB300.db","user=AB300")
   

2. Add a line to control the debugging level of the serial line 'GPIB' driver. A level of 2 prints out every byte sent to or received from the serial line and is very useful during initial debugging.

   var drvTermiosTtyGpibDebug 2
   

3. Set up the 'link' between the IOC and the filter wheel.
   • If you're using an Ethernet/RS-232 converter or a device which communicates over a telnet-style socket connection you need to specify the Internet host and port number like:

     drvTermiosTtyGpibConfigure(0,"164.54.9.90:4002")
     

   • If you're using a serial line directly attached to the IOC you need something like:

     stty("--file=/dev/ttyS0","cs8","-parenb","-crtscts","clocal")
     drvTermiosTtyGpibConfigure(0,"/dev/ttyS0")
     

   • If you're using a serial line directly attached to a vxWorks IOC you must first configure the serial port. The following example shows the commands to configure a port on a GreenSprings UART Industry-Pack module. Note that these are vxWorks shell commands and not IOC shell commands.

     ipacAddCarrier(&vipc616_01,"0x6000,B0000000")
     tyGSOctalDrv 1
     octalUart0 = tyGSOctalModuleInit("GSIP_OCTAL232", 0x80, 0, 0)
     port0 = tyGSOctalDevCreate("/tyGS/0/0",octalUart0,0,1000,1000)
     tyGSOctalConfig(port0,9600,'N',1,8,'N')
     

     Once the serial port has been configured you can invoke the drvTermiosTtyGpibConfigure command from either shell as:

     drvTermiosTtyGpibConfigure(0,"/tyGS/0/0")
     

   In all of the above examples the first argument of the drvTermiosTtyGpibConfigure command is the link number and must match the L value in the EPICS database record INP and OUT fields.