Vaios,

The DR5000 only works with DCC.? If your decoders are set to anything else (Marklin, Motorola, etc...), I could be wrong but I don't believe they will go.? I believe this is why you can read them and they run with a different controller.? Maybe of our European friends can weigh in since I'm not that familiar with some of those brands and protocols.??

You may also need to turn off RailCom since some decoders are not compatible.??

ESU decoders work just fine even with RailCom turned on.

Ryan

开云体育

Thanks for the pointer Dennis. I think the page is suitable for Debian Buster and there are a lot of options that I hadn't seen before as I was looking solely at the winehq web pages.

I will be sticking to the amd64 version (as opposed to ARM based systems used to control my layout software) for Wine so that should avoid architecture conflicts. That said the multiarch option is needed for i386/ 32 bit software.

I will try some things out and hopefully get a screenshot of the errors which may be helpful.

I just wish Digikeijs had Linux (and presumably MacOS) versions for those not wedded to Microsoft.

Might want to read this.

https://wiki.debian.org/Wine

I do not think the Digikeijs Apps will run this way.

Have not seen anyone post that this works.

If some has, please post how to do it.

Dennis

I am a newcomer to this group and I may not know all the exact protocol needed here but I hope I can contribute.

After much cussing, mind-bending, abandoning for a time, trial and many errors I have finally got my Digikeijs DR5052 turntable controller do do what I want (operate a Fleischmann 9152C) in Rocrail. The problem is that there are just too many different options both in Rocrail and DR5052 - but naturally these MUST be present. Choosing the right options is the problem.

I am using the fl6915 controller option in Rocrail. I attach a screenshot of the Rocrail diagram and tracks to show my Rocrail Track settings. Note I cannot use the default DR5052 address (200) as it is in use.



I also attach a zipped spreadsheet (created in Libreoffice but using old .xls format) to record my settings. I must warn that the sheet does have address calculation formulae (not macros) which, although benign, might need virus checking etc.

If these are of use to anyone they are welcome to adopt/adapt as they wish for other devices.

Tony

Since MS Windows 7 support is due to end on Jan 14th 2020, I will no longer use Microsoft Windows, completing the switch to Linux (Debian) and as far as possible Open Source. I already use Rocrail in Linux controlling my DR5000, DR5088's and nearly my DR5052.

I have attempted to run the DR5000 configuration application in Linux/WINE but it gives errors and will not run. It will install in WINE but fails when invoked. Looking at the error window, it seems that there are registry problems.

Has anyone successfully set up Digikeijs apps to run in a Linux environment, either natively or in WINE? If yes, I would be grateful for advice about installing and configuration.

Tony

开云体育

It's quite likely that the decoder is tied up for the time it takes for the light to dim, and is ignoring further commands, so that might be worth trying.

Martin

Just thinking outloud, so this may be total nonsense Mike, but if you have more than one DR4018 could you split the three addresses per signal across the two (or more) units and speed the commands up that way?

The decoders are on different boards and modules so not practical. I did do a similar thing in our storage yards with a different make of decoders to give them time to charge before firing the next motor. I use the same make for the yard signals and they have no problems I can change all outputs as fast as the commands go out, but they can't do the nice signal effects that the DR4018 can. Which is a thought, I wonder if they work better if I remove the dimming action. I'll try that at the next meeting.

Mike

开云体育

开云体育

That is why you don't have a problem, I find putting delays between commands makes the decoder work. The problem when operating signals is that too much delay can make the signals momentarily show the wrong aspect.

I did contact Digikeijs and they said not to send commands too fast, but as signals are set by a code to three addresses per signal head they need to accept at least three rapidly.

Mike

开云体育

Yes Martin you found how to do it.

As to systems used, I've tried Lenz and the DR5000 with the same results. I know JMRI with Lenz sends several off commands, but I think one on command.

I use the same delays for each DR4018 as the problem is just in each decoder. I set a different delay for each output, I think with repeat twice. If I send a single command from the JMRI turnout table it always works. The other thing with JMRI is I set Logix outputs to always send even if JMRI thinks it already in the correct state, then if it does miss a command a rerun of the Logix normally corrects it.

Iain do you operate all turnouts at the same time or one after another?

Mike

开云体育

I also raised this question on the Sprog group and there's some interesting information there -?/g/sprog-dcc/topic/pi_sprog_with_dr4018_only/34303883?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,34303883

It seems that it is normal practice with train decoders to send commands several times because it's quite possible commands will be lost on the track. However the JMRI/Sprog setup is to only send accessory decoder commands once since the command should never be lost.

It could be that the Dijikeis command station (and possibly others) automatically send the command several times and therefore the problem isn't seen.

However this doesn't answer the question as to why the DR4018 doesn't react to the first command. Maybe it's saying "Are you sure?" :-)

I've raised this with support, I'll wait to see their response.

I would like to know if the problem is in the Pi-Sprog setup or JMRI or all Command stations.

Have done a lot of testing of the DR4018 with no problems, using all Digikeijs products.

One think i still need to do is try to blast the DR4018 with a lot of data.

Have one DR4018 setup with three different setups.

This is a interesting topic and if there is an issue we need to documents and post it here.

Dennis
Owner of the Forum

My word, I think he's got it!

I had a closer look in the turnout tables and set up the turnout in there. I then went to the Automation menu and set NoFeedback - times to try 2, Interval 100 (ms presumably, the minimum). I then set the turnout automation from "Off" to "NoFeedback" and it now sends the command twice and the DR4018 works as expected.