Porovnávané verzie

Kľúč

  • Tento riadok sa pridal
  • Riadok je odstránený.
  • Formátovanie sa zmenilo.

...

Note: if the D2000 KOM process is running on a Linux/Raspberry PI platform, you must enter the Device parameter value as a full path to the device that corresponds to the serial port (eg /dev/ttyAMA0 or /dev/ttyS0, or /dev/ttyUSB0 for the Serial2USB converter).

Parameters

Baud rate
Setting of the line baud rate. Valid values: 110, 150, 300, 600, 1200, 2400, 4800, 9600, 19200, 38400.
Number of bits
A number of data bits. Valid values: 5, 6, 7, 8.
Number of stop bits
A number of stop bits. Valid values: 1, 1.5, 2.
Illegal combinations:
5 data bits and 2 stop bits,
6, 7, or 8 data bits and 1.5 stop bit.

...

Configuration of handshaking on the level of Windows driver level.

  • None
  • RTS/CTS - hardware handshake
  • XON/XOFF - software handshake
  • Custom - own configuration of the handshake

None
It allows the setting of RTS , and DTR signals to required permanent values.

RTS/CTS
RTS signal is used for the standard hardware handshake controlled directly by the serial asynchronous port driver. It allows setting a permanent value of the DTR signal.

XON/XOFF
Software XON/XOFF handshaking is controlled directly by the serial asynchronous port driver.

Custom
At transmissionWhen transmitting, RTS and DTR signals may be controlled by by Receive Delay and Transmit Delay time parameters. Own setting of the handshaking is suitable to use The custom handshaking setting is useful for RS232/485 converters controlled by these signals.

...

DTR/DSR
Custom mode sets DTR as the active signal for the handshaking control.

RTS/CTS
Custom mode sets RTS as the active signal for the handshaking control.

Inverse
For the handshaking of Custom type, controlled signals RTS or DTR are inverted.

RTS=0 (RTS=1)
It sets a constant RTS signal level in case that is not actively used by the selected handshaking type.

DTR=0 (DTR=1)
It sets a constant DTR signal level in case that is not actively used by the selected handshaking type.

WaitTxEMPTY
If the option is enabled, the communication thread is waiting for the transmission to end. The option enables the synchronization of RTS or DTR signal control at the end of the transmission (see Receive delay) in case of the handshake of Custom type. As the standard serial drivers of Windows operating systems allow to get information only about the transmission of the last byte into the transmission shift register of the UART device (but not physically sent out), then in the case of this option, there is 1 character with 0xFF value added to the end of the transmitted message. At the moment of transmission indication of this character into the transmit register, the inherent message is sent out safely, and the Receive delay (if nonzero) is starting starts to tick. See also Note.

Transmit delay
Delay (in milliseconds), that is inserted between the RTS signal setting (Custom handshaking RTS/CTS) or DTR signal setting (Custom handshaking DTR/DSR) and the beginning of message transmission.

Receive delay
Delay (in milliseconds), that is inserted from the end of the transmission to the deactivation of the RTS signal (Custom handshaking RTS/CTS) or DTR signal (Custom handshaking DTR/DSR). For the real starting of this delay at the moment of the transmission end, it is necessary to use the WaitTxEMPTY option.

...

ConstOpen
If the option is enabled, then the communication port of the line is permanently opened, otherwise, the port is used only in case of need. The option allows sharing ports with other applications.

CheckError
If the option is enabled, the communication error check will be executed - Parity, Frame, Overrun, Break Error.

Ballast
A number of empty unimportant characters (with 0x00 value) , which that are inserted before the transmitted message. It is advantageous when controlling modems/radiomodems radio modems or converters controlled by their own data signal. See also Note.

Note: Ballast and WaitTxEMPTY options insert special characters before (or behind) the transferred message, which may disable the communication with devices. Further information can be found in the documentation for individual individual communication protocols that communicate via asynchronous serial ports.

...