12-18-2014 12:49 AM
1. I have a microcontroller board sedind data tp FT232R(usb uart IC) which then forms a COM port on PC to commnicate with labview serial visa.
2. I am able to communicate with standard baud rates with any problem like 9600 or 38400 bps.
3. I want to know can I can communicate wit non-standard baud rates like 500Kbps with labview also???
12-18-2014 01:04 AM
12-18-2014 01:11 AM
12-18-2014 01:11 AM
1. As I had told I have custom microcontroller board which set the baud rate.
2. I want to know if I send data from non standard baud rate from microcontroller baud to PC, will labview be able to receive them correcly.
because hyperterminal don't give any option to set non standard baud rate?
12-18-2014 01:14 AM
12-18-2014
11:36 AM
- last edited on
03-25-2025
10:31 AM
by
Content Cleaner
LabVIEW supports this card which supports any integer baud rate from 2 to 1,000,000 baud
12-18-2014 11:51 PM
What is the device model number? Can you post a link to the manual?
Dennis, you missed something here- I do not often even attempt to correct you.
VISA baud rates are variable by integer values.- not enums!
the FTDI chip sets baud rates are often are negotiable, the firmware on the other end.....:,) is often not.
You are absoloutly correct to request the manual!
@the OP what is the device? Have you read the manual?
12-19-2014 01:41 AM
12-19-2014 10:32 AM - edited 12-19-2014 10:34 AM
@Dennis_Knutson wrote:
Where did I say that the VISA baud rate is an enum?
My Bad - I wasn't paying attention! No wonder I seldom attempt to correct you!
So lets talk about serial baud rates. LabVIEW does not have anything to do with it other than implement calls to the VISA API- VISA not LabVIEW handles serial communications.
VISA does not limit serial baud rate to anything other than "a positive non zero integer "(Actually a 0 baud rate just garuntees a timeout error and is silly, negative baud rates are sillier still- think about it for a moment)
Most hardware today detects the clock rate of the incomming TX and adapts baud properly.
Some legacy devices exist that were designed prior to the advent of clock recovery. These are mostly obsolete and should be considered for replacement.
Some modern hardware that could support clock recovery has firmware developed without support for the feature either for "optimization" (it may be run from an underpowered CPU) or because the developer has been copy-pasting that same #include for decades. Those firmware engineers are also mostly obsolete and IMHO should be considered for replacement.
All that being said 500K baud is not inconcievable- but, you better watch out for noise in your cabling and inside the hardware too! including the COM port of the PC!