I have a Digitrax system using Version 4.19.5 running on windows 10 One of my locomotives has a DH165LO decoder along with a SFX004 sound decoder. How do I get Decoder Pro to recognize that this is a single unit.
Thanks in advance.?
Phil
|
Here's a link to the help:
Dan
|
Locked
Re: Can I change the decoder type after I create a entry
Yes thanks I fixed it just wondered if I could change it. Apparently not would be a nice feature to keep all the metadata and re read the decoder type like a dup with replace option.
Jamesq
On Mon, May 11, 2020 at 07:02 AM, Jamos Bond wrote:
I have another BLI Heavy Pacific I used rolling thunder (prolly should of used steam) and all function names are blank on throttle. They do have the same functions is there a way to change the decoder type?
You simply used the wrong definition.
Rolling Thunder definition does not have throttle function names simply because it does not use them.? This definition is to be used? to setup the receiver box once
it is attached to the DCC system using the provided cable for the DCC signal.? Nothing to do with the engine.
Rolling Thunder related CV's as they apply to the Paragon3 decoders (Diesel, Steam, Steam w/depleting coal, smoke)? are in the Paragon3 definition.
That Rolling Thunder definition should indicate? RECEIVER ONLY? Much confusion as it is.? Not the first time people get it wrong.
Marc
|
Locked
Re: Error on XML File should I be concerned?
Ok tell me when u have it I will update
On Tue, May 12, 2020, 2:12 AM Dave Heap < dgheap@...> wrote:
On 12 May 2020, at 9:45 AM, Dave Heap via < dgheap@...> wrote: In 2019 I changed functionLabels and soundlabels from fixed-length arrays to HashMaps to allow for planned expansions. But I forgot to update "locomotive-config.xsd" to reflect the changes.
As a result, direct XML validation of roster.xml will fail if any ESU Generation 5 decoders are in the current roster. But everything works fine.
Thanks for finding this. A fix is in the works at?.
?
Dave in Australia
?
?
?
|
Locked
Re: Turnouts - individual blocks or part of other blocks
Hi Steve,
Nothing beats hardware detection for switches separately as their own block. But as Tony said, it will add up moneywise. And in terms of wire. An alternative is to have the block sensors in JMRI, but without the hardware. In that case you need the logic (possibly in Logix) to calculate the expected occupancy taking into account train speeds (either measured or, more simple, expected), train direction, timing and neighbouring block occupancy. Less precision, a lot less money, less effort if you don't count creating the logic, which isn't entirely trivial.
Wouter
On Tue, 12 May 2020 at 11:08, SteveM < steve@...> wrote: Hi everyone,
With the aim of achieving layout automation either via warrants or dispatcher (rather than purely coding) when designing and laying out the track should turnouts be isolated blocks or can? they part of an exiting block. If a turnout is an isolated block then I suppose it would need it's own occupancy sensor rather if part of an existing block and able to be assigned the same sensor for the rest of the block. ?
I think I must be the slowest modeller at achieving some form of automation, trying to bring all the elements together and taking one slow step after another.? It appears with jmri you can achieve the same or similar results via different routes and it seems experience often dictates which route you take,? oh for some experience
thanks Steve
|
Locked
Re: Turnouts - individual blocks or part of other blocks
Dear Steve ? ?My 8x8 layout has almost 40 switches. Do you really want to buy detection units @ over $100.00 per 8 detections using digitrax for all your switches and run all those extra wires. The claim is that separate blocks for switches works best. ?It’s best if they are located on the end of the block if you dont want to isolate them. ?I pretend switches in middle of block dont exist. I have been testing automation using dispatcher on a 2 loop 4x2 layout for over 6 months, every day since the shut down and so far achieved running 2 engines on a single loop for about 4 minutes before failure occurs. ?Either my hardware works perfectly for a while and then does something bad or the software logic runs perfectly for a while and somehow loses track of things.
Tony
toggle quoted message
Show quoted text
On May 12, 2020, at 6:08 AM, SteveM <steve@...> wrote:
?Hi everyone,
With the aim of achieving layout automation either via warrants or dispatcher (rather than purely coding) when designing and laying out the track should turnouts be isolated blocks or can? they part of an exiting block. If a turnout is an isolated block then I suppose it would need it's own occupancy sensor rather if part of an existing block and able to be assigned the same sensor for the rest of the block. ?
I think I must be the slowest modeller at achieving some form of automation, trying to bring all the elements together and taking one slow step after another.? It appears with jmri you can achieve the same or similar results via different routes and it seems experience often dictates which route you take,? oh for some experience
thanks Steve
|
Locked
Re: Turnouts - individual blocks or part of other blocks
I'd say in an ideal world they'd be separate blocks but to save on detection I've made mine part of the block to which the toe of the turnout connects. I worked on the basis you couldn't enter that block from either of the diverging routes if it was occupied so you couldn't run onto the turnout. In the other direction you could exit the block via the turnout to one of the two diverging routes if the other was occupied. Does that make sense?
--
Chris White
|
Locked
Turnouts - individual blocks or part of other blocks
Hi everyone,
With the aim of achieving layout automation either via warrants or dispatcher (rather than purely coding) when designing and laying out the track should turnouts be isolated blocks or can? they part of an exiting block. If a turnout is an isolated block then I suppose it would need it's own occupancy sensor rather if part of an existing block and able to be assigned the same sensor for the rest of the block. ?
I think I must be the slowest modeller at achieving some form of automation, trying to bring all the elements together and taking one slow step after another.? It appears with jmri you can achieve the same or similar results via different routes and it seems experience often dictates which route you take,? oh for some experience
thanks Steve
|
I found it in my panel file and was able to fix it, but if you could please address this in the next version.
Thanks!
On Tue, May 12, 2020 at 3:36 AM Keith Ruberson via <keithruberson= [email protected]> wrote: Gents,
It appears in JMRI version 4.19.6 that Edit Turnout window does not save the Continuing Route Turnout State when done is selected. I would change it in the xml file if i knew where to look.
Thanks,
Keith Ruberson
|
Gents,
It appears in JMRI version 4.19.6 that Edit Turnout window does not save the Continuing Route Turnout State when done is selected. I would change it in the xml file if i knew where to look.
Thanks,
Keith Ruberson
|
Locked
Re: Error on XML File should I be concerned?
On 12 May 2020, at 9:45 AM, Dave Heap via < dgheap@...> wrote: In 2019 I changed functionLabels and soundlabels from fixed-length arrays to HashMaps to allow for planned expansions. But I forgot to update "locomotive-config.xsd" to reflect the changes.
As a result, direct XML validation of roster.xml will fail if any ESU Generation 5 decoders are in the current roster. But everything works fine. Thanks for finding this. A fix is in the works at?.
Dave in Australia
|
Locked
Re: Can I change the decoder type after I create a entry
On Mon, May 11, 2020 at 10:23 AM, Jamos Bond wrote:
It seemed to do so automatically I see no errors on the pages.
Errors are not? a required action or the rule. Sometimes things go right? and the full CV page is read. ? The more complex the decoder, the more possibility of? a ' fail to read' Marc?
|
Locked
Re: Can I change the decoder type after I create a entry
On Mon, May 11, 2020 at 07:02 AM, Jamos Bond wrote:
I have another BLI Heavy Pacific I used rolling thunder (prolly should of used steam) and all function names are blank on throttle. They do have the same functions is there a way to change the decoder type?
You simply used the wrong definition. Rolling Thunder definition does not have throttle function names simply because it does not use them.? This definition is to be used? to setup the receiver box once it is attached to the DCC system using the provided cable for the DCC signal.? Nothing to do with the engine. Rolling Thunder related CV's as they apply to the Paragon3 decoders (Diesel, Steam, Steam w/depleting coal, smoke)? are in the Paragon3 definition. That Rolling Thunder definition should indicate? RECEIVER ONLY? Much confusion as it is.? Not the first time people get it wrong. Marc
|
How does OpPro differently use yard tracks and classification tracks?
Michael Boyle
|
Royce,
In addition to Marc's suggestion to update to a newer version of JMRI, if you're trying to use the PR4 as a stand-alone programmer you should get rid of the PTB-100. It's not needed with the PR4 and anecdotal evidence indicates it actually prevents the PR4 from reading some makes/models of sound decoders.
HTH,
Steve
"Breezlys"
|
JMRI 3.10 is rather dated.
The Digitrax PR4, contrary o the PR3, prefers Direct Byte mode while the PR3 worked when in Paged mode.? Changes were added to later versions of JMRI regarding this preference.
So I suggest you try and use the PR4 in Direct Byte.
Marc
|
The car has to be on a C/I track for the restriction to be in place.? Look at your C/I tracks, and those cars could have restrictions on them. Again, don't use them and you won't have an issue.
Dan?
|
Locked
Re: Error on XML File should I be concerned?
Bob, On 12 May 2020, at 9:00 AM, Dave Heap via groups.io <dgheap@...> wrote:
I'm not seeing this problem at all with HEAD of Master.
Sound Labels 33 and 34 are valid in the code, needed for the decoder definition and are loading fine for me. I can't see where the schema error is happening. Found the problem: In 2019 I changed functionLabels and soundlabels from fixed-length arrays to HashMaps to allow for planned expansions. But I forgot to update "locomotive-config.xsd" to reflect the changes. As a result, direct XML validation of roster.xml will fail if any ESU Generation 5 decoders are in the current roster. But everything works fine. I'll push through a fix. Dave in Australia
|
Locked
Re: Error on XML File should I be concerned?
On 12 May 2020, at 12:19 AM, Jamos Bond < jambri@...> wrote: I'm worried if I upgrade jmri with that error I would get a blank roster due to that error. Can't I just modify the XML file to remove that entry?
On Mon, May 11, 2020, 10:16 AM Bob Jacobsen <rgj1927@...> wrote:
Thanks.? It’s saying that the num field in the sound label description can only go to 28, and it found 33? (not a particularly clear message though).
That check happens as the file is read, before the rest of the code processes it.? If 33 is actually something that the rest of the code can handle, you can run the jython/TurnOffXmlValidation.py script in the JMRI startup options. That’ll turn off this check.
I don’t know whether that 33 value will cause downstream problems, though.
I'm not seeing this problem at all with HEAD of Master.
Sound Labels 33 and 34 are valid in the code, needed for the decoder definition and are loading fine for me. I can't see where the schema error is happening.
James, what version on JMRI do you have?
Dave in Australia
|
Phil
By any chance do you know how jmri marks a car to prevent it from being picked up by a train using the same route that dropped it off. ?Is there a way for me to examine my car database ?or other place to see which are so restricted.
Tony
toggle quoted message
Show quoted text
On May 11, 2020, at 11:51 AM, Phil in gorgeous Young Harris via groups.io <philabernathy@...> wrote:
?Identical content (or change anything you want), but a different name.? JMRI will not allow you to have two Routes with the same name.
Phil
|
Jamos Bond
Christopher White
Michael Boyle