POWERKEY PRO & POWERKEY

Similar documents
J1939 USER MANUAL POWERKEY PRO SERIES

PowerKey 1000 J1939 user manual

J1939 user manual. Summary: PowerKey pro series

PowerKey and PowerKey pro serier. J1939 Programmers Manual

PKP-2200-SI J1939 USER MANUAL THE PRESENT MANUAL IS FOR REFERENCE ONLY AND MIGHT BE NOT UP TO DATE TO THE LATEST VERSION.

Touch Encoder. Interface Control Document (CANBUS J1939 Protocol)

PKP2300-Motorsport. Summary:

UPB US1-40 Single Rocker Wall Switch with Dimmer Firmware Specification

MODBUS Protocol. The ecode Encoders contain both single register (16 bit) and double register (32 bit) values.

Venstar Thermostat Adapter

AN-881 APPLICATION NOTE

AN-946 APPLICATION NOTE

EGON FAMILY PROGRAMMING NOTES

GIGAVAC Contactors J1939 Protocol

Developer Notes INSTEON Thermostat v012. Developer Notes. INSTEON Thermostat. Revision History

Digi-Star ISOBUS / CAN Application Notes

Application Note. Introduction AN2471/D 3/2003. PC Master Software Communication Protocol Specification

Developer Notes for KeypadLinc Line

Micro Module Shutter. Micro Module Shutter

UPB US2-40 Series Quad Rocker Wall Switch with Dimmer Firmware Specification

INSTEON Hidden Door Sensor

CaMate Series User s Manual

CTT MODBUS-RTU COMMUNICATION PROTOCOL TEMPERATURE MONITOR DEVICE

The RS-485 user manual for B800 series communication

Home Automation, Inc. Omni-Link. Serial Protocol Description

CAN / RS485. Product Description. Technical Reference Note. Interface Adapter. Special Features

Manual. BMV - NMEA 2000 drop cable

Application Note: Using Modbus With the Conext CL Series. Important Safety Instructions

Tag4M Getting Started

Conto D2 COMMUNICATION PROTOCOL CONTENTS 1.0 INTRODUCTION

SwitchLinc 2-Wire Dimmer (RF Only) (2474DWH - Dev 0x01 / Sub 0x24)

EZ Protocol. Communication Protocol for EZPLC. For use of EZAutomation and AVG Customers with EZPLC Products. Copyright 2005 AVG

Modbus Map: Conext System Control Panel (SCP) Device

1 Firmware Description

PRODUCT RELIABILITY HOST COMMUNICATIONS PACKET STRUCTURE SPECIFICATION. % of Initial Brightness (New Module) NOTE. <type><data_length><data><crc> type

1. Implemented CM11 protocol

ArduCAM-M-2MP Camera Shield

Eaton E32 3-switch modules

PRE32 RS232 protocol v1.21 Tomas Andersson

Technical Documentation 0630

IF96017 MODBUS COMMUNICATION PROTOCOL

CE4DMID01 COMMUNICATION PROTOCOL CONTENTS 1.0 INTRODUCTION

AN434: CP2110/4 Interface Specification

COMMUNICATION MODBUS PROTOCOL

COMMUNICATION M-BUS PROTOCOL CE4DMID0M (MBus meter)

Device: MOD This document Version: 1.0. Matches module version: v1. Date: 24 February Description: MP3 Audio Module

Using an I 2 C EEPROM During MSC8157 Initialization

Solutions - Homework 2 (Due date: October 4 5:30 pm) Presentation and clarity are very important! Show your procedure!

2G Actuator Communications Protocol Document Rotary & Linear Actuators

Kinetis Bootloader to Update Multiple Devices in a Field Bus Network

Operator Interface User Manual Rev 1.0

CANopen. Network configuration. Operating instructions Software. Integration of Bürkert devices in CANopen networks

COMMUNICATION M-BUS PROTOCOL PR 118

Nuvoton Touch Key Series NT1160 Datasheet

NMEA2000 to Modbus Gateway Part No User Manual

Modbus Map: System Control Panel (SCP) Device

Serial Boot Loader For CC2538 SoC

RS485 MODBUS Module 16I-M

Interface design document MODBUS Protocol. Ab s t r a c t Description of the MODBUS implementation for the Modbus I/O board

Interfacing with ANT General Purpose Chipsets and Modules

Operating Instructions

Electrohydraulic Actuators PVE-CI, Series 6

NOVOtechnik. Content. TIM CANopen Gebrauchsanleitung TIM CANopen user manual SIEDLE GRUPPE

T7 Modbus Communication User Guide

HelmView 450 Model HV450. Operation Manual Section 78

UM2330 User manual. ST8500 boot. Introduction

Home Automation, Inc. Omni-Link II. Protocol Description

BNI DNT Z001 DeviceNet IO-Link Master User s Guide

TECH TIP. Tritex Modbus Protocol Specification

Embit Binary Interface - WMBus Specific Documentation. embit s.r.l.

Sens it Discovery. Payload Structure. 1

Custom Installation Notes: Serial programming interface and IR remote commands for Arcam UDP411 BD Player

Technical Specification. Third Party Control Protocol. AV Revolution

Aeon Labs Nano Dimmer

Aeon Labs Smart Switch 6 (Z-Wave Smart Switch 6)

Radiocrafts Embedded Wireless Solutions

Member of the ams Group

Communication protocols description of. Hx4xx and Hx3xx regulators with RS485 and RS232 communication interface

COMMUNICATION MODBUS PROTOCOL

Modbus/TCP is supported on some controllers. See QCI-AN028 Modbus TCP.

EEPROM Emulation with the ez80f91 MCU. Discussion

RS485 MODBUS Module 8I8O

IO-Link parameter description

Q.link protocol ver Q.link protocol. QuickWood Automation /16

SC1602LCPro-YG ( Yellow Green Backlight ) SC1602LCPro-B ( Blue Backlight ) Large Character Size ( 4.88x9.66 mm )

HP channel analog to CAN (mode = 0) or 6/8 key inputs to CAN (mode = 1)

CLOCKAUDIO. MR88 Automatic Microphone Mixer RS232 Programming Version 4.2

AND8386/D. Bootloading BelaSigna 250 Using the I 2 C Interface APPLICATION NOTE

Modbus TCP + Ethernet EN

Application Note: JN-AN-1003 JN51xx Boot Loader Operation

The Extended MBR (version 1.05) (dated: 01 Nov 2018) by Benjamin David Lunt Copyright (c) Forever Young Software

TIP815. ARCNET Controller. Version 1.0. User Manual. Issue September 2009

COMMUNICATION MODBUS PROTOCOL

OPTIGRID MOTORIZATION USB HID CLASS INTERFACE INSTRUCTION. Approved by:... Steve Mounnarat, Director of Engineering

Technical manual for HP9642. CAN bus keypad & LED. Firmware version 1.0. Date: \KT-HP

OCEANIC SYSTEMS NMEA2000 AC MODBUS GATWAY Part Numbers: 3155 USER MANUAL

SC1602LC 16x2 Large Characters RS232 LCD Module. User s Manual. Large Viewing Area 99mm x 24mm. Large Character Size. 4.84mm x 9.66mm.

CANBus Data Interface Rev R Lithionics LLC

Sigma DeviceNet Tool Change Systems USER S GUIDE Rev 05

Optris CT/ CTlaser/ CTvideo communication interface

Transcription:

0101010101010101010101010 01010101010101010101010101010101010101 0101010101010101010101010 1010101010101010101010101 010101010101010101010101010101010101010101010101010101010 0101010101010101010101010101010101010101010010101010101010101010 POWERKEY PRO & POWERKEY J1939 PROGRAMMERS MANUAL 0101010101010101010101010101010101010101010010101010101010101010 010101010101010101010101010101010101010101010101010101010 01010101010101010101010101010101010101010101010101 01010101010101010101010101010101010101 0101010101010101010101010 01

Contents WARNING... 4 Introduction... 5 Keypad Functionality... 5 Default Configuration... 5 Programming Protocol... 5 Group Function Definitions 7 Keypad Contact Status/Led Command (0x01)... 7 Dim Level (0x02)... 8 Back Light Level (0x03)... 8 Set ECU Source Address (0x70)... 8 Periodic Status Transmission (0x71)... 9 Event Status Transmission (0x72)... 9 LED Acknowledgement (0x73)... 9 Address Claim (0x74)... 10 Heartbeat (0x75)... 10 Heart Beat Message Format... 10 Periodic Key Message Period (0x77)... 11 Start Demo Mode (0x7A)... 11 Set Backlight Startup (0x7B)... 11 Set Led Dim Startup (0x7C)... 12 Enter Boot Mode (0XF0)... 13 Configuration Tool Commands...14 Basic Command Structure...14 CAN ID Used For Commands from the Configuration Software... 14 Command Message Data Descriptions... 14 Continuation Frames Data... 14 Time between main command and continuation frames must be greater than 1ms but not more than 5ms. This also is the time between continuation frames.... 14 Keypad Response Structure... 15 CAN ID Used For Keypad Responses.... 15 Keypad Response Data Bytes... 15 Continuation of response frames data... 15 Configuration Commands... 16 Set Periodic transmission... 16 02

Get Periodic transmission... 16 Set maximum power value... 16 Get maximum power value... 16 Set Virtual key values... 16 Get Virtual Key Values... 16 Set Virtual LED Values... 16 Get Virtual LED Values... 16 Get Model ID... 16 Configuration Commands Continuation... 17 Set LED Reply... 17 Get LED Reply... 17 Set CAN and RS485 Address... 17 Get CAN and RS485 Address... 17 Set Event Key Status Enable... 17 Get Event Key Status Enable... 17 Configuration Commands Continuation... 18 Set Default Dim Level... 18 Get Default Dim Level... 18 Set Backlight Level... 18 Get Backlight Level... 18 Get Number of LEDS... 18 Configuration Commands Continuation... 19 Get LED States... 19 Get Number of Switches... 19 Get Serial Number... 19 Set Startup Keys Message... 19 Get Startup Keys Message... 19 Get Software Revision... 19 Set CAN Address... 19 Get CAN Address... 19 Revision Record... 20 03

WARNING IMPROPER SELECTION, IMPROPER USE AND/OR FAILURE OF THE POWERKEY PRO PRODUCTS DESCRIBED HEREIN OR RELATED ITEMS CAN CAUSE DEATH, PERSONAL INJURY AND PROPERTY DAMAGE. This document and other information from Digital Switching Systems, LLC, provide product and/or system options for further investigation by users having technical expertise. It is important to analyze all aspects of the application, including consequences of any failure. Due to the variety of operating conditions and applications for these product(s), the manufacturer of the application is solely responsible for making the final selection of the product(s) and system(s) and assuring that all performance, safety and warning requirements of the application are met. The products described herein, including without limitation, product features, specifications, designs, availability and pricing, are subject to change by Digital Switching Systems, LLC at any time without notice. 04

INTRODUCTION This document describes the PowerKey Pro (PKP) keypad s functionalility, default configuration and programmable parameters. KEYPAD FUNCTIONALITY The PowerKey Pro is a microcontroller based momentary contact keypad with LED illumination that can be interfaced to CAN and RS485 networks. Keypad contact closures are monitored by the microcontroller and their occurrence is transmitted on the CAN and/or RS485 interface. LED illumination states are received over the CAN and/or RS485 interface by the microcontroller, which then illuminates the LEDs accordingly. DEFAULT CONFIGURATION The PowerKey Pro keypad s default configuration is as follows: The keypad s amber LEDs flash instantenously at power-up The contact type is set to momentary The Green and Red indicator LEDs are set to OFF Back lighting is set to off The CAN source address is set to 0x21 The Keypad Identifier is set to 0x21 Periodic Status Transmission is disabled Event Status Transmission is enabled LED Acknowledgement is disabled Address Claim Transmission is disabled Demo Mode is disabled PROGRAMMING PROTOCOL Parameter group numbers (PGNs) and group functions are used to control/command the PowerKey Pro keypad. The following sections define the proprietary format used by Digital Switching Systems (DSS) for NMEA 2000 Addressable Proprietary Single Frame (SF) parameter group (PGN 61184), as well as the assigned group functions/commands. 05

Proprietary Single Frame Parameter Group PGN 61184 is defined by both J1939 and NMEA 2000. This parameter group number (PGN) is also known in J1939 as Proprietary A. DSS has defined this parameter group as a group function type of parameter group. A Group function parameter group uses an enumerated Group Function field to identify the purpose of the parameter group. Typically, the remaining fields in the parameter group following the group function field are defined specifically for that group function. The general format of the parameter group definition is shown below. DSS Proprietary SF Group Function (PGN 61184) (Based on NMEA 2000 Proprietary SF A General Message Format) This proprietary message is defined as a group function with a maximum available payload of 5 bytes # Field Name Size Description 1 Manufacturer Code 11 bits Field 1-3 make up the Definer Tag that ensures the definition of 2 Reserved 2 bits (each bit set to logical 1 ) 3 Industry Group 3 bits Marine = 4 4 Group Function 1 byte See Assigned Group Function Codes TBD TBD TBD Allocated/defined in accordance with group function code TBD TBD TBD (for a total of 5 bytes) The first three bytes of the parameter group are always encoded as shown in the following diagram. This diagram illustrates one aspect of CAN data transmissions that is frequently misunderstood. CAN data bytes are transmitted LSB first, and fields are defined according to the bit order defined by transmission. For fields that overlap byte boundaries, the higher order bits are mapped into the lower bits of the next byte before the next field is mapped / transmitted. As Transmitted 1 2 3 4 5 6 7 8 9 10 11 1 2 1 2 3 1 2 3 4 5 6 7 8 As Returned in Data Bytes Byte 1 Byte 2 Byte 3 8 7 6 5 4 3 2 1 3 2 1 2 1 11 10 9 8 7 6 5 4 3 2 1 MSB LSB MSB LSB MSB LSB Manufacturer Code Reserved Industry Group Group Function On each receipt of the PGN 61184, the receiving keypad first tests to see if the Destination address in the CANId matches the keypad s own address, and to see if the Definer Tag in the first two data bytes matches the DSS manufacturer and industry code. The third byte of each frame is the group function byte used to determine the format and use of any remaining data bytes. 06

GROUP FUNCTION DEFINITIONS This section contains data format definitions for assigned group functions defined for the DSS Proprietary SF Parameter Group (PGN 61184). Field numbers may not directly map to byte positions. Unused bits and bytes are set to all 1 s (0xFF). Keypad Contact Status/Led Command (0x01) This group function is used to send contact status from or receive LED commands by a keypad. The group function is defined differently depending on whether it is sent from or received by a keypad ECU. Contact Status: Broadcast with Destination Address = 255 from a Source Address assigned to a keypad. LED Command: Addressed to a specific keypad Destination Address. # Byte # Field Name Size Description 4 2 Group Function 1 byte Keypad Contact Status/LED Command = 0x01 Remaining Field Defined Only When Transmitted From A Keypad ECU Source Address (Keypad Transmit) 5 3 Key Code/ID 1 byte Contact Identifier For Red LED Key Code = Key Number For Green LED Key Code = Key Number + n (where n = total number of keys on keypad) Example: PKP2400 has 8 keys, therefore n = 8. The Key Code for Key #3 is 0x03 for the Red LED And 0x0B for the Green LED. 6 4 Contact State 1 byte 0x00 = [Turn off, Disable, Reset] 0x01 = [Turn on, Enable, Set] 0x02 = [Blink RED] 7 5 Keypad Identifier 1-byte Valid range 0x21 to 0x2F 8 6 Contact Process Type 1-byte 0x01 = Momentary 07

Dim Level (0x02) This group function transmits the desired LED illumination level when on. The illumination level is given as an integer value from 0 no illumination, to 64 full illumination. Transmitted level applies to all LEDs. 4 2 Group Function 1 byte Dim Level = 0x02 5 3 LED Brightness 1 byte Valid range 0 to 64 Back Light Level (0x03) This group function transmits the desired LED back lighting level when on. The back lighting level is given as an integer value from 0 no back lighting, to 64 full back lighting. Transmitted level applies to all LEDs. 4 2 Group Function 1 byte Back light Level = 0x03 5 3 LED Brightness 1 byte Valid range 0 to 64 Set ECU Source Address (0x70) This group function is used to change the ECU CAN Source Address and/or keypad identifier. Either or both the Source Address or Keypad Identifier may be changed independently. It is required that only the one keypad be connected to the Bus when changing the keypad address. 4 2 Group Function 1 byte Set ECU Source Address = 0x70 5 3 CAN Source Address 1 byte Valid range 0 to 252 Values 253 and 254 reserved Value 255 = No change. 6 4 Keypad Identifier 1 byte Valid range 0x21 to 0x2F Value =0xFF = No change 08

Periodic Status Transmission (0x71) This group function enables or disables periodic ECU status transmissions at a rate of 10 messages per second. For example, a keypad may transmit the status of all contacts periodically; this enables or disables that feature. 4 2 Group Function 1 byte Configuration Periodic Status Transmission = 0x71 5 3 Periodic Status Transmission Flag 1 byte 0x00 = [Off, Disabled, Reset] 0x01 = [On, Enabled, Set] Event Status Transmission (0x72) This group function enables or disables event driven ECU status transmissions. For example, a keypad may transmit the status of a contact at the time that the contact changes state (opens or closes); this enables or disables that feature. 4 2 Group Function 1 byte Configuration Event Status Transmission = 0x72 5 3 Event Status Transmission 1 byte 0x00 = [Off, Disabled, Reset] 0x01 = [On, Enabled, Set] LED Acknowledgement (0x73) This group function enables or disables the transmission of an LED Acknowledgement. For example, a keypad may transmit an acknowledgement each time an LED Command is received; this enables or disables that feature. 4 2 Group Function 1 byte Configuration LED Acknowledgement = 0x73 5 3 LED Acknowledge 1 byte 0x00 = [Off, Disabled, Reset] 0x01 = [On, Enabled, Set] 09

Address Claim (0x74) This group function enables or disables the CAN Address claim when the keypad boots up 4 2 Group Function 1 byte Configuration Address Claim = 0x74 5 3 Address Claim 1 byte 0x00 = [Off, Disabled, Reset] 0x01 = [On, Enabled, Set] Heartbeat (0x75) This group function enables or disables the transmission of Heartbeat message. This message is transmitted 10 times per second. It is designed to indicate to other devises on the bus that this unit continues to function. 4 2 Group Function 1 byte Configuration Heartbeat = 0x75 5 3 Enable Bit 1 Byte Enables or Disables the Heart Beat 0 = Disable 1 = Enable 6 4 Heart Beat Period in 10ms tics 1 Byte Sets the Heartbeat Period time is in 10ms tics. With a range from 100ms to 2.55 seconds Heart Beat Message Format 4 2 Group Function 1 byte Heart Beat = 0xF9 5 3 Toggle Bit 1 Byte Bit Toggles [0/1] every message sent; used to indicate new message 10

Periodic Key Message Period (0x77) This group function sets the period time for the Key status messages. This does not enable or disable the keys periodic status messages. 4 2 Group Function 1 byte Configuration Message Period = 0x77 5 3 Key Status Period (10ms ticks) 1 byte This contains the period value in 10ms tics. Minimum value is 10 (100ms); maximum is 255 ( 2.55 sec) Start Demo Mode (0x7A) This group function puts the keypad into a demo mode. The key pad reverts back to normal once a valid CAN message is received. 4 2 Group Function 1 byte Configuration Demo Mode = 0x7A 5 3 Demo Mode 1 byte 0x00 = [Off, Disabled, Reset] 0x01 = [On, Enabled, Set] Set Backlight Startup (0x7B) This group function sets the value of the backlight when the system resets. The value is 0 63 for 0 to 100% of the backlight range. 4 2 Group Function 1 byte Configuration Set Backlight = 0x7B 5 3 LED Brightness 1 byte Valid range 0 to 64 11

Set Led Dim Startup (0x7C) This group function sets the value of the LED Dim when the system resets. The value is 0 63 for 0 to 100% of the LED DIM range. 4 2 Group Function 1 byte Configuration Set Dim Level = 0x7C 5 3 LED Brightness 1 byte Valid range 0 to 64 12

Enter Boot Mode (0XF0) This group function places the keypad into boot mode which allows keypad to be programmed. 4 2 Group Function 1 byte Boot Loader Command = 0xF0 13

CONFIGURATION TOOL COMMANDS The command used by the configuration tool has CAN message definitions different from previous allowing for more powerful commands. This is allowed due to the fact that the keypad is the only device connected on the CAN buss during setup and no other device will be effected by commands. This also allows room for future changes without effecting existing messages during normal operation. BASIC COMMAND STRUCTURE The basic commands consist of the command sent by the configuration software and the keypad responses with either acknowledge or requested data. Commands can be of multiple frames commands with data lengths that cannot fit into a single CAN message. 0x18EF1000 Byte Number CAN ID Used For Commands from the Configuration Software This indicates a message from the master configuration software (0x00) to the keypads command device (0x10) Description Command Message Data Descriptions 0 Command Byte allows up to 239 commands (0x10 0xFF) 1 Number of frames to follow. Zero indicates single frame command 2-7 Command related data Continuation Frames Data Time between main command and continuation frames must be greater than 1ms but not more than 5ms. This also is the time between continuation frames. 0 Indicates frame count first frame is 1 etc. 1-7 Contains command data for this frame 14

0x18EF0010 Byte Number KEYPAD RESPONSE STRUCTURE CAN ID Used For Keypad Responses. Indicates a message from the keypad command device (0x10) to The configuration software (00) Description Keypad Response Data Bytes 0 Echo s the requested command 1 Number of frames to follow. Zero indicates single frame response. 2 Response Status. 0x06 Command accepted 0x01 Command not understood 0x02 Command data out of range 0x03 Command not used in this model 0x15 Command not accepted due to command rules 3-7 Data returned that is requested by command Continuation of response frames data 0 Indicates frame count first frame is 1 etc. 1-7 Contains Response data for this frame 15

Command Byte 0x10 0x11 0x12 0x13 0x14 0x15 0x16 0x17 0x19 Configuration Commands Description Set Periodic transmission Data 0 = Enable/Disable Individual key status periodic transmission Data 1 = Enable/Disable Heart beat periodic transmission Data 2 = Period between Key status ( time in 10ms slices 100ms to 2.55 seconds) Data 3 = Period between heart beat ( time in 10ms slices 100ms to 2.55 seconds) Get Periodic transmission Data 0 = Enable/Disable Individual key status periodic transmission Data 1 = Enable/Disable Heart beat periodic transmission Data 2 = Time period between Key status ( time in 10ms slices max 2.55 seconds) Data 3 = Time period between heart beat ( time in 10ms slices max 2.55 seconds) Set maximum power value Data 0 = Power in percentage of maximum. Range 0-100% Get maximum power value Data 0 = Power in percentage of maximum. Range 0-100% Set Virtual key values Keys are set in 4 bytes Byte 0 Key Code (Virtual Number) Byte 1 Key Type ( Momentary or Latching) Byte 2 Logic Sense ( 0 or 1 for contact closed ) Byte 3 Actual Key Number Keys are set one at a time. Get Virtual Key Values This requests all the virtual key settings for the keypad. (Using above Command Structure) Set Virtual LED Values LEDS are in sets of 2 Bytes Byte 0 Led Code (Virtual Number) Byte 1 Actual LED Number Get Virtual LED Values This requests all the virtual LED settings for the keypad. Get Model ID Returns the stored Model ID as a string of 16 bytes. 16

Command Byte 0x1A 0x1B 0x1C 0x1D 0x1E 0x1F Configuration Commands Continuation Description Set LED Reply Enables / Disables CAN acknowledge message after LED command Byte 0 0 = Disable, 1 = Enable Get LED Reply Returns the present state of the Reply setting Byte 0 0 = Disable, 1 = Enable Set CAN and RS485 Address Sets the keyboard address used in CAN and RS485 Byte 0 = CAN Address Byte 1 = RS485 Address Get CAN and RS485 Address Returns the present address of the CAN and RS485 Byte 0 = CAN Address Byte 1 = RS485 Address Set Event Key Status Enable Sets whether Key change event triggers CAN Message Byte 0 0 = Disable, 1 = Enable Byte 1 = Periodic Status Byte 2 = Periodic Period Get Event Key Status Enable Sets state of whether Key change event triggers CAN Message Byte 0 0 = Disable, 1 = Enable Byte 1 = Periodic Status Byte 2 = Periodic Period 17

Command Byte 0x20 0x21 0x22 0x23 0x24 Configuration Commands Continuation Description Set Default Dim Level This sets the DIM level default values Valid numbers must be 0-63 Byte(0) = Present Dim Level Byte(1)= Startup DIM Level Get Default Dim Level This returns the present Default DIM Level Byte(0) = Present Dim Level Byte(1) = Default Dim Level Set Backlight Level Sets the backlight level LEDs Valid Number must be 0-62 Byte(0) = LED Backlight Level Byte(1)= LED Backlight Startup Level Get Backlight Level Gets the stored backlight Level Byte(0) = LED Backlight Level Byte(1) = LED Backlight Startup Level Get Number of LEDS Gets the total number of LEDS Byte = Number of LEDS 18

Command Byte 0x25 0x26 0x27 0x28 0x29 0x2A 0x2B 0x2C Configuration Commands Continuation Description Get LED States Returns the present LED State for each LED 0 = OFF, 1 = ON, 2 = Blink OFF, 3 = Blink On Each data byte contains 4 LED states each occupies Two bits. MSB contains lowest LED. Get Number of Switches Gets the total Number of Switches Byte(0) = Number of switches Get Serial Number Returns Binary value of key boards SN Returns 0xFFFFFF if not set. Byte(0) = MSB (0x??XXXX) Byte(1) = (0xXX??XX) Byte(2) = (0xXXXX??) Set Startup Keys Message This command enables/disables the sending of all the keys during power up. The Enable / Disable is sent in Byte (0) Get Startup Keys Message This command returns the setting of the startup message enable. Byte(0) = 0; Disabled Byte(0) = 1; Enabled Get Software Revision This command retrieves the Firmware revision, The value is returned in three bytes Byte(0) = Major Revision Byte(1) = Minor Revision Byte(2) = Sub Minor Revision Set CAN Address This command sets the CAN address of the device. Available range is 1 to 15. And corresponds to actual addresses of 0x21 to 0x2F Get CAN Address This command retrieves the CAN address of the connected key pad. Valid range of 0x21 to 0x2F 19

Revision Record Date Rev Filename Comment 5-31-10 A PowerKey Pro Programmers Manual Initial Release 6-2-10 B PowerKey Pro Programmers Manual Modified Table, page 9 6-4-10 C PowerKey Pro Programmers Manual REVC Updated Paragraph 2, page 3 5-1-11 D PowerKey Pro Programmers Manual REVD Corrected Errors and updated for REV-C software release 10-19-12 5_6 PowerKey Pro Programmers Manual REV5_6 Added additional capabilities for new PKP platform, including the new PKP2200 keypad. 20