Keyboard Shortcuts
Likes
- Jmriusers
- Messages
Search
LogixNG some help requested
#logixng
I have a turnout that requires a 2-bit operation: two outputs for each direction (straight or divert), with pulsed output signal (on two outputs).
"Divert" or "Straight" are driven by two separate inputs: either of them pulsed.
?
For example: if Sensor_001 is pulsed 'low', then output Turnout_001 is pulsed 'low'. If Sensor_002 is pulsed 'low' then output Turnout_002 is pulsed 'low'.
Turnout_001 and Turnout_002 are two bits for the same turnout.
?
How should this be programmed in LogixNG? I am lost with all the possible parameters ("Add"/"Item"/ "Sensor" or "Turnout" or "Sensor Edge", ...
?
Thanks for any help and/or references,.. !
Erik
? |
JMRI import of separate track layers from Anyrail not working
#anyrail
Anyrail v7.8.3 export of separate layers is not working.
I have a track plan with an undersection and an upper section separated in two different layers.
When hiding one layer for export to JMRI .xml, and imorting into JMRI still the full track plan is shown leading to an unsightly spaghetti mess.
?
How to proceed to obtain just selected layers of track from Anyrail into JMRI?
?
And also, in the panel selection for turnouts I had to delete all 60+ turnouts individually, even thought the box "remember choice for next tile" is ticked. How to delete a selection of turnouts in Panels? |
Re: VSD dont work
#vsdecoder
Angel,
toggle quoted message
Show quoted text
This message points to an issue in a config.xml file. Look for the line <sound name="ENGINE" type="SD70"> "SD70" is not valid, use "diesel3" instead. Valid sound types are: configurable, diesel, diesel3, steam, steam1 Klaus Am 21.05.2025 um 04:36 schrieb Angel Mora via groups.io: Hello, good evening. I'm trying to set up my own VSD file configuration for JMRI, and after many attempts and modifications, I came across a message that hasn't let me move forward: "Unsupported sound type: SD70." I checked the .wav files and, of course, I had recorded them at 48 kHz as the sample rate, which I reduced to 11 kHz. I repackaged everything, but the message remained exactly the same. Can anyone tell me if this has happened to them and how they resolved it? Thank you very much. |
Re: Starting with JMRI sensor reading and signal output: help request
Erik, Look at?. Information on using AnyRail is at?. Dave Sand ----- Original message ----- From: "Erik84750 via groups.io" <e.arckens=[email protected]> Subject: Re: [jmriusers] Starting with JMRI sensor reading and signal output: help request Date: Tuesday, May 20, 2025 11:25 PM On Wed, May 21, 2025 at 03:33 AM, Ken Cameron wrote: Yes you have to put a Layout Panel together to explain to the SML what is where What is an "SML"? ? I just discovered the Layout Editor: is there any way to import from an external track plan editor such as Anyrail? If not then it is an immense task to draft a plan for a large layout witch, say, 60 or so turnouts; ... or are there 'shortcuts'? ? For three-lamp signals and "searchlight" single tri-colour LED's I have schematics that use block detection to determine signal colour, from an issue of Model Railroader of April 2001. ? Meanwhile thank the both of you for your comments, it is much appreciated! Erik ? |
Re: Starting with JMRI sensor reading and signal output: help request
On Wed, May 21, 2025 at 03:33 AM, Ken Cameron wrote:
Yes you have to put a Layout Panel together to explain to the SML what is whereWhat is an "SML"? ?
I just discovered the Layout Editor: is there any way to import from an external track plan editor such as Anyrail? If not then it is an immense task to draft a plan for a large layout witch, say, 60 or so turnouts; ... or are there 'shortcuts'?
?
For three-lamp signals and "searchlight" single tri-colour LED's I have schematics that use block detection to determine signal colour, from an issue of Model Railroader of April 2001.
?
Meanwhile thank the both of you for your comments, it is much appreciated!
Erik
? |
VSD dont work
#vsdecoder
Hello, good evening. I'm trying to set up my own VSD file configuration for JMRI, and after many attempts and modifications, I came across a message that hasn't let me move forward: "Unsupported sound type: SD70." I checked the .wav files and, of course, I had recorded them at 48 kHz as the sample rate, which I reduced to 11 kHz. I repackaged everything, but the message remained exactly the same. Can anyone tell me if this has happened to them and how they resolved it? Thank you very much. |
Re: Audio Icon on Web Panel - Java
¿ªÔÆÌåÓýVinny, Is the web browser on top? Or another app on top of the web browser? If the web browser is on top, is a non JMRI window on top of a JMRI window in the web browser? Daniel On 2025-05-20 03:31, Vinny DeRobertis
via groups.io wrote:
|
Re: Starting with JMRI sensor reading and signal output: help request
¿ªÔÆÌåÓýSince you are using CMRI, that means to JMRI the inputs are sensors and outputs are turnouts. You can built signal heads from the turnouts, that¡¯s the simplest way and easy testing. The you can make a mast of signal heads (even if only one head) and then use the Signal Mast Logic to run them. Yes you have to put a Layout Panel together to explain to the SML what is where. But once you do that, it will do the rest of the signal management for you. ? Using Logix or LogixNG for signals is a whole lot of work and easy to make mistakes. ? -Ken Cameron, Member JMRI Dev Team
? ? |
Re: Starting with JMRI sensor reading and signal output: help request
¿ªÔÆÌåÓýErik, I don't have any experience with C/MRI so I will leave most questions for others to answer. > 2. where to find tutorials on using LogixNG for driving output signals, based on sensor inputs? First, you need to ensure that JMRI can control the signals and listen to the sensors. JMRI is only able to control signals that JMRI can control, and listen to sensors that JMRI can read. After that, the documentation for LogixNG is here:
Daniel On 2025-05-20 05:54, Erik84750 via
groups.io wrote:
|
Re: C/MRI 72-Input node: how to configure in JMRI?
#cmri
OK, thanks BillyBob, that is good enough: the initiation code for the Susic (in my comment) is correct, I checked just now. I prefer a second opinion but for lack of that I trust in .. :) |
Re: Edit dialog boxes do not open with full width
Vince, That is some really weird behavior. If you are interested, rename or move the user-interface.xml file and see what happens. Dave Sand ----- Original message ----- From: "Vince Guarna via groups.io" <vince=[email protected]> Subject: Re: [jmriusers] Edit dialog boxes do not open with full width Date: Tuesday, May 20, 2025 2:20 PM Following up: I created a new config profile with both monitors plugged in. I'm leaving everything in the default location (~/Library/Preferences/JMRI/<profile>.jmri)? now even though I had no problem with that in the past. I set the new profile as active and then restarted JMRI. Skinny windows for the settings window and other windows such as all of the edit windows. I closed JMRI and unplugged the secondary monitor. Restart JMRI and everything appeared to work OK. I re-plugged in the second monitor and everything still appears to work as it has for years. I copied a tables file with a lot of data (turnouts, sensors, blocks, signals, LogixNG, etc) into the new profile. Restart JMRI and loaded the new tables file. Everything appears to display fine and all of the edit dialogs are full size as they should be. ? So, it's a little inconvenient to create a new profile but that's a rare event, of course. Most of the functionality is working OK so far so this is very usable. I'll keep plucking away and report back if any showstoppers crop up in the future. ? Thanks for the help, Dave. ? Vince |
Re: Edit dialog boxes do not open with full width
Following up: I created a new config profile with both monitors plugged in. I'm leaving everything in the default location (~/Library/Preferences/JMRI/<profile>.jmri)? now even though I had no problem with that in the past. I set the new profile as active and then restarted JMRI. Skinny windows for the settings window and other windows such as all of the edit windows. I closed JMRI and unplugged the secondary monitor. Restart JMRI and everything appeared to work OK. I re-plugged in the second monitor and everything still appears to work as it has for years. I copied a tables file with a lot of data (turnouts, sensors, blocks, signals, LogixNG, etc) into the new profile. Restart JMRI and loaded the new tables file. Everything appears to display fine and all of the edit dialogs are full size as they should be.
?
So, it's a little inconvenient to create a new profile but that's a rare event, of course. Most of the functionality is working OK so far so this is very usable. I'll keep plucking away and report back if any showstoppers crop up in the future.
?
Thanks for the help, Dave.
?
Vince |
Re: C/MRI 72-Input node: how to configure in JMRI?
#cmri
On 5/20/2025 1:32 PM, Erik84750 via groups.io wrote:
@billybob thank you for that complete answer.That will have to be answered by someone who knows the (Arduind?) code base you are using. And that isn't me. 2. How do you manage to include the 'B' before the input number?(You've answered this yourself.) |
Re: Engine and bell sounds work but no horn after decoder install
Thank you Heiko, that does help. I did not know that you could look at the projects online. Thanks for the links. According to the ESU description, the horn should be in sound slot 3 for this project. But it's not apparently. I have ordered a LocProgrammer to see what's going on, figuring I'll be able to put it to other uses since I have about 20 locos (purchased) with ESU decoders, and plan to do more ESU installs in others.
Best Regards,
Dan
? |
Re: C/MRI 72-Input node: how to configure in JMRI?
#cmri
I think i found the answer to my second question:
Alternate Numbering Scheme for C/MRI System NamesStill remains question 1: is this initiation for SUSIC 72 inputs, node address 1 correct: CMRI cmri(CMRI_ADDR, 72, 0, bus); |
Re: C/MRI 72-Input node: how to configure in JMRI?
#cmri
@billybob thank you for that complete answer.
?
I have a few questions on that:
1. "Your code would need to handle the C/MRI "Init" message as if it was an SUSIC.": CMRI cmri(CMRI_ADDR, 72, 0, bus);? .correct?
2. How do you manage to include the 'B' before the input number? |
Re: C/MRI 72-Input node: how to configure in JMRI?
#cmri
On 5/20/2025 11:38 AM, Erik84750 via groups.io wrote:
After some searching I discovered that a SUSIC can be configured for 24 or 32 bits, and selectable IO. I then made a SUSIC node 24 bit, with three cards being defined as inputs. In the resulting summary I now see a SUSIC with 0 out bits and 72 in bits.It _can_ work, if you implement your (Auduino?) code correctly. Your code would need to handle the C/MRI "Init" message as if it was an SUSIC. 2. how do I address these inputs if the node address = 1? Is that 1001 for the first input and 1072 for the last input?Almost. JMRI (usually) uses "CS" a "prefix" to define its "System Addresses" for CMRI Sensors. That makes it "CS1001" thru "CS1072" for a CMRI "node" that implements 72 "inputs". Or JMRI can use an "alternate" way of dealing with the "System Address". In the alternate way, the "CS" prefix stays the same, but the "node address" portion is separated from "input number" by a "B". In this case, the "System Name"s for your case would be "CS1B1" thru "CS1B72". (I prefer to use the "B" method, because I find the extra "B" helps me see the node address separately from the input/output number.) Note that the _card_ number is _not_ specificly used as part of the JMRI "System Address". C/MRI's data streams simply do not include a card number. The "Init" message tells the SUSIC how to route data to/from a "card" and the RS-485; only the "Init" message has anything to do with C/MRI "card numbers" when configuring a USIC/SUSIC. And for completeness, JMRI "System Address"es for Turnouts (C/MRI outputs) use the (usual) prefix "CT", and are otherwise similar to JMRI "System Address"es for JMRI Sensors (C/MRI Inputs), as described above. Again, JMRI's System Addresses start at address 1 for a given node. It doesn't matter which C/MRI "card" implements the first output (JMRI "Turnout"). And JMRI can use then "alternate" way of addressing Turnout "System Addresses", too. The JMRI "Turnouts" start at - "CS(node number)(3-digit address, starting at 001)", or, alternately, - "CS(node number)B(address, starting at 1)". |
Re: Edit dialog boxes do not open with full width
Cosmic -- I had just had the same thought when your email came in. I unplugged the Thunderbolt and, sure enough, the turnout edit dialog appears in full size!
?
This is partially good news...but I frequently have many tables open... as well as two full screen layout panels. Very crowded. I would also hate to have to unplug and replug a monitor every time I go into and out of JMRI.
?
Is there something I can look at to see what is different in the UI with one vs two monitors?
?
Also, I don't suppose it's relevant, but the older (working) machine runs with Adoptium version of Java 11.
?
Vince |