开云体育

Hi Bill, Apologies for the delay in progressing this. A fix has been merged into the core code, available for download from developer package release 3481

Inobu, I think I'm seeing one of the fundamental differences in the user interface vs the commands. Your statements make me think many of the commands have predefined actions and that a loco may have

It is definitely prototype that a locomotive might move, even move a train, in run 1. Depends on the locomotive. And it can do so with the locomotive brake applied. It will not happen with the train

Bob, Part of understanding a problem is to reproduce that problem. I offered a scenario that would allow you to see the issue and hand and you flatly refused. It would have taken you a minute to

Stephen Bartlett Oct 24 #165068 ( /g/jmriusers/message/165068 ) Idle and Run 1 have the same (Idle) RPM. the engine does not rev up until Run 2. The motor might start turning in Run

Because people are trying to help you understand how JMRI works. Several of the people who commented on this thread _actually_ _wrote_ the code involved. We may misunderstand what you’re saying,

Alan, Then why did you even comment on something you will never use. This is unbelievable.

Jim, There are 2 levels of legacy commands and base stations the Cab1L and the Cab2L. Your crane operates at Cab1L level. The Cab2L is the extended version and uses 9 byes that last being the

We understand that TMCC is different to DCC. What you don't understand is that the differences between the various hardware systems is dealt with in the underlying abstraction layer of JMRI. I don't

Alan, Will you please just try it. So you can see. Start up a TMCC connection in simulation mode. Open the TMCC monitor and Send TMCC command windows. Then pull up a throttle and set the address to

Ken, TMCC-2 has 253 commands. How can 28 function key support that? The TMCC-2 commands are completely different from the TMCC-1 structured. For example. If you were running a TMCC-1 engine on a

I think you are taking Bobs message the wrong way. JMRI is designed so that the user interface is the same whatever hardware is attached to it. So it is YOUR job to make an abstraction layer that

Rick, The frameserver takes "screenshots" of JMRI windows. So if the window has been reduced, that's what you get a screenshot of. One item of note, the window can be minimized and still work with the

Am 24.10.2019 um 20:12 schrieb Renato Albano Petersen FIlho: The official resource for "Locomotive sound files" (VSD files) within JMRI is https://github.com/JMRI/vsdecoder . Some variants of VSD

John: I couldn't think of anything I could actually do with my Sinclair even when it was new... even with extra RAM... The Heathkit H-8 was much better... An XP machine is fine for JMRI and the RR if

Bob, You could not have done it anyways. The coding is not completed in JMRI which is my point. Had you even bothered to try it would have been quite evident. But I'll follow through with what I said

Bob is exactly right. I have only a TMCC command station and I have some Legacy ( TMCC 2 ) . Equipment. They work fine for the features that the basic TMCC command set sends out but I cannot control

Thanks Steve, The size question is (trying to be more clear this time): If the panel is small enough that it fits within the frame then we can use it via the frame server, but if the panel does not

Hey guy! Sorry about the late reply, work got a little crazy for a bit there.. Bob, I was going to upload my file, but then I saw Dave's comment. I have just saved and opened my panel file

Besides python scripts run within JMRI, you also have the option of (for the operations roster, not the decoder programming roster) using the JMRI REST API for your database program to write to JMRI.