This is the constructor of the serial interface connection.
serialConnection(name, port = "com1", mode = "115200,n,8,1",
buffering = "none", newline = 0, eof = "", translation = "lf",
handshake = "none")optional name for the connection
comport name; also virtual com's are supported; maybe USB schould work too
communication mode "<BAUD>, <PARITY>, <DATABITS>, <STOPBITS>"
BAUDsets the baud rate (bits per second)
PARITYn, o, e, m, s stands for "none", "odd", "even", "mark" and "space"
DATABITSinteger number of data bits. The value can range from 5 to 8
STOPBITSinteger number of stop bits. This can be "1" or "2"
"none", for RS232 serial interface, other modes don't work in this case
<BOOL>, whether a new transmission starts with a newline or not.
TRUE or 1send newline-char according to <translation> befor transmitting
FALSE or 0no newline
<CHAR>, termination char of the datastream. It only makes sense
if <translation> is 'binary' and the stream is a file
each transmitted string is terminated by the transmission character. This could be 'lf', 'cr', 'crlf', 'binary'
determines the type of handshaking the communication
none"no handshake is done
rtscts"hardware handshake is enabled
xonxoff"software handshake via extra characters is enabled
An object of the class "serialConnection" is returned
Linux and Windows behave a little bit different, when utilizing serial com ports. Still, by providing the name (like "COM1" or "ttyS1") and the appropriate settings, the serial interface can be used. Even virtual com ports, like the FTDI usb uart chips will work, as long they map to a standard serial interface in the system.