Data logging Error out -1073807339, Working but not

[JonThorn]

I have a basic data logging program.  Its working but not working.  I have everything working in the lab, where the program reads and writes out in using a loop at a defined interval.

When I take it out to the field take it out to log data (note: different transducer but same make and model) It still reads and writes out the data on the loop at the defined interval.

I cannot figure out what needs to be change to get rid of the error out and cannot find out what the error out code -107380733 means.

Any suggestions?

[RavensFan]

Right click on the error in the front panel and choose "Explain Error".

That is not a data logging error.  It is a VISA error, specifically a timeout error.  The VISA Read didn't get the data it was expecting to receive in time.

The first thought is something is wrong with your cable hooked up to this other PC, but since you say you are getting data otherwise, it is probably not that.

It would have been nice if you also attached the actual VI so we can inspect it.  What other differences are there between the VI on the once PC where it works and here.

[JonThorn]

I will check connections.  When running it in the lab I have the time to make sure all connections are solid.  Recording while I'm doing the field work things are never as neat.  One thing I noticed in the wire diagram, my wait count now has a red dot indicator where my ms wait is input.  On the lab setup this error notification is not there.  What does it mean?  How can it be corrected?

[RavensFan]

A red dot means that the data is being coerced.  In your case the constant is an I32,  while the wait is expecting a U32.  Not a problem in this case.  But to avoid coercion dots, it is usually best to create constants by right clicking on the terminal. The it will automatically create a constant of the correct type.

But the fact the same VI on your lab computer doesn't show a coercion dot, that is strange.  Use context help and hover over the constant to see what datatype it is, and over the wait function to see what kind of input it is expecting.  Could the dot be there, but it is a different color than red?  The Tools >> Options >>  Environment settings page has a section for colors where the color of the coercion dot can be changed.