开云体育

This one is making me nuts! So I started reading the code and I think I found the issue (maybe)…I have these two devices: ECoS - ECoS 50200 ECoSDetector RC - 50098 which only has four ports Custom

Hi Spuds, Thanks for your reaction! The fun I'm going to have is building stuff on top of the very basic JMRI things linke turnouts, signalling, sensors and throttles. I have no doubt that JMRI can do

So there's some conflict here - System names commence with MT We want channel name first Best practice as per?https://www.hivemq.com/blog/mqtt-essentials-part-5-mqtt-topics-best-practices/? (which I

SwissChris, Thanks helpful info!! Kind regards, Joseph

Bob, Went to the website great info!!? I think I'm heading in the right direction now. Thanks for the help Kind regards, Joseph

Dick L I'm running DCC++, JMRI 4.14+Rd060e0b, Java 1.8.0_191 on a Windows10 computer.? Model is KATO N gauge.? I have 3 KATO turnouts connected to a Digitrax DS64 defined as follows. ?

Actually the way it should be is /channename/MT, so /trains/MT/01? The channel name should always be first in the MQTT topic.? Chris

Folks, I'm seeking some clarification on the finer details of what topic structure we are proposing and how the system name will get defined for each MQTT device. ? Bob mentioned "system names should

Your end (and intermediate) goal, as written needs no custom or external scripts. All the functionality is already within JMRI. The hard part for you will probably be detection. For automated train

A variation of this issue came up about 18 months ago. See the message thread starting with #139664. At that time, with a lot of help from Dave Sand, I was able to modify a script written by Bob

I'm preparing an update for the Athearn RTR Eco definition but I'm no longer getting replies to my emails to Soundtraxx for more info, so can only add decoders that I have or someone who does that is

Joseph, I use both NCE for trains and Loconet for turnouts, sensors and signalling. More info is on my web site at http://www.quaker-valley.com/CTC/QV_CTCnew.html#DCC_Hardware As others have said, the

There are various methods of connecting Non loconet to loconet. Digitrax themselves gve circuits and there are a couple of circuits here in MRi. Railsync from NCE controller can be found

How to do the connection is in the link in my prior post: http://jmri.org/help/en/html/hardware/loconet/StandaloneLocoNet.shtml#rsfromncecs but you should probably read that entire page, particularly

Could you email me your panel file? (jacobsen@...) I’ll update it and send it back to you. Bob -- Bob Jacobsen rgj1927@...

Bob, I have heard this before in some online articles.? Please excuse my ignorance but, do you know where I can find anything on how to go about? connecting the NCE DCC signal to the Railsync on the

Bob: My example RR is old enough that the host computer that it started with was back in the dark ages... processors with clock speeds in Mega Hertz... So as the computer evolved the C/MRI bus speed

I have upgraded to JMRI Version 4.14 recently. The old DCC++ Connection prefix was DCCP, which is now showing as “This is a legacy prefix which should be migrated…” I believe that the correct

Graham, Please see my answers below. Am 07.01.2019 um 22:03 schrieb SettleDown: Because building the GUI is skipped too. I have to look closer on this to understand, whether there is a solution to go.

Don, In that layout we moved the RS-485 and the terminator to trade them. So now the terminator is at node 0 and the RS-485 serial is at the end past node 4. The way Bob had worded his statement of