Professional Documents
Culture Documents
Tier 4 Guide Revise
Tier 4 Guide Revise
The communications driver can be customized by the user or support engineer to fix a particular hardware
or setup problem that may be encountered. This is done with the use of Registry settings. These settings
are read when the comms driver starts, and when the main communications settings are changed. To edit
a setting, the main comms driver registry key needs to be created, and the setting that you want to alter
needs to have an element created
for it with the correct name (as described below), and be of type DWORD. You then set the value of the
entry to the value that you want the driver to use. To return to the default value, simply delete the
element.
The following is the main registry key for the comms driver. If it doesn't exist, then you need to create it,
taking care to NAME IT EXACTLY AS STATED HERE. Once the key is in place, you can add the
appropriate elements.
"HKEY_LOCAL_MACHINE\\SOFTWARE\\TechnologLtd\\PMACPlus\\CommsHandler"
Here are the elements that you can add to alter the behaviour of the driver. The programmed default
valued are also noted.
Timeouts
"CRCRxInterCharTimeout"
This sets the maximum time that the driver waits between characters in a E5565 protocol packet. Default: 1650ms.
"NONCRCRxInterCharTimeout"
This sets the maximum time that the driver waits between characters in a packet that is neither E5565 or Technolog
protocol. Default: 440ms.
"ChecksumRxInterCharTimeout"
This sets the maximum time that the driver waits between characters in a Technolog protocol packet. Default:
1980ms.
"NetworkResponseTime"
This is a value that is used in packet timeout calculations. It represents an estimate of the transmition delay.
Default: 6050ms
"AlarmAnswerTimeout"
This sets the maximum time that the driver waits for a packet from the logger after the modems have connected for
an alarm. Default: 15015ms.
"ModemRecover"
This sets the maximum time that the driver waits for the modem to recover itself after sending "ATH0" to
disconnect. Default: 1980ms.
"RemoteDialTimeout"
This sets the maximum time that the driver waits for a packet from the logger after the modems have connected
during a dial-out. Default: 60060ms.
"X28DialTimeout"
This sets the maximum time that the driver waits for a packet from the logger after the X.25 PAD's have connected
during an X.28 dial-out. Default: 60060ms.
"X28TalkTimeout"
This sets the maximum time that the driver waits between characters in an X.28 (neither E5565 or Technolog
protocol) packet. Default: 28160ms.
"TotalKeepAwakeTime"
This is the time that the driver keeps a remote connection on-line before timing out due to inactivity. Default:
60000ms.
"KeepAwakePeriod"
This is the interval that the driver waits between checks for activity. Default: 10000ms.
"AlarmSetupTimeout"
This sets the timeout that the driver uses when sending the alarm setup string to the modem. Default: 1000ms.
Retries
"LocalCRCRetry"
This sets the maximum number of packet send retrys for a local connection. Default: 3.
"RemoteRetry"
This sets the maximum number of packet send retrys for a modem connection. Default: 6.
"X28Retry"
This sets the maximum number of packet send retrys for a X.28 connection. Default: 6.
"UpdateModemSetup"
This tells the driver whether to send the modem setup string every time the modem is used, or just once the first
time. Default: 1(ON). (0 = OFF, 1 = ON)
"DisconnectBackoff"
This is the interval that the driver waits between '+''s when disconnecting if the preceding option is active. Default:
1000ms.
"AlarmSetupVerify"
This tells the driver if it should check the return (or otherwise) from the alarm modem setup string. Setting this
option to 'ON' will let the driver alert the user of modem setup problems and suggest corrective action. Default:
1(ON). (0=OFF, 1=ON)
DCD Control
"CheckDCDTime"
This is the overall time the driver waits while it is checking the modem DCD, to eliminate the effects of modems
that 'bounce' the DCD line. Default: 1000ms.
“IgnoreDCD” (Version 3.37 and later)
This tells the communications driver to not check the status of DCD. This is for modems that do not support the
carrier detect feature. The driver assumes that the carrier is in the expected state for the current comms procedure.
Default: 0 (Don’t ignore). (0=OFF, 1 = ON)
Workarounds
General Setup