That’s right. I’d need to map turnout to lock address anyway. My transits usually start with an allocation hold sensor so the transit is running but the route might not be allocated yet. How to determine if route has been allocated?
--
Ken NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959) Loconet * JMRI 5.11.1 * OSX,Win10,Ubuntu
Blog: ?
Youtube:
|
Ken,
The simple approach is to use a LogixNG CSV table that maps a transit name to the turnouts in the transit. ?When the transit is active while in ABS mode, the locks are enabled.
Dave Sand
----- Original message -----
Subject: [jmriusers] How to Identify Turnouts Activated by An Allocated Section #dispatcher #logixng
Date: Friday, March 07, 2025 9:18 PM
I have turnout controls (QuadLN_S) that use an auxiliary turnout address to lock out local fascia control.
These are locked when I run the layout in CTC mode (unlock by dispatcher with local crew request).
?
Now, when I run an ops session in ABS, I plan at least one passenger run in the schedule driven by JMRI Dispatcher.
I'd like to write LogixNG code that will activate the auxiliary turnout addresses when turnouts are allocated on a transit.
My issue is how to determine the turnouts allocated on the transit run.
Is there some object that listens for turnout allocation from Dispatcher?
--
Ken
NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959)
Loconet * JMRI 5.11.1 * OSX,Win10,Ubuntu
Blog: ?
Youtube:
|
I have turnout controls (QuadLN_S) that use an auxiliary turnout address to lock out local fascia control.
These are locked when I run the layout in CTC mode (unlock by dispatcher with local crew request).
?
Now, when I run an ops session in ABS, I plan at least one passenger run in the schedule driven by JMRI Dispatcher.
I'd like to write LogixNG code that will activate the auxiliary turnout addresses when turnouts are allocated on a transit.
My issue is how to determine the turnouts allocated on the transit run.
Is there some object that listens for turnout allocation from Dispatcher?
--
Ken NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959) Loconet * JMRI 5.11.1 * OSX,Win10,Ubuntu
Blog: ?
Youtube:
|
Re: command centre same loconet operation over and over and over and over in a loop
Darrell, your "photo attached" didn't make it. It might be very helpful to know exactly what messages are repeating. Without that detail, my guess is that you need to change "turnout handling" to "once".
--SteveT
|
Re: command centre same loconet operation over and over and over and over in a loop
Will try in morning, thanks
|
Re: command centre same loconet operation over and over and over and over in a loop
Reset your DS64. You may have a route configured and it is creating a trap (instruction loop that keeps cycling)
the the DS64 cannot get out of.?
?
Inobu ?
|
Re: command centre same loconet operation over and over and over and over in a loop
Darrell,
This is a result of a new 'feature' in the newer command
stations. If track power is off, then when you send some commands,
the commands get buffered by the command station, until it gets
full! (peanut sized buffer) Once it is full, then the command
station barfs and tells JMRI to resend the command. That is what
you are seeing and it will continue until you turn track power on.
Dick :)
On 3/7/2025 4:23 PM, Darrell via
groups.io wrote:
toggle quoted message
Show quoted text
Hi hope someone can help with this problem?
Trying
to upgrade to an DCS 210+ from dcs100. ? I have replaced the
command station and set up new 210+, everything works until I
hook up a computer to loconet via usb cable direct into
command centre or usb via PR4. ?Once I hook up to computer I
do a couple switch commands and after a couple of commands the
command station sends out repeating commands over and over.
?At this point the “Net” Status light goes from solid red or
slow blinking red to very fast blinking, the Solid Blue USB
light also goes into a very fast blinking mode. The DS64 I
sent the command to is quickly trying to throw the switch over
and over and over as well. ?My loconet monitoring log looks
like the photo attached. ?If I unplug usb it stops running the
command after a few seconds and command station works again
until I reattach a computer. ? I have tried it with two other
computers, ?a fresh download of Jmri with no previous files
attached, new usb cables, new interface cables to ds64, tried
a new PR4 as well the command station has the same behaviour.
?I did factory reset on command station hooked up a brand new
ds64 and still happens. ?I reinstalled the original command
centre and take the 210+ plus out of the system and the
computer and dcs 100 respond as normal.
?
I
contact the Digitrax help desk and they said they do not
support 3rd party hardware software etc, which I understand,
they went on to suggest I change my JMRI preferences which I
think I have done unless I am missing a step. ?I am open to
ideas and thoughts on this. ?At the moment I have the 210+ and
a Ds64 isolated on my workbench so I can try out any
suggestions thrown my way.
|
command centre same loconet operation over and over and over and over in a loop
Hi hope someone can help with this problem?
Trying to upgrade to an DCS 210+ from dcs100. ? I have replaced the command station and set up new 210+, everything works until I hook up a computer to loconet via usb cable direct into command centre or usb via PR4. ?Once I hook up to computer I do a couple switch commands and after a couple of commands the command station sends out repeating commands over and over. ?At this point the “Net” Status light goes from solid red or slow blinking red to very fast blinking, the Solid Blue USB light also goes into a very fast blinking mode. The DS64 I sent the command to is quickly trying to throw the switch over and over and over as well. ?My loconet monitoring log looks like the photo attached. ?If I unplug usb it stops running the command after a few seconds and command station works again until I reattach a computer. ? I have tried it with two other computers, ?a fresh download of Jmri with no previous files attached, new usb cables, new interface cables to ds64, tried a new PR4 as well the command station has the same behaviour. ?I did factory reset on command station hooked up a brand new ds64 and still happens. ?I reinstalled the original command centre and take the 210+ plus out of the system and the computer and dcs 100 respond as normal.
?
I contact the Digitrax help desk and they said they do not support 3rd party hardware software etc, which I understand, they went on to suggest I change my JMRI preferences which I think I have done unless I am missing a step. ?I am open to ideas and thoughts on this. ?At the moment I have the 210+ and a Ds64 isolated on my workbench so I can try out any suggestions thrown my way.
|
Thanks Ken. I've played around a bit with automation and wondered how little was required. Had some success with a small 4 block end to end?
Neil W
For automation, you need minimum contiguous block detection for the automated part of the layout.
I also recommend profiling your locomotives with the roster profiler.
Signals are not necessary to automate, but they help.
I defined all my control point signals as masts, most are virtual (no hardware).
With defined signal mast logic (SML), you can automatically generate sections.
Once you have sections, you can define transits.
Then you can create trains that run on those transits.
--
Ken NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959) Loconet * JMRI 5.11.1 * OSX,Win10,Ubuntu
Blog: ?
Youtube:
|
On Sat, Mar 8, 2025 at 02:47 AM, <peterparsons.pub@...> wrote:
I am glad I can do that virtually - as I dont want to wire anything else physically at this point - in case I 'learn' that I need/want to restart again.?
I'm simulating my layout using JMRI's Warrants method of automation. It's been a good way of learning things like signals/SML and LogixNG.
Should be able to transition that to the real thing over the next few months.
?
--
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
|
Re: Error message “Could not locate configuration file default_lcf.xml
Thank you very much for your help. The information you provided worked.
Kind regards.
|
Re: Decoder pro cant read decoder
I use digitrax dcs100 on my test layout which is where i program decoders.
? I do have a pbt100 and will try it. Decoder pro list of decoders under soundtraxx tsunami steam has about 4 choices and many sub-choices in each of those. ?Can you possibly look at it and guess which one is in the old big boy
Tony
toggle quoted message
Show quoted text
On Mar 7, 2025, at 3:55?AM, Mick Moignard <mick@...> wrote:
? You can’t read decoders on the main. You must use the program track.?
What command station are you using? This loco probably has a Tsunami-1 decoder, which requires a program track booster like Soundtraxx’s PTB-100 with older Digitrax command stations. ?You’re not using a DB150, by any chance? ?That one doesn’t have a readable program track at all.
Mick ________________________________ Mick Moignard Specialising in DCC Soundm: +44 7774 652504
The week may start M,T but it always ends WTF.
|
Re: Decoder pro cant read decoder
I do have a pbt100 and will try it. Decoder pro list of decoders under soundtraxx tsunami steam has about 4 choices and many sub-choices in each of those. ?Can you possibly look at it and guess which one is in the old big boy
Tony
toggle quoted message
Show quoted text
On Mar 7, 2025, at 3:55?AM, Mick Moignard <mick@...> wrote:
? You can’t read decoders on the main. You must use the program track.?
What command station are you using? This loco probably has a Tsunami-1 decoder, which requires a program track booster like Soundtraxx’s PTB-100 with older Digitrax command stations. ?You’re not using a DB150, by any chance? ?That one doesn’t have a readable program track at all.
Mick ________________________________ Mick Moignard Specialising in DCC Soundm: +44 7774 652504
The week may start M,T but it always ends WTF.
|
thanks Ken
?I was reading the dispatcher documtation last night and thought 'oh first I need to figure out signals'. I am glad I can do that virtually - as I dont want to wire anything else physically at this point - in case I 'learn' that I need/want to restart again.? Your comments help me with these next 'learn'n' to be done?
-p
?
|
For automation, you need minimum contiguous block detection for the automated part of the layout.
I also recommend profiling your locomotives with the roster profiler.
Signals are not necessary to automate, but they help.
I defined all my control point signals as masts, most are virtual (no hardware).
With defined signal mast logic (SML), you can automatically generate sections.
Once you have sections, you can define transits.
Then you can create trains that run on those transits.
--
Ken NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959) Loconet * JMRI 5.11.1 * OSX,Win10,Ubuntu
Blog: ?
Youtube:
|
Re: Decoder pro cant read decoder
On 3/6/2025 10:31 PM, Marc N Fournier via groups.io wrote: First off, no DCC System will READ on the Main without additional hardware. Not quite. I own a commercially-available DCC command station which _can_ read mobile decoder CV values "On the Main" from _some_ mobile decoders _without_ additional hardware. Owned it for a few years. There are some other DCC command stations, by different manufacturers, which can do so, too. But _all_ of these systems have limitations for allowing "Programming on the Main CV Reads", including: . Those command stations can support "reading of mobile decoder CVs On the Main" from only certain types of mobile decoders. Some of these solutions only support reading of mobile decoder CVs On The Main when using the DCC system manufacturer's decoders using its special electrical signaling. Other solutions support a different electrical mechanism that is aligned with the NMRA's optional "RailCom" feature. If the mobile decoder does not support the required electrical signaling solution, then the decoder cannot be "read" using the command station's special hardware which can otherwise support CV Reads when performing "programming on the Main". - Those command stations can support "reading of mobile decoder CVs On the Main" when the supported decoder decoder is on a chunk of track that is powered by the command station's DCC Track outputs. If the mobile decoder is located on track powered by a different "booster", it will (probably) not be readable "on the main". - Those command stations can support "reading of mobile decoder CVs On the Main" when the supported decoder decoder is configured to allow Programming on the Main "Read" access. If the decoder supports the Programming on the main Read" feature, but has it "disabled", then the mobile decoder will not be able to perform "programming on the main reads". Other restrictions may apply, like "certain manufacturers' decoders put so much electrical interference onto the DCC track signal that they can prevent Programming on the Main CV Reads from working reliably to _other_ decoders". In this case, it may be necessary to remove those badly-behaving locos from the command station's trackage when trying to perform Programming on the Main CV Reads. FYI - I believe that at least _some_ Tsunami mobile decoders _can_ have their CVs "read" via "Programming on the main" with a certain manufacturer's command station hardware. Check with SoundTraxx and the command station's manufacturer for confirmation.
|
Re: Decoder pro cant read decoder
You can’t read decoders on the main. You must use the program track.?
What command station are you using? This loco probably has a Tsunami-1 decoder, which requires a program track booster like Soundtraxx’s PTB-100 with older Digitrax command stations. ?You’re not using a DB150, by any chance? ?That one doesn’t have a readable program track at all.
Mick ________________________________ Mick Moignard Specialising in DCC Soundm: +44 7774 652504
The week may start M,T but it always ends WTF.
|
Re: Decoder pro cant read decoder
While not impossible, it’s VERY challenging to correctly change addresses on the main. Best avoided at all costs (you can easily end up with your loco misprogrammed!)
Set the address ON THE PROGRAMMING TRACK, then you can do everything else on the main
toggle quoted message
Show quoted text
On 7 Mar 2025, at 01:35, AD via groups.io <bklyns_baseball_club@...> wrote:
? Sorry i misread your message.
I did place the Athern big boy on the programming track and selected new loco and read the decoder.
Got no response and error message about an acknowledgement.
Thus i cannot determine what decoder is in the engine.
So i use another engine and have decoder pro identify its decoder. I then select programming on the main and put the bigboy on the main. ?I write the long address to the decoder and get message that there is no engine on the mainline.
So what do i now do
Tony
On Mar 6, 2025, at 7:43?PM, thomasmclae via groups.io <mclae5-lists@...> wrote:
?
First no reading with POM. (Programming on Main)
Place your Lok on the programming track and do new decoder, followed by read type from decoder.
read the main page to get the Lok address. Find the pages with stuff you want to change and read those pages t00. (All is best if you have the time)
Save that as roster entry.
The you can go to POM and select that roster entry, which has the address and other data.
You can now program everything except the address with POM.
--
---
Thomas
DeSoto, TX
|
Re: Decoder pro cant read decoder
That means decoder pro is looking for the engine on the programming track when it’s on the main . The ‘program on main’ is selected but whited out. Since i cant read the decoder i cant get the decoder pro to select ‘program on main’ using the big boy.
Yes it’s an old tsunami decoder but decoder pro lists many versions of that decoder under the title of steam engines and a bunch of different steam engines.. Do you know what version is in the bigboy and the challenger
Tony
toggle quoted message
Show quoted text
On Mar 6, 2025, at 10:31?PM, Marc N Fournier via groups.io <forfoum@...> wrote:
?First off, no DCC System will READ on the Main without additional hardware.
Second These Athearn engines used the older Tsunami decoder and they require a Program Track Booster (PTB-100) to READ on the Program track other wise they will fail on the READ.
There is no ACK involved in a WRITE on MAIN, so your last error indicator makes no sense ( no engine on Main ) as the system does a blind write on the main.
Marc
|
Re: Decoder pro cant read decoder
First off, no DCC System will READ on the Main without additional hardware.
Second These Athearn engines used the older Tsunami decoder and they require a Program Track Booster (PTB-100) to READ on the Program track other wise they will fail on the READ.
There is no ACK involved in a WRITE on MAIN, so your last error indicator makes no sense ( no engine on Main ) as the system does a blind write on the main.
Marc
|
Ken Heywood
Neil Watson