Honeywell VX6, Reference Manual, Page: 313 / 356

Creating Custom Key Maps for the VX6 293
E-EQ-VX6RG-F VX6 Reference Guide
No definition for MapHead.keyscan2
No Scan Key 2 definition was found. The keyboard driver requires this key to be defined
somewhere in one of the keymaps. This message comes from the post-parse validation, so no line
# is specified.
No definition for MapHead.keyscan3
No Trigger Button definition was found. The keyboard driver requires this key to be defined
somewhere in one of the keymaps. This message comes from the post-parse validation, so no line
# is specified.
No definition for MapHead.keyshift
No SHIFT modifier key definition was found. The keyboard driver requires this key to be defined
somewhere in one of the keymaps. This message comes from the post-parse validation, so no line
# is specified.
No definition for MapHead.keyuparrow
No up arrow definition was found The keyboard driver requires this key to be defined somewhere
in one of the keymaps. This message comes from the post-parse validation, so no line # is
specified.
No equal in value line
A value line must be of the form
value=data
. A value line was expected, but there was no equal
in it.
(or)
A comment line did not begin with a semicolon (;).
No MAPNAME defined
There is no map name defined. The keyboard driver requires this name to be able to load the
keymap tables. This message comes from the post-parse validation, so no line # is specified.
Scan code algorithm required
A COLxROWx data value was found before any ALGOR statement. ALGOR algorithm is parsed
to decide how to encode COLxROWx into a keymap value.
Too many maps for specified MAPCNT
There are more MAP sections defined that the MAPCNT field specified.
Unknown scan code algorithm
The ALGOR algorithm specified is not one that KEYCOMP understands.
Unrecognized scancode algorithm %s
The ALGOR algorithm specified is not one that KEYCOMP understands.
Value outside of section
A value (defined as
value=data
) is only valid within a section (defined as
[section]
). A value line
was found when a section header line was expected.