Motorola V.34-SDC, and V.32bis, 326X V.34 manual Fast Call=Off AT*FC0 in it

326X Series Modem Troubleshooting Guide (Continued)

Problem	Diagnosis/Test	Possible Solution
	Check whether modem is set for	If your DTE cannot handle Tx clock stopping, set
	Flow=Tx Clk (AT*FL5).	Flow=Off (AT*FL0) or use CTS flow control.
	Check if TpDlyMin=Rx Clk	If your DTE equipment cannot handle Rx clock stopping,
	(AT*TD1).	set TpDlyMin=Off (AT*TD0) or set TpDlyMin=RxD
		Dly (AT*TD2).
	If both modems are 326X-SDC,	If the option sets are not the same, select the same option
	check to ensure option sets are	sets in both modems using Select Options (ATZ) com-
	the same in both modems.	mand.
	Check if one of your modems	If the local or remote modem is a 326X-SDC modem, set
	(local or remote) is a 326X-SDC	Fast Call=Off (AT*FC0) in it.
	unit.
Poor throughput	Check your applications proto-
performance	col:
	• If a window size of one is	Increase window size.
	used (half duplex proto-
	col)...

Troubleshooting

• If using Novell IPX...

Check whether TpDlyMin=Off (AT*TD0) or TpD- lyMin=RxD Dly (AT*TD2).

Check if modem is set for Flow=Off (AT*FL0).

If performance is not satisfac- tory, experiment with frame and window sizes.

If link utilization is low

(as shown in the front panel throughput and link utilization status display)...

Ensure burst mode is selected.

If your DTE can handle Rx clock stopping, set TpDlyMin=Rx Clk.

If your DTE can handle Tx clock stopping, set Flow=Tx Clk (AT*FL5). If it does not support Tx clock stopping, use CTS.

The optimum frame size for most applications is between 128 and 1024 bytes.

The optimum window size for most applications is 7 to 4.

Increase the DTE rate.

Poor throughput delay Check the setting of the flow	Use Tx clock or CTS for flow control and Rx clock for
control option.	throughput minimization delay.

6-8 Troubleshooting Guide