Interpreter commands to enter the terminal's system menu

Menu numbers zero to nine are assigned to functions which are usually accessable through the "main" system menu:

sys.menu(0)

Dummy to leave the terminal's system menu (not available for the user application)

sys.menu(1)

Enters the system's main menu.

sys.menu(2)

Enters the "User Settings" (if the terminal's system menu has such a function).

sys.menu(3)

Enters the "Hardware Setup" menu.

sys.menu(4)

Enters the "Hardware Test" menu.

sys.menu(5)

Enters the "Diagnostic" menu.

sys.menu(6)

Enters the "General Settings" menu.

sys.menu(7)

Reserved for remotely controlling the system menu.

sys.menu(8)

Enters the "Error History" display (if the terminal has such a function).

sys.menu(9)

Enters the built-in clock / calendar display, where the real time clock can be set.
(Only available if the terminal has an RTC installed, of course ! ).

Menu numbers 10 and above are highly hardware dependent:

sys.menu(10)

Diagnostics: show memory nodes

sys.menu(11)

Diagnostics: show storage directory

sys.menu(12)

Diagnostics: browse the text array

sys.menu(13)

Diagnostics: show structure sizes, array dimensions, etc.

sys.menu(14)

Diagnostics: show CANdb import history (where applicable)

sys.menu(15)

Diagnostics: show CANdb message list (where applicable)

sys.menu(16)

Diagnostics: list all communication channels (where applicable)

sys.menu(17)

Diagnostics: show CANopen configuration (where applicable)

sys.menu(18)

Diagnostics: show application variables (only available in "debug"-versions of the firmware)

sys.menu(19)

Diagnostics: list of display pages (only available in "debug"-versions of the firmware)

sys.menu(20) .. sys.menu(29)

Reserved for other "diagnostic" submenus

The following system menus are only available if there is an integrated CAN-LOGGER feature:

sys.menu(30)

Enters the CAN Logger's configuration menu

sys.menu(31)

Shows the basic CAN Logger states (passive, enabled, triggered, ....)

sys.menu(32)

Shows the CAN Logger's trigger conditions .

.-.-.

W.B. , 2007-11-29

back to the index