Need Help by TCP/IP issue with Error 1 in Labview Code

[Kyle97330]

I can't actually look at your VIs, but I am familiar with the error codes.

The first one (1073676294) is pretty common and just means that when you did a VISA Read, there may have been characters left that you didn't read.  This is something that you can often ignore but it can be a warning sign that you did something wrong.  

The second one (-1073807252) means that your input buffer is full.  This usually happens when you are getting more information in than you're reading out of the VISA read function.  It usually happens when you do a "write" without doing a "read" to clear what was read back, or if you activate some form of "continuous send" function on your device.

So, check to see if every time you do a "write", you do a read back to get its reply, and check that none of the commands that you are sending are turning on a continuous sending mode.  (Or, if you do want it to send continuously, make sure that the loop doing the reading of the continuous values is running fast enough to keep up.)

[Bob_Schor · Accepted solution]

---

@gabrielstephane12 wrote:

To find the device I opened MAX and got this error message (attached picture): The device is not accessible means (Das Gerät ist nicht erreichbar)

---

MAX is telling you the cDAQ is located at 192.168.1.101.  In your earlier e-mail, you mentioned the address that you tried to Ping (192.168.0.30), but there doesn't see to be any hardware there.  Try 192.168.1.101, where there is hardware -- you should see a successful Ping.

Do you have any colleagues who are familiar with LabVIEW, especially connecting Hardware and using MAX to find and test the hardware?  You would benefit a lot from a half-hour consultation with someone who could work directly with you and get you started with connecting the hardware.

Bob Schor

[gabrielstephane12]

Hi,

thank you for the help you gave me last time. Now I have another problem with the error message -1073807246. 

The aim is to tare the scale with the corresponding communication and commands and to read out the current weight display. Now I have difficulties controlling this, because I always get the error message -1073807246 in LabVIEW.

This error means: The resource is valid, but VISA cannot access it at the moment. For this I need your help please. what is the best way to fix this error message???

[gabrielstephane12]

Hi,

thank you for the help you gave me last time. Now I have another problem with the error message -1073807246. 

The aim is to tare the scale with the corresponding communication and commands and to read out the current weight display. Now I have difficulties controlling this, because I always get the error message -1073807246 in LabVIEW. Attached I send you all the VIs I used for this. 

This error means: The resource is valid, but VISA cannot access it at the moment. For this I need your help please. what is the best way to fix this error message???

[Bob_Schor]

When I get an Error Message, in addition to the Error Code and what it means, LabVIEW usually tells me what VI/Function caused the Error, and if it doesn't, I run the code again, with Highlight Execution turned on for the sub-VI in which the Error occurred, and I watch and see which VI caused the Error.

So which VI/sub-VI caused the Error?  Knowing this, you can read the Help for that function and often figure out what you forgot to wire, what input parameter was wrong, or what you forgot to do (like wait for I/O to complete) before executing the function.

Can you provide us this additional information?

Bob Schor

[Kyle97330]

-1073807246 usually means that some other program is using the device at the same time as your program.  Do you maybe have NI max open, or another program that is communicating with the same instrumentation as you?

If you think you have closed all other programs using it and still get the error, you may need to reboot the PC to clear it up.  Also, if you're on a PC that other people use, if they didn't close a program using the device it might also lock out LabVIEW, which you can also reboot to resolve, or possibly have the other user switch back to their profile and exit the program in question.