serial-communication

I am sending commands over a serial port from a Linux embedded device to some serial enabled firmware. For easy debugging and simplicity we are using ascii human-readable commands terminated by newlines. Is it appropriate to use canonical mode here, or is canonical mode usually reserved for interactive terminals? The examples I find online all use raw mode. In particular, in canonical mode, how do I check without blocking if an entire line is available for reading. according to Linux Serial Programming documentation : This is the normal processing mode for terminals, but can also be useful for

I am using SerialPort class to communicate with an external device. I start the communication at 300 Baud per second however after the initial "handshake" I have to switch to a Baud rate specified by the device (usually 9600 Bps). I have been unsuccessful in my attempts to continue communicating after I increase Baud rate however I am not sure why. That leads me to my question: What is the proper way of changing the Baud rate? Can it be done while the connection is open, or should I close the connection first? I have been unable to find any information about this in the documentation... I have

I'm trying to write a C++ MFC application that uses the serial port (e.g. COM8). Every time I try to set the DCB it fails. If someone can point out what I'm doing wrong, I'd really appreciate it. DCB dcb = {0}; dcb.DCBlength = sizeof(DCB); port.Insert( 0, L"\\\\.\\" ); m_hComm = CreateFile( port, // Virtual COM port GENERIC_READ | GENERIC_WRITE, // Access: Read and write 0, // Share: No sharing NULL, // Security: None OPEN_EXISTING, // The COM port already exists. FILE_FLAG_OVERLAPPED, // Asynchronous I/O. NULL // No template file for COM port. ); if ( m_hComm == INVALID_HANDLE_VALUE ) { TRACE

In a serial communication link, what is the prefered framing/sync method? framing with SOF and escaping sequences, like in HDLC? relying on using a header with length info and CRC? It's an embedded system using DMA transfers of data from UART to memory. I think the framing method with SOF is most attractive, but maybe the other one is good enough? Does anyone has pros and cons for these two methods? Following based on UART serial experience, not research. I have found fewer communication issues when the following are included - or in other words, do both SOF/EOF and (length - maybe)/checkcode.

I am really having hard time understanding the difference. Some say they are same, while others say there is a slight difference. What's the difference, exactly? I would like it if you explained with some analogy. Bits per second is straightforward. It is exactly what it sounds like. If I have 1000 bits and am sending them at 1000 bps, it will take exactly one second to transmit them. Baud is symbols per second. If these symbols — the indivisible elements of your data encoding — are not bits, the baud rate will be lower than the bit rate by the factor of bits per symbol. That is, if there are

If I use the Arduino IDE's Serial monitor I can read the pair of comma separated values as below: I want to first replicate this behavior in SciLab terminal. I used the Serial Communication Toolbox : h = openserial(7, "9600,n,8,1") // open COM7 disp(readserial(h)) closeserial(h) which returns either empty or , 169 228, 179 228, 228, 205 228, 209 228, putting the disp(readserial(h)) in a while loop also doesn't help. Not only there are too many empty lines, if I stop the while loop it does not close the port (something like try-catch should be used I think). I would appreciate if you could help