Benchtop Measurement and Test
Distributed Measurement and Control
High-Performance Test
Systems Engineering Software
Perspectives showcases how NI sees what’s next in the world of test and technology.
You can request repair, RMA, schedule calibration, or get technical support. A valid service agreement may be required.
Provides support for NI data acquisition and signal conditioning devices.
Provides support for Ethernet, GPIB, serial, USB, and other types of instruments.
Provides support for NI GPIB controllers and NI embedded controllers with GPIB ports.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
04-25-2019 08:40 AM - edited 04-25-2019 08:42 AM
LabVIEW 2014 is ending 5 bytes to a VB.NET 2010 program.
The VB.NET 2010 program is responding with 127 bytes.
115200
8 data bits
1 stop bit
odd parity
no handshaking
So, out COM 28 for LabVIEW and in COM 30 on VB.NET
All the data bytes are received, but getting framing error on LabVIEW VISA Read.
The jumper from COM 28 to COM 30 is a 4-inch "cable".
Any ideas?
04-25-2019 08:48 AM
Bad cable?
The serial port settings on your VBNET program doesn't match your LabVIEW program?
04-25-2019 10:59 AM
@psuedonym wrote: LabVIEW 2014 is ending 5 bytes to a VB.NET 2010 program. The VB.NET 2010 program is responding with 127 bytes. 115200 8 data bits 1 stop bit odd parity no handshaking So, out COM 28 for LabVIEW and in COM 30 on VB.NET All the data bytes are received, but getting framing error on LabVIEW VISA Read. The jumper from COM 28 to COM 30 is a 4-inch "cable". Any ideas?
Framing errors are usually due to slightly mismatched baud rates.
IOW: Check all of your settings and try a slower baud rate...
What do you need our team of experts to assist you with?
Thanks!
We'll be in touch soon!
