Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

Camac and Labview

"I have a Lecroy 2249SG adc with a DSP6001 control board.  I upgraded from LabView 5.0 to LabView 6.0 and now my Sub vi's for communicating with the CAMAC do not work.  The drivers were from DSP and were for Windows NT and a previous lab member modified them to work with Windows 98.  The drivers are .dll files.  When I send a LAM to the CAMAC, I get a Q=0 and/or a X=0  back from the CAMAC - Q=0 means no response, and X=0 means command not accepted.  My previous lab member explained the modifications like this: "I remember that I somehow looked at the code and besides a lot of unintelligable symbols I saw things that looked like the expected CAMAC commands except that they had a lot of really strange extra symbols attached to them. I then we
nt into LabVIEW and replaced the expected command names by these slightly messed-up versions and - surprisingly - it worked." At this point I think it is a Labview problem because the hardware works fine using a test program from the company.

I'm attaching the driver(WINCAM32.dll) and the vi that is used to generate the calls.

Thanks.

Shaun"
Download All
0 Kudos
Message 1 of 3
(3,942 Views)
Hi,

I don't know of any changes in the Library function call node between any version of LabVIEW.

Are you able to use the dll from other enviroments, sush as Visual Studio?. Does the test program from the company use the same dll (WINCAM32.dll).

DiegoF
National Instruments.
0 Kudos
Message 2 of 3
(3,942 Views)
Diego,

I am not sure about other environments such as visual studio, but the test program uses the same driver and seems to communicate fine. I am pretty baffled at this point!

Shaun
0 Kudos
Message 3 of 3
(3,942 Views)