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

Similar Messages

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

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

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

Visa Read Errors

Hey, Im using a Model 81000 ultrasonic anemometer and Im having a few problems with visa errors. I have it running at 38400 baud rate, which is what it should be running at. Ive run it in hyperterminal and it works fine.
The problem Im mainly getting is that when I run it, sometimes it starts with a random sybol or character, and then it stops running and tells me I have a framing error. Sometimes as well, when I start it, nothing happens at all, and then after a lttle wait, it says I have a timeout error. Another error I sometimes get is the string that comes in is separated and placed on to 2 separate lines which I cannot work with. About half of the time it works fine, but for the other half im getting these errors.
When running fine, it should read one line of data which works out to 35 bytes. I have the anemometer running at 32 lines of data per second, so I changed the delay to give me just one line so that I can break up the string into various tokens, which I then save to a file.
Any help would be greatly appreciated.
Attachments:
Serial Read.vi ‏72 KB
Retrieve Token String.vi ‏8 KB
Channel Name.vi ‏36 KB

You've indicated you have two different problems. One is the timeout error. Since you've disabled termination character recognition on reads you need to specify the correct number of bytes to read. The previous suggestion is the correct approach. You will need to use a shift register to carry around what's been read so far, and when you actually have 35 characters then you can do whatever it is you need to do.
The other problem is the framing error. Framing errors are generated by the UART on your motherboard. Thus, it's hardware-related. A typical cause is a mismatch in baud rate or other serial port configuration. Another cause is a bad cable or noise on the line. Do a search on framing errors and you'll come across a lot of hits.

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.

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 close error

Hello,
I use simultaneously the attached 3 VIs. Each of them is a PID loop, reading data from some Keithleys, and driving the loops using Keithley 2400 sourcemeters. So there are 3 2400 sourcemeters in my project. The data communication is via GPIB (NI HI-USB GPIB controller)
I use the official VISA drivers for the Keithley 2400s (some minor modifications in the "configure output" VI, I use double precision instead of single precision as in the official driver).
Everything works perfect, the three VIs run parallel, no communication error, so all is good.
But, randomly, lets say 50 percent of the time, when I want to shut down only one of the VIs, I get the VISA Close error in the error output.
Here is a screenshot when I get this error: http://dl.dropbox.com/u/8148153/Untitled.jpg
What can cause this such a error? The same VISA drivers are not allowed to be used parallel?
Thanks for help!
Attachments:
waterloop1.vi ‏34 KB
Base_loop_coarse.vi ‏34 KB
Base_loop_fine.vi ‏35 KB

Hello,
The Automatically close VISA sessions is unchecked (i think it is also the default state). So this cannot cause the experienced problem. So far this problem is not that serious, since I am at just the prototyping phase in my project (that is why i run the 3 VIs separated), the final MAIN VI will close all the VISA resources at once at shut down.
But I like to learn, so i am still curious about what this strange problem with VISA...
Regards,

Storage VIs internal error, TDMS file

I use LabView 8.5.1, DAQmx 9.0.2. and a module NI-USB6216.
I configure on my application a task as follows: 15 channels activated with a sample rate of 1sample/10s (very slow). My acquisition has to run for a few days or more.
Sometimes, I obtain the error "Storage VIs internal" error (code -2500). then I cannot read my TDMS file (see attached the file) and I cannot treat my data.
Do you know the exact meaning of this error on the case of a TDMS file. Do yo have a solution to treat my data?
Best regards, Daniel.
Solved!
Go to Solution.
Attachments:
Data.zip ‏436 KB

I tried with LabVIEW 2010 and didn't see the problem when reading your attached TDMS file.
Please download the latest TDMS installer from here:
http://zone.ni.com/devzone/cda/tut/p/id/9995
Please backup tdms.dll on your computer like in c:\program files\national instruments\shared\tdms\ and then run the installer.

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.

Old visa open, error code 1073807343, using VISA with a GPIB device, and VISA resource names

Hi everyone,
I'm trying to get a SRS model SR720 LCR meter (manual on this page) working with LabView, connecting it to my PC with an Agilent 82357A GPIB/USB interface (manual on this page). I'm running MAX version 14.0, and NI-VISA version 14.0. I'm running LabView version 13.0f2, 32 bit.
I followed the directions on this page, and I'm pretty confident I can communicate with my LCR meter, because I can go to NI MAX->GPIB0::17::INSTR under "devices and interfaces", then go to the VISA test panel, go to the I/O tab, and I can enter a few commands from the SR720 manual, like changing the frequency, and I see the light on the LCR meter change to what I just told it to do. Here is a picture, just to illustrate it:
Also, if I do the *IDN? command, it returns "
9: Write Operation (*IDN?)
Return Count: 5 bytes
10: Read Operation
Return Count: 41 bytes
StanfordResearchSystems,SR720,08087,1.03\n
So, that's good too. I also made the alias of this device "MyLCRmeter", but that shouldn't matter for now.
Now I'm trying to get it to work in a more usable way. The SR7xx drivers that LabView found for me came with a couple sample programs, one called "Getting Started.vi". I tried to just simply see if it worked, changing the "instrument descriptor" field to "GPIB0::17::INSTR", since that's the one that seemed to be the right device in MAX. Here is a picture of the front panel of "Getting Started.vi":
Trying to run it like this gave me this error (code -1073807343):
Old VISA Open in SR715/720 Initialize.vi->SR715/720 Getting Started.vi
Doing a bit of searching on these forums, I found these few threads (1 2 3), which seem to tell me that, since this program was written, the way you open VISA has changed. In the 2nd of those links, one guy said:
You just have to replace the Old VISA Open function with the VISA Open that is on the Instrument I/O>VISA>VISA Advanced palette. When you do that, the wire to the string that was used for the resource name will be broken. Delete the string and make the actual VISA Resource Name visible on the front panel. Wire the VISA Resource Name control to the connector pane where the string control was (upper left connection).
So, I went into the sub-VI Initialize.vi, and did that. Here is a picture of what the front panel and block diagram of the sub-VI Initialize2.vi (I changed the name in case I screwed things up, but I'm pretty sure the new one is the one being called by Getting Started.vi) looked like before I changed anything (you can see the Old VISA Open):
and here it is after replacing that with the regular VISA Open, deleting the instrument descriptor string and replacing it with a VISA resource, and connecting that to the VISA Open:
However, as you can see in the image above, and it seems like someone else had this problem in the 2nd thread linked above, I don't see my device listed in the drop-down menu (even if I refresh), only "LPT1" (I don't even know what that is):
No, I wasnt able to select the visa resource from the pull down menu. somehow it seems disabled or something.
If I just enter the VISA resource name from MAX manually, GPIB0::17::INSTR, and save and try running that, I get the error(code -1073807346):
VISA Open in SR715/720 Initialize2.vi->SR715/720 Getting Started.vi
So I'm not sure where to go from there, or why it's not in the drop down menu to begin with. I'm sorry if I've missed something but I've searched about as far as I can go. If I had to guess, maybe one thing could be that in MAX, under Tools->NI-VISA->VISA Options->My System->Conflict manager, I have both Agilent VISA and NI VISA enabled; I know sometimes problems arise from conflicts between different software fighting over the same hardware. Is this okay, or do I need to change it?
Thank you and please let me know if there is any other code/screenshots I could provide that could help!

Hi, I did indeed enable NiVisaTulip.dll under MAX->Tools->NI-VISA->VISA Options->My system->Passports->List of passports. Sorry, I should have mentioned that explicitly.
By install as primary, do you just mean as it is here, where it is selected as the "Preferred VISA"?
Or somewhere else? I installed NI-VISA first I believe, and then the Agilent one, and during the installation of the Agilent one, I'm pretty sure I made it not the primary. Here's what I have in the Agilent (it's called Keysight now) Connection Expert software:
I also have this under the "Keysight 488 options" tab:
Should that be checked? I don't actually know the role of VISA vs 488 here...
What could I try?
Thank you!

Standard report vis fail (error 1) after report toolkit loaded

Labview 6.1 report vis will not work (when dealing with standard report types) after loading the report generation toolkit 1.0.1. This is depite fixing the known issues found in the knowledge base. ie replace automation open with automation close in font style vi and recompiling the vis.
Running the text report example.vi included demonstrates the problem. Error 1 will be returned.
A sub vi in this called tables.vi appears to have 4 automation close vis two of which are inside for loops. I think these need to be outside of the loops? This then transfers the problem to the set font.vi which then returns error 1.

I have the same problem. I am using LabVIEW 6.1 and Microsoft Office 97. I have installed and reinstalled the Toolkit. Whenever I try to run ANY sample VI's that come with the toolkit (by going to "FIND EXAMPLES"), none of them run. The ERROR LIST says that none of the subVI's are found. Why are these subVI's not being found? I see that they are there. Is there a directory error? Both LabVIEW and the Toolkit were installed in their default directories. The Toolkit is in C:\Program Files\National Instruments\LabVIEW 6.1\vi.lib\addons\_office
Advice Please?! I have a sample screenshot.
Attachments:
screenshot.jpg ‏72 KB

VISA Write Error when using loop Err 1073807339

My program requires that I 'Start' my VISA device, poll it every second 10 times without clearing the device buffer. It is a counter and we are trying to accumulate counts over a 10 second period.
I first initialize the device with the 'Sart' command then try to get data.
For some reason the vi consistently runs successfully only 9 times and generates an error on the 10th run.
I guess the simple answer would be 'Why don't you just take 9 samples for your data?' I'm hoping there is a better explanation so that I can do it properly.
Attachments:
VISA_loop.png ‏68 KB
VISA_loop.vi ‏26 KB
Ortec Start2.vi ‏29 KB

The time out error on the VISA write to a GPIB device could be that the device did not ACK that it read the message.
On a quick look at your code, it first looked like you are sending \n at the end of your command, but you did not set the display mode of the Combo Box to "\' Code Display. So in fact what you are sending is SHOW_COUNTS follow by the "\" follow by the letter "n" and not a line feed.
How does your device handle the text "\n" at the end of the commands?
Does your device responed to the "System Error" command or the *STB command to see if it is setting an error flag?
Is it a SCPI device?
Most SCPI devices will hold up to 10 errors in it's system error buffer.
Just a guess without knowing much about your GPIB device.
Omar

VISA framing error BFFF0068

Similar Messages

Maybe you are looking for