-
Notifications
You must be signed in to change notification settings - Fork 4
Prodigy Advance DCC Packets
Notes from analyzing the DCC signal of the MRC Prodigy Advance².
This controller doesn't support RailCom, so no difference is observed with a loco on the rails or not.
Controller uses 56µs for 1, and an over-sized 112µs for 0.
Controller uses 18 bits for the preamble.
Controller continually sends Idle packets.
With the controller set to 28 speed steps, the controller continually sends the standard packet for the loco.
No 5ms gap between packets is observed.
With a loco selected and the speed set to zero, the controller instead continually sends standard Stop packets with the direction indicator set according to the screen.
If the emergency stop button is pressed, the controller continually sends the packet with the ignore direction bit set.
With the controller set to 128 speed steps, the extra length packet is sent instead.
No gap between packets is observed.
With two locomotives being controlled, the controller sends both packets over and over. There seems to be no direct rule for which order, often two or more packets for one locomotive are sent before the other, etc.
No gaps are held for the 5ms rule.
When a function is toggled on or off, the controller sends a set of packets to do so. Unlike the speed, it doesn't repeat these forever, instead it seems to just send 5.
This was tested without any locomotive on the track to acknowledge them by drawing a current.
The controller's