Experimental Physics and
Industrial Control System

I am upgrading a VME IOC software from EPICS R3.13.2, vxWorks probably 5.3 to EPICS R3.13.11 vxWorks 6.6.

The hardware is being upgraded from mvme177P, VME64 crate to mvme6100 and VME64x.

The AB scanner module is giving me much trouble.

-1- First I tried to build the “old” version of the AB Support module, which proved rather stubborn.

I have downloaded AB VME-AB1771, 6008-SV2R R2.2 support module, which built fine.

My IOC with the AB R2.2 software loads with an error during iocInit phase:

          abDrv: SET_UP failed link 0

          record TR00:STN:DCM:MODU init error No Card

Observing the AB VME board during boot, the activity on the LED lights on the front panel indicates that the IOC software is poking the board.  I get this error each time I reload the IOC software.

-2- Next I set ab_debug=5 in drvAb.c file.  Rebuild the module and IOC.  This resulted in the following messages:

       Link 0 already initialized

       sc_lock

       sc_lock

       drvAb link 0 sysBusTas failed

       drvAb link 0 sysBusTas failed

       drvAb: link 0 sc_lock failure fl_lock 0

       link_status: sc_lock failed -1

       sc_lock

       drvAb link 0 sysBusTas failed

       drvAb link 0 sysBusTas failed

       drvAb: link 0 sc_lock failure fl_lock 0

       link_status: sc_lock failed -1

the last five lines are printed endlessly.

-3- Finally, I set ab_debug=0, rebuilt and reloaded IOC software and now the SET_UP failed link… error no longer is printed.

This is very curious.

At this point the IOC is not working correctly in spite the fact that there are no errors printed.

No data is transferred from the hardware.  This is of course true for test -1- as well.

Has anyone successfully used AB R2.2 with mvme6100, EPICS R3.13.11, and vxWorks 6.6?

Thanks for any ideas, suggestions, etc.

Zen