User Tools

Site Tools


dr5000-en

This is an old revision of the document!


DigiKeijs DR5000

ContentCommand StationsDigiKeijs



Use always the USB port in case of DR5000 configuration.

Setup USB


Devices

Following serial devices are added for the DR5000:

Windows Linux & RaspBerry Pi Mac OS X Protocol Library Sub-Library / Type Baudrate
COM4 /dev/ttyACM0 /dev/tty.usbmodem1411 LocoNet loconet LocoBuffer 57600
COM6 /dev/ttyACM1 /dev/tty.usbmodem1413 Xpressnet xpressnet Li-USB 57600
COM5 /dev/ttyACM2 /dev/tty.usbmodem1415 Dr.Command (Setup) - - -

After successful configuration, several other commonly used protocol types can be used with Rocrail.

Setup USB LocoNet Rocrail



More details are described below.

Setup LAN

LocoNet, LNTCP, is recommended for the DR5000 communication. (Xpressnet seems to be too slow and is missing some events.)

LocoNet LAN

Hostname LAN

Host name or IP-Address from the DR5000.
The LAN connection will get its IP address by DHCP: Hostname DR5000-<Serialnumber>.
Example: "DR5000-5000A0000008"

Hostname WiFi

The WiFi IP-Address of the DR5000: 192.168.16.254
This can only be used if the computer has been connected to the WiFi Hotspot of the DR5000.
WiFi is not recommended for controlling a layout.

Port

The DR5000 TCP/IP port is 5550. (The port number cannot be changed; Fixed by the manufacturer.)

Type

The LNTCP type must be selected for this communication protocol.
Rocrail will expect an echo for every command in case CTS is set active.
(Error message: Trace timer timed out for OPCODE 0xB0, fix increase timer)

Options

Some LocoNet Throttles do not set an ID and therefore the Speed will not be updated in the Rocrail clients. (Rocview, andRoc, Rocweb…)
See: Zero Throttle ID for more information about this issue.


LocoNet Details


Wait for slot data

This number should be increased, max. 128, if the following error occurs:

Could not get slot for loco addr=xx

Default Rocrail will read up to 16 packets until it give up waiting for a free slot.
This figure, the default of 16, seems to be too low for the DR5000.


Z21

DR5088RC

If using the Z21 protocol in combination with DR5088RC there is a shift in reported feedback and block(RailCom) addressing.
A possible workaround is to decrease the Feedback addresses by one:


DrCmd

12.740+
The drcmd library has only limited support because the protocol is not documented.

Supported commands:

  • Power ON/OFF
  • Switch (FADA only)
  • Loco speed, direction and F0-F28
  • Programming Track
  • POM

Supported events:

  • S88 reporting
  • Switch reporting
  • Power events
  • Current and temperature
  • Loco speed, direction and F0 reporting


Xpressnet LAN

Addressing

Accessory

Switches, Outputs and Signals.

Protocol Addressing
LocoNet FADA, PADA, MADA


Programming Track

Only direct CV programming is supported.


dr5000-en.1585134586.txt.gz · Last modified: 2020/03/25 12:09 by smitt48