开云体育

Dale, Your XML defines 5 panels. Your log shows 5 WARN messages. That is one WARN per panel. That is what I would expect. If I understand the JMRI code correctly, and if I understand the 3rd-party

Hey all, This quick-start guide is for viewing (and then copy/pasting) those "Build Reports" for when someone is seeking help with problem builds... -Pete-

steambigboy, I've just looked into this and in fact the DP definitions are setting the default in all modes to 3. But there's a recently-reported bug in JMRI that is causing the defaults to be ignored

The following files have been uploaded to the Files area of the [email protected] group. * How-To #002b - Viewing a Build Report (

Allen Your log shows proof of your problem. You are not talking to the command station, requests for anything are being ignored. Ensure that the com port is correct.? Ensure you are not using?

File moved to 'Problems being worked on' /g/jmriusers/files/ProblemsBeingWorkedOn/Allan%20Altheim -- Peter Ulvestad *Think before you post, try to be positive, and you do not always

No do not update to any test release. Update to latest production release. Jmri4.22 Check the notes. If you haven’t updated for a long time you will have to update first to a lower version. Tony

Have replaced the USB cable between PR4 & PC. Following is the sequence last attempted: Started Decoder Pro (DP) Started Sys Console Started Loconet Monitoring Closed WiThrottle Panel From DP All

The following files have been uploaded to the Files area of the [email protected] group. * /Console_Loco Log 16 Mar 21.pdf ( /g/jmriusers/files/Console_Loco Log 16 Mar 21.pdf )

Upload the xml data file to the group's ProblemsBeingWorkedOn folder and we can take it look at it. Dave Sand

Some time ago I read a string of posts about updating jmri. The problem someone had, seemed to be solved by a recommendation that the originator of the post update all releases between the older

Hey Mihael, Did you find an answer to your "leave and return" staging using the reclassify trick? -Pete-

cribstone, That's quite untrue. ESU locos can be set back to project-defaults (i.e. as loaded by LokProgrammer). The reset should be done on the Program Track, not Program on Main (ESU's advice). In

BTW, I tried recreating the logic for T38R and T38L and saving it.? Then restarted the system.? Didn't help - still reporting similar errors plus added in one more from an unrelated turnout.? I'm

The release notes for 4.22, 4.23.1, and 4.23.2 were updated yesterday. You may need to do a browser page refresh. Dave Sand

Should this be posted as a "known issue" in the release notes of 4.22?

Thanks Dave.? There are 2 error messages about siglets that could be causing the problem.? The others are about missing .py scripts which I temporarily removed in case they were causing the problem

Hello All, I have an Atlas HO Dash 8-40c with ESU Loksound5 DCC which I have been using in consist with an Athearn SD40.? I have an NCE Powercab, though mostly I've been running it via JMRI on an

Billybob, Please ignore my previous message #187704.? That log was from the first startup after installing 4.22 and has not appeared again on startup. Related to the other Warning messages, I have

I built an Arduino based block occupancy detection system using CMRI as the interface to JMRI. It worked great but I am now converting this system to the more robust CBUS interface. The old system