LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

NI-DAQ 7.3 and v6.9.1 compatability

Hi. I have a complicated situation involving LabWindows/CVI and NI-DAQ software which is used to run a MediPix2 chip designed by CERN. The equipment includes a MediPix chip and an interface board, both of which worked ok at CERN. The following software/hardware was used there: LabWindows/CVI version 6.0: NI-DAQ (v6.9.1).
We are now using LabWindows/CVI version7.1 and NI-DAQ 7 (v7.3) and find that the we can no longer obtain sensible data from the MediPix chip. Can anyone tell me if there are compatability issues between either versions of NI-DAQ boards/drivers or the two versions of LabWindows? I appreciate more information may be required so please contact me. I would be very grateful for any assistance. <ajb175@student.canterbury.ac.nz>
0 Kudos
Message 1 of 4
(3,161 Views)
Hello,
 
What are you controlling with NI-DAQ?  Is it a National Instruments DAQ device?  There is no way to control 3rd party device with NI-DAQ.
What exactly are you seeing with the new verion of NI-DAQ?  Are you receiving an error?
 
Regards,
Sean C.
0 Kudos
Message 2 of 4
(3,145 Views)

Hi. We are running a PCI-DIO-32HS card which communicates with the interface MUROS board (see http://medipix.web.cern.ch/MEDIPIX/Publications/2002_portable.pdf  for details - although we are using the Medipix1 chip which is not onboard the MUROS board). We are not receiving errors from the compiler or any National Instruments application directly, only from the MEDISoft software program. When we run a test, the software should write data to the chip's pixel memory and read it back, count the number of read/write matches and produce a percentage error. We are getting 99% error.(which really means 100%)

The MEDISoft software, MUROS board and MEDIPix chip are the same ones that we used at CERN. I wonder if changing to more recent versions of LabWindows or NI-DAQ board may be causing problems and the MEDISoft software needs fine-tuning somehow. Does this help?
Thanks for your assistance.

Alan.

0 Kudos
Message 3 of 4
(3,136 Views)

Hello Alan,

That link was broken.

Is the MEDISoft software code written with LabWindows?  Can you remove the 3rd party hardware from the system and verify that the PCI-DIO-32HS is behaving as expected?  If it is, then there is most likely a problem with the other hardware.  If the PCI-DIO-32HS does not behave as expected, please provide me with more details about your application (what should be happening versus what is happening).
 
Regards,
Sean C.
0 Kudos
Message 4 of 4
(3,117 Views)