开云体育

Hello all I'm working on a passenger car lighting project so my question Is. Is there a easy way to program the digitrax TF4s 4 function to come on in different times.

Hi all, I'm having issues getting a LokCommander decoder by MD Electronics to work properly with JMRI. Here's the required information: JMRI version: 5.10+Rca461bd266 Java version: 21.0.3 OS: Windows 11 (build 10.0.22631) Computer: Acer Swift (Intel Core i7, 12 GB RAM) Other DCC devices in use: SPROG 3 DCC Programmer (only) Previous JMRI version: I have been using JMRI for over 10 years, but have only upgraded from a previous stable version. I'm using LokCommander decoders by Micron-Dynamics Electronics (Decoderwerk) (CV8 = 163). These are DCC decoders targeted at H0 scale locomotives. Here's what I'm encountering: Decoder Identification: "Identify Decoder" returns only the manufacturer (MD Electronics). No decoder model is detected. Decoder Address is correctly reported as 3. Function Mapping Issue: When pressing F0 in JMRI, nothing happens. Pressing F1 activates F0 lights. Pressing F2 activates F1, and so on. CV33–CV46 are correctly programmed with standard NMRA values: CV33 = 1 (F0 Forward), CV34 = 2, CV35 = 4 (F1), CV36 = 8, etc. Attempt to create custom decoder file: I created a file Decoderwerk_LokCommander.xml and referenced it in decoderIndex.xml. Placed both under C:\Users\bonde\JMRI\decoders\ The decoder does not appear in the selection menu when creating a new roster entry. No error message appears. Manufacturer’s support: I contacted MD Electronics directly. They were not familiar with JMRI and could not provide any CV map or integration support. What I’d like to achieve: Proper identification of the decoder in JMRI. Correct function mapping (F0 should activate F0, not F1). Get guidance on what might be missing in my XML file. Possibly contribute to adding this decoder to the JMRI decoder database. I’m happy to share my custom XML file and any logs needed. Thanks a lot for your help and for the amazing work behind JMRI! Best regards, Pablo (Santiago, Chile)

Seven years after posting this topic (link here in case my message title hack to bypass the system that "locks" messages after a period of time should not work), I think that it is time for an update. Recap: the original post and the timetable project In 2018, I was evaluating train control software for a layout that was then in planning. In particular, I was comparing JMRI with TrainController. After some discussion and helpful input from members here, I decided to use TrainController because the latter had more abstraction layers allowing for timetabled working with less work than JMRI. The layout ("Oxcott") has been built (track laying and electrics being largely completed in 2021), although, for complex reasons relating to other layouts that I am planning to use the same space that have to be built in a particular sequence, I have not completed work on that layout, and it is awaiting works on other layouts before completion. Nevertheless, I have been able to set up some significant automation with it. See the below videos for examples of what I have done: Timetabled working Coupling by computer Virtual extension Problems with TrainController However, TrainController has a number of problems of its own. The company (I believe a one man band) that runs it is untrustworthy: it/he routinely censors basic things such as bug reports on the forum, including requiring prior approval for all of my posts because I once wrote that I was "concerned" by something (I forget now what), the latest version of the software, which introduced threading to improve performance, has become unreliable in a number of critical respects relating to macros, which, at least in the version that I tried most recently, randomly failed to work as documented, information on what bugs that the updates fix is deliberately suppressed, and discussion of it censored. Once, I posted a bug report, which was met by an e-mail from the developer offering to look into fixing it on condition that I agree to pay him roughly ?3,000 if it should turn out that the problem with my macros that I had reported was not a bug. I spent some hours making very sure that what I had reported was a bug, then agreed to go ahead, giving him all the information that I had found from my extensive testing to assist him in tracking down the problem, but then he refused to undertake the work, citing some unspecified other project on which he was supposedly then working. Moreover, the licensing for the latest version requires a constant internet connexion, meaning that it is not suitable to use this software for layouts that may need to be taken to exhibitions where an internet connexion cannot be guaranteed. More than that, however, after using it for some time, even TrainController does not have the layers of abstraction that are really needed for proper timetable working. It does have one thing that JMRI does not, which is the ability to start train movements from a schedule. However, the basic system for doing this turned out to be inadequate for what I actually needed, and I had to use macros extensively in order to get this to work properly. Those macros are much harder to work with than code for anything that complex, and, as stated above, they can sometimes not work as documented, and the developer cannot be trusted to fix the code for them. I have also looked at iTrain, whose developer seems much more reasonable than that of TrainController. The current version, however, has even less in the way of abstraction than TrainController, and although the next version is rumoured to be imminent, it has not materialised yet and there is no telling what features may be in it. New projects The layout on which I was working in 2018 ("Oxcott") is too far along to change course on its automation now, but I am also working on other layouts which will in time need an automation solution. Some of these I intend to be able to take to exhibitions, so TrainController is unlikely to be suitable. Moreover, the ones that I intend to be able to take to exhibitions are simpler than Oxcott and, in par

I've been making some changes to my Layout Editor panel. After taking a break for a couple of days, the panel would load but is mostly unresponsive. Could not "wake-up" any of the 40-some CTC controlled turnouts/signals, except for the two double slip switches. I could also throw turnouts that are not CTC controlled but are included on the panel. I tried using several of the older panel files but got the same result. Pasted below is a screen shot of the session.log. I'm not surprised with the six error messages at the end as they all appear to be items I was working on but not completed. I'm wondering if the "Info" item just before the error messages might be the problem. I am using JMRI 5.10 and Java 17. The layout (Digitrax hardware) fires up just fine and I can aquire and run locos in the expected manner. Any thoughts? Thanks, John P.