Using HM1008-2 with Labview

[astroman]

Hi,

I'm running Labview 8.2 and 8.6. And I've got an oscilloscope made by Hameg. The Scope is a HM1008-2 and has an USB/Serial Interface HO720. My Problem now is, the scope is using SCPI commands and I'd like to use it with Labview. It's hooked up to my PC via USB. Are there some modules to use? Or do I need to programm everything myself?

Also the Labview docs about SCPI is very small and everything tells me, that SCPI is to be used over GBIP..

 Thanks for Help 😞

[Dennis_Knutson]

NI does not have a driver for that model scope but there is one for the 1004. This is written by Hameg and not supported by NI but it might be close. Even if it's not 100% compatible, it would be a good starting point.

SCPI stands for Standard Commands for Programmable Instruments. It was developed many years ago in an attempt to make programming instruments less cryptic. I don't remember which organization is responsible for the SCPI standard but it is not NI. SCPI was first applied to GPIB programmable instruments but can just as easily be used for an instrument with any type of connection. Everything you need to know about SCPI should be in the instrument's programming manual.

[astroman]

Thanks for the fast reply!

I will try the Driver for HM1004-3 but I don't think it will work. Because Hameg has changed their protocol from something own to SCPI. The programming manual I've already downloaded.

But I don't get how to communicate. I don't want to rewrite everything... That's why I asked if there's something in particular usable. But it doesn't seem so...

No GPIB no SCPI 😞

I'll try a Visa Tutorial and create my own communication routines.

greets

[Dennis_Knutson]

You DO NOT need GPIB for SCPI! Read what I said. SCPI is the command set built into your instrument and will work whether you have GPIB/Serial/Ethernet.

Usually the only difference between a GPIB instrument and a serial one is that you need to append a termination character (or characters) onto the end of each command. The term character is often a CR/LF, or both.

Yes, it sounds like you will need to write the driver yourself. You also have the option of using the Instrument I/O Assistant. Test everything in either MAX or Hyperterminal first before you decide to write any code.

[astroman]

I've read your post. But I wanted to know if there are some already useable vi's for communication.

As far as I've understand SCPI it's a standard which all (supported) devices know. That's why I've asked if there's something.

Ok I'll try writing my own stuff maybe I'll realease it if it works 🙂

Hyperterm is problematic because, the HO720 interface doesn't register as standard usb<->serial converter. Although an FTDI FT245is built in it. I'll look if I can find a way.

Greets

[Dennis_Knutson]

Your previous post, you had said 'No GPIB No SCPI' and that is clearly incorrect. You also need to understand that a SCPI implementation on a scope from vendor A is going to be quite different from a SCPI implementation on a scope from vendor B. You can look at drivers from Tek and Agilent to get an idea. You've got the Create Instrument Driver Project wizard that can create a basic framework for a scope driver.

The problem is going to be with your last statement. You originally said it had a USB/Serial interface. If it does not appear to windows as an RS-232 interface, it will not appear as an RS-232 interface to LabVIEW. You really need to get some more information about the USB interface. If it's a USBTMC class instrument, then you should have no problems.