Hey Charlie,
?
Q1)? This is accurate, and I have never found the need to filter other than through the schedule.? If you prevent E and L from leaving staging, you need not exclude those from any spur either.
?
Q2)? While you can filter car/load for C/I tracks at a yard, if you are filtering by "destination", then only those car/loads tagged with the allowed destination should make it into those C/I tracks.? You can further ensure that the cars allowed in must have Final Dests. but be aware, this might limit the occasional empty car type from making into this track if it could be then sent along to meet a schedule line request.? Think the odd empty not tagged (by another schedule) to go a specific place...
?
Q3)? The exception has a caveat... If the sending schedule points to a specific destination, the track at that location must also be named.? I.e. ship to [dest = Denver], + [track = Keebler Co.].? ?AND, there is the load conversion issue, whereby the custom load (since it is not named in a schedule) would convert to a default E, or if a custom empty, then conversion leads to a default L.
If you are looking to get a car pointed almost, but not all the way, to a spur, use the schedule to name a yard track that could then be served by the final train necessary to spot the car.? This will circumvent the "enroute" filter and the car will eventually get spotted.? Example of this might look like this...
?
Schedule at Spur A "ships" the boxcar of <parts> to Denver, Roper Trk 3.
Roper Trk 3 serves only downtown Denver Industrial Area using Train (DEN Tramp).
Denver, Keebler Co. (the receiving spur) schedule "receives" boxcar of <parts>.? This will "pull" the loaded boxcar in when there is adequate space on the spur.
?
Since Roper Trk 3 serves only DDIA, the car will not be allowed to leave and fill some other schedule calling for a boxcar of <parts>...
Be aware that the cars waiting in Trk 3 might lose their order of movement, if other cars are assigned to go straight to Keebler from another schedule.? This is because those cars would have named final dests. and be counted as "enroute" cars for Keebler.? So, when you build the DEN Tramp, the waiting cars would be seen as overfills at Keebler...? ?Hopefully that all make sense.
?
Happy to help, hope it helps,
<Pete Johnson>
?
?
|
Obviously I'm new to these Groups too :)? The reply above was to Nags :)
|
I'm sure it's a very good suggestion, unfortunately I'm new to the JMRI and I don't understand much of what you wrote... :(
|
Thanks a lot for the suggestion of putting the delay in the connection settings - it worked great for routes: I removed the additional delay in the route configuration and routes work well now using the "main" delay set in the connection.
?
Unfortunately Dispatcher seems to ignore that setting... As soon as it starts allocating sections, it sends several turnout commands almost simultaneously and only some of them are executed by my decoder... :(
?
Pawel
|
Locked
Listening for webThrottle button changes
Does anyone know to get the throttle function buttons and add to their functionality, in jython??
?
I can get all the buttons of all opened windows, but adding the .actionPerformed listener to them seems to override their currently function.
?
So far I found 2 other ways to do this:
1. Send an ajax call from the webThrottle page, that happens on a button click, to change a sensor or memory variable which has a jython listener attached.
2. In a jython while loop, check for changes to the buttons state, and do stuff when state is changed.
?
The above methods work fine, but it seems like there should be a more proper JMRI way to do this.
|
On Sun, Dec 1, 2024 at 03:25 AM, <pawel.k@...> wrote:
Or some other trick that I could use to make me setup work with the Dispatcher?...
Just putting it out there, how about LogixNG with Execute Delayed to throw the subsequent turnouts.
This would run shortly after the first turnout changes, and progressively for each turnout.
?
--
H.O. Australia (Layout in Progress)
Digikeijs DR5000 LocoNet
JMRI v5.8 DecoderPro/Warrants/CPE/SML/LogixNG
Windows 10
|
Locked
Re: DecoderPro associated with decoder failure??
#nce
I would agree with Steve and others, odds of the decoders being bad are extremely low. Having been around DCC for 25 years I¡¯ve never seen or heard of a case where a decoder was truly failed by faulty decoder programming. All reports pointed to other issues. ? -Ken Cameron, Member JMRI Dev Team
? ?
|
Locked
Decoder Index Rebuild - entityExpansionLimit
When I do a decoder index rebuild, I see the following in the
console
19:34:22,124 ri.jmrit.decoderdefn.DecoderIndexFile INFO? -
update decoder index [AWT-EventQueue-0]
Warning: org.jdom2.transform.JDOMSource$DocumentReader:
Warning: org.jdom2.transform.JDOMSource$DocumentReader:
Is this something to be concerned about?
JAVA 17 on a Ras Pi
Thanks
Phil G
|
Locked
Re: DecoderPro associated with decoder failure??
#nce
?
David /KarenWoomer writes in part:
?
"Then it goes on the rails, and operates just fine with the new programming.? But THE NEXT DAY, when I try to run the loco, it will not move.? Often, the lights and sound will work, but sometimes none of it works.? Back to programming track, review programming, save it again, and back on the rails with zero results - does not run.? CS-105 has worked well and has been used in several op sessions with no problems."
?
?The first things I would check/review are the instructions for the decoders involved.? Current generation decoders have a variety of "start up" options, and they don't all do it the same way.? Lots of "it won't run" problems on the various DCC lists have been resolved when the OP takes the time to read, understand, and follow the features the manufacturer has provided in the decoders.??
?
I'm not saying that's the problem in this case, but it costs nothing but a bit of time to test this out.
?
"I pulled the decoders out of the locos and put them on the DTK - no motor control on any of them."
?
The same vendor specific features I mentioned above might be at play here.
?
"Decoder goes in the trash.? I have spent well over $200 in new decoders in the past 3 months, and THEY all get fried."
?
If you haven't emptied that trash yet I'd dig real deep and pull those decoders out.? They may still be good.
?
Decoder Pro can't do _anything to your decoders your DCC command station can't do.? JMRI tells your command station what standard DCC commands to send to the decoder, both to program the decoder and operate it.
?
Best regards,
?
Steve
?
Steve Haas
Snoqualmie, WA
|
Locked
Re: DecoderPro associated with decoder failure??
#nce
I have checked speed steps on all the non-working decoders, they are all set t0 28/128.
My JMRI version is 5.4+R9005ecb4ac.
|
Over time I have accumulated a lot of spurs with ¡°accept only¡± load restrictions. All spurs on the layout have schedules for receiving and shipping car/load combos. The long list of accepted car/load combos matches the list of car/load combos in the schedules for those spurs. This gets a bit cumbersome when changing schedules for industries.
?
Question 1: If I understand the program correctly it will not send a car/load combo to a spur unless it matches a schedule, even if many other combos are allowed on the spur. Therefore I could change all those spurs to ¡°exclude¡± ?where only default E and L are excluded. Is this correct?
?
Question 2: Same question for intervening tracks like yard C/I tracks. If a yard C/I track has its served locations set to only one location and all spurs at that location have schedules, will the program only deliver cars to that C/I that match the locations spur schedules? The C/I could be set to E2 (E and L) and still only receive cars matching the locations spur schedules?
?
Question 3: The exception might be where an originating spur schedule specifically ships a car load to another specific spur. The program would force delivery to the receiving spur even if the receiving spur did not have a corresponding schedule entry. I think Pete said ¡°it¡¯s goin¡¯ there¡±. Correct?
?
All questions assume the tracks are set to "serve" the corresponding rolling stock in the top setting under "locations".
?
Charlie in Northern Colorado
|
There is a connection specific delay you can add, but that would be for all turnout commands. It¡¯s worth a try, it is an additional configuration value in the connection. There may be other ways but that¡¯s a simple one to try. ? -Ken Cameron, Member JMRI Dev Team
? ?
|
Dispatcher simply sends the turnout commands, it is up to the turnout handler for a given interface? to know how to pace them.
?
For example? digitrax configurations have a setting Turnout Command Handling which can be set to "Spread" and/or an output interval.
?
Steve G.
?
?
?
?
|
I use three Modellbau Union new turnout decoders on my layout. Each controls eight turnouts (Kato Unitrack, with no feedback). They work great when turnouts are changed individually, but when more are changed in a fast sequence, the decoder is apparently not able to process it and only one or a couple of turnouts are switched, the others are omitted...
?
I encountered this problem first defining routes, but I fixed it easily by adding delay in the route configuration. Now routes take longer time to be set, but they work fine.
?
But I cannot find a solution for the Dispatcher... :(?
When it allocates sections, it apparently sends commands to all turnouts in those sections simultaneously (or in a very fast sequence). And my turnout decoders can't handle it - only the first called turnout on each decoder receives the command properly and changes, the others don't... And because there is no feedback available, JMRI thinks the turnout were changed fine, while in fact they were not, so the trains continue running onto wrong tracks with quite unpleasant results...
?
Does anyone have any idea if there is a way to inject delays between turnouts commands sent by the Dispatcher, when it allocates sections, like I did with the routes? I'm pretty sure there is no such option available in the standard JMRI interface, but maybe something can be scripted?
Or some other trick that I could use to make me setup work with the Dispatcher?...
|
Ian, ? I think you need to prove the USB device from the DCS52. ? One usual method is to: - Open a command window on the Linux system
- Go to the devices directory, ¡°cd /dev¡± will get you there.
- Execute this line (without the quotes) ¡°ls -lart |tail -5¡±
- That should show the devices by active date. Note the names.
- Plug in the USB from the DCS52.
- Repeat the command from #3, there should be something new in the list. That¡¯s what the system named it.
- Remove the USB to the DCS52.
- Repeat command in #3. That name should have left the list. This confirms the name.
? If that name isn¡¯t being offered in the JMRI connection, let us know what name you found. We can figure out why it isn¡¯t working right. ? -Ken Cameron, Member JMRI Dev Team
? ?
|
Locked
Re: DecoderPro associated with decoder failure??
#nce
Are you referring to different versions of JMRI?? I am still trying to learn JMRI and not too familiar with the different releases.? If I decide to install an older version, how do ili get rid of the defective one, or is it automatic?
On Sat, Nov 30, 2024 at 6:52, David /Karen Woomer <dkwoomer@...> wrote: I have a switching layout, and rarely consist.? But I have checked CV19 on all these decoders, it has consistently remained at 0 and was not changed.? Decoders have all been reset multiple times with no results. I will check the speed step settings. On Sat, Nov 30, 2024 at 2:20, uligg100 via groups.io <uligg100@...> wrote: I don't think JMRI can destroy the decoder hardware, but it can mess up the firmware. JMRI only sends commands to your DCC command station, which then communicates with the decoder.
Have you tried resetting your decoders to factory settings with CV8=8 (or similar)?
It could also be a problem with a different specification of the number of speed steps (14 or 28/128) between the DCC command station and the locomotive decoder. The digital commands in the two modes are different.
?
|
Locked
Re: DecoderPro associated with decoder failure??
#nce
I have a switching layout, and rarely consist.? But I have checked CV19 on all these decoders, it has consistently remained at 0 and was not changed.? Decoders have all been reset multiple times with no results. I will check the speed step settings.
On Sat, Nov 30, 2024 at 2:20, uligg100 via groups.io <uligg100@...> wrote: I don't think JMRI can destroy the decoder hardware, but it can mess up the firmware. JMRI only sends commands to your DCC command station, which then communicates with the decoder.
Have you tried resetting your decoders to factory settings with CV8=8 (or similar)?
It could also be a problem with a different specification of the number of speed steps (14 or 28/128) between the DCC command station and the locomotive decoder. The digital commands in the two modes are different.
?
|
I have selected DCS52 USB Interface
Serial Port:- ttyACM0 - this is the only choice I am offered
Command Station Type - DCS52 (Zephyr Express)
toggle quoted message
Show quoted text
The log shows you are trying to setup a Locobuffer USB for your DCS52 zephyr Extra.??
Since the DCS52 has built in PR4, why did you select Locobuffer as a connection type ?
Unless? you have and are trying to use a Locobuffer,? this might be your error. You should have selected the? DCS52 USB Interface in PREFERENCES and let it use the Integrated PR4.
Marc
|
Understood. I will do my own filtering. No worries. It may be useful to document this though.
?
On Sat, Nov 30, 2024 at 07:58 AM, Bob Jacobsen wrote:
I don¡¯t think you¡¯re doing anything wrong.
The message filtering is an idea that dates back to the very beginning of JMRI. Back then, there was a concern that typical home computers would have trouble keeping up with LocoNet, so the filtering was built in to the design. Turns out it wasn¡¯t needed back then, so IIRC it was never implemented. Definitely don¡¯t need it now...
Bob
On Nov 29, 2024, at 11:11?PM, Gopal Patnaik via groups.io <gopalpatnaik@...> wrote:
I am trying to add a LocoNet listener in a script as follows: TC.addLocoNetListener(1, handle_response()). I want handle_response to fire for slot messages only, so I set the mask to 1. However, handle_response fires for every Loconet message. Of course, I could simply ignore all messages except for the slot messages in handle_response, but this seems wasteful. What am I doing wrong?
Gopal
¡ª
Bob Jacobsen
rgj1927@...
|
I don¡¯t think you¡¯re doing anything wrong. The message filtering is an idea that dates back to the very beginning of JMRI. Back then, there was a concern that typical home computers would have trouble keeping up with LocoNet, so the filtering was built in to the design. Turns out it wasn¡¯t needed back then, so IIRC it was never implemented. Definitely don¡¯t need it now... Bob On Nov 29, 2024, at 11:11?PM, Gopal Patnaik via groups.io <gopalpatnaik@...> wrote:
I am trying to add a LocoNet listener in a script as follows: TC.addLocoNetListener(1, handle_response()). I want handle_response to fire for slot messages only, so I set the mask to 1. However, handle_response fires for every Loconet message. Of course, I could simply ignore all messages except for the slot messages in handle_response, but this seems wasteful. What am I doing wrong?
Gopal
¡ª Bob Jacobsen rgj1927@...
|
Ken Cameron
Bob Jacobsen