LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Agilent 66000 Value Setting&READING

Hi all,
         I attempt to combine Power Supply default value setting and reading function into one VI. These individual vi have proven to work well . But when they are combined together ,it is easier to generate I/O conflict.
         I think time overlap may contribute to that problem since  the board need time to boot up ,then we can get the reading.
         Pls have a look at the attachment. Figure 1 is the defaut value setting vi, Figure 2 is the reading VI.
         Who can extend me the support for that problem?Thanks.
BR,
Evan
0 Kudos
Message 1 of 7
(3,253 Views)

Is this the same issue as in this thread?

http://forums.ni.com/ni/board/message?board.id=170&message.id=249698

 

Message 2 of 7
(3,244 Views)
Hi Richard,

as JoeLabView noted you are sending  mutliple threads Smiley Mad

Stick with the same thread, it is easilier for every one to follow.

You extremely large jpg indicates that you experience with labview is limited.  try saving the diagram as a tiff!

Check out the examples that are provided with labview. failing that,usually agilent pack a generic example with their
instrument drivers.

Your diagram indicates that you are not 'tying' the vi's together ! So which one executes first.( what happens if your default setup accidental states that all vi execute- if boolean is true  this will happenSmiley Wink)

When using the same instrument if you do not close the session then use the reference to that vi to link them.

Strongly suggest that you ask your boss for a training course in labview- >believe me the cost is recovered very quickly)


goodluck

xseadog




Message 3 of 7
(3,242 Views)
Hi ,
       Thanks for your suggestion.I'll talk about the training issue with my line manager. BTY ,what does" use the referrence"mean?Thanks.
BR
Evan
0 Kudos
Message 4 of 7
(3,193 Views)


@xseadog wrote:

You extremely large jpg indicates that you experience with labview is limited.  try saving the diagram as a tiff!





Really it is much better to save the diagrams as .png files.  And the real problem with that attachment is that although it claims to have .jpg extension, when I try to download it, it seems to actually be a .bmp which are the worst in terms of size.
Message 5 of 7
(3,189 Views)
0 Kudos
Message 6 of 7
(3,185 Views)

Your new attachment, is that the latest code?

You really need to provide proper dataflow.  The easiest way is to wire the error cluster to force a dataflow.

Consider what actions need to occur and define a sequence for the actions.  Then look at which vi's perform that action. 

Most vi's will support wiring an error cluster.  For those that don't, you can enclose them within a Flat Sequence Structure..  But don't abuse them..

RayR

Message 7 of 7
(3,174 Views)