Coding behavior becomes even easier with the new Event Logging Keyboard

Easy scoring of the beginning and end of states
 
Scoring the beginning, as well as the end of different behaviors at the same time, requires quite some exercise. The new Event Logging Keyboard can be a solution, allowing coding of behaviors as on/off states – occurring when the key is held pressed down, and not occurring for the remainder of the time. The good ergonomic design of the keyboard helps preventing errors during scoring, and allows you to concentrate on the observation, rather then on the scoring itself.
 
How does it work?
 
The Event Logging Keyboard has 12 keys, either with codes A to L or M to X. Each key can be used to score in two different modes:

1. Standard mode, in which the key functions as a normal key.

2. “Press and hold down” mode. In this mode, a lowercase character is sent to the
    computer when the key is pressed down; when it is released, the keyboard sends the
    corresponding uppercase character. For example, when the key labeled A is pressed
    down, a lowercase “a” is generated (e.g. “a” = grooming); when it is released the
    keyboard sends the uppercase letter “A” (e.g. “A” = not grooming).

Operation and connection
 
There are two banks of 6 DIP switches, each of which corresponds with one key (i.e. the most left DIP switch refers to the most left key on the keypad (either A or M)). Turning the switch to the ‘on’ (or upper) position will result in “press and hold down mode for that key. These switches may be changed with the keyboard attached to the computer. The Event Logging Keyboard is to be used with a normal computer keyboard attached. It is fitted with leads with PS/2 connectors, and also has a PS/2 socket, so other Event Logging Keyboards may be attached in series. This provides an ideal solution when multiple observers are scoring simultaneously!
 
Configuration
 
When making a configuration in The Observer for using the Event Logging Keyboard, the following rules are important:

Behaviors that are scored in press and hold down mode, should each have their own class. So for every behavior scored in press and hold down mode, there is one class with only 2 behaviors. One behavior is for the on state, the other behavior is for the off state, for example 'Grooming' and 'Not Grooming'.
Both behaviors should be scored using the same letter, where the lower case is the on state, the upper case the off state. This also means that you have to differentiate between Upper and Lower case in the Keyboard Definition.