Framing error

I have a device (TSI flow meter) that reads data every 10 ms and updates the display. It also sends the data over a serial bus at 38400 baud 8 data bits, no parity, 1 stop, and no flow. I have the device pluged into a serial to usb converter ( serialgear). If I use the simple "visa read/write.vi" that ships..by the way I still have LV7.1, w Labview I get a framing error after 2 or 3 trys w the delay before reads set to 500 ms. If I increase the delay to 1 sec it looks like it can go on for ever. Problem is I can't wait 1 sec. I need around 20, 30 or so msec for my data to be meaningful. Any thoughts/suggestions??

Does it work with Hyperterm or another app?
Any chance you can try plugging it in to a "real" com port? Those USB things can be flakey. I understand that you are probably using it because you don't have a real RS232 port. But is there another computer you can try it on? I know what a pain. But those USB converters usually are.
=====================
LabVIEW 2012

Similar Messages

I am getting a framing error when running a VI via RS-232. Any thoughts?

I have a Keithley 2700 multi meter and am trying to get its IDN. I am getting error number 800, on the multimeter, back when running the VI

A framing error indicates that you don't have the same serial parameters set the same on the pc and on the instrument. Double check baud rate, parity, data bits, and flow control and make sure they match.

How do i get rid of the the framing error

Hello,
I am a student working on a Pulse Oximeter and i am supposed to send sample values to Labview via the RS232 serial configuration. I am able to view the data in VISA but i am unable get the graph running constantly. There is always a framing error(-1073807253) whenever i run the VI and the graph only appears for a few seconds before the whole VI halts to display the error. How do i get rid of the error. I am only sending 8 bits of data. I have even tried using even the most simplest program whereby i send only characters A & C and even then i am getting the framing error. Please help me, i am in need of urgent and desperate help. I am sending these cahracters from the PIC16F877 using assembly language and i have attached the code to this forum thread. I have even tried making use of 9 bit transmission and parity bits and nothing seems to work for me. Please provide me with some help and suggestions. Have a look at my program and VI and sugggest some solutions as soon as possible. Your help will be greatly appreciated.
Thank You
Best regards,
Samarth Pawar
Temasek Polytechnic
Singapore
Below is my program to send the data:
#include
TXSTA_INIT EQU 0x24
TRISC_INIT EQU 0x80
RCSTA_INIT EQU 0x90
#define Freq .4000000
#define Baud(X) (Freq/(.16*X))- .1
call SetupSerial
Loop:
movlw 'A'
movwf TXREG
call Usart_Send
movlw 'C'
movwf TXREG
call Usart_Send
bcf TXSTA,TXEN
goto Loop
;;;;;;;;;;;;1MS DELAY;;;;;;;;;;;
DLY1MS MOVLW D'40'
MOVWF H'31'
LOOP2 CALL DLY
DECFSZ H'31'
GOTO LOOP2
RETURN
DLY MOVLW D'1'
MOVWF H'30'
NOP
LOOP1 DECFSZ H'30'
GOTO LOOP1
NOP
RETURN
SetupSerial:
Banksel TRISC
movlw TRISC_INIT
movwf TRISC
movlw Baud(.9600)
movwf SPBRG
movlw TXSTA_INIT
movwf TXSTA
Banksel RCSTA
movlw RCSTA_INIT
movwf RCSTA
Return
Usart_Send:
banksel TXSTA
SS_Wait btfss TXSTA,TRMT
goto SS_Wait
bcf STATUS,RP0
CALL DLY1MS
Return
END ; directive 'end of program'
Attachments:
New_ash.vi ‏180 KB

Four things to check when having problems with serial com:
1. Make sure the baud rate matches the device.
2. Make sure the parity bit matches the device.
3. Make sure the number of stop bits matches the device.
4. Look for buffer overruns if you do not use flow control.
Like CC said, using Hyperterminal will verify that you are getting good responses from your device. If it runs fine for a while, then you start getting errors, the most likely cause is buffer overruns. You will have to use flow control to prevent this from happening. You will have to know what type of flow control your device supports, hardware flow control (RTS-CTS), or software flow control (XON-XOFF).
CC: Look again, he did post his vi.
- tbob
Inventor of the WORM Global

Error -1073807253 occurred at VISA Read in transient SR830.vi VISA: (Hex 0xBFFF006B) A framing error occurred during transfer.

Hi,
I am have written a program with labview to make transient c-v measurement using a stanford research SR830 lockin amplifier. The program seems to be runing fine, but sometimes it is givvibg an error:
Error -1073807253 occurred at VISA Read in transient SR830.vi
Possible reason(s):
VISA: (Hex 0xBFFF006B) A framing error occurred during transfer.
Error -1073807253 occurred at VISA Read in transient SR830.vi
Possible reason(s):
VISA: (Hex 0xBFFF006B) A framing error occurred during transfer.
but if I press ok, the program again starts running. What might be the poblem? BTW I googled a bit and I see that in the labview topic "RS-232 Framing Error with HP 34401A Mulitmeter" by pkennedy32 this is what is said about framing error:
""Framing Error" in an RS-232 context means a very specific thing - when the receiver was expecting a stop bit, the line was not in SPACE condition. This can be the result of:
1... Baud rate mismatch (although other problems would likely crop up first).
2... Data Length problem, If I send 8 data bits and you expect 7, the stop bit is in the wrong place.
3... Parity setting mismatch - If I send 7 data bits + parity and you expect 7 data bits and no parity, the stop bit is in the wrong place.
4... Mismatch in # Stop bits - If I send you 7 Data bits + parity + one stop bit, and you expect 7 data bits + parity + TWO stop bits, the second one might not be correct, although most devices do not complain about this.
But, I must say that this is the same com port setting that I use to measure c-v hysterysis, but I never gt this error there.
I attach the program herewith for your kind perusal. Please help me resolve this issue.
Thanks in advance.
Solved!
Go to Solution.
Attachments:
transient SR830.vi ‏94 KB
csac.vi ‏8 KB
sr830 initialize1.vi ‏15 KB

@Dennis Knutson you are right I checked the read indicator in backslash mode, and instead of a \n it is sending \r. So I changed the \n in my write strings to \r. But, if I keep the CLOSE VISA outside my loop instead of inside as you suggested, the termination character appears to come in the middle of the read string instead at the end. And since the read terminates at the \r so it is displaying some junk value before the \r, but if I put the CLOSE VISA outside the loop and play along with the bytes at the read buffer, I see the whole read string with the \r at the end of the string. But, whenever the values are in exponential form (when close to zero) like 6.938839 e-5, I always get a time out error whatever be the timeout that I put at the VISA initialize. And subsequently, if I stop the program and run it again the machine program hangs and I donot get any reading. Then after I close it again and start, sometimes it hangs for some more or starts working. If I put an arbitrarily large byte count at the READ VISA, then I always get the time out before the operation completed error.
@ Ravens Fan I have removed the CSAC VI altogether and taking the CH! And CH” reading separately, instead as one string. So, no more issues with that.
I use the control at the delay so that I can choose how much delay I want to set, and I use the math operation because I am using adding up the delay time to keep track of the time elapsed. Because in the end I have t plot a time vs. CH! And CH” readings.
I am not sure but probably I am making some silly errors. Please help me out.
Attachments:
transient SR830-2.vi ‏103 KB
sr830 initialize1.vi ‏15 KB

Framing error on seriell port

Hi,
I am trying to read data from the seriell port. I doesn't know exactly
the correct setting for communication with the external device, but I
know, I use the correct baud rate.
My problem is, I get from the "Bytes atseriell port.vi" the error 4008h
(framing error). What is the meaning of this error? Any suggestions? I
read 2 bytes more from the port, then I should. This is independent from
the string length.
Regards
Ralf

"Rolf Østvik" wrote:
>
> On Tue, 30 May 2000 13:03:28 +0200, Ralf =?iso-8859-1?Q?K=E4hler?=
> wrote:
> >I am trying to read data from the seriell port. I doesn't know exactly
> >the correct setting for communication with the external device, but I
> >know, I use the correct baud rate.
> >
> >My problem is, I get from the "Bytes atseriell port.vi" the error 4008h
> >(framing error). What is the meaning of this error? Any suggestions? I
> >read 2 bytes more from the port, then I should. This is independent from
> >the string length.
>
> You might try to experiment with different types of parity (and maybe
> number of stop bits). Do the change of parity with the
> 'Serial Port Init.VI'
>
> --
> Rolf
Thank's.
I tryed this and so
lved the problem. Another type of parity and 2 stop
bits, this was all.
Ralf

Modbus error code 6101 and framing error

Using the Vi's MB INIT and MB WR to monitor the registers of a Micro-Motion sensor but keep getting either Framing error 1073807253 or timeout 6101. The communication is RS232, 1 stop bit, RTU (8 data bits), 9600 Baud and the program reads 50 consecutive registers (Floating), timeout is set to 2000 ms. Usually the errors occur after about 5 minutes or so.
Labview Version 8.5
Labview Version 8.6
Labview Version 2013

Hello Romain
Please find attached my Vi. I have reduced the amount of registers taht were originally read from 50 down to 20 and increased time delays which seems to have removed the error code problem.
However I still miss data, for example the temperature reading will be fine for a few minutes but then go to zero or a large number. The same thing occurs with other registers that are being read.
Thanks
Jack
Labview Version 8.5
Labview Version 8.6
Labview Version 2013
Attachments:
MODBUS MVD VER1.vi ‏37 KB

Framing error with Labview7.1 and RS232-RS485 converter...

i am trying to communicate to a measurement board (is based on RS485 interface) using Labview7.1 and RS232-RS485 converter. I'm using the same settings as the Board. I am able to read the data but at the end end of each serial read, every time I find 'Framing Error'. And the data is corrupted. Please help out ...
Please go thru my code (attachment) and let me know if i'm going wrong anywhere.
Attachments:
serialRead.vi ‏62 KB

Please see the reply in this post:
http://forums.ni.com/ni/board/message?board.id=140&message.id=13692
Michael Chaney
Systems Engineer - TestStand
National Instruments

VISA framing error BFFF0068

Hello,
I am getting a VISA framing error code BFFF0068 with the
serial com demo VI that I found in lab view. How does a "normal
human being" understand what this error means so that it can be fixed?
The device that I am trying to communicate with has detected a error
condition and it transmitting error messages galore. The device
comminucates via COM12 at a baud rate of 260417.
Amy ideas what BFFF0068 means?
Regards,
Kaspar

A framing error can also be due to a driver configuration error, such as a baud rate mismatch. Since you are using a non-standard baud rate of 260417, this is probably the cause. Since you are using COM12 as your resource, I assume you are using an add-in serial board. Make sure your board supports the baud rate you are trying to use.
Here's a KB that talks more about framing errors:
http://digital.ni.com/public.nsf/websearch/13A20C0F9DF265FB86256FC60066D9C2?OpenDocument
Message Edited by Michael C on 02-14-2006 02:14 PM
Michael Chaney
Systems Engineer - TestStand
National Instruments

VISA: (Hex 0xBFFF006B) A framing error occurred during transfer when read write done in lab view

Hello LabViewians,.
I am getting this error. when i run this program in lab view7.1 the data i'm sending it not read but it read randomly any character . So, please help me out great minds out there. .
Thanks,.
rajesh
Attachments:
read_frame.vi ‏485 KB
read_frame.vi ‏485 KB

Framing errors usually indicate you have a problem with the serial port settings used, such as parity, data bits, or stop bits. Verify the values you use in your VI match what the instrument is expecting.

IO_AI Buffer Read error programming Iotech DAQ 2000 board.

Hi,
I am new to Labview and am using Labview 5.1.
I am trying to collect data from a multifunction Iotech Daq2000 board and save data into records. I am collecting the data, saving it, waiting a few seconds and repeating the same procedure. The first record saves correctly but I then receive the following error while recording the second record. Further probing indicates that the error occurs in the daqAdcTransferGetStat VI and the error appears
to be related to the Device Handle.
Thank you for any help.
Frank
Error -115
This error occurred first at the IO_AO Control VI immediately after
a record was completed. It then appeared a second time at the IO_AI
Buffer Read VI part way through the second record
Possible reasons:
Windows GetCommError: the hex value of this code is FF8D
Interpret it bitwise as follows:
X4000: serial port VI error
X0001: receiving queue overflowed or character was received after end-of-file charachter
X0002: character was lost by overwrite
X0004: parity error
X0008: framing error
X0010: break condition
X0020: CTS timeout
X0040: DSR timeout
X0080: RLSD timeout
X0100: transmission queue ws full when new character arrived
X0200: parallel device timeout
X0400: parallel device I/O error
X0800: parallel device not selected
X1000: parallel device out of paper
X8000: requested mode is not supported or the idComDev parameter is invalid
Consult the LabVIEW serial port manual for more info.

Hello,
The problem you are seeing seems rooted in the driver for your lotech card. Since that isn't an NI product, you may not find many people with experience using it here.
Sorry I can't be of more help!
Best of luck!
JLS
Best,
JLS
Sixclear

What types of Interface Errors lead to Input/Output Drops/Discards?

Hi All,
I was wondering if anyone knows if all of the following errors would lead to packet drops/discards.
Runts
Giants
Framing Errors
Overrun Errors
Abort Errors
Also, are there any types of interface errors that don't lead to packet drops/discards?
So if all interface errors lead to packet drops/discards, I may not have to poll for multiple OIDs for these errors, but instead just poll for packet drops/discards.
Any insight would be appreciated.
Thanks,
David

ifInDrops do not related to errors. In fact, ifInDiscards specifically count packets that were discarded without an associated error. This could be due to a lack of buffer space (e.g. no queue slot), or there was no listener for a TCP connection. The same is true for ifOutDiscards.
For a consolidated error count, look at ifInErrors and ifOutErrors. It will depend on the interface/encapsulation type as to what exactly will be counted as an error, but anything that would be an encap-specific error should appear in one of the interface error counters.

16640 and 16409 errors

Im writing a driver for an serial interface (RS232).
Why do I get Errors 16640 (x4100) and 16409 (x4019) and how do I fix them?
Rafael Kaiser
News suchen, lesen, schreiben mit http://newsgroups.web.de

From a very old faq I found the following text:
4019:--> you had receive buffer overrun,framing error and a break
and the other 4100 shows transmitbuffer full while trying to send.
Hex Value Error Name Meaning
0x0001 CE_RXOVER Receiving queue overflowed. There was either no room in the input queue or a character was received after the end-of-file character was received.
0x0002 CE_OVERRUN Character was not read from the hardware before the next character arrived. The character was lost.
0x0004 CE_RXPARITY Hardware detected a parity error.
0x0008 CE_FRAME Hardware detected a framing error.
0x0010 CE_BREAK Hardware detected a break condition.
0x0020 CE_CTSTO CTS (clear-to-send) timeout. While a character was being transmitted, CTS was low for the d
uration specified by the fCtsHold member of COMSTAT.
0x0040 CE_DSRTO DSR (data-set-ready) timeout. While a character was being transmitted, DSR was low for the duration specified by the fDsrHold member of COMSTAT.
0x0080 CE_RLSDTO RLSD (receive-line-signal-detect) timeout. While a character was being transmitted, RLSD was low for the duration specified by the fRlsdHold member of COMSTAT.
0x0100 CE_TXFULL Transmission queue was full when a function attempted to queue a character.
0x0200 CE_PTO Timeout occurred during an attempt to communicate with a parallel device.
0x0400 CE_IOE I/O error occurred during an attempt to communicate with a parallel device.
0x0800 CE_DNS Parallel device was not selected.
0x1000 CE_OOP Parallel device signaled that it is out of paper.
0x8000 CE_MODE Requested mode is not supported, or the idComDev parameter is invalid. If set, CE_MODE is the only valid error.
To use this table, take the error number and disect it into its error components. Fo
r example, if Serial Port Write.vi returns the error 16,408, then the errors returned are CE_BREAK and CE_FRAME (16,408 = 16,384 + 16 + 8 = 0x4000 + 0x0010 + 0x0008).
greetings from the Netherlands

Error 1073807253

Hi guys!
I´m back with another question. When I try too recieve my my signal in the waveform chart a get an error It says: "Error 1073807253 occured at VISA Read in Basic Serial Write and Read.vi Possible reason(s): VISA: (HEX 0xBFFF006B) A framing error occurred during transfer". I recieve the signal but every now ang then this messeage comes up. I read from the serial port. I´m using the example "Basic serial Write and Read" from "Hardware Input and Output". I´ve tried to put a flush buffer in this example after the Visa configuaration but this won´t help. And I´ve already checked that the configuaration (baud rate, stop bit, flow controll etc) is matched I hope someone can help me.
Thanks

Hi again...I send you the code and give you a picture of the front panel...
Thank you for your time!
Attachments:
Error_picture.JPG ‏138 KB
Basic Serial Write and Read1.vi ‏64 KB

Serial Communication Error -1073807253

Hello!
I'm trying to make a simple serial port reader VI and i can't get over this:
Error -1073807253 occurred at VISA Read in communication.vi
Possible reason(s):
VISA: (Hex 0xBFFF006B) A framing error occurred during transfer.
I'm pretty shure that the device sending a data works properly and the parameteres like a boud rate, parity etc. are set correctly because I've already communicate with that device via Matlab.
Although I've noticed that somebody here have the problem with this error, but I can't find any solution for me.
There is a picture of my simple VI diagram in Attachments. The parameters of the communication are set at the beginnig, after that and a litle delay the input buffer is flushed, then the loop starts. When the buffer contain nine or more bytes this bytes are readen.
Please, can anybody tell me what I'm doing wrong?
Thanks
Attachments:
VI-rs232-trouble.jpg ‏106 KB

chikvadrat wrote:
The VI works well after launch. It also read first 9 character correctly, but after that it crashs.
So what happens if by the time the loops comes back around, you have 10 bytes waiting for you at the port?
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

Error code:-1967362023(0x8abc 7019)

Hi everyone,
When I run the VILogger software using a NIPCI6221 and a CB-68LPR terminal block appears the following error:
Engine Error!
Error code = -1967362023(0x8abc 7019)
Description=Error -19637362023 ocurred at an unidentified location.
Possible reason (s):
Windows GetCommError: the hex value of this code is x4000
Interpret it bit-wise as follows:
x4000:serial port VI error
x0001:receiving queu overflowed or character was received after end-of-file character
x:0002:character was lost by overwrite
x0004arity error
x0008:framing error
x0010:break condition
x0020:CTS timeout
x0040SR timeout
x0080:RLSD timeout
x01000:Transmission queue was full when new character arrived
x:0200: parallel device timeout
x:0400arallel device I/O error
x0800arallel device not selected
x1000: parallel device out of paper
x8000:requested mode is not supported or the idComDev parameter is invalid
The terminal configuration used is Signal NRSE
The signal Input range is: Max 10V, Min -10V
Please, if anyone knows the error and can suggest me what to do, it will be appreciated
Thanks
Luis

Hi,
You probably do not have access to the database for VI Logger. Follow these steps to get access to the database.
Most users won't have write access to this folder. You need to enable
write access to this folder for all users. To do this, follow the
following steps:
Open a Windows Explorer window and select the menu Tools»Folder Options
Check the last option called Use Simple File Sharing as the following image.
Find the database folder. If you cannot find it, you might need to show the hidden folders.
Right click over the folder and select Sharing and Security. On the Security tab add the user(s) you would like to have access to the database.
Make sure you check Full Access to the user. The following image is an example.
Also, for the error that you are getting, you might want to create a new database and see if that helps as well.
All of this information is given in the following document.
Why Do I Get "Engine Error!" in VI Logger When Logged in as a Different User?
That should solve your problem.
Best regards,
Raajit L
National Instruments

Framing error

Similar Messages

Maybe you are looking for