com.esf.device.serial.comm.service

Class SerialMode

java.lang.Object

com.esf.device.serial.comm.service.SerialMode

public class SerialMode
extends java.lang.Object

This static class provides the available operating modes.

Modes listed in this class are used for parameter checking in all methods where the operating mode may be modified. Not all modes are supported by all devices, half-duplex modes are only supported by acscomm devices.

Author:

matt.demaree

Field Summary

Fields

Modifier and Type	Field and Description
static int	FullDuplexHandshake Forces DTR active and cycles RTS with TX and holds of TX if CTS not active.
static int	FullDuplexNoHandshake Ignores DSR, DCD and CTS.
static int	HalfDuplexHandshake For acscomm devices: forces DTR active and RTS active during TX.
static int	HalfDuplexNoHandshake For acscomm devices: forces RTS and DTR active and operates in half duplex mode.
static int	HalfDuplexRtsExtended For acscomm devices: forces DTR active and RTS extended active during TX.

Method Summary

Methods inherited from class java.lang.Object

equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

FullDuplexNoHandshake

public static final int FullDuplexNoHandshake

Ignores DSR, DCD and CTS. For acscomm devices, this mode forces DTR and RTS active; the same cannot be guaranteed for other devices, refer to OS documentation for the particular device being used.

See Also:

Constant Field Values

HalfDuplexNoHandshake

public static final int HalfDuplexNoHandshake

For acscomm devices: forces RTS and DTR active and operates in half duplex mode. This mode is not available on devices other than acscomm devices.

Note This mode is a true half duplex mode, reception is blocked during transmission, so data is not just thrown away or held in a buffer, it is actually not seen. Further, if data is coming in at the end of transmission, it may cause invalid data to be received for multiple bytes as the receiver attempts to syncronize with the incoming data.

See Also:

Constant Field Values

FullDuplexHandshake

public static final int FullDuplexHandshake

Forces DTR active and cycles RTS with TX and holds of TX if CTS not active. Data may be received at any time without regard for the RTS/CTS signal states.

Note For acscomm devices only, the RTS signal is extended to ensure it is active for the final byte transmission and may be extended up to 1 millisecond beyond the end of the final stop bit. This extension is for compatibility with RS485 interfaces.

See Also:

Constant Field Values

HalfDuplexHandshake

public static final int HalfDuplexHandshake

For acscomm devices: forces DTR active and RTS active during TX. This mode is not available with device other than acscomm devices.

Note The RTS signal is extended to ensure it is active for the final byte transmission and may be extended up to 1 millisecond beyond the end of the final stop bit. This extension is for compatibility with RS485 interfaces.

Note This mode is a true half duplex mode, reception is blocked during transmission, so data is not just thrown away or held in a buffer, it is actually not seen. Further, if data is coming in at the end of transmission, it may cause invalid data to be received for multiple bytes as the receiver attempts to syncronize with the incoming data.

See Also:

Constant Field Values

HalfDuplexRtsExtended

public static final int HalfDuplexRtsExtended

For acscomm devices: forces DTR active and RTS extended active during TX. CTS is ignored. This mode is not available with devices other than acscomm devices.

Note The RTS signal may be extended both before TX with the warmUp value and after TX with the warmDown value. These values are set in milliseconds. The warmDown is timed after the end of the last stop bit of the last byte and may vary by 1 full millisecond.

Note This mode is a true half duplex mode, reception is blocked during transmission, so data is not just thrown away or held in a buffer, it is actually not seen. Further, if data is coming in at the end of transmission, it may cause invalid data to be received for multiple bytes as the receiver attempts to syncronize with the incoming data.

See Also:

Constant Field Values