error 1073807253 at VISA Read appreared after 2 years of problem free use.

[glovellette]

System: IBM laptop with windows 2000, labview 7.0, caliper (alternately Sartorious precision balance) attached to RS232 COM1. Data string sent to port by pushing send button on instrument.

Problem: After nearly 2 years of trouble free operation (besides operator errors), VI runs but does not read with "Error 1073807253 at VISA Read. Possible reasons: VISA (HEX 0xbfffoo6b) A framing error occured during transfer".

Troublshooting completed: Checked RS323 connections, checked COM1 in control panel, settings match, checked COM1 with diagnostic software, COM1 working properly, connected caliper to my personal laptop with same VI and Labview 7.1, VI worked there. Loaded labview 7.1 on original laptop. Same error occurs. Connected caliper to backup IBM laptop with Labview 7.0, VI runs but does not read with "Error 1073807254 at VISA Read. Possible reasons: VISA (HEX 0xbfffoo6a) A parity error occured during transfer". Checked COM1 in control panel, settings match.

The most confusing part of the problem is that the system worked for a considerable time and suddenly appeared without any known changes. 

[nyc_(is_out_of_here)]

Was new software installed recently or Windows updates?

[Albert.Geven]

Don' forget to check the rs232 connectors and cables

[glovellette]

Thank you for the response. No new software was installed but we did recieve a security update about the time the problem started. I will contact our network folks about it. That being said, do you have any further suggestions. Thanks.....Greg Lovellette

[nyc_(is_out_of_here)]

I suppose there's always the possiblity that COM1 got damanged in some way. Maybe try COM2. Though I have never seen a COM port go bad. Usually it's issues with cables/connectors or software.

[Ebele_Obijiofor]

Hello,

I would suggest upgrading to the latest version of VISA (3.6) if you haven't already done so. You can find the VISA download here.
If you are running your code in a while loop, make sure you have a delay/wait in the while loop (it can be something relatively small) to allow you r processor time to complete other tasks. The last thing I would suggest is to have a small delay before any read and write calls to your instrument to make sure the instrument is "ready" before you send to/read from it. Hope these suggestions help. good luck!

Regards,