Sierra Wireless 300 manual Control Lines, Rts/Cts

DART 300 Migration Guide Difference Summary

3.1.2.Control Lines

The DART 300 does not allow configuration of the DCD and DSR signals; a feature supported in the DART 200.

Flow control on the DART 300 is through hardware only via RTS/CTS and DTR.

	DART 200	DART 300
RTS/CTS	Hardware and software flow	Hardware flow control only.
	control both supported via AT	RTS must be asserted to allow
	command.
		serial communication from the
	Only active in online mode.	DART 300 to the host.
		DTR must also be asserted to
		allow received data state traffic to
		flow to the host.
DCD	Configurable to track CDPD	Asserted while online with an
	registration state, link established,	active session. Not configurable.
	or connection established
DSR	Configurable to track CDPD	Always on when the modem is
	registration state, link established,	powered up. Not configurable.
	or connection established
DTR	Supports &D0, and host activated	&D0 ignores DTR transitions1.
	escape via &D1, and &D2.	&D1 enters command state
	Hardware debounce is 15μs.
		without changing on/off-line
		condition.
		&D2 hangs up and enters
		command state with auto-answer
		disabled.
		Software polling used to
		determine state. No debounce.
		DTR must be asserted to allow
		received data to flow to the host.
RI	Not supported.	Triggered on UDP/TCP mode
		connection requests.
		Configurable operation in
		SLIP/PPP modes.

1The DART 300 using the &D0 setting still requires DTR to be asserted in order to pass received data to the local host.

2110291 Rev 1.0 Page 11