anyone using an Agilent U3606A?

[Christopher80]

I am trying to use an Agilent U3606A in LabView. I am new to LabView, but I am learning quickly. However, when I try to use the drivers that are online, I can not turn off my auto range. I wasn't able to read current from the DMM until I change the command line in the vi to MEAS:CUR? from SENS:CUR. I will upload my vi's in the morning when I get to work. Any suggestions as to attempt to resolve this would be so very helpful and appreciated.

[Christopher80]

"Hello World"  lil humor in the morning.

I am attaching the vi file for the project I am wortking on. All help, suggestions, and feed back is greatly appreciated.

[jjp377]

There is an existing LabVIEW driver on IDNet for the U3606

[Christopher80]

That is the driver I have loaded, it shoots out errors. Even in the examples. It wont function. I'm starting to think I bought the wrong Meter/Power Supply. Damn space contraints.

[Dennis_Knutson]

You need to provide the error codes that you get, which functions are returning the errors, as well as the connection type.

[Christopher80]

I am using a USB connection. I don't get an error code. The problem I am having is the auto range will not turn off. It stays on no matter what. Am I wiring something wrong?

[Dennis_Knutson]

I don't understand. You said that it shoots out errors and now you say you don't get an error code. What then do you mean by 'shoots out errors'?

In the VI you posted, you have autorange turned on. Turn on NI-Spy/NI-Trace and run the VI. Compare the command sent with what is in the manual for the range command. Attach the spy/trace file.

[Christopher80]

Ohh, my aplogies. I wasn't clear. Prior to me changing the command to MEAS:CURR? from SENS:CURR?  I was getting errors. But I got around that. The issue I am having is the auto range problem. 

[JÞB]

Yup- the developer Doinked it up!

Take a look at the format strings in this case structure.  What are all the semicolons doing in there?

CONFigure[:VOLTage][:DC] [<range>|AUTO|MAX|MIN|DEF[,{<resolution>|MAX|MIN|DEF}]] is the command syntax so a valid command would be

Conf:Curr:DC 1e+0,10000   NOT

Conf:Curr:DC ; 1e+0,;10000  

Get rid of the semicolons 

And shall we post that resolution calculation to the Rube-Goldeberg thread? What's wrong with a ring type-def [4.5 Digits, 5.5 digits],[ 10000, 100000]? 

Aren't certified driver submissions supposed to be accompanied with test data?

Edit: read the smilies as colon ":"DC

[Dennis_Knutson]

I don't get the ; when I probe the VISA Write string. The syntac for specifying a period decimal is %,; so the semi-colon should not be part of the string.