Spiricon LBAPC laser beam analyzer use GPIB or ActiveX?

[laserhead]

We wrote several LabVIEW programs to process camera frames acquired thru the GPIB interface on a Spiricon LBA-100.  The LBA-100 quit communicating so we traded it in for a PCI card version, called LBAPC.  Ophir-Spiricon suggests using ActiveX to communicate between LBAPC software and LabVIEW.  Their OnNewBitmap.vi works, but LabVIEW8 tells me CreateActiveX_Event.vi and some other ActiveX vi are no longer supported.  The LBAPC manual chapter 10 is about Remote GPIB Operation, but no trace of the LBAPC shows up in MAX. 

Is ActiveX outmoded, not the way to go? 
How can I use GPIB to get camera data loaded into our old LabVIEW programs?

[Albert.Geven]

Hi
ActiveX is not outmoded, if you have a good documentation.
It is better or comparable with direct dll calls.
The question is, do you still have a gpib interface connected to the IO card?

[laserhead]

The other pci slot still contains NI-GPIB-PCI card which is connected to other instruments in our expt.  This gpib card used to connect to the LBA-100 GPIB connector, but the new LBAPC is just a pci frame grabber card with software.  To run Spiricon's OnNewBitmap.vi, the LBAPC software must be running, then LabVIEW can get the newest camera frame and any other data. 

The question is do I replace gpib calls in our old LabVIEW programs with ActiveX calls?  If not, How do I address LBAPC as a gpib device if it is not connected to our gpib controller card?

[Albert.Geven]

Hi

You have to replace the gpib calls by corresponding calls to the LBAPC card.
In fact if you are using IMAQ vision you probably can select the framegrabber, but I'm not an expert in vision.
If there is no GPIB connector on the framegrabber you probably can not use GPIB anymore.

Your best option is to ask Spiricon how to proceed.