LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

buffer being kept full? One step not working after another, even though they're in series

I'm having trouble getting LabVIEW to give me both px and vx information, per attachment.  If I toggle the Boolean button, one of the 2 works, if I toggle back, the other of the 2 works.  I have a suspicion the area where I give it instructions for ac, sp, dc, etc. is tying up the connection, but A) I don't know how to get arround it, B) I'm not certain that's the problem.

Any suggestions?

Thanks!

 

p.s. I'm a very novice LabVIEW user and the program was written by somebody else who left no documentation for me.

0 Kudos
Message 1 of 11
(3,249 Views)

It would be very helpful to people helping you if you post the code instead of screenshots. Why are you setting the VISA receive buffer size to the default after every read?

=====================
LabVIEW 2012


0 Kudos
Message 2 of 11
(3,232 Views)

That is the Flush buffer not Set buffer size.

 

taguhi,

 

Do you get any errors?  What makes you think the problem is what you suspect?

 

As Steve said, please post your code.  It is quite difficult to debug a picture.

 

Lynn

0 Kudos
Message 3 of 11
(3,214 Views)

@johnsold wrote:

That is the Flush buffer not Set buffer size.

.  It is quite difficult to debug a picture.

 

Lynn



And without the context help it is difficult to identify functions that I do not use.

=====================
LabVIEW 2012


0 Kudos
Message 4 of 11
(3,210 Views)

I looked it up.  I do not use it either.

 

Lynn

0 Kudos
Message 5 of 11
(3,205 Views)

Yea, I looked it up too. The two look very similar and I got the wrong one.

 

This is a very good example of why people should always post code and not images.

=====================
LabVIEW 2012


0 Kudos
Message 6 of 11
(3,196 Views)

Folks,

Thanks so much for the quick responses.  I was not near the computer to respond on time.

My colleague has fiddled around with the program a little more, but I'm still pretty sure that the communication line gets hung up between giving it instructions and querying for status.

This time I have attached the code.

Thanks again!

0 Kudos
Message 7 of 11
(3,156 Views)

Just because I asked for help the problem is solved.

Thanks for all your help.

0 Kudos
Message 8 of 11
(3,150 Views)

For the benefit of others who may think they have a similar problem, can you please report what you found and how you fixed it?

 

Thank you,

 

Lynn

0 Kudos
Message 9 of 11
(3,124 Views)

Per Lynn's suggestion, I have attached the updated code.  The problem was solved by having the 2 sets of data querying operations in series, with a time delay in between.  Whereas I had a time delay between the 2 operations, but they were in the same case structure.

 

I'm now working on a whole new problem that's driving me up the wall, but this one is solved.

 

Thanks!

Message 10 of 11
(3,116 Views)