
		       SICC-E -release
		       ================


			    08/94

  General:
  --------

  -	A sample batch file that loads the firmware can be
	found in LOAD_SX.BAT.

  -	The controller can be configured with the utility XPUTIL.EXE, see
  	the description of the parameter file syntax below and file
	CONF_SX.BAT. Currently the configuration process requires that
	the drivers TIBAPTD.EXE and TIBAPN are loaded. Future
	releases will contain a more comfortable configuration tool that
	uses TICAPI.EXE. Note that in CONF_SX.BAT the TIBAPxx drivers are
	removed from memory when the configuration is completed! TICAPI.EXE
	cannot be loaded when they are in memory and vice versa.



  Loading the firmware:
  ---------------------

  The batch file LOAD_SX.BAT illustrates the loading of the firmware.
  In this example it is assumed that the SICC-E I/O base address is 260H
  and that interrupt 10 is used.


  Configuration and activation of the SICC-E controller:
  ------------------------------------------------------

  Currently the utility XPUTIL.EXE is used to configure and to activate
  the controller (type XPUTIL -? for more information about the command
  line parameters). Before execution of XPUTIL the environment variable
  x31 must have the value "d" or "b" and the drivers TIBAPTD.EXE and
  TIBAPN.EXE must be loaded (see LOAD_SX.BAT). The controller then becomes
  operational in two steps:

  	XPUTIL -p <parameter file>	configuration
	XPUTIL -a			activation

  The X25 link (layer 2) is activated if XPUTIL -a terminates without
  any error messages. If the link is down (for example return value
  800H: layer 1 offline), the controller tries to activate layer 2 as
  soon as layer 1 becomes ready. In this case, a subsequent XPUTIL -a
  would terminate without any error message.

  The most relevant values returned by the XPUTIL -p command are:

	842H :	request may not be issued twice (see note below)
	843H :	illegal or inconsistent values in parameter file

  The controller must be reset by XPUTIL -i before it can be reconfigured
  with a new XPUTIL -p command. When resetting the controller the driver
  TICAPI should not be loaded (can be removed from memory with TICAPI -d).


  Configuration parameter file syntax:
  ------------------------------------

  The parameter file entries have the following format (an example is given
  in XP.PAR):

	:<parameter name>	<value>

  Lines with '*' or ' ' in column 1 are regarded as comments:

	*this is a comment


  Description of parameters:
  --------------------------

  Name		Range/Default	Meaning
  -------------------------------------------------------------------------
  br		0..17 / 0	Baud rate:
  				0  -	external clock (normal mode)
				Internal clock if nonzero:
				3  -	600 Baud
				5  -	1200
				7  -	2400
				9  -	4800
				11 -	9600
				13 -	19200
				15 -	48000
				17 -	64000

  dce		1,3 / 3		LAP-B DCE address:
  				3  -	DTE operation (normal mode)
				1  -	DCE operation

  dte		1,3 / 1		LAP-B DTE address:
  				1  -	DTE operation (normal mode)
				3  -	DCE operation

  t1		0..3 / 3	LAP-B timer T1 in seconds

  t2		>= 0 / t1/2	LAP-B timer T2 in seconds

  n2		0..10 / 10	LAP-B repetition counter N2

  k		1..7 / 7	LAP-B window size (*)

  tstart	>= 0 / 0	Link activation timeout in seconds:
  				0  -	no timeout

  dlen		<= 2048 / 128	Layer 3 packet size in bytes (*)

  xiot		1..64 / 64	Number of packet layer I/O tasks

  bsize		<= 2048 / 2048	Size of application data buffer in bytes

  mod		8 / 8		X25 numbering scheme (must be 8 currently)

  w		2..7 / 2	Layer 3 window size (*)

  lxad		>= 0 / 15	Maximum length of X25 addresses

  lfac		>= 0 / 63	Maximum length of X25 facility data

  lud 		>= 0 / 16	Maximum length of X25 user data

  pid		0..255 / 0	Protocol ID, relevant for incoming calls
  				only. If this value is not zero, the call
				will only be accepted if the first byte of
				the user data field in the CALL packet matches
				this value. This check is disabled if the
				value is zero (normal case)

  xnr		- / none	Own X25 address, 15 digits maximum (not
  				required for the DATEX-P network)

  pvc		0..64 / 0	Number of permanent virtual circuits
  				(see note on X25 group numbers below)

  svci		0..64 / 0	Number of virtual circuits for incoming
  				calls only
  				(see note on X25 group numbers below)

  svcio		0..64 / 0	Number of virtual circuits for incoming
  				and outgoing calls (two way channels)
  				(see note on X25 group numbers below)

  svco		0..64 / 0	Number of virtual circuits for outgoing
  				calls only
  				(see note on X25 group numbers below)

  -------------------------------------------------------------------------

  (*):	these values should normally not be modified!


  X25 channel group numbers:
  --------------------------

  Internally the values pvc, svci, svcio and svco are coded as 2 byte
  words: the low byte contains the number of channels of this type, the
  high word contains the channel group number (normally 0). If 16 two
  way channels with channel group number 0 should be specified, the entry
  in the parameter file could be coded as:

  	:svcio	16

  16 channels with channel group number 1 are defined by

  	:svcio	272		(272=256+16)


  Note that for normal operation only a small subset of the parameters
  described above must be specified. The simplest parameter file could
  comprise a single line:

  	:svcio	16


  Back-to-back operation (V.24):
  ------------------------------

  Two SICC-E can be connected for back-to-back operation (without X25
  network) if a special cable is used (null modem cable). The cable
  must connect the 2 DSUB25 plugs as follows:

  	Plug 1 / Pins			Plug 2 / Pins
	-------------			-------------

	Shield	----------------------------   Shield

	(NC) 1  ----------------------------   1 (NC)

	TxD  2  ----------------------------   3 RxD
	RxD  3  ----------------------------   2 TxD

	RTS  4  ----------------------------   8 DCD

	CTS  5  ----------------------------  20 DTR
	DSR  6  ----|

	GND  7  ----------------------------   7 GND

	DCD  8  ----------------------------   4 RTS

	T2  15  ----------------------------  24 T1
	T4  17  ----|

	DTR 20  ----------------------------   5 CTS
				       |----   6 DSR

	T1  24  ----------------------------  15 T2
				       |----  17 T4


  One of the SICC-Es must operate in DCE mode and must generate the
  clock cycles according to the required baud rate. For 64Kbit baud
  rate the parameter file could be:

	:svcio	16
	*null modem values (speed: 3=600 Baud,5=1200,7=2400,9=4800,
	*11=9600,13=19200,15=48000,17=64000):
	*null modem values (DCE mode operation):
	:br	17
	:dce	1
	:dte	3


  CAPI for SICC-E (TICAPI.EXE):
  -----------------------------

  Applications based on the CAPI interface can run on the CPV-Stollmann
  ISDN controllers of the tina family, as well as on the X25 controllers
  SICC-E and SICC-PC. The only restrictions that apply are:

  - The procotol used (see CAPI V1.1 specification) must be mappable
    to the X25 protocol (voice applications will not work ...)

  - The M-bit may be used in data blocks (CAPI DATA_B3_REQs) only if
    the block size is an integral multiple of the layer 3 packet size
    ("dlen" in the parameter file). If possible, the M-bit should not
    be used.

  - A CAPI DATA_B3_REQ with Q- or M-bit set and data length zero (trans-
    mission of flags only) may not be issued.


  TICAPI command line parameters are displayed when TICAPI is called as

  	TICAPI -?

  The current -version of TICAPI supports

  	16 X.25 channels
	2 SICC-E controllers
	4 applications

  For proper operation at least 2 X.25 channels ("svco", "svcio" and "svci"
  in the parameter file) and 4 packet layer I/O tasks ("xiot") should be
  generated.  This is due to the fact that TICAPI transforms a CAPI
  LISTEN_REQ into two internal listen requests, which in turn occupy the
  resources for two I/O tasks. The reason behind this procedure is, that
  ISDN applications that do channel bundling on two B-channels generate two
  almost simultaneous incoming calls. One of these calls might be lost if
  only one internal listen request would have been generated. When an incoming
  call is received, TICAPI issues a new listen request. Consequently, in order
  to handle ISDN application (using two B-channels, incoming and outgoing
  calls) correctly, at least 4 I/O tasks should be generated. Note that each
  X.25 channels requires one I/O task!

  The number of internal listen requests that TICAPI generates due to
  a CAPI LISTEN_REQ can be modified with with the command line parameter
  "-l":
  	TICAPI -l4

   would result in 4 internal listen requests (default: 2).


  Known bugs in the SICC-E -version:
  -----------------------------------

  a) If the link becomes offline (layer 1 or 2) LISTEN_REQs are lost. The
     application must must issue a new LISTEN_REQ.
     Normally this does not happen at the public X.25 network (unless the
     cable is unplugged).

  b) No mapping of X.25 cause and diagnostic values to 1TR6 causes
     (info value in DISCONNECT_IND is always 0x3400).

