开云体育

You must have changed something for this to happen.? Can you recall any changes at all you made to JMRI or your computer setup between when everything worked and you noticed your issues? -- Tom

Dick, I read it differently. I quote: "It became necessary to RE-install". That implies an existing installation, with (who knows?) any of panel files, scripts, roster, profiles, connected hardware.

Test release 5.11.5 of JMRI/DecoderPro is available for download. This is the next in a series of test releases that will culminate in a production release, hopefully in June 2025. It's really

Still need where speed can be controlled when using automation Tony

Wouter, He is not trying to get something that was working working again. He has upgraded to a completely new machine and installed from scratch. What I am suggesting is that he shouldn't try to

Don: True, everything seem to be working now. Thanks, Joe Sent: Friday, April 11, 2025 6:55 AM To: [email protected] Subject: Re: [jmriusers] Paragon4 (400a) Decoder Programming

*So, what type of turnout are you using? -* All signal masts are controlled by CT turnouts (CMRI Network). All signals correspond to their CT values as intended and function as intended when the

I could not disagree more. Much better to get working what was once working (albeit on other hardware), than to try to upgrade from something that does not work, in the (guaranteed vain) hope of a

A signal mast that is only a SML destination mast will automatically display Stop. Dave Sand

So, "No, but yes". "No", because you are not uning "signal heads". But "YES", because you are using "Output Matrix Mast" signals which each can use multiple "Turnouts". So, what type of turnout are

Richard, You have a modern computer, but are running very old software. Uninstall Java 8. It is a decade old now and no longer supported. Go to

*"Are you using flashing aspects?" -* We do not use any flashing aspects. *"you would be using turnout driven signal heads which are then on a signal mast using signal heads, correct?" -* I setup

1). I am seeing this with all signal masts on the layout. 2). It seems to be present on startup and then come and go after I let it settle for several minutes after startup. It seems like it chokes

Hunter, Are you using flashing aspects? Now with the masts being on CMRI, that means you would be using turnout driven signal heads which are then on a signal mast using signal heads,

Sorry for the trouble you’re having. Getting "the same result running the layout in simulation” pretty much rules out problems with the physical C/MRI network and LocoNet. So we need to look at

I use logix and a few custom scripts that only run during operations (rarely). The logix is primarily for telling the system a Digitrax LT switch is supposed to correspond to a CMRI CT switch. I also

Thomas, While I use a Digitrax EVOXD for main track power, on the programming track where I do all my programming, I use a Sprog 3. Would the possibility of a slot issue affect there? And bluntly,

Thanks Dan.? Keep forgetting that 1 train restriction.? Had my Arrival track set for pickups "any" Doug

Joe, I've also posted before about my own experience with CV 217 and Paragon3s. I've mentioned the values that have worked for me with various models (20-70), and that the trick on the programming

Are you using ANY "Logix", "LogixNG", or "Jython Scripting" which can cause a signal mast to change its indication? That could cause the "SML logic" to "oscillate" between indications - one from