From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

113 undefined header, 0 no error

Hi all, 

I have this programme in LabVIEW for Photo-CELIV ( charge extraction by linearly increasing voltage). I a using the Keysight B2912A so using the driver B2900a. 

 

I am getting the error messages:

Agilent B2900 Series.lvlib:Error Query.vi<ERR>
Instrument reports:
-113,"Undefined header"
+0,"No error"

 

<b>Complete call chain:</b>
Agilent B2900 Series.lvlib:Error Query.vi
Agilent B2900 Series.lvlib:Configure Source.vi

 

I have looked up the error message indicates the header is syntactically correct, but it is undefined for this specific device. For example, *XYZ is not defined for any device.'  but as someone new to LabVIEW I am struggling to fix this. 

 

I have attached the program FYI.

 

Thanks, 

Ellie

0 Kudos
Message 1 of 8
(2,545 Views)

I'm concerned you have 2 parallel things happening with the same VISA resource.  You should be initializing before your loop and not closing until after the loop.  You can then do all of the other stuff you want.  But you definitely need a data dependency between your two tasks or you could be attempting to send multiple commands at the same time, possibly corrupting the communication and therefore causing your error.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 2 of 8
(2,529 Views)

Hi, thank you for this. Should I create two subVIs to fix this and then call them in the main VI?

0 Kudos
Message 3 of 8
(2,515 Views)

Hi ELLIE,

 

as pointed out: don't run serial communication in parallel!

 

Cleanup your blockdiagram to improve readability. And create two subVIs as indicated by the sequence frames:

Now execution order is purely dictated by DATAFLOW: the communication should be more stable than before…

You could (probably) also remove that frame with your wait function once you created your two subVIs.

 

What's the point of this (Rube-Goldberg) operation:

Why do you need to create a 2D array containing two rows just to index both rows immediatly after?

(And did you know IndexArray provides more than just one output?)

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Download All
0 Kudos
Message 4 of 8
(2,513 Views)

Hi GerdW, that is great- thank you for your insight! Quick question- how did you go from the below picture to just 'Typ'?

 

THanks again, 

Ellie

0 Kudos
Message 5 of 8
(2,492 Views)

Hi Ellie,

 


@ELLIEg wrote:

how did you go from the below picture to just 'Typ'?


It's the same as with IndexArray: you can change the size of that element/the number of inputs/outputs!

With latest LabVIEW versions you can even hide the event data nodes completely. Read the help for the event structure…

 

(As I have installed the German LabVIEW version: "Typ" is German for "type".)

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 6 of 8
(2,485 Views)

Hi again GerdW, 

I have tidied the diagram up and added in the flat sequence structures however am still getting the same error codes:

Agilent B2900 Series.lvlib:Error Query.vi<ERR>
Instrument reports:
-113,"Undefined header"
+0,"No error"

 

<b>Complete call chain:</b>
Agilent B2900 Series.lvlib:Error Query.vi
Agilent B2900 Series.lvlib:Configure Source.vi

 

 

do you have any other ideas on how to fix?

 

THanks!

Ellie

0 Kudos
Message 7 of 8
(2,447 Views)

I guess you'd better check what's going into the configure source VI and see if all the input values are valid.  Common causes could be an empty string that causes the command to be concatenated in a "strange" way.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 8 of 8
(2,438 Views)