开云体育

Moreno, Build 2696 or later should have all this fix. The problem was an incomplete interpretation of the LocoNet message received. Paul

Right click the roster entry, duplicate. Mick ________________________________ Mick Moignard m: +44 7774 652504 Skype: mickmoignard Sent from my iPad, so please excuse the typos.

Benny, I have created a fix for the color change during route setting problem. It sounds like your panel configuration is a good test case for debugging route selection. Dave Sand

I have done that several times. I have 2 turnouts half way to target sensor jmri always selects instead of the 2 closest to source sensor leaving the train half on track 1 and half on track 2. I put

It is an addiction. I don't care what people think or say. It is an addiction! [email protected]> wrote: -- John Griffin __________________________________ I've lost my dog and my

On the Roster Entry page, right click on the roster entry you want to duplicate. From the drop-down menu, select “Duplicate…”. In the input box that pops up, enter the id for the new roster

It’s really a feature of Python/Jython community, which strongly believes that indenting with spaces (not tabs) is the right way to go: Thus spake the Lord: Thou shalt indent with four spaces. No

Derek, Place the first engine on a programming track and create a roster entry for it. That is, select 'New Loco' and identify the decoder that the engine has. Once you do this select the CV sheet

Jerry, The tabs vs. spaces question can generate heated discussions. It has nothing to do with JMRI or Jython, it is a Python characteristic. The only rule is never mix tabs and spaces. I always

James, Each scheduled train has its own transit. This is required since the times are added as actions. This eliminates the shared transit limitation. An “active train” in the Dispatcher sense

If you were _only_ working on the tables (Logix et al), not panels, you can do: — Make copies of _everything__ — Load the old file, with panels — Load the new file, overwriting the older

Thanks Cliff and Bob. ?I’ve been opening the script output window but will now also open the system console and look into logging. ?Cliff - you solved the indentation issue: ?I thought it was

Bob, ? ? ?Everytime you save a panel JMRI saves the backup file.? I believe the folder is called Backup. Roger

That is an interesting idea, although I wonder how that will work in conjunction with the limitation that only one train can run a single transit at a time. Also, I wonder how easy that the UI would

Using DecoderPro, how can I read a sound decoder configuration and copy that config to another identical decoder. I have two locos with the same sound decoder installed in both and I want them both to

Your statement seems self-contradictory. Before programming an ESU LokSound decoder, it is essential that you get the correct default CVs for your project (one of thousands) into your project: ESU

Ok, I did a dumb thing.? I was editing my logix and before closing, it reminded me to save the configuration before exiting.? So I saved the configuration (only) from the menu on the logix table

I have a situation...I had a previous version, 4.10.X, of JMRI on my laptop and tried programming locos and it would say it wrote the changes but they would not show in the loco. I was to to check

Hello. ?I tried to change the DCC address on my NEW Atlas Gold Series GP7 HO locomotive which is factory equipped with an ESU LokSound Select Sound-Decoder. I have the Digitrax DCS240 and have it

Jay Using cable plugged into pr4. Start PanelPro. Create new connection for pr3 programmer, configure and save. Restart. Then if error still exists, I'm sure there's a faint hope clause, post the