The synchronous ports (SYNC)

[18:17:22] ABILIS_CPX: D P PO:1 

PO:1   ------------------------------------------------------------------------
SYNC   LOG:DS      int:V24     CLK:EXT        SP:19200     CODING:NRZ   MPX:NO      
       IDLE:FLAG   FDCD:500    FCTS:500       mode:FULL    RTSDLY:0     CD:NO     
       frame:2100  d-rxbuf:14  dma-rxbuf:10   dma-txbuf:1     

Usually this parameter makes possible to activate/deactivate logging functionalities of meaningful events of the port as well as the detection and signalling of alarms in case of critical events.

The following table shows the available options and the related functionalities usable by the parameter:

Option	Meaning
D	Recording of the driver state changes and/or the meaningful events in Debug Log
S	Recording of the driver state changes and/or the meaningful events in the System Log
A	Periodic detection of possible alarms. The detected alarms can be displayed the command ALARM VIEW or by the analogous command available on the UTILITY of the LCD display on the front panel
L	On alarm detection, acoustic signal generation plus a message on the LCD display. This function depends on activation of alarms detection by the "A" option
T	Generation by the Agent SNMP of Abilis CPX of SNMP traps corresponding to any change of the driver state and/or occurring of meaningful events

Beside the already described options the following values are also allowed:

Option	Meaning
NO	It means that all the logging functionalities, alarms detection and generation, above mentioned, are disabled.
ALL	It means that all the logging functionalities, alarms detection and generation, above mentioned, are enabled.
+E	This option added to one or more of the previous ones, extends its (their) set of meaningful events. The value "ALL+E" activates all the options and extends the set of meaningful events. The value "NO+E" is meaningless so it is ignored.

Options can be combined together.

Some examples:

• setting "LOG:DS+E", activates the extended logging functions for Events Log and System Log
• setting "LOG:STA", activates the extended logging functions for System Log, SNMP traps generation and periodic detection of alarm states;

By using the characters "+" and "-" as prefix of one or more options is possible to add or delete one or more functionalities without setting from the scratch the value of the parameters.

Some examples:

• Suppose the current value of the parameter is "LOG:DSTA", by setting "LOG:-A", the periodic detection of eventual alarm states is removed, leaving unchanged all the remaining options; in such way the final value of the parameter will be "LOG:DST";
• Suppose the current value of the parameter is "LOG:ST", by setting "LOG:+DA", the logging function of the events on the Events Log and the periodic alarm detection are added to the already activated options; in such way the final value of the parameter will be "LOG:DSTA".

The changes made on this parameter are immediately activated, without the need of initialization commands.

On a running CPX it specifies which interface module has been installed on the communication board, which is automatically detected at system startup.

In the Off-line configurator it just specifies the "expected" interface or the interface detected the last time the system ran.

V24 is equivalent to EIA RS232 and CCITT V24/V28 interfaces.

It sets the synchronism signal (clock) source, which is going to be used for data transmitting and receiving.

The ESB boards have less options than the HSCB ones.

This parameter has also relationship with the line coding type, configured in the parameter CODING:. The following table shows the available combinations between both parameters:

HSCB board

CODING value:	CLK value:	Source:
NRZ, NRZI, MAN, FM0, FM1	EXT	Tx and Rx clock must be supplied from the outside
NRZ, NRZI, MAN, FM0, FM1	INT	Tx and Rx clock are generated inside the board and supplied to the outside
NRZ, NRZI	SYM	Tx clock is generated inside the board and be supplied to the outside; Rx clock must be provided by external signal
MAN, FM0, FM1	PCLK	625 kbit/sec Tx and Rx clock are generated inside the board

ESB board

CODING value:	CLK value:	Source:
NRZ, NRZI	EXT	Tx and Rx clock must be supplied from the outside
NRZ, NRZI	INT	Tx and Rx clock are generated inside the board and supplied to the outside
NRZ, NRZI	SYM	Tx clock is generated inside the board and supplied to the outside; Rx clock must be provided by external signal

It sets the internal clock frequency. Refer to the parameter CLK: for its real use.

Binary coding, configurable in the parameter CODING:, also influences the speed. The following table shows the range of "SP" allowed values, according to the parameter "CODING:":

CODING value:	SP value:
NRZ, NRZI	2400 - 2500000 bit/sec
MAN, FM0, FM1	2400 - 156250 bit/sec

Important: if the speed is less than 19.200 bit/sec, SP value should be the same as the real speed, even in case of tx/rx external synchronism (CLK:EXT).

It allows to choose the desired binary coding.

The value "MAN" means the Manchester coding has been chosen, but it requires a suitable interface with a Manchester coder.

This parameter has relationship either with speed (parameter SP:) and the synchronism type (parameter CLK:). The following table shows the allowed combinations of the parameters:

CODING value:	SP value:	CLK value:
NRZ, NRZI	2400 - 2048000 bit/sec	EXT, INT, SIM
MAN, FM0, FM1	2400 - 156250 bit/sec	EXT, INT, PCLK

It allows to select how to manage the "Idle" state.

It sets the time interval necessary to detect the DCD signal state. It is checked every CPU tick (55 milliseconds c.a.) and, in order to avoid detection of useless fluctuations, it is considered valid only if constant during the time interval defined by the parameter.

It sets the time interval necessary to detect the CTS signal state. It is checked every CPU tick (55 milliseconds c.a.) and, in order to avoid detection of useless fluctuations, it is considered valid only if constant during the time interval defined by the parameter.

It sets the transmission/receiving mode.

Value	Meaning
FULL	Full duplex mode, the signal RTS is always active.
HDTE	Half duplex-DTE mode, the signal RTS is activated only when each frame has to be sent. The level 1 driver waits the CTS signal to start sending data.
HDCE	Half duplex-DCE, where, once the CTS is received, the RTS one must be activated after the time interval, defined RTSDLY is elapsed..

The parameter "MODE:" is used only to properly check the RTS signal. Actually, Level 1 driver is always able to work in Full duplex mode.

It sets the activation delay of the RTS signal in case of Half duplex-DCE operating mode.

It allows to check the signal DCD.

If it is set to "NO", the Level 1 state is "UP".

If it is set to "YES", the Level 1 state is directly depending on the signal DCD state.

It sets the maximum frame length, excluding Flags and CRC.

It sets the number of receiving buffers in use.

It sets the number of dma receive buffers in use.

It sets the number of transmission buffers in use.

It allows to activate the VOICE/DATA multiplexing.

[18:17:22] ABILIS_CPX: D S PO:1

PO:1   ------------------------------------------------------------------------
SYNC   STATE:UP          SP:19200          XTAL:X1-1,8MHz   CARD:ESB       
       DTR:UP            DCD:UP            RTS:UP           CTS:UP         
       ------------------------------------------------------------------------
       FIFO:USED         TXSIZE:2          RXSIZE:10       
       -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
       CHR        |1364250    |1364138    |FRM        |227367     |227368     |
       CHR-D      |7          |15         |FRM-D      |2          |5          |
       CHR-V      |0          |0          |FRM-V      |0          |0          |
       CHR-C      |1364243    |1364123    |FRM-C      |227365     |227363     |
       RX-OVR     |0          |           |TX-UND     |           |0          |
       BAD-FCS    |0          |           |ABORT      |0          |0          |
       SHORT      |0          |0          |OTHERS     |0          |           |
       LONG-D     |0          |0          |LOST-D     |0          |           |
       LONG-C     |0          |0          |LOST-C     |16         |           |
       LONG-V     |0          |0          |LOST-V     |0          |           |
       CTS-TOUT   |0          |           |
       ------------------------------------------------------------------------

[18:17:22] ABILIS_CPX: D SE PO:1

PO:1   ------------------------------------------------------------------------
SYNC   --- Cleared 003:21:49:21 ago, on 12/05/2000 at 12:11:40 ----------------
       -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
       CHR        |1364442    |1364330    |FRM        |227399     |227400     |
       CHR-D      |7          |15         |FRM-D      |2          |5          |
       CHR-V      |0          |0          |FRM-V      |0          |0          |
       CHR-C      |1364435    |1364315    |FRM-C      |227397     |227395     |
       RX-OVR     |0          |           |TX-UND     |           |0          |
       BAD-FCS    |0          |           |ABORT      |0          |0          |
       SHORT      |0          |0          |OTHERS     |0          |           |
       LONG-D     |0          |0          |LOST-D     |0          |           |
       LONG-C     |0          |0          |LOST-C     |16         |           |
       LONG-V     |0          |0          |LOST-V     |0          |           |
       CTS-TOUT   |0          |           |
       ------------------------------------------------------------------------

It reports the current state of the SYNC Level 1 driver.

Driver	States	Meaning	Values shown in:
			System Log	Events Log	LCD Display
SYNC	DOWN	The port is not active	dn
	UP	Level 1 is active	UP
	HALTED	The port is not working	HT
	ERR	Software error. Contact Abilis service.	NA

It reports the exact speed in use.
This is required because not all the values configured in SP: parameter can be precisely generated as internal clock, some rounding is applied and the exact speed is shown here.

It reports the xtal oscillator used to generate internal clocks, for informational purpose only.

It reports the card to which the port belongs.
The distinction between HSCB and ESB/ESB2 is due to the configuration, while the distinction between ESB and ESB2 depends on the card actually detected by the driver.

It reports the current state of the signal DTR.

Driver	States	Meaning	Values shown in:
			System Log	Events Log	LCD Display
SYNC (DTR signal)	DOWN	The signal DTR is not active	0	dn	0
	UP	The signal DTR is active	1	UP	1
	N/A	The signal state is not available.	2	NA	2

It reports the current state of the signal DCD.

Driver	States	Meaning	Values shown in:
			System Log	Events Log	LCD Display
SYNC (DCD signal)	DOWN	The signal DCD is not active	0	dn	0
	UP	The signal DCD is active	1	UP	1
	N/A	The signal state is not available.	2	NA	2

It reports the current state of the signal RTS.

Driver	States	Meaning	Values shown in:
			System Log	Events Log	LCD Display
SYNC (RTS signal)	DOWN	The signal RTS is not active
	UP	The signal RTS is active
	N/A	The signal state is not available.

It reports the current state of the signal CTS.

Driver	States	Meaning	Values shown in:
			System Log	Events Log	LCD Display
SYNC (CTS signal)	DOWN	The signal CTS is not active
	UP	The signal CTS is active
	N/A	The signal state is not available.

FIFO state can be one among the followings:

• UNKNOWN: FIFO has not been identified.

• NOTVALID: FIFO is not in a valid state.

• USED: FIFO has been correctly identified and it is in use.

The counter TXSIZE reports the size of the transmitting FIFO.

For HSCB it shows the bytes actually available in the on-board transmit fifo, however because of hw contrain just one frame can be placed there.

For ESB and ESB2 it shows the number of frames of frame length that can be stored in the dma transmit buffer.
It is important to note that the default value 2 is the optimum for voice/dat/link-check priority control, while higher value are better for throughput improvement.
Also note that value 0 is used for a special mode required by SDLC driver and when upper port is SDLC this value can't be changed.

The counter RXSIZE reports the size of the receiving FIFO.

For HSCB it shows the bytes actually available in the on-board receive fifo that can buffer up to 10 frames or up to RXSIZE bytes, whichever is reached first.

For ESB and ESB2 it shows the number of frames of frame length that can be stored in the dma receive buffer. It is important to note that the receive buffering is optimised on 128 chuncks leading to a more effective buffering, example:
RXSIZE=10, FRAME=2100 -> up to 10 frames 2100 bytes long, or up to 164 frames 128 bytes long.

The counter CHR (INPUT) is incremented every time a frame is received. The counter CHR (OUTPUT) is incremented every time a frame is sent.

The counter FRM (INPUT) is incremented every time a frame is received. The counter FRM (OUTPUT) is incremented every time a frame is sent.

The counter CHR-D (INPUT) is incremented every time a DATA frame is received. The counter CHR-D (OUTPUT) is incremented every time a DATA frame is sent.

The counter CHR-C (INPUT) is incremented every time a Link-Check frame is received. The counter CHR-C (OUTPUT) is incremented every time a Link-Check frame is sent.

The counter CHR-V (INPUT) is incremented every time a VOICE frame is received. The counter CHR-V (OUTPUT) is incremented every time a VOICE frame is sent.

The counter FRM-D (INPUT) is incremented every time a DATA frame is received. The counter FRM-D (OUTPUT) is incremented every time a DATA frame is sent.

The counter FRM-C (INPUT) is incremented every time a Link-Check frame is received. The counter FRM-C (OUTPUT) is incremented every time a Link-Check frame is sent.

The counter FRM-V (INPUT) is incremented every time a VOICE frame is received. The counter FRM-V (OUTPUT) is incremented every time a VOICE frame is sent.

The counter RX-OVR (INPUT) is incremented every time the communication board reports an "overrun" due to the received data.

High values, especially if growing, of this counter could mean either hardware problems of the Abilis CPX or, most probably, communication speed too high.

The counter TX-UND (OUTPUT) is incremented every time the communication board reports an "underrun" due to the sent DATA.

High value, especially if growing, of this counter could mean either hardware problems of the Abilis CPX or, most probably, communication speed too high.

The counter FCS-I is incremented every time the FCS (or CRC) control of a received frame is unsuccessful.

High values, especially if growing, of this counter could mean a bad quality of the transmission line, corrupting the received data. A bad quality turns into a performance lowering and into possible breaks out of the link.

The counter ABORT (INPUT) is incremented every time an "abort" event occurs while a frame is received. The counter ABORT (OUTPUT) is incremented every time an "abort" event occurs while a frame is going to be sent.

High values, especially if growing, of this counter could mean a bad quality of the transmission line, corrupting the received data. A bad quality turns into a performance lowering and into possible breaks out of the link.

The counter SHORT (INPUT) is incremented every time the length of a received frame is smaller than the minimum size (2 bytes without CRC). The counter SHORT (OUTPUT) is incremented if the length of the frame received by upper level is smaller than the minimum size (2 bytes except the CRC).

The counter OTHER is incremented every time other events, not classifiable in the already mentioned, occur.

The counter LONG-D (INPUT) is incremented every time the DATA frame received by the lower level is too long. The counter LON-D (OUTPUT) is incremented if the DATA frame received by the upper level is too long.

The counter LONG-C (INPUT) is incremented every time the Link-Check frame received by the lower level is too long. The counter LONG-C (OUTPUT) is incremented if the Link-Check frame received by the upper level is too long.

The counter LONG-V (INPUT) is incremented every time the VOICE frame received by the lower level is too long. The counter LONG-V (OUTPUT) is incremented if the VOICE frame received by the upper level is too long.

The counter LONG-D (INPUT) is incremented every time a DATA frame is discarded because there are no available receiving buffers.

The counter LONG-C (INPUT) is incremented every time a Link-Check frame is discarded because there are no available receiving buffers.

The counter LONG-V (INPUT) is incremented every time a VOICE frame is discarded because there are no available receiving buffers.

The counter CTS-TOUT is incremented every time the CTS time-out expires.

This variable gives the number of the CPX port which the SNMP trap refers to.

This variable shows either the port type (in this case SYNC) which the trap refers to, and the description the user could associate to it.

This variable shows the current state of the synchronous Level 1 of the SYNC port which the trap refers to. In the following table is shown the relationship among the state values shown in the SNMP variable and the ones obtained executing the command D S.

Value of the SNMP variable	Corresponding state of the PAD port Level 1
down(0)	DOWN
up(1)	UP
halted(2)	HALTED

This variable shows the current state of the SYNC port signal DCD which the trap refers to. In the following table is shown the relationship among the state values stored in the SNMP variable and the ones obtained executing the command D S.

Value of the SNMP variable	Corresponding state of the signal DCD
down(0)	DOWN
up(1)	UP
not-available(2)	N/A

This variable shows the current state of the SYNC port signal DTR which the trap refers to. In the following table is shown the relationship among the state values stored in the SNMP variable and the ones obtained executing the command D S.

Value of the SNMP variable	Corresponding state of the signal DTR
down(0)	DOWN
up(1)	UP
not-available(2)	N/A

This variable stores the elapsed time (in cents of second) since the system start caused by the event occurrence, which has also generated the SNMP traps. This value is usually stored as days:hours:minutes:seconds.