LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Simple Power Supply Test Program (Keysight E3649A)

Solved!
Go to solution

Trying to test the SCPI commands for this power supply without a FSM first. I can easily select between OUT1 and OUT2 as well as the programmable voltage or current value, but the following are giving me errors:

 

NOTE: I did *IDN? and *TST? successfully and ensured front panel display's accuracy when selecting desired voltage

 

1. Choosing between OUTP OFF and OUTP ON

2. Choosing between P35V and P60V

 

 

AnalogEE_1-1616174728466.png

 

AnalogEE_0-1616174703947.png

 

0 Kudos
Message 1 of 10
(4,303 Views)

Hi AnalogEE,

 


@AnalogEE wrote:

Another question: can you recommend a resource full of pure SCPI command examples for power supplies? 


What about the (programming) manual of your Keysight device?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 10
(4,282 Views)

@AnalogEE wrote:

 

Another question: can you recommend a resource full of pure SCPI command examples for power supplies? 

 

 


Well YES!  The manual for the device has every single one of the commands listed.  You should look into that;)

 

It looks like your OUTP ON command is unterminated.  


"Should be" isn't "Is" -Jay
0 Kudos
Message 3 of 10
(4,280 Views)

@AnalogEE wrote:

 but the following are giving me errors:

 


What errors are you getting?

 

Some things I see:

  1. Your OUTP ON command doesn't end with a carriage return.
  2. Your VOLT:LEV 0 command doesn't end with a carriage return.  (And the concatenate strings function there serves no purpose.)
  3. When you have \r in a constant and it is in \codes mode like it seems to be, you should make the display style visible on those constants so it is obvious.  It is a good rule of thumb that any controls, indicators, and constants that aren't using the typical display style should have the display style or radix indicators visible.
  4. You don't have an VISA serial configure in there.  (VISA Open isn't needed).  So are you sure your PC and/or MAX have configured that serial port for the correct communication parameters.
  5. You are sending several commands in a row right away, any chance the device needs a little pause between those steps for them to execute properly?

 

0 Kudos
Message 4 of 10
(4,276 Views)

Hi,

 

Below is a snippet I'm following and still getting an error on the front panel display. The model I have has P35V and P60V so disregard the P8V below. 

 

AnalogEE_0-1616176334815.png

AnalogEE_1-1616176360899.png

 

 

 

 

0 Kudos
Message 5 of 10
(4,273 Views)

WHAT DOES THE ERROR SAY?

 

Does the "front panel display" mean the device itself?  I can't read screen that from where I am.

 

If by front panel you mean that small section of your LabVIEW VI front panel, it doesn't show any error.

0 Kudos
Message 6 of 10
(4,254 Views)
Solution
Accepted by AnalogEE

You know it would probably save you a lot of time to just use the LabVIEW Drivers for your E3649A 

 

BTW: HP "test and measure" was spun off and became Agilent. Then Agilent became Keysight.

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 7 of 10
(4,253 Views)

The error is -113 which means undefined header. The front panel display refers to the device being automated. 

0 Kudos
Message 8 of 10
(4,243 Views)

Now there's a little piece of information we can work with.

 

I googled Keysight header error  and found this link.   https://edadocs.software.keysight.com/kkbopen/why-do-i-get-syntax-and-undefined-header-errors-when-u...

 

It talks about termination characters, and that may or may not be the cause of your error.

 

But back in message 2, items #1 and 2, I commented on missing carriage returns.  Have you investigated that yet?  I'd suggest reading the manual as perhaps it needs to be a carriage return line feed.

 

And as RTSLVU suggested, downloading the LabVIEW drivers for it might save you a lot of troubleshooting effort.

0 Kudos
Message 9 of 10
(4,236 Views)

Take a look inside the "drivers" and you will probably see that they are nothing more than the SCPI commands wrapped up in LabVIEW vi's.

 

I mean I get it wanting to know how to do it yourself, but in my company time is money. 

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 10 of 10
(4,225 Views)