开云体育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 would not be seen. The buttons to the Switch8 do not interface with the cab bus so the monitoring method would not know what they did. ? -Ken Cameron, Member JMRI Dev Team
? ? |
|
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 Panel if they are out of synch. It takes a second touch on the icon to change the turnout position. I just have not figured out what that first step is yet nor how to access that programmatically.
?
The main panel display is on iPads accessing the Panel Pro Web Server. That works well.
?
However, I wanted to supplement that with physical buttons located at the edge that can also change turnouts without going to the Main Panel. Below is an example of one such button that changes a crossover.
?
It would be very nice if activation of the local button would update the Panel Pro Main Panel.
?
The major reason I stopped building elaborate panels is to reduce physical wiring and make things more software driven. However, individual button controls like this are very nice to have especially in support of local operations. Adding another circuit to incorporate a sensor is another added piece of wiring infrastructure to install and maintain. |
|
Re: RFID triggering Move within operations
#operationspro
#paneleditor
#rfid
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 this.?
Thank you again?
Micheal |
|
Re: Enhancement idea for Engine Driver
#enginedriver
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 releases the brake. I believe this is a reasonable model of the prototype. Using the volume buttons for the throttle works very well for me. I don't have to look at the screen let alone touch it. I always use ED when operating at our museum club layout. So much better than using the clumsy DT602. We are not allowed(!) to incorporate momentum in any of our locos there. But if the speed step in ED is set to a high value then using the throttle buttons automatically simulate momentum. That is, pushing the up button and holding it will ramp up the speed but only somewhat slowly. You can always use the slider or the stop button to stop immediately.
?
Seems to me this concept would not be difficult to add to ED except for the incremental part. Just activate a configured function on the down press, deactivate it on the up press.
?
To make a short story long, consider that my app is part of a system that I developed for my own use called the Onboard Loco Simulator. It places a bit of hardware (ESP32 based) in the loco between a power source (track or battery) and the existing DCC sound decoder. It acts as a DCC command station, an MQTT client for commands and telemetry and a web server for configuration. It also acts as a simulator (like a really lame version of Flight Simulator) constantly computing acceleration as the sum of the forces acting on the loco divided by the sum of the mass of the train. Thus acceleration and deceleration curves are non-linear as they are in real life. There are a lot of features in this system that make it very prototypical feeling and fun to use. The most important is that the user controls power, not speed. Real engineers do not directly control the speed of their train by twisting a knob. The app I built communicates with the loco using MQTT which is a tried and true industry standard protocol. Locos communicate with each other for consisting using the same protocol. This system overcomes many of the shortcomings of using straight DCC. As an example, being bidirectional it can feed back data to the app like true scale speed and distance traveled. It requires no external DCC system to operate although it can use the DCC track voltage for power. I'm only using existing DCC decoders because I don't want to reinvent that wheel. Also I'm not smart enough. The ideal solution would be to have one piece of hardware, incorporating OLS and the existing superb sound and motor control capability of modern DCC decoders. Having that, we could say good bye and good riddance to DCC.
?
George
Edgewood, WA |
|
Re: Semaphore signals
#semaphore
As a matter of interest if I were to also add some aspect type signalling would this decoder be appropriate?
?
?
also I’m having a problem that when saving a panel not all (some do) the signal logic works when I reopen. I have to do a new discovery?
? |
|
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 first change color to its actual state. If I touch a second time it will physically change its state. Therefore, I was looking for a way to poll each turnout (without changing its position) and update Panel Pro Main Panel accordingly.
?
In Visual Studio Code with Copilot (ChatGPT) tried this code but I did not work. UpdateTurnoutState function was supposed to read state and then set turnout to that state without changing it - simulating what happens when you touch the screen once and it updates.
?
class setStartup(jmri.jmrit.automat.AbstractAutomaton) :
? ? def init(self): ? ? ? ? self.turnouts = jmri.InstanceManager.getDefault(jmri.TurnoutManager) ? ? ? ? return ? ?? ? ? def handle(self): ? ? ? ? self.waitMsec(500) ? ? ? ? self.updateTurnoutState("1001") ? ? ? ? self.waitMsec(500)
? ? ? ? self.updateTurnoutState("1002") # repeat for as many turnouts
?
? ? ?def updateTurnoutState(self, turnoutId):
? ? ? ? turnout = self.turnouts.provideTurnout(turnoutId) ? ? ? ? currentState = turnout.getState() ? ? ? ? turnout.setState(currentState) ?
? |
开云体育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 fine. It won’t matter if JMRI, a throttle, or a button tells a turnout to move. ? -Ken Cameron, Member JMRI Dev Team
? ? |
|
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 need to run an additional circuit from an AIU port to the contacts on the Tortoise Switch machine (that would close when the turnout is in a closed position) and back to the ground connection on the AIU. The AIU port would light up if the switch was closed. Then edit the Turnout table to assign that AIU port address as Sensor 1? |
开云体育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 remembers the last turnout commands seen by it. Sensors in JMRI are updated by it reading memory in the command station which polls the AIU boards while it is talking with all the other cabs. ? But the problem is the button boards talk directly to the Switch8 board and nothing goes on the cab bus to let others know about it. If you don’t have the AIU monitoring the status of the turnouts, that can get out of sync. ? Make sure you have reviewed the NCE page at for some of the other details. ? -Ken Cameron, Member JMRI Dev Team
? ? |
|
Going to the West Springfield MA Train Show?
开云体育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 meeting for people to ask questions. I also run a help desk (Stroh 115F) for one on one conversations and demos. ? I have a setup with programming tracks and a number of LCC products to show and tell. I have one set of nodes that I use for the development of the software running Morris Junction. That’s a Free-mo module set that is a fully signaled diamond crossing using LCC nodes and interfacing to the other modules via MSS (Modular Signal Standard). You can see that in action at the Mallory Complex 147. ? I support Op-Sig, the NMRA special interest Group on model railroad operations. Also supporting LD-Sig, the NMRA special interest Group on layout design issues who’s moto is “Only make new mistakes” meaning don’t make the mistakes that others have made before you. ? -Ken Cameron, Member JMRI Dev Team
? |
|
Re: Usb volume control with engine driver beeps
#enginedriver
On Wed, Jan 8, 2025 at 07:56 PM, James Parker wrote:
The beeps come from the phone, the device doesnt have a speaker (In answer to another question - its connected via USB) 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 it.
?
--
Peter Akers? [Brisbane - Queensland - Australia]? |
|
Locked
Test Release 5.11.2 on Friday
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 13th. Bob — Bob Jacobsen rgj1927@... |
|
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 Simple Signaling Logic.
?
I have selected Monitored for all my turnouts, but I still do not get an automated update of turnout position on the Main Panel after NCE Switch8 Mk2 / Button Board action changes the turnout position. I did notice that upon restarting, PanelPro now does seem to know the positions of all turnouts. Before, I had to run a script to set all the turnouts and get Panel Pro Main Panel updated.? |
Ken Cameron
Eric Troup
Micheal Hodgson
George Hofmann
Howard Witt
Peter Akers
Bob Jacobsen