DR5088RC RailCom

[vikr]

Hallo Reinder,

@reinder

I’ve a DigiKeijs DR5088RC (16+1 input LocoNet RailCom detector), the DR5088RC was also designed by Karst Drenth, so the YD6016LN-RC most likely is an improved version of the DR5008RC.

you can read by traintastic every RC-Messages from the Dcoder, sendet on the track.

That won’t work, the limit here is LocoNet, for standard RailCom the LocoNet OPC_MULTI_SENSE message is used, it can only carry an loco address and a detector address. The DR5088RC and YD6016LN-RC have an option to use the highest bit of the loco address or detector address as direction indication. Traintastic supports both. Alternative is the unofficial OPC_MULTI_SENSE_LONG message (also supported by Traintastic) that can be enabled on the DR5088RC and YD6016LN-RC, this message can carry more RailCom data, e.g. quality of service and some other.

Here for example the DR5088RC in Kombination with the Lenz LZV200 under Windigipet:

V20 on sensor 1

V20 flipped:

V20 on sensor 2

Is there a way to configure it similary in Traintastic 0.4.0 Build 2066?
It should work with every Central who gives a propper DCC-Signal and a booster, build in or not, who cuts the cut exactly.

kindly regards

vik

[reinder]

Hi @vikr,

Yes that is possible, I’ve created a world as example.

It uses sensor addresses 1 and 2.

You might need to update the LocoNet connection settings for your setup.
Depending in how your DR5088RC is configured you might need to correct the OPC_MULTI_SENSE direction setting:

The world: DR5088RC-railcom-example 2026-06-19.ctw you can import it using: File → Import

Greetings,
Reinder

[vikr]

Hi Reinder

@reinder

I’ve created a world as example.

It uses sensor addresses 1 and 2.

You might need to update the LocoNet connection settings for your setup.
Depending in how your DR5088RC is configured you might need to correct the OPC_MULTI_SENSE direction setting:

The world: DR5088RC-railcom-example 2026-06-19.ctw you can import it using: File → Import

thanks, but how to configure my LZV200?

Greetings

vik

[reinder]

Hi @vikr,

@vikr

but how to configure my LZV200?

Based on the LZV200 manual (chapter 5.8.1), this should work:

Greetings,
Reinder

[vikr]

Hi Reinder,

@reinder

Based on the LZV200 manual (chapter 5.8.1), this should work:
image481×386 22.4 KB

Thanks for the immediately answer.

For further experiments i`ve to combine some boards (for example pendel-line, Model railway Y-junction, Oval), one to three lokomotives and different interfaces.

Is there a possibility to export configured working boards or lokomotives, out of an existing world, in a file and later import in annother world?

kindly regards

vik

[reinder]

Hi @vikr,

@vikr

Is there a possibility to export configured working boards or lokomotives, out of an existing world, in a file and later import in annother world?

No there isn’t yet, it is something I’d like to add in the future. The export is not that difficult, but the import is challenging, it has to resolve missing references handle conflicts etc. so that will take some time to figure out.

What I could add more easily is a world clone option, then you have a copy that you can adjust. Would that help?

Greetings,
Reinder

[vikr]

Hi Reinder,

@reinder

What I could add more easily is a world clone option, then you have a copy that you can adjust. Would that help?

of course this will be helbful!

Greetings

vik

[reinder]

I’ll see what I can do this weekend

[vikr]

Hallo Reinder,

a short hopefully preview!
V20 starting on Sensor1 Lok-Direction to the EAST (direction-arrow OK!):

V20 on Sensor1 FLIPPED (direction-arrow unchanged!):

V20 on Sensor2 (no direction-arrow):

traintastic_diagnostic_report_20260620_113912.zip (30.8 KB)

hope it helps

Greetings

vik

[reinder]

Hi @vikr,

How is your DR5088RC configured in the windows configuration program?

What I see in the log is that:
OPC_MULTI_SENSE is both times decoded as transponderDirection=fwd
OPC_MULTI_SENSE_LONG is reporting different directions

That will confuse Traintastic.

Greetings,
Reinder

[vikr]

Hi Reinder,

@reinder

How is your DR5088RC configured in the windows configuration program?

Karst Drenth reportet, that the final firmware for the 5088RC was 1.4.3. Earlyer Versions are buggy.
Unfortunately i’ve only firmwareversion 1.4.2.

With which Firmwareversion do you use your 5088RC?

Any idea, why - with the same hardware, configured identically - Traintastic will be confused, but Windigipet seems to be able reporting the real direction?

I, ll try to change the firmwaresettings next time, but at the moment i`ve no time to test.
Do you have a complete list, which settings I should choose in the 5088RC with firmware 1.4.2?

Any experience withe the YD6016LN-RC? Which firmwareversion, how configured?

Greetings

vik

[DL7BJ]

Moin,

are you sure that WinDigipet use the real Railcom Data for the direction?

Greetings, Tom

[reinder]

Hi @vikr,

@vikr

Karst Drenth reportet, that the final firmware for the 5088RC was 1.4.3. Earlyer Versions are buggy.
Unfortunately i’ve only firmwareversion 1.4.2.

Mine is v1.4.2 too, al least that is what the DR5088RC config too reports as latest version. To be sure I’ll have to check with the real device which is in a storage box.

@vikr

Any idea, why - with the same hardware, configured identically - Traintastic will be confused, but Windigipet seems to be able reporting the real direction?

The challenge with the OPC_MULTI_SENSE message sent by the DR5088RC is that you can configure it to have three different formats:

• No direction information
• Direction in sensor address
• Direction in loco address

Traintastic (or WinDigiPet, or other software) must intrepid this the same, else it won’t work as expected.

Can you change the OPC_MULTI_SENSE direction setting to None:

@vikr

Any experience withe the YD6016LN-RC? Which firmwareversion, how configured?

No, not yet, I don’t have one yet. But I expect it will work with Traintastic, as the LocoNet messages are identical to those sent by the DR5088RC.

Greetings,
Reinder

[DL7BJ]

Moin Reinder,

as you know, all these software uses often his own tracking information and not always the Railcom data. I have found some articles about that, with links to the WinDigipet site, but it seems, it’s down.

If you don’t know what other software actually uses for the display, whether it’s own tracking data or real time data from a RailCom detector, I wouldn’t put any stock in it at all.

Greetings, Tom

[vikr]

Hallo Tom,

@DL7BJ

are you sure that WinDigipet use the real Railcom Data for the direction?

very sure!
Windigipet and traintastic are working in all my here presentet settings as pure graphical track-monitor, driven always manually directly by real throttle or as alternativ the graphic throttle. No automatic outside the decoder-settings.

Greetings

vik

[vikr]

Hi reinder,

@reinder

Mine is v1.4.2 too, al least that is what the DR5088RC config too reports as latest version. To be sure I’ll have to check with the real device which is in a storage box.

Can you change the OPC_MULTI_SENSE direction setting to None:
image475×308 14.6 KB

Thanks, probably next tuesday.

MfG

vik

[vikr]

@DL7BJ

as you know, all these software uses often his own tracking information and not always the Railcom data.

You are completely right! All these programms (iTrain, Rocrail, TC, Windigipet etc.) are using there own informations in there reposery, if there is a collision, they use theire stored data independent of the age of these stored data! (its a little bit like within Galilei and his observations of the moving earth…

But there is a reason! The hardware itselves is to often delivering inconsistent data. The 5088RC is one example. Unfortunately its the same with ECoS and there own Detectors (or even with Lenz). There ist not really a Referenz-Implementation for the complet way of the RailCom-Informations (and their context) from the Decoder to the user-gui.

So i`am rather hopeful, traintastic is doing it much better…

MfG

vik