Re: Fast Clock on Engine Driver and LNWI #digitrax #enginedriver

#236897

On 11/30/2024 5:39 PM, Ken Cameron wrote:
Mike,
You would have to have the JMRI clock follow the LocoNet clock. Simple to setup in the clock controls in the Tools menu.This is not what Mike wants - he wants the LocoNet fast clock to follow "Real Time".  That is "doable", but requires different settings in the "Tools"->"Clocks"->"Setup Fast Clock..." settings than what you suggest.

And, depending on your hardware, there can be "issues", like some hardware doesn't like to be "set" to some specific times, and other 3rd-party hardware seems to interpret times differently than Digitrax throttles.

And, in general, Digitrax in specific, but LocoNet in general, _does not keep reliable track of time_, and LocoNet devices will generally "guess" when a minute should end, regardless wf when the "master" says it should.  This means that t LocoNet device can get ahead of the "master".

So just be sure that you do not "rely" on a LocoNet device to show "real" times!

Re: DecoderPro associated with decoder failure?? #nce

#236896

开云体育

?

Rick Uhlenkott comments:

?

“I had something similar happen with 5-9-1.? I had several decoders scramble during a session.? While re-configuring with 5-9-1, the decoder would suddenly stop responding during a second compare all.? After this happened to the? seventh or eighth decoder I had begun to suspect JMRI.? I cut my losses and re-installed 5-7-9, and have had no further incidents like that occur on the programing track.? With 5-7-9 I was able to recover all but three of the affected decoders, which are remaining quite stubborn and are still candidates for replacement.”

?

For starters, did you review and follow the instructions in the Release Announcement for this version?? Specifically, the comment about changes in the serial libraries and the request to contact the developers if any problems were encountered.
Not likely this is a problem inherent to JMRI.

One of the developers would have to confirm, but other than the potential issues discussed in the release notes this is unlikely to be an issue with the communication between JMRI, the computer, and the DCC system(s) in use.? If there were, this list would have heard of this complaint loud and often,? This hasn’t been the case, so it is more likely “local” issues are more likely the problem.
Over the years, the development community has created a very large set of test cases and runs them on a wide variety of hardware before the software is released. ?An issue such as this is unlikely to be missed.
Neither JMRI nor its developers can control the environment it runs in/on.?? Before one throughs rocks, one should make sure that all potential causes of problems _external_? should be eliminated.

????????????????????????????????????????????????????????????????????????????? i.??????? Was the download monitored to be sure it was complete and successful?

??????????????????????????????????????????????????????????????????????????? ii.??????? Was the installation completed and successful?

????????????????????????????????????????????????????????????????????????? iii.?????? Were the release notes read and understood prior to the download and install?? Were recommendation actions taken?

I’m not saying it is impossible for this to be a problem with JMRI, but other than the possible serial library issue already discussed in the release notes this is highly unlikely to be a JMRI problem.
It’s highly unlikely any of those decoders need replacement.? But if they do, it is not due to JMRI:

JMRI doesn’t talk to your decoders, it talks to your command station.? Your command station formats the commands sent to your decoder.
Instead of trashing them, put then aside for a later time and try them again.?

?

Best regards,

?

Steve

?

Steve Haas

Snoqualmie, WA

Re: DecoderPro associated with decoder failure?? #nce

David /Karen Woomer

#236895

I have been? through the manuals on all these decoders, and find nothing out of line.? Been through most of the CVs on them, also.

CONFIDENTIALITY NOTICE: This e-mail message (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any unauthorized review, use, disclosure dissemination, copying, forwarding or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient but do not wish to receive communications through this medium, please so advise the sender immediately.

On Saturday, November 30, 2024 at 01:31:15 PM CST, Steve Haas via groups.io <goatfisher2@...> wrote:

?

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

Re: Fast Clock on Engine Driver and LNWI #digitrax #enginedriver

#236894

开云体育

Mike,

?

You would have to have the JMRI clock follow the LocoNet clock. Simple to setup in the clock controls in the Tools menu.

?

-Ken Cameron, Member JMRI Dev Team

?

Re: How to add delay between turnout commands in Dispatcher? #dispatcher

#236893

On Sun, Dec 1, 2024 at 08:53 AM, <pawel.k@...> wrote:

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... :(

Yep, us mere mortals start off that way.

LogixNG isn't too hard to learn. Basically, it gives you a relatively easy way to get JMRI to "do stuff' using commands.

?

--

H.O. Australia (Layout in Progress)
Digikeijs DR5000 LocoNet
JMRI v5.8 DecoderPro/Warrants/CPE/SML/LogixNG
Windows 10

Parse error on permissive SML #logixng #sml

#236892

Hi,

?

I don't understand where can it be the problem. I want to implement a call of on the home signals of an station. I set the permissive on the block and all works correctly. I used the logixng to program the option. I can save correctly but the problem comes at the loading of the panel on a next session. When I load the panel I have a Parse error that says that:

?

Error on line 5256: cvc-enumeration-valid: Value 'PermissiveSmlDisabled' is not facet-valid with respect to enumeration '[Aspect, Lit, NotLit, Held, NotHeld, IsPermissiveSmlDisabled, IsPermissiveSmlNotDisabled]'. It must be a value from the enumeration.

?

I open the xml file and I modify the line indicated and write IsPermissiveSmlDisabled where it says PermissiveSmlDisabled and I save the file. I open the file on panel pro and it works but all related to the Permissive SML on the signal is blank and obviously it doesn't work. Why if the error indicates that it must be on a kind of value if you use it it doesn't work? The panel on origin was created on JMRI 5.3 but all the logixng conditions have been created on 5.8.?

?

Can someone help me?

?

Best Regards

?

César Alcalá

Fast Clock on Engine Driver and LNWI #digitrax #enginedriver

#236891

Hi

When I connect to Engine Driver via wifi the time shown is real time. ?When I connect via LNWI it shows fast time on a 7:1 basis. ?How can I connect via LNWI using real time and no fast clock? JMRI clock is set to computer real time.

Thanks

--

Mike from Calgary

Re: Accepted and excluded car/load combos on spurs and C/I tracks #operationspro

#236890

Thanks Pete,

?

This will save me lots of complexity and time. I hadn't thought about limiting the E and L shipments at staging. Good tip. I'm really liking schedules the more I get them deployed. I'll save your other tip for future use.

?

Charlie in Northern Colorado

Re: How to add delay between turnout commands in Dispatcher? #dispatcher

#236889

开云体育

Pawel,

?

Use the LocoNet Monitor and turn on timestamps to measure the delay or absence of delay. I would consider it a fault if Dispatcher was somehow bypassing the delay. But a trace with those timestamps would prove it.

?

-Ken Cameron, Member JMRI Dev Team

?

Re: Accepted and excluded car/load combos on spurs and C/I tracks #operationspro

#236888

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,

?

Re: How to add delay between turnout commands in Dispatcher? #dispatcher

#236887

Obviously I'm new to these Groups too :)? The reply above was to Nags :)

Re: How to add delay between turnout commands in Dispatcher? #dispatcher

#236886

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... :(

Re: How to add delay between turnout commands in Dispatcher? #dispatcher

#236885

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

Listening for webThrottle button changes

#236884

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.

Re: How to add delay between turnout commands in Dispatcher? #dispatcher

#236883

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

Re: DecoderPro associated with decoder failure?? #nce

#236882

开云体育

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

?

Decoder Index Rebuild - entityExpansionLimit

#236881

开云体育

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

Re: DecoderPro associated with decoder failure?? #nce

#236880

?

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

Re: DecoderPro associated with decoder failure?? #nce

David /Karen Woomer

#236879

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.

Accepted and excluded car/load combos on spurs and C/I tracks #operationspro

#236878

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