开云体育

Eric, The other option would be having the buttons drive the AIU. Then JMRI would watch that and drive the turnouts. That would mean the turnouts only move in response to turnout commands known to

Eric, Monitoring mode would like it track all the commands (via the cab bus) to the turnouts. Like anything commanded by the throttles would be seen. But things like direct movement of the turnout

Well, the script was supposed to do nothing. I wanted to simulate pushing the turnout icon once on the Panel Pro Main Panel. Something happens that reports the physical state and updates the Main

Have to admit I have heard of scripts and no idea what Logixng is. I’m hoping to find someone to help me. With the amount of modellers out there I feel I can’t be the only one that would use

John: To make a long story short, in my app pushing the volume down button at idle applies 20% more brake for each push until reaching 100%. It latches. Pushing the up button when the brake is applied

Hi, Is it possible to set the metric system as a default for the blocks lengths? Thanks. -- --------------------------------------------- Jean-Louis

As a matter of interest if I were to also add some aspect type signalling would this decoder be appropriate? http://www.mollehem.se/index.php/en/loconet-components/signaldecoder-us-2-detail also

Your script does not do anything. It is getting and setting the JMRI turnout state which does not change anything. It appears that your goal is to get the "layout" turnout state and set the JMRI

Also I was attempting to draft a script that would ping each turnout in JMRI and return its current state. I note that the first time I touch the turnout icon in Panel Pro Main Panel, the turnout will

Ok but what was the discussion about "monitoring" mode. That sounded like it would provide the needed feedback. So, I am a bit confused by the above conversation about trying "Monitoring".

Eric, Yes, that's the usual way. Tortoise motors are nice, you have one set of contacts to power the frog and one for feedback. Set that sensor as ONESENSOR in the turnout table and it will follow

Currently I am using the AIU to monitor the status of BD20s. I have not used the AIU to monitor turnout position. To monitor turnout position with the AIU, am I correct in understanding that I would

Eric, Are the AIU conveying status of just the blocks or are they also monitoring the positions of the turnouts? By default turnout status is returned to JMRI from the command station which

I'm giving a clinic at noon both days that covers the high points of JMRI and LCC. It covers what's been happening for the last year and some hints of things coming up. It acts like a user group

I can't think of anything in engine driver that would cause that. Have a look at the Android system settings for sounds, and see if any of the 'Call', 'Ring' 'notification' or 'alarm' settings change

I would like to build the JMRI 5.11.2 test release some time this coming Friday, January 10th. Let me know if this is inconvenient, please. The next available time would be Monday January

Via USB, but there is a BT version (about 10 times the price, but then the price was < ?2) It actually has five 'controls' (turn right, turn left, press, press-turn right, press-turn left.) these

The beeps come from the phone, the device doesnt have a speaker (In answer to another question - its connected via USB)

Have PowerPro, 40 turnouts, Switch8 Mk2+Button Boards, and several AIU-01 Boards that I use for BD20 block occupancy sensing. I am running JMRI Panel Pro on Windows 11 and have good success with

Tom, I agree with you. My locos that don't have sound decoders yet aren't used much anymore. DCC was a great first step for independent control of trains without constant block power switching. But,