Locked
Re: Best Command Station to use with Decoder Pro
Mark,
The difference with RailCom is that it is part of the
NMRA specifications, not proprietary, and it may be supported by
any manufacturer. As far as I know TCS and MRC (NEXXT) are the
only US manufacturers either supporting, or planning for RailCom
support. That is a manufacturer's marketing choice, and the
European companies have chosen to support it for some time. It is
probably supported by more systems than not. (at least recently)
Note that ESU decoders support RailCom, not just their own closed
ecosystem. The chances are pretty good that if you have a loco
with a modern European decoder, it already includes RailCom.
By ignoring RailCom the big US companies have effectively kept it
hidden from the US market place. Then they excuse themselves by
claiming that their users don't ask for it. Duh!
Dick :)
On 3/20/2025 9:29 AM, Mark Granville
wrote:
toggle quoted message
Show quoted text
Heath, As others have
indicated, the LokProgrammer is faster because it only works
with ESU decoders. Kinda like that question you asked about
function labels and BLI. Single manufacturer means special
methods can be used. DecoderPro uses the NMRA method because
it has to work with a wide range of manufacturer decoders. I
have read that there is faster reads IF (1) you have a
Railcom enabled command station AND (2) the decoder is
Railcom capable and enabled. It also allows reads using POM.
Mark Granville
|
Re: Anyone Have a Schedule Strategy to Put Long Train Into Multiple Staging Cassettes?
#operationspro
I'll try a strategy of changing the staging cassettes to a spur pool.
I think it will be an extra burden on the yardmaster, but we'll see.
--
Ken NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959) Loconet * JMRI 5.11.1 * OSX,Win10,Ubuntu
Blog: ?
Youtube:
|
Locked
Re: Best Command Station to use with Decoder Pro
On 3/20/2025 9:29 AM, Mark Granville wrote: Heath, As others have indicated, the LokProgrammer is faster because it only works with ESU decoders. Kinda like that question you asked about function labels and BLI. Single manufacturer means special methods can be used. DecoderPro uses the NMRA method because it has to work with a wide range of manufacturer decoders. I have read that there is faster reads IF (1) you have a Railcom enabled command station AND (2) the decoder is Railcom capable and enabled. It also allows reads using POM. _Or_ if you have: - a LocoNet system, and - Digitrax "Transponding" equipment, and - a mobile decoder that supports Digitrax "Transponding", and - the decoder has its "Transponding" feature enabled, and - that decoder is in a "transponding-enabled" track section, method. In this particular situation, mobile decoder CV reads are MUCH quicker than with "Service-mode" CV reads.
|
Locked
Re: Best Command Station to use with Decoder Pro
Heath, As others have indicated, the LokProgrammer is faster because it only works with ESU decoders. Kinda like that question you asked about function labels and BLI. Single manufacturer means special methods can be used. DecoderPro uses the NMRA method because it has to work with a wide range of manufacturer decoders. I have read that there is faster reads IF (1) you have a Railcom enabled command station AND (2) the decoder is Railcom capable and enabled. It also allows reads using POM.
Mark Granville
|
Tony
Head Only.
This means that only the head of the train can be detected.
You must specify a train length and all your blocks must have their lengths specified.
It works best if you use speed profiles.
When the head of train leaves a block, that block will not be released until the calculated position of the tail is beyond it. The section will not show occupied, but it will continue to show allocated during this period.
?
The very serious disadvantages are that if a train breaks in two another train? can crash into the tail, if the head stutters, stalls or plays silly Bs then the position of the tail is nolonger reliable and another crash happens. It cannot be used for forth and back running. I recommend the use of a remotely controlled power outlet for the command station and boosters, no keep alives, no analog, no resume on track power on, and that a twenty year old in top mental and physical condition keeps the remote control in their hand.?
?
Ghosts.
Ghost blocks were designed for those short pieces of track needed to join 2 switchs and keep the block routing table / SML straight. The fact they appear to work for switchs was pure dumb luck.? Do not use with head only. The train must always be in a detected block and not disappear into a ghost.
?
|
Locked
Re: Best Command Station to use with Decoder Pro
Crew:
Not reading the entire thread...
If sound loading or modification is a needed function the the Lok programmer is a must and independent of your DCC system...
Gotca is that Lok software is Windows only that might be the bigger issue. Anyone on Linux ever get it running under WINE?
Jim
|
Locked
Re: Best Command Station to use with Decoder Pro
Heath, ? I’ve been very happy with my TCS LT-50 using RailCom and LCC to interface with it. I can read LokSound decoders in under 5 minutes that way. ? -Ken Cameron, Member JMRI Dev Team
? ?
|
Locked
Re: Best Command Station to use with Decoder Pro
Guys,
I have also used a SPROG 3 for many years - never
let me down.
Gerry
On 20/03/2025 4:37 pm, Don Shroyer via
groups.io wrote:
All,
?
I've used a SPROG 3 for several years now as my programming
track interface to DecoderPro. Has been very reliable.
?
Regards
--
Gerry Hopkins MMR #177 FNMRA
Great Northern Downunder
|
Locked
Re: Best Command Station to use with Decoder Pro
As others have said, the ESU Programmer uses a proprietary closed method to communicate.?
The fastest route for decoders that support RailCom (includes ESU) via JMRI is a Command Station which supports Programming on the main Read by using RailCom.? ?That is massively quicker than any service mode (programming track) reading of a decoder.?
? There are several Command Stations which do this which are supported by JMRI.??
- Nigel
toggle quoted message
Show quoted text
------ Original Message ------
Date 20/03/2025 00:17:52
Subject [jmriusers] Best Command Station to use with Decoder Pro
I really like Decoder Pro. But, the ESU Programmer is significantly faster at reading/writing ESU decoders. Is there a command station or other computer to DCC interface that I can use with JMRI Decoder Pro that would give me similar read/write as the
ESU Programmer?
?
It is my understanding that the weak link of decoder pro is the computer to track interface.
--
|
Re: Signal Mast Logic
#sml
Hi
?
Thank you so much for your help with this.
It is very much appreciated.
?
I have just uploaded the latest exhib1.xml file to the same location.
?
Most issues are now solved but there are still a few minor issues remaining.
?
1. Tools check non-contiguous blocks highlights 6 errors.
Removing and re-adding those blocks does not solve the issue.
It would be good to fix the errors but they do not seem to be causing a problem.
?
2. Three of the buffer stop masts show an unknown state.
?
3. Related to 2. above, i have tried to add a mast at the anchor point A21 between Tr_SE6a and Tr_SW4f (to control movement in the reverse direction into the sidings ) but the SML generated for that mast is totally wrong.
I could generate the SML manually if the buffer masts worked.
?
Note that I am not concerned about the Masts Mst_SdS[1-6]
I will control them by scripting rather than SML.
I have attached these masts to the points in order to place them ( for display purposes only) onto the panel.
Is that the correct way to add masts that are for display only and play no part in SML ?
?
?
|
Locked
Re: Best Command Station to use with Decoder Pro
But, how often do you need to read all cvs anyway??
I typically do it ONCE per decoder, so the wait isn’t that onerous - even with a Ras Pi.
toggle quoted message
Show quoted text
On 20 Mar 2025, at 01:34, Breezlys via groups.io <livinthelife@...> wrote:
?
Heath,
?
?Not a command station, but my PR4 will reliably read all the CV's on a LokSound in about 20-25 minutes. That's not as fast as the LokProgrammer, because as Ross pointed out, the LokProgrammer uses a proprietary method. But it is quicker than at least
some command stations.
?
What I did before the PR4, and still do to a lesser extent, is open the CV's tab and tell it to read the page. Then I find something else to busy myself with until it finishes.
?
HTH,
Steve
"Breezlys"
?
?
?
?
|
Re: Block occupancy without resistive wheelsets
On Thu, Mar 20, 2025 at 04:15 AM, Dana wrote:
Brsidesa, you are trusting the operator to run at a very precise speerd. Probably impossible. Rspecially with track conditions and other issues.
Considering those issues, JMRI Warrants don't use train length but does provide for 'Automatic Speed Profiling'. Essentially calculating the time a train should take to traverse a block.
If you used the Roster Speed Profiling tool most likely you ran an engine running light over a straight level track. With Warrant dynamic speed profiling, measurements are made over straight level track, but also upgrade, down grade, curved gently or severely, running light or pulling 30+ cars. The track speeds are not going to be all the same for a given throttle setting. When merging, new values are averaged with the old, with the intention of a composite speed profile that reflects average use.
www.jmri.org/help/en/package/jmri/jmrit/logix/SpeedChanges.shtml
?
--
H.O. Australia (Layout in Progress)
Digikeijs DR5000 LocoNet
JMRI v5.10 DecoderPro/Warrants/CPE/SML/LogixNG
Java: OpenLogic jre-17.0.12.7 ? Windows 10
|
Locked
Re: Best Command Station to use with Decoder Pro
All,
?
I've used a SPROG 3 for several years now as my programming track interface to DecoderPro. Has been very reliable.
?
Regards
|
Either name will work. ?I use the user name.
Dave Sand
----- Original message -----
From: "Canadian Locomotive Logistics via groups.io" <CanadianLocomotiveLogistics= [email protected]> Subject: Re: [jmriusers] Changing signal Mast Aspect with jython #jython #signalheads
Date: Wednesday, March 19, 2025 11:11 PM
Mast name is system name or user name?
?
?
|
Mast name is system name or user name?
?
?
|
Locked
Re: Best Command Station to use with Decoder Pro
Thank You all for the very informative answers.
--
|
DEAR STEVE Can you fill me in on the apparently new features in automation - using train length instead of having your last car and if needed your middle car with resistive wheels and using a ghost section/block for each switch instead of using logix.
Can you give me links to the info in manual and is the info there adequate to understand and use these features.
It would be nice to eliminate cabooses or box cars at the ends of my unlit passenger trains and not have huge logix files to debug.
Tony
toggle quoted message
Show quoted text
On Jan 19, 2025, at 7:30?PM, Steve_G via groups.io <RailRodder22@...> wrote:
? Tony
When running under "No Signals" a train will not enter a section unless all switches are set to the exit section. Or that's the theory.?
Steve G.
?
|
The information is in the JMRI Javadoc. ?For signal masts, it is at?
Here is a Jython fragment.
mast = masts.getSignalMast('mast name')
if mast:
??? mast.setAspect('aspect name')
else:
??? print 'Mast not found'???????
The "if" statement checks to see if the mast was found. ?The name literals can also be variable names that have valid content. ? ? ??
Dave Sand
----- Original message -----
From: "Canadian Locomotive Logistics via groups.io" <CanadianLocomotiveLogistics= [email protected]> Subject: [jmriusers] Changing signal Mast Aspect with jython #jython #signalheads
Date: Wednesday, March 19, 2025 8:28 PM
Here is a list of signal mast i have set up
does anyone have the syntax for jython to change the aspect of the signal.?
i’m not finding it anywhere.?
|
On 3/19/2025 9:28 PM, Canadian Locomotive Logistics via groups.io wrote: Here is a list of signal mast i have set up
does anyone have the syntax for jython to change the aspect of the signal.
i’m not finding it anywhere. See JMRI's SignalMastFollower.py script. It uses: self.outSignal.setAspect(self.inSignal.getAspect()) This is what that script needs to do to make one signal mast reflect another signal mast's aspect. There are a number of requirements that make this a usable solution. One limitation is that the signal referred to in "self.outSignal" does NOT implement Signal Mast Logic! One can instead allow a script to "selectively-override" a mast's SML-defined Aspect information. One can implement Signal Mast Logic for the signal mast, and implement a "listener" to trigger a script bit that can determine when the aspect is not appropriate, and "override" the Aspect. Note that the mast might possibly show the original Aspect, briefly before showing the "overridden" Aspect. To avoid this, one _could_ implement something more like a "signalMastFollower.py" script, with optional Aspect-overriding, and displaying the overridden Aspect on the physical mast. This would probably not be appropriate for any kind of JMRI "automation", though, unless your automation mechanism does not rely on the overridden Aspect, or unless some other "hack" is used. (It _might_ be appropriate to create a new "signal mast" type for the "Prototype Signaling System", rather than hacking a Jython script, though! That might be a better solution than hacking the Aspect via Jython...)
|
Locked
Re: Best Command Station to use with Decoder Pro
Heath,
?
?Not a command station, but my PR4 will reliably read all the CV's on a LokSound in about 20-25 minutes. That's not as fast as the LokProgrammer, because as Ross pointed out, the LokProgrammer uses a proprietary method. But it is quicker than at least some command stations.
?
What I did before the PR4, and still do to a lesser extent, is open the CV's tab and tell it to read the page. Then I find something else to busy myself with until it finishes.
?
HTH,
Steve
"Breezlys"
?
?
?
?
|
Ken Heywood
Ken Cameron
Canadian Locomotive Logistics
Heath @ Human[c]ity Junction