Instrument Control (GPIB, Serial, VISA, IVI)
overrun error when using multiple serial ports
Hi
I tried to understand your program and I advise to study how LabVIEW parallel programming really works.
You add sequence frames all over the place to prevent parallellisme where simply connecting error wires already do the job.
Overrun means that your input buffer fills up more quickly than you are reading from it.
I stopped at analyzing your program also because my screen is "only" 1280 by 800 pixels and your program is a bit too big for this screen.
try to read from the serial line as fast as possible and do that for both serial ports and eventually buffer the data yourself.
but first make your program mor readable by wiring neatly and proably you see what is what faster.
I tried to understand your program and I advise to study how LabVIEW parallel programming really works.
You add sequence frames all over the place to prevent parallellisme where simply connecting error wires already do the job.
Overrun means that your input buffer fills up more quickly than you are reading from it.
I stopped at analyzing your program also because my screen is "only" 1280 by 800 pixels and your program is a bit too big for this screen.
try to read from the serial line as fast as possible and do that for both serial ports and eventually buffer the data yourself.
but first make your program mor readable by wiring neatly and proably you see what is what faster.
In short, read the manual about parallellism in LabVIEw.
Even simpler though, all items that are not connected by wires (the wire dictates execution order) CAN run in parallel.
Can, because it depends on your system, the compiler, the hardware etc.
On a dual core pc some will run in parallel and in quad core, even more will run in parallel.
good luck, parallel processing in LabVIEW is so simple that above rules are enough.
Even simpler though, all items that are not connected by wires (the wire dictates execution order) CAN run in parallel.
Can, because it depends on your system, the compiler, the hardware etc.
On a dual core pc some will run in parallel and in quad core, even more will run in parallel.
good luck, parallel processing in LabVIEW is so simple that above rules are enough.
your baudrate is the speed on the serial line and overrun occcurs in your pc
your simply not reading fast enough and taking the highes possible baudrate makes it worse.
In your main vi you need two loops (running in parallel)
in one read reaad all seril ports one by one and dump the data in an action engine (see link below on action engines)
http://forums.ni.com/ni/board/message?board.id=170&message.id=240328
In the other loop read from the action engine and process the data.
good luck
your simply not reading fast enough and taking the highes possible baudrate makes it worse.
In your main vi you need two loops (running in parallel)
in one read reaad all seril ports one by one and dump the data in an action engine (see link below on action engines)
http://forums.ni.com/ni/board/message?board.id=170&message.id=240328
In the other loop read from the action engine and process the data.
good luck
I'll do my best but reading and trying action engines is possible for yourself.
Just draw what happens.
The trick is the uninitialised shiftregister that keeps information over calls.
try with a simple vi with just a while and an uninitialised shiftregister and a case statement with in each case an action.
and see what happens.
Just draw what happens.
The trick is the uninitialised shiftregister that keeps information over calls.
try with a simple vi with just a while and an uninitialised shiftregister and a case statement with in each case an action.
and see what happens.
Hi Toni
Here is an example of an extreme sinple action engine.
It does not solve your overrun problem but structures your code.
One of the essential problems you had was a bad error handling.
Now the program stops on an error and shows you this in error out
One of the things you can do in the serial read to overcome overrun is to check how many bytes are available and read them all in one string.
the main vi is "more serial lines.vi"
Here is an example of an extreme sinple action engine.
It does not solve your overrun problem but structures your code.
One of the essential problems you had was a bad error handling.
Now the program stops on an error and shows you this in error out
One of the things you can do in the serial read to overcome overrun is to check how many bytes are available and read them all in one string.
the main vi is "more serial lines.vi"
