Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

Trying to control Jungo device

Hello,

  I'm new to labview, so please bare with me. I've been in contact with Labview engineering support, as well as with my device manufacturer, but so far no luck. I've tried all of the simple and obvious tricks that one might think of, and I've read every applicable knowledge base article to the best of my knowledge.

 

I'm trying to connect a Bartington MS3 magnetic susceptibility coil to LabView, and I'm having trouble figuring out what route I need to take. The device plugs into my PC(windows 7) using a USB cable, but doesn't show up in MAX under any . It shows up in the device manager under "Jungo", which is the manufacturer driver type. I tried running the visa driver wizard for USB, and interestingly, the wizard recognizes the device. If I hit next to start creating a driver, I get the message "This device is a member of the USB test and measurement class (USBTMC). NI-VISA can already detect and control it. Do not use this wizard to create an INF file." This sounds like good news, but if it were true, shoudnt MAX recognize the device?

 

Below, I've attached a copy of the inf text file. Now, I'm also having trouble telling what driver for the device needs to be installed. One article I read said that the device's native drivers need to be installed, but another article stated that a USBTMC device needs to have an NI VISA driver controlling it, and that VISA should recognize the device and install drivers for it when I plug it in. I uninstalled the device's drivers and software and plugged it in, but no luck. I also tried manually selecting folders to install drivers from for the device, such as in program files (and program files 86) > National instruments, or program files > ivi...etc.

 

If it is in fact a USBTMC device, It should be obvious, but I'm starting to think that is must be something else. I can get into device manager and tell you the port and hub number, but it doesnt show up under any type of USB heading there or in MAX. Do I need to create a PXI/PCI connection? Possibly a DLL call of some kind? There must be something I'm missing.

0 Kudos
Message 1 of 7
(4,646 Views)

It looks like the device drivers that come with the device only support the software that they provide with the device.  The best way then to integrate with the device would be to use the DLL's that are installed with the device, and call them from LabVIEW.  So look more into what DLL drivers the company provides with their hardware.

Systems Engineer
SISU
Message 2 of 7
(4,615 Views)

I do believe you're right, Nathan, and thanks for the reply. I just got word back from the manufacturer on this, and although I have a limited understanding of the subject, they do seem to corraborate the need for a DLL of some kind. For the good of the board, and for any further advice,  I'll paste my answer fom them here:

 

Hi D****,
 
The uniqueness of MS3 is that its a custom device (as opposed to devices such as USB memory storage...etc.) which means you need a kernel level driver, so that the host OS loads it as soon as it is detected. Therefore, you need to have installed the MS3 USB device driver. This driver is installed when Bartsoft is installed, or we can provide it separately, if a user does not want to install Bartsoft. Here I am assuming you are choosing to make USB connection with MS3 (not RS232).
 
After having the driver installed on the host PC, you have two options to communicate with MS3.
 
1) Use a Windows DLL that we can supply. This DLL loads the low-level USB driver DLL and exports C style function calls that greatly simplify the communication protocol. This will require calling C functions and passing parameters that (in case of Asynchronous calls), include either call-back function pointers or a Windows Handle that will receive Windows messages (notifications) with pointer to a C style structure that contains measurements data. This approach hides complexity of MS3's communication protocol and its strict timing requirements. 
 
2) Communicate with MS3 directly, using USB driver calls. In this case, you will still need to make DLL calls to the MS3's USB driver but this will be the USB DLL (not an intermediate DLL, as it happens in the first approach). The advantage here is that you don't rely on an intermediate DLL code and its possible bugs.
 
My colleague J*** D****, has had some experience connecting to MS3, using Labview on XP but when I asked him to help, he said he has not been able to do this since he had Windows 7. He did this by using VISA's driver wizard that created a driver. He is having a second look at this and I will forward you any results as soon as available.
 
Please let me know which way you would like to precede and I will be happy to send you the .DLL and .LIB files if you wish. I have VC++ application that shows how to load this DLL and use it but I am afraid have no Labview VI at the moment.
 
Thank you,
M*****

Based on this information, would it be possible for you to provide a short synopsis of the steps I'll need to take and the functions I'll need to use in labview to get this working? Your help is greatly appreciated!

0 Kudos
Message 3 of 7
(4,610 Views)
I would use the dll and their api. You can import the dll into LabVIEW. If the engineer from the vendor had problems with VISA and USB RAW, I would expect that you would have even more.
0 Kudos
Message 4 of 7
(4,594 Views)

I would believe it, Dennis. With my skill level, the DLL calls sound a bit forboding as well. I think what I'm going to try right now is to run the VISA wizard in "Windows XP mode" 32 bit emulator and see if that might help. If someone else has done the work already, I can claim the glory. Plus I needed to run it all in 32 bit mode anyway to gain access to the parallel port! I'll update this and let you know if it worked.

0 Kudos
Message 5 of 7
(4,592 Views)

Another update: I tried running on the 32 bit virtual machine, and it appears that I got access to the parallel port for my other application (PortOut.VI), which is good. But, the VISA driver wizard still tries to tell me that my device is a USBTMC, so I cant create a RAW driver. Looks like its DLLs unless the manufacturer comes up with something better. Its going to be difficult. Thanks!

0 Kudos
Message 6 of 7
(4,588 Views)

Hello,

It's an old post I know, but I'm in the same situation regarding MS3 device.
Do you have a solution for me?

Regards,

Julien

0 Kudos
Message 7 of 7
(1,694 Views)