General

General Commands

Mostly commands which don't fit anywhere else.

00 General Acknowledgement (ACK)

Format: <00>

Positive response to query/request performed or report of availability on-line. Probably not needed. See opcode 7C.

01 General No Ack(NAK)

Format: <01>

Negative response to query/request denied. Probably not needed. See opcode 7C.

02 Bus Halt (HLT)

Format: <02>

Commonly broadcast to all devices by the command station to indicate CBus is not available and no further packets should be sent until a BON or ARST is received. Probably not needed.

03 Bus ON (BON)

Format: <03>

Commonly broadcast to all devices by the command station to indicate CBus is available. Probably not needed.

0B Request firmware Version (RVER)

Format: <0B>

Sent by any device to request firmware version information from a node in 'setup' mode. Probably not needed. See opcode 10.

10 Read node parameters

Format: <10>

Read a 7 byte node parameter string while the node is in 'setup' mode. Reply is opc=EF. Probably neededs to be replaced.

(How do nodes know whether to respond to this? It doesn't e.g. carry the NN that should reply)

Only one node should be in 'setup' mode.

3F Extended op-code with no data byte packet (EXTC)

Format: <3F><Ext_OPC>

Used if the basic set of 32 OPCs is not enough. Allows an additional 256 OPCs.

43 Version report (VER)

Format: <43><Vmaj><Vmin>

<Dat1> is major version number <Dat2> is minor version number

Sent by a device or command station in response to a RVER packet. Probably not needed. See opcode EF. Deleted ?

5F Extended op-code with 1 data byte packet. (EXTC1)

Format: <5F><Ext_OPC><param1> Used if the basic set of 32 OPCs is not enough. Allows an additional 256 OPCs.

7F Extended op-code with 2 data byte packets. (EXTC2)

Format: <7F><Ext_OPC><param1><param2>

Used if the basic set of 32 OPCs is not enough. Allows an additional 256 OPCs.

83 Node version report (VER)

Probably not needed. See opcode EF. Deleted in version 5 of the spec.

9F Extended op-code with 3 data byte packets. (EXTC3)

Format: <9F><Ext_OPC><param1><param2><Param3>

Used if the basic set of 32 OPCs is not enough. Allows an additional 256 OPCs.

BF Extended op-code with 3 data byte packets. (EXTC3)

Format: <BF><Ext-OPC><Param1><Param2><Param3>

Used if the basic set of 32 OPCs is not enough. Allows an additional 256 OPCs.

DF Extended op-code with 4 data byte packets. (EXTC4)

Format: <DF><Ext-OPC><Param1><Param2><Param3><Param4>

Extended op-code with space for the full 4 byte event. <NN hi><NN lo><EN hi><EN lo> Used if the basic set of 32 OPCs is not enough. Allows an additional 256 OPCs

EF Node parameters

Format: <EF><Param1><Param2><Param3><Param4><Param5><Param6><Param7>

Send in 'setup' mode in reply to opc=10. The payload bytes Param1-Param7 are identification information for the node.

Mike Bolton has proposed:

• Param1-Param2: 16 bit manufacturer ID
• Param3: Manufacturer's model number (what the module is)
• Param4: Version number
• Param5-Param7: Spare/Reserved