The OEM-5400 Development kit includes a comprehensive software development toolset that allows developers to quickly deploy and test various Screenkey solutions. The software toolset enables the integration of ScreenKey controls into high-level programming languages. Windows COM objects are employed making it easy to integrate Screenkeys with most Windows based high-level programming languages, e.g. VC++, VB, Delphi, etc.
The OEM-5400 Windows Development kit is supplied with the following:
The panel of 12 Screenkeys is supplied in a 3x4 matrix and is offered in one of four configurations:
Additional ScreenKey panels may be purchased and are interchangeable. The OEM-5400 CPU controller board automatically detects the type of Screenkey panel attached and configures itself accordingly. The OEM-5400 controller board interfaces to a host computer via an RS-232 serial interface.
Windows COM technology is used to provide developers with easy-to-use ActiveX components that are readily incorporated into most high-level programming languages, e.g. VC++, VB, Delphi, etc. Language specific wrappers are available for development languages that do not support COM technology.
The SKI ActiveX component can be used to directly drive the ScreenKey module and control text, graphics and colours on individual keys.
A higher-level SAC Engine ActiveX component is used to control the panel of ScreenKeys using a predefined drill-down menu system (SAC files see below). This tool removes the programming burden from the developer while still allowing direct low-level control if and when required.
A full Windows-based ScreenKeys SAC Editor is provided as part of the package to allow users to design a SAC file offline from the application code. This SAC file is used by the SAC Engine to implement the interface as designed in the SAC Editor. A SAC file contains multiple menus including graphics and text for each LCD key, plus navigation instructions on how these menus interact. It also includes any keypress information to be returned on the keyboard channel when a particular ScreenKey is pressed.
Even faster integration can be achieved using the SAC Controller application. This tool operates in a standalone mode and controls the ScreenKey console based on a specified SAC file. Keypress return information, as per the SAC file, is returned via the keyboard channel to the active Windows application as if it was typed from the QWERTY keyboard. This method can greatly accelerate the initial integration task.
The OEM-5400 Windows Prototyping and Development Kit overview document is available to download here.