User Tools

Site Tools


public:cbuspublic:jmriacccmd

Commanding Accessory Decoders using CANCMD & JMRI

Back to introduction
Here is a quote from Forum topic CANCMD and accessory decoder
I can confirm that RDCC3, RDCC4, RDCC5 and RDCC6 are implemented in CANCMD, Andrew put these in and I have not changed them in any way, although I have never tried them myself.

To send accessory commands using these opcodes, you would need to implement specific routines in the software driving your CBUS, to encode the required DCC accessory commands into the RDCCx message.

For example, in JMRI you would have to create your turnout table entries using CBUS commands that send explicit RDCCx commands, rather than the usual CBUS events.

For details of how to do this in JMRI, see:

http://jmri.sourceforge.net/help/en/html/hardware/can/cbus/index.shtml

and search down the page for “it's possible to connect a Sensor to arbitrary can frames….”

0x80 RDCC3

Decimal 128 - Request 3-byte DCC Packet
Format:
[<MjPri><MinPri=2><CANID>]<80><REP><Byte0>..<Byte2>
<Dat1(REP)> is number of repetitions in sending the packet.
<Dat2>..<Dat4> 3 bytes of the DCC packet.
Allows a CAB or equivalent to request a 3 byte DCC packet to be sent to the track. The packet is sent <REP> times and is not refreshed on a regular basis. Note: a 3 byte DCC packet is the minimum allowed.

0xA0 RDCC4

Decimal 160 - Request 4-byte DCC Packet
Format:
[<MjPri><MinPri=2><CANID>]<A0><REP><Byte0>..<Byte3>
<Dat1(REP)> is number of repetitions in sending the packet.
<Dat2>..<Dat5> 4 bytes of the DCC packet.
Allows a CAB or equivalent to request a 4 byte DCC packet to be sent to the track. The packet is sent <REP> times and is not refreshed on a regular basis.

0xC0 RDCC5

Decimal 192 - Request 5-byte DCC Packet
Format:
[<MjPri><MinPri=2><CANID>]<C0><REP><Byte0>..<Byte4>
<Dat1(REP)> is # of repetitions in sending the packet.
<Dat2>..<Dat6> 5 bytes of the DCC packet.
Allows a CAB or equivalent to request a 5 byte DCC packet to be sent to the track. The packet is sent <REP> times and is not refreshed on a regular basis.

0xE0 RDCC6

Decimal 224 - Request 6-byte DCC Packet
Format:
[<MjPri><MinPri=2><CANID>]<E0><REP><Byte0>..<Byte5>
<Dat1(REP)> is number of repetitions in sending the packet.
<Dat2>..<Dat7> 6 bytes of the DCC packet.
Allows a CAB or equivalent to request a 6 byte DCC packet to be sent to the track. The packet is sent <REP> times and is not refreshed on a regular basis.

public/cbuspublic/jmriacccmd.txt · Last modified: 2017/05/03 07:09 (external edit)