开云体育

Robert, I don't know of any system that supports 174 as a short address. AFAIK, the NMRA standard says all with the long mode address from 128 and above. -Ken Cameron, Member JMRI Dev Team

Chris, Are you sure the panel file is being loaded at startup time? -Ken Cameron, Member JMRI Dev Team www.jmri.org www.fingerlakeslivesteamers.org www.cnymod.com www.syracusemodelrr.org

Hi Chris, Apologies if I'm being too obvious, but - you did save your panels before quitting? Wouter

Hi Robert, I am totally unsure what you actually did. This is what I get from your description, but I cannot work out the rather important details. I put it on the program track *- Check.* It read as

Hello All, I am fairly new to JMRI but have used it in the past. I am using V4.14, (Java is updated), Windows 10. I am setting up my new layout and am having issues with all my turnout data

Hello everybody from Italy, I understand these old command stations may not be the main focus of development at the present time, but, since there are many people who still use them (they are quite

Hey newbie here so please be gentle! I have sent the last few months looking at you tube videos and systems until I am blue in the face. I am looking to build a layout in my loft. So initially I

Dear Robert, This seems to be a problem encountered often with many owners of BLI locomotives. I own a number of BLI N Scale locomotives, both steam and diesels. BLI locos are notoriously poor in

Last knight a club member came to me with a Broadway ltd Pennsy K4 and I put it on the program track, It read as short address 174, correct long address but with short bulleted I corrected that and

I believe JMRI wants a *Connection Prefix* , an *Optional Number* (I tested 9999) and then the *Unique* part. [So club layouts might need to put a "module serial number" in their Topics] The JMRI

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