The CAN bus configuration file (default: canserv.cfg) contains two types of sections. The first section defines the base address and interrupt vector of the JANZ VMOD I/O carrier board. It is labelled with [VMOD] and must contain the following parameters:
| vme.base | hexadecimal number (prefixed by 0x), base address of the VMOD I/O carrier board. This address can be selected with four switches on the board. |
| vme.vector | hexadecimal number (prefixed by 0x), four most significant bits of the interrupt vector generated by any of the ICAN2 modules. These four bits can be selected with jumpers on the VMOD I/O. |
| vme.irq | The IRQ level with which the incoming interrupts are answered on the VME CPU. Range: 0-7, small numbers indicating high priority. |
Parameters and values must be separated by a colon (:). Only one [VMOD] section may be defined at the moment. This limits the number of CAN buses which can be controlled by one program to four.
The other type of section is labelled [CAN]. There can be more than one sections of this type in a file, thus enabling the program to address several CAN buses (up to four at the moment).
A [CAN] section must contain the following parameters:
| module | The place where the ICAN2 module is fitted into the VMOD carrier board. They are numbered from top to bottom, starting with 0 and ending with 3. |
| speed | The CAN bus speed in kbits/sec. Accepted values are 1000, 500, 250, 125, 100 and 50. To operate SLIOs the speed must not exceed 125 kbits/sec. A speed of 100 kbits/sec however seems to enable a more reliable communication with the SLIOs. |
| busnumber | A logical number to denote this CAN bus. It should be unique within one configuration file and is used to determine which CAN bus can program a specific HELIX chip. |
| SLIO | yes or no. Set this flag to yes if there are SLIOs attached to the CAN bus. This enables the automatic sending of calibration messages to the SLIOs. If no SLIO parameter is given, its value defaults to no. |
Parameters and values must be separated by a colon (:). A sample configuration file can be found in Appendix A.1.