Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Jmriusers
- Messages
Search
Locked
Re: Mobile Control II and Side bottons
This is the question I asked them.
Topic:???????????????? Mobile Control II Your question:? I have bought a Mobile Control II and use it together with the Enginee Driver app. I have programmed the upper left side button to function 2 and this function is set to latching. I can get a long horn sound when I keep the function button on the screen pressed down but I can\'t get a long horn sound when I use the side button. I have asked a question on the JMRI forum and got an answer that this was hardware related. I also got another reply that one person had one Mobile Control II with the same problem as I have but he also had one Mobile Control II were he could get a long horn sound when he pressed the side button. Have you changed the hardware anytime which could explain this difference. Roland Levin? |
Locked
Re: Mobile Control II and Side bottons
Hi Matt
I have the same 'Kernel version' and 'Build number' as you but my 'ESU Input Services' - is only version 1.06. Your version 1.07 is the latest acccordingbtomtheir Update software for Mobile control II. I did your test with the ESU software and the upper right key activates then immediately de-activates the horn. I have written a question to ESU about this and asked them if they have changed the hardware. Best regards? Roland L |
Locked
Re: Complex use of logix to ensure a particular order of execution
Just noticed the change of subject.
You can have many conditionals in a Logix, they are calculated from the top to bottom, you can move them around so make sure the ones that overwrite another comes later. I have some Logix with over 30 conditionals in them. Usually for the modular layout I have one Logix per interlocking, that would be up to four signal heads and several turnouts each. Mike |
Locked
Re: How to install JMRI using OPENJDK
Sorry Matt, installing on a windows 10 machine. And installing JMRI v4.14.4.?
|
Locked
Re: Injecting a delay between turnout operations
It appears from a quick test that a route triggers in order of turnout number, not internal or sensors. So a turnout with a number higher than the turnouts in the route should react after the last turnout command is given.
I'm running into a similar problem on my old module that I've just installed signals on. It used to use routes for setting the turnouts (I did it quick for a modular meeting), but the decoder has a long delay between starting each motor (it only does one at a time) and the max delay in a route is 1s, much shorter than the decoder, meaning I can't get the program to workout when they have finished, so would have to have a 1 minute delay for the signals to ensure all turnouts have moved. Looks like I'll have to put this one into Logix where delays can be long enough. At least it will then be compatible with the newer modules, and I can have parallel moves. Mike |
Locked
Re: How to install JMRI using OPENJDK
Peter, Which operating system and version are you attempting the install on? Best regards, Matt H |
Locked
Re: Complex use of logix to ensure a particular order of execution
Dave,
Thanks I think I get all that.? I'll experiment with getting it right over the weekend. You mention "conditionals" rather than Logix.? Are you suggesting I can merge these three into one Logix with 3 conditionals within it, or is it just a turn of phrase? The conditional for the first set of actions will actually be destroyed by the second set - since the original tests that the routes are clear, and the second then sets the routes as occupied.? So the third action would probably need to be separate. To be honest I have no idea how to nest these conditionals anyway! Iain |
Locked
Re: Controlling loco from JMRI
Thanks Dave. You are absolutely right. I now have 2 throttles in JMRI, each independently controlling each of the 2 locos I have.
Yippeee? ?!!!!!! |
Locked
Re: Interpreting decoder type
Thanks Dave -> Changing Preferences -> Defaults from internal to NCE solved the problem.?
Thanks once again.? Woohooo ... Now, I can play with this some more :-) |
Locked
Re: Controlling loco from JMRI
¿ªÔÆÌåÓýThis problem has the same cause as your other question about interpreting decoder type. See my answer to that question: --? Dave in Australia On 10 Nov 2018, at 1:34 PM, tnmkumar_us <tnkumar@...> wrote:
I connected my JMRI through NCE USB to NCE Powercab.? |
Locked
Re: Interpreting decoder type
¿ªÔÆÌåÓýIf you get "Found mfg 123 (Masoth Electronic, GMBH) version 123; no such decoder defined.", and/or all CVs return a value of 123 and long address 15,227 it is 100% certain that you cannot communicate with the decoder and that one of two possibilities have happened: 1) Preferences->Defaults has Service Programmer (and possibly other items) set to Infernal. 2) Preferences->Connections has System Connection set to Simulator. Possibility (1) is the most likely. It would most likely have occurred due to a previous failure to open a connection. If there is no alternative to Infernal, you currently have a problem with the connection to your DCC system and you need to resolve the connection problem before proceeding. If an alternative is available select that, restart JMRI and try again. Warning, the Infernal problem can happen again in the future if you have any connection problems. See comments at: --? Dave in Australia In Create New Loco, when I "Read type from decoder, it says "Found mfg 123 (Massoth Elektronik GmbH) version 123; no such decoder defined". What do I need to do? |
Locked
Interpreting decoder type
In Create New Loco, when I "Read type from decoder, it says "Found mfg 123 (Massoth Elektronik GmbH) version 123; no such decoder defined". What do I need to do?
|
Locked
Controlling loco from JMRI
I connected my JMRI through NCE USB to NCE Powercab.?
I can see the Powercab on my JMRI NCE -> NCE show cabs In NCE -> Show NCE cabs, when I refresh, I see commands in NCE: Command monitor and also see the status of the Powercab - e.g. speed = 020 or 024 This tells me that a read communication between NCE Powercab and JMRI has been established How can I control my locomotive from JMRI -> send control commands to the Powercab? |
Locked
Re: Dispatcher - SML - auto-allocation problem
¿ªÔÆÌåÓýNotePad doesn't work well with many JMRI files. It doesn't understand the Mac/UNIX style LF line terminators we use, expecting the Windows CRLF style. As a result, all the file may show on a very long first line. WordPad is fine, but I'm sure NotePad++ has better features for JMRI work. --? Dave in Australia On 10 Nov 2018, at 12:12 PM, Steve_G <RailRodder@...> wrote:
As I recall notepad should work, turning off line wrap helps. |
Locked
Re: Dispatcher - SML - auto-allocation problem
Yep, just worked it out as you replied.. haha
Okay, I added sensors to my panel for simulating trains running around the inner circle and coming across the crossover into the inner circle. Setting starting sensors to active, creating auto-active trains for each train, and then clicking through the route of 50037 from block 01 to block 05 As soon as block 01 goes in-active, 37254 allocates to S06. And then 50037 allocates over the top. If I keep 50037 going, the both legs of a turnout that they depart using the same route, both go allocated for their seperate transits, showign that they are both deffinitely allocating at the same time and continuing on to their seperate destintions. When the initial overlap happens at LT5, JMRI system console spits out the following: ?
118089 [AWT-EventQueue-0] ERROR jmri.jmrit.dispatcher.AutoAllocate? - Allocation request section does not match active train next section to allocate
118102 [AWT-EventQueue-0] ERROR jmri.jmrit.dispatcher.AutoAllocate? - Section to allocate S01:S06
118105 [AWT-EventQueue-0] ERROR jmri.jmrit.dispatcher.AutoAllocate? - Active Train expected S06:S09
118309 [AWT-EventQueue-0] ERROR jmri.jmrit.dispatcher.AutoAllocate? - Allocation request section does not match active train next section to allocate
118310 [AWT-EventQueue-0] ERROR jmri.jmrit.dispatcher.AutoAllocate? - Section to allocate S01:S06
118311 [AWT-EventQueue-0] ERROR jmri.jmrit.dispatcher.AutoAllocate? - Active Train expected S06:S09
118313 [AWT-EventQueue-0] ERROR jmri.jmrit.dispatcher.AutoAllocate? - Allocation request section does not match active train next section to allocate
118315 [AWT-EventQueue-0] ERROR jmri.jmrit.dispatcher.AutoAllocate? - Section to allocate S01:S06
118316 [AWT-EventQueue-0] ERROR jmri.jmrit.dispatcher.AutoAllocate? - Active Train expected S06:S09
118317 [AWT-EventQueue-0] ERROR jmri.jmrit.dispatcher.AutoAllocate? - Allocation request section does not match active train next section to allocate
118318 [AWT-EventQueue-0] ERROR jmri.jmrit.dispatcher.AutoAllocate? - Section to allocate S01:S06
118319 [AWT-EventQueue-0] ERROR jmri.jmrit.dispatcher.AutoAllocate? - Active Train expected S06:S09
I think this is telling me that it was EXPECTING 37254 but 50037 allocated anyway, or the other way around.. either way it is logging the conflict we are seeing. In a way, I am relived I'm not crazy! Thanks Mitch |
Locked
Re: Dispatcher - SML - auto-allocation problem
As I recall notepad should work, turning off line wrap helps.
toggle quoted message
Show quoted text
Otherwise there is notepad++ that can be found here Steve G. On November 9, 2018 9:27:23 AM EST, "Mitchell via Groups.Io" <mitchell.scott93@...> wrote: Thanks Steve, --
Sent from my Android device with K-9 Mail. Please excuse my brevity. |
Locked
Re: Complex use of logix to ensure a particular order of execution
Iain,
toggle quoted message
Show quoted text
The Route duration will be the sum of the delays between turnouts. Without feedback, the last turnout will still be moving when the completion sensor has been set. I would not worry about block setting and final signal mast changes. It is possible the signal will change a few ms before the last block changes, but I doubt it will be noticeable. The additional sensor and conditional actually compensates for the lack of feedback with the added value of insuring that the blocks are set before the mast. With testing, the optimum delay time can be determined. In summary: - conditional 1: Triggered by panel button, check for valid states, set Route if OK. - conditional 2: Triggered by route sensor, set blocks, set sensor with delay to compensate for lack of feedback. - conditional 3: Triggered by delayed sensor, set signal mast. Dave Sand On Nov 9, 2018, at 4:00 PM, Iain <iain@...> wrote: |
Locked
Re: Complex use of logix to ensure a particular order of execution
Thanks Dave.? I have found the box on the Route table. It's obvious when you know to look for it!
Using that will provide me with a sensor set, then I write the next Logix for the block setting triggered by that sensor.? But that too will need to point to yet another Logix to set the signal, otherwise the signal may be set before the route is illuminated fully (longest is 8 blocks at the moment).? Unless there is a similar trigger that I haven't yet seen, I can only do that by making the signal trigger sensor a delayed set?? Maybe just a couple of seconds? Basically you are saying my interpretation of what I have read and what you have said is correct?? Iain |
Locked
Re: Complex use of logix to ensure a particular order of execution
Iain,
toggle quoted message
Show quoted text
Going off the deep end, think about this solution: A Route table entry has the ability to set a sensor state when the turnouts have reached the desired state. The could be used to trigger the final actions. I created a script that I use to simulate TWOSENSOR feedback when I am developing away from the layout. This could be adapted to provide virtual turnout feedback with an appropriate delay after 1 sensor goes Inactive and the other one Active. This emulates the behavior of a Tortoise. Dave Sand On Nov 9, 2018, at 2:56 PM, Iain <iain@...> wrote: |
Locked
Re: UK 3 aspect signal with feather using NCE PowerCab and TrainTech signal
Cracked it!!!
I assumed I was supposed to change the turnout state in the Logix, which certainly worked on the physical light.? Now changed to the Signal Mast Aspect and everything is now hunky dory!! Thanks for the pointers - I knew it must be me being dense! Torben |
to navigate to use esc to dismiss