Hi all,
I have been using MainWindowToBack.py to successfully send my main layout editor panel to the back of several other windows displayed on my monitor. That was using PanelPro 5.11.6, Java 17.0.14 on Rpi 400 with Bullseye OS. Updating the Pi400 to latest Bookworm using Labwc Wayland and MainWindowToBack.py no longer works. I have tried with Java 17.0.14 and Java Java 17.0.15. To test if the script was running I deliberately misspelt the panel name and I did get the "Did not find main window, probably need a longer delay" error message, suggesting the script is running. Also tried altering the self.wait amount to check for panels to no avail. I think its possibly a Java issue but a bit lost. The script momentarily appears in thread monitor with no error messages in system console, apart from when I deliberately misspell the panel name. All my other py scripts are working well. Cheers, John.
|
Re: Decoder not identified correctly ¨C MD Electronics LokCommander (functions offset, custom XML not loaded)
#definitions
On point (3).? ??
There is no need to manually edit "decoderIndex.xml", and if anything manual editing may create more problems.
The usual file-path for user-created decoders will be:?
\users\[username]\JMRI\[railroadname]\decoders
The default [railroadname] is "My_JMRI_Railroad.jmri",? and is set in the preferences for JMRI.??
Usually on creation of a new decoder file, its necessary to select the "recreate decoder index" from one of the menus - the command can take quite a while to run (minute or two).? That will incorporate the new decoder.? ?Before running
the command, I recommend opening the "system console" as that will report any major errors in your decoder file.??
Once the decoder file has been introduced, further editing of the file does not usually need the "recreate decoder index" to be run.??
On Point (1).? ?
JMRI reports CV8=163 as "WP Railshops".? ?
Whereas CV8=160 is "MD Electronics"
The NMRA file of manufacturers ID numbers agrees with JMRI.?
DecoderWerk's website manual for small decoders seems to agree with 160 as the value.??
There are a very small number of MD Electronics files within JMRI, and if they are for decoders which have similar CV structure to your decoder, they may be a good place to start editing.??
On Point (2).?
I'd suggest this is likely either a decoder problem, or a how it has been programmed (check both function mapping, and number of speed steps expected by decoder (usually CV29)).? ?
It is not likely to be a JMRI bug/fault.??JMRI will be sending a F0 command to the track when the F0 is pressed.? ?
If your setup sends the correct F0 to other locomotives with different decoders, then I'd suggest we can rule out both the Sprog hardware and JMRI from the problem.??
- Nigel
toggle quoted message
Show quoted text
------ Original Message ------
Date 31/05/2025 15:57:13
Subject [jmriusers] Decoder not identified correctly ¨C MD Electronics LokCommander (functions offset, custom XML not loaded) #definitions
Hi all,
I'm having issues getting a LokCommander decoder by MD Electronics to work properly with JMRI. Here's the required information:
?
JMRI version: 5.10+Rca461bd266
Java version: 21.0.3
OS: Windows 11 (build 10.0.22631)
Computer: Acer Swift (Intel Core i7, 12 GB RAM)
Other DCC devices in use: SPROG 3 DCC Programmer (only)
Previous JMRI version: I have been using JMRI for over 10 years, but have only upgraded from a previous stable version.
I'm using LokCommander decoders by Micron-Dynamics Electronics (Decoderwerk) (CV8 = 163). These are DCC decoders targeted at H0 scale locomotives. Here's what I'm encountering:
-
Decoder Identification:
-
"Identify Decoder" returns only the manufacturer (MD Electronics).
-
No decoder model is detected.
-
Decoder Address is correctly reported as 3.
-
Function Mapping Issue:
-
When pressing F0 in JMRI, nothing happens.
-
Pressing F1 activates F0 lights.
-
Pressing F2 activates F1, and so on.
-
CV33¨CCV46 are correctly programmed with standard NMRA values:
-
CV33 = 1 (F0 Forward), CV34 = 2, CV35 = 4 (F1), CV36 = 8, etc.
-
Attempt to create custom decoder file:
-
I created a file Decoderwerk_LokCommander.xml and referenced it in
decoderIndex.xml.
-
Placed both under C:\Users\bonde\JMRI\decoders\
-
The decoder does not appear in the selection menu when creating a new roster entry.
-
No error message appears.
-
Manufacturer¡¯s support:
What I¡¯d like to achieve:
-
Proper identification of the decoder in JMRI.
-
Correct function mapping (F0 should activate F0, not F1).
-
Get guidance on what might be missing in my XML file.
-
Possibly contribute to adding this decoder to the JMRI decoder database.
I¡¯m happy to share my custom XML file and any logs needed.
Thanks a lot for your help and for the amazing work behind JMRI!
Best regards,
Pablo?
(Santiago, Chile)
|
Re: Decoder not identified correctly ¨C MD Electronics LokCommander (functions offset, custom XML not loaded)
#definitions
In step 3 you need to do a ¡°rebuild decoder index¡±. That will pick up your new definition and add it to the list
You can do a ¡°validate¡± first to check for errors
Phil G
toggle quoted message
Show quoted text
On 31 May 2025, at 16:01, vspec034 via groups.io <vspec034@...> wrote:
?
Hi all,
I'm having issues getting a LokCommander decoder by MD Electronics to work properly with JMRI. Here's the required information:
?
JMRI version: 5.10+Rca461bd266
Java version: 21.0.3
OS: Windows 11 (build 10.0.22631)
Computer: Acer Swift (Intel Core i7, 12 GB RAM)
Other DCC devices in use: SPROG 3 DCC Programmer (only)
Previous JMRI version: I have been using JMRI for over 10 years, but have only upgraded from a previous stable version.
I'm using LokCommander decoders by Micron-Dynamics Electronics (Decoderwerk) (CV8 = 163). These are DCC decoders targeted at H0 scale locomotives. Here's what I'm encountering:
-
Decoder Identification:
-
"Identify Decoder" returns only the manufacturer (MD Electronics).
-
No decoder model is detected.
-
Decoder Address is correctly reported as 3.
-
Function Mapping Issue:
-
When pressing F0 in JMRI, nothing happens.
-
Pressing F1 activates F0 lights.
-
Pressing F2 activates F1, and so on.
-
CV33¨CCV46 are correctly programmed with standard NMRA values:
-
CV33 = 1 (F0 Forward), CV34 = 2, CV35 = 4 (F1), CV36 = 8, etc.
-
Attempt to create custom decoder file:
-
I created a file Decoderwerk_LokCommander.xml and referenced it in
decoderIndex.xml.
-
Placed both under C:\Users\bonde\JMRI\decoders\
-
The decoder does not appear in the selection menu when creating a new roster entry.
-
No error message appears.
-
Manufacturer¡¯s support:
What I¡¯d like to achieve:
-
Proper identification of the decoder in JMRI.
-
Correct function mapping (F0 should activate F0, not F1).
-
Get guidance on what might be missing in my XML file.
-
Possibly contribute to adding this decoder to the JMRI decoder database.
I¡¯m happy to share my custom XML file and any logs needed.
Thanks a lot for your help and for the amazing work behind JMRI!
Best regards,
Pablo?
(Santiago, Chile)
|
Re: LogixNG Table example: yard ladder Table?
#logixng
I am delighted with your response Dave! So many thanks, I will review it the coming week.
Today I just returned from my sailing trip, but tomorrow I am off again for another three days of sailing, back Tuesday evening or Wednesday morning.
I will get into this and respond by Wednesday.
I appreciate your input so much,
Erik
?
|
Decoder not identified correctly ¨C MD Electronics LokCommander (functions offset, custom XML not loaded)
#definitions
Hi all,
I'm having issues getting a LokCommander decoder by MD Electronics to work properly with JMRI. Here's the required information:
?
JMRI version: 5.10+Rca461bd266
Java version: 21.0.3
OS: Windows 11 (build 10.0.22631)
Computer: Acer Swift (Intel Core i7, 12 GB RAM)
Other DCC devices in use: SPROG 3 DCC Programmer (only)
Previous JMRI version: I have been using JMRI for over 10 years, but have only upgraded from a previous stable version.
I'm using LokCommander decoders by Micron-Dynamics Electronics (Decoderwerk) (CV8 = 163). These are DCC decoders targeted at H0 scale locomotives. Here's what I'm encountering:
-
Decoder Identification:
-
"Identify Decoder" returns only the manufacturer (MD Electronics).
-
No decoder model is detected.
-
Decoder Address is correctly reported as 3.
-
Function Mapping Issue:
-
When pressing F0 in JMRI, nothing happens.
-
Pressing F1 activates F0 lights.
-
Pressing F2 activates F1, and so on.
-
CV33¨CCV46 are correctly programmed with standard NMRA values:
-
CV33 = 1 (F0 Forward), CV34 = 2, CV35 = 4 (F1), CV36 = 8, etc.
-
Attempt to create custom decoder file:
-
I created a file Decoderwerk_LokCommander.xml and referenced it in decoderIndex.xml.
-
Placed both under C:\Users\bonde\JMRI\decoders\
-
The decoder does not appear in the selection menu when creating a new roster entry.
-
No error message appears.
-
Manufacturer¡¯s support:
What I¡¯d like to achieve:
-
Proper identification of the decoder in JMRI.
-
Correct function mapping (F0 should activate F0, not F1).
-
Get guidance on what might be missing in my XML file.
-
Possibly contribute to adding this decoder to the JMRI decoder database.
I¡¯m happy to share my custom XML file and any logs needed.
Thanks a lot for your help and for the amazing work behind JMRI!
Best regards,
Pablo?
(Santiago, Chile)
|
SO, to recap, you can consist these same 2 locos using the
Digitrax throttles, and that works, but when you use JMRI to
consist them, that does not work for this pair, but does work for
other, similar pairs.? You said that the other pairs were done
some time ago with JMRI.
When you used the Digirtax throttles to do the consisting, did
you use the default "UniVersal Consisting", which does NOT alter
the CVs?? (That puts the consisting info in the command station,
and does not change the decoders.)
It occurs to me that you may still have the consisting for the
new pair in the command station if you tried that way, and that
when you also consisted them with JMRI to change their CVs, that
the command station may think that address 44 is not the top
address and won't send speed or direction commands to that
address.? Not sure how you set up the "44" and "172" addresses in
each case, so I am just raising the possibility, even though? I
would expect addressing "44" would work it the command station
thinks that is a top.
Please check the JMRI slot monitor and see if there is a consist
in the command station involving "44" and "172" or anything else
with "44", and, if so, what the "top" address is for any consist
involving address "44".? Also, please tell us if a throttle set to
address 44 is able to turn the headlight off and on.? That would
usually be a quick test, but? I don't know what else in the CVs
you may have programmed the different consist locos to do or not
do in a consist.
Steve Long
On 5/31/2025 6:25 AM, David Richards
via groups.io wrote:
toggle quoted message
Show quoted text
Steve,
?
Yes CV19 is set at 44 and 172 and I am using 44 as the
consist address.
?
Dave R.
|
Steve,
?
Yes CV19 is set at 44 and 172 and I am using 44 as the consist address.
?
Dave R.
|
Re: EngineDriver Beta v2.40.199 now available from the Play Store
#enginedriver
Can't you make all the functions the same? I don't have experience of those decoders but have been doing this with Lenz, Soundtraxx, ESU and TCS decoders for over 20 years.
?
Mike
|
Re: Select throttle in engine driver from JMRI rather than from Engine Driver UI
#enginedriver
On Fri, May 30, 2025 at 09:30 PM, Ken Cameron wrote:
You might be able to use something from the web interface and copy/paste the loco id into ED.
I am not familiar with the web interface (ED doesn't use it other than for the icons) so something may be possible that way.
?
--
Peter Akers?
[South East Queensland - Australia - UTC+10]?
|
Re: Simple way to move any loco between two points (automated)?
Nags,
It all depends on what you are trying to do. ?The help pages have a lot of useful information. ?An excellent resource is the jython directory in the JMRI install package. ?There are probably an example of just anything you want to do.
For me, LogixNG has reduced the number of scripts that I use. ?There are still some cases where a script works better, such as your move loco request.
Dave Sand
----- Original message ----- Subject: Re: [jmriusers] Simple way to move any loco between two points (automated)? Date: Friday, May 30, 2025 10:31 PM
On Sat, May 31, 2025 at 10:36 AM, Dave Sand wrote: I normally use the getXXX format with predefined items. Thanks, I'm still coming to terms with the structure. ? Besides get, set and provide any others that I should be aware of? ?
|
Re: Simple way to move any loco between two points (automated)?
On Sat, May 31, 2025 at 10:36 AM, Dave Sand wrote:
I normally use the getXXX format with predefined items.
Thanks, I'm still coming to terms with the structure.
?
Besides get, set and provide any others that I should be aware of?
?
|
Re: Simple way to move any loco between two points (automated)?
Nags,
Those should work.
I prefer to predefine items in a table before using them in a script. ?The "provideXXX" syntax will create a new item if one does not exist. ?This can lead to interesting side effects.
For example, if "mysensor" does not exist and you are using a NCE connection, provideSensor will try to create a sensor with the NSmysensor system name. ?This will fail since a NCE sensor has a numeric system name, such as NS123. ?
I normally use the getXXX format with predefined items.
When working with scripts, make sure that you have the JMRI System Console open. ?This is where script failures show up.
Dave Sand
----- Original message ----- Subject: Re: [jmriusers] Simple way to move any loco between two points (automated)? Date: Friday, May 30, 2025 7:20 PM
Dave, is this the correct structure? ? sensors.provideSensor("mysensor").setState(ACTIVE) ? memories.provideMemory("mymemvar").setValue(value) ?
|
Re: Simple way to move any loco between two points (automated)?
Dave, is this the correct structure?
?
sensors.provideSensor("mysensor").setState(ACTIVE)
?
memories.provideMemory("mymemvar").setValue(value)
?
|
Re: EngineDriver Beta v2.40.199 now available from the Play Store
#enginedriver
Thanks again.? I was hoping that would be the case but had not had a chance to try it.? My HUGE roster of 4 steam engines and one Diesel have decoders from 3 different mfrs (BLI, MTH, & Roku).? Naturally, all three use different Function keys for the same important functions (e.g., Sound on and off).
?
I don't suppose you have any magical way of simulating the start of a Diesel engine twice without a shutdown in between, do you?? That would solve the dilemma I have with my one Roku sound equipped Diesel.? This particular engine, a GE 44-ton switcher, actually had two prime movers and an engineer would be foolish to try to start both simultaneously.? The Function key to start the Diesel sound works very nicely but a second press of that key shuts down the prime mover.
|
Re: Simple way to move any loco between two points (automated)?
toggle quoted message
Show quoted text
----- Original message ----- Subject: Re: [jmriusers] Simple way to move any loco between two points (automated)? Date: Friday, May 30, 2025 4:35 PM
Delving into this further, are there commands to 1. Set a sensor 2. Set a memory or local variable ? -- 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: Simple way to move any loco between two points (automated)?
Delving into this further, are there commands to
1. Set a sensor
2. Set a memory or local variable
?
--
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: LogixNG Table example: yard ladder Table?
#logixng
Erik,
I have reviewed your uploads.
-- Tables --
You have four LogixNG Tables defined but you are only using IQT_AUTO_0004. ?You can delete the other tables. ?I recommend that you ?assign a user name to the table. ?A descriptive user name makes table references easier.
-- Local Variables --
When local variables are used to assign state settings, such as turnouts and sensors, the state names have to be in English. ?Here is the set turnout dialog: If you click on the "Show valid names" button, you will get a list showing the required English names and the language names. To set the turnout closed, the stateName local variable value needs to be "Closed".
There are at least three ways to deal with this issue. ?The first one is to fix the local variable value before using it to set the turnout. The second method is to use the local variable value and set the turnout directly. The third method is to use the English names in the CSV table cells. ?That requires changing the E3 and E5 expressions to also use the English names.
Note: ?You used "Rechtdoor" for turnout closed but JMRI uses "Rechtstand".
-- Turnouts/Sensors/Panel/Sensor Group/LogixNG --
The panel is still using the original turnouts and sensors. ?You need to edit each turnout and change the assigned turnout table entry. ?The sensors need to be replaced. ?The sensor group needs to be deleted and re-added with the new sensors.
There is an alternate way to accomplish the previous changes. ?Create the new CMRI turnouts and sensors without user names. ?Then "move" the user names from the internal items to the CMRI items. With a few exceptions that do not apply to this case, the references are updated automatically. ?This includes the panel, sensor group and LogixNG. ?Changing the user name by using "Rename" does the same automatic updates.
Once you have done a store and quit, you can delete the internal items during the next PanelPro session.
Dave Sand
----- Original message ----- Subject: Re: [jmriusers] LogixNG Table example: yard ladder Table? #logixng Date: Thursday, May 29, 2025 7:40 AM
I will be off until Saturday (gone sailing on the North Sea).
|
Have you read the CV19 values for those decoders to be sure that
they are
"44" and "172"?
If the CV19s are set, are you trying to control the consist with
address 44,
or are you trying to use an alias such as the lead loco road
number?
Steve Long
On 5/30/2025 9:44 AM, David Richards
via groups.io wrote:
toggle quoted message
Show quoted text
Hi guys,
?
Using Digitax DCC and programming decoders with JMRI.
?
44 is the consist address which sets CV19 to 44 for the lead
loco and 172 for the second loco running in reverse.
?
Have set up 2 pair of Locos in the same manner some time ago
and have checked CV values for those against the new pair and
everything appears to match. Addresses change of course. The
only difference is the earlier pairs used DN163K1Cs where the
later used DN147K1Cs, which are the latest for SD70MACs
according to Digitrax.
?
Dave R
|
Hi guys,
?
Using Digitax DCC and programming decoders with JMRI.
?
44 is the consist address which sets CV19 to 44 for the lead loco and 172 for the second loco running in reverse.
?
Have set up 2 pair of Locos in the same manner some time ago and have checked CV values for those against the new pair and everything appears to match. Addresses change of course. The only difference is the earlier pairs used DN163K1Cs where the later used DN147K1Cs, which are the latest for SD70MACs according to Digitrax.
?
Dave R
|
It would help to know what command station you are using and how
you consisted with JMRI.
I THINK you mean that you are using 44 as the consist address.?
Not sure if you wrote that to the CV19s in each decoder, or tried
to use the same long or short address for each loco, without
writing to CV19s in the decoders.
One possibility that comes to mind is that if you tried making
all of the long addresses? 44 and activated the long addresses,
those would not run on a Digitrax system, because Digitrax will
not use long addresses where they overlap with the short address
space (1 to 127).
Steve Long
On 5/29/2025 9:37 PM, David Richards
via groups.io wrote:
toggle quoted message
Show quoted text
Morning all,
?
Have recently purchased
2 new Kato SD70MACs and have fitted 2 new DN147K1Cs. Both
Locos run fine individually and when MU¡¯d with throttles.
When I have consisted
through JMRI using address 44 locos will not run. Have tried
different addresses with the same result.
I have 2 other pairs of
SD70MACs setup which run well and have compared CVs with
them and the new combination and all seems the same.
Hopefully someone can
offer a solution as I am stumped.
?
Many thanks,
Dave R from down under.
|
Erik84750
Peter Akers