开云体育

Date

Locked Re: M?rklin CS3 and DCC accessories #maerklin

 

This may well be because the original coding was to connect to the CS1 which did not have the alternative protocols available.
It may well require modification to enable DCC mode for accessories.


On Fri, 5 May 2023 at 17:27, S?ren Jacob Lauritsen via <m=[email protected]> wrote:
I had a look at the source code for turnout control (MarklinTurnout.java). Since my experience with the source code of JMRI is somewhat limited,?I?may?be missing something, it does, however, look as if the MarklinTurnout class is unintentionally hardcoded to the MM protocol.


Locked Locomotive programming using Decoder Pro problems

 

I have been using Decoder Pro for some time now.? It is much easier to use when it works but lately, it is a headache. I can put a locomotive on the programming track and it will tell me the programming is being put in the decoder just fine but when I put the loco on the main to run it; nothing was programmed. I have one of those circuit boards that you put in between the command control unit and the programming track that is supposed to increase the power going to the programming track to help in programming. It has a small LED that flashes when it's working and the command control unit also shows a flashing light when it is sending command programming.? Both of those say they are doing their job and Decoder Pro says the same, yet it is not happening. Any ideas on what is going on here? Also, it is not the decoder. This happens to all of them now. This is on a laptop running Windows 10.


Locked Re: restricting classification yards by location #operationspro

 

I thought of that.? That is a good idea.??
--
Tom


Locked Re: logix vs logixNG #logix #logixng

 

Brian,

I doubt that LogixNG will ever supplant Logix. ?However, Logix will probably never be enhanced. ?All new capabilities will be done in LogixNG. ?It is designed to be extended. ?For example, adding a new table type is done by adding new classes. ?Logix required modifying the existing code which is risky.

For people who are comfortable with if-then-else, loops and sub-routines, the LogixNG concepts are easy to understand. ?In addition to language type structures, there are lot of specialized actions.

Here is a LogixNG that eliminated calls to several Jython scripts.
Dave Sand


----- Original message -----
From: Brian Wong <blwatlongwood@...>
Subject: [jmriusers] logix vs logixNG
Date: Friday, May 05, 2023 3:19 PM

For a new installation, is there any reason to use logix as opposed to logixng? It appears that NG is intended to (eventually) completely supplant logix, so probably the answer is no. However I suppose that there may be some straggling bits that haven't been redone yet or something like that.


 

Hi Dave,

Your solution works fine it is the correct way.

Thanks for your help.

颁é蝉补谤

En viernes, 5 de mayo de 2023, 22:28:56 CEST, Dave Sand <ds@...> escribió:


颁é蝉补谤,

Try this crazy idea.

Remove Invert from the linked turnouts. ?Set the "Continuing Route Turnout State" for CanvV6V20 to Thrown. ?This makes the diverging leg be the Closed position.

Remove and re-discover the SML routes between the two turnouts. ?

See if this makes a difference after storing and re-starting.

Dave Sand


----- Original message -----
From: "Cesar Alcala via groups.io" <shegar81=[email protected]>
Subject: Re: [jmriusers] Signal Mast Logic #signalmasts #turnouts
Date: Friday, May 05, 2023 3:09 PM


Hi,

I will try to show it by images.

I have this layout. You can see the signals SAL2O( text above the signal) and S2/6 ( text next to the signal) that text is next to them. Also there is involved turnouts CanvV6V2O( turnoutbelow the text) and CanvV2V6O(turnout above the text)

Imagen en el mensaje

Configuration of turnout CanvV2V6O

Imagen en el mensaje

On signalMast logic this is what happens about the position on the turnouts.
Imagen en el mensaje
I tried to configure SignalMast Logic it without the link between turnouts and it works correctly even if I establish later the connection but when I start JMRI it happens this.

I hope it is clearer now with the images

Best Regards

颁é蝉补谤


En viernes, 5 de mayo de 2023, 21:38:44 CEST, Dave Sand <ds@...> escribió:


颁é蝉补谤,

We will need a least a picture of what you are trying to do. ?The best approach is to upload the xml file to the group's ProblemsBeingWorkedOn file folder.

Dave Sand

----- Original message -----
From: "Cesar Alcala via groups.io" <shegar81=[email protected]>
Subject: [jmriusers] Signal Mast Logic #signalmasts #turnouts
Date: Friday, May 05, 2023 2:29 PM

Hello,

I have detected and issue on the signal mast logic or at least I have the problem. It is related to turnouts that are connected. I have two turnouts that are directly connected one on closed position and the other on throw. On the configuration on the turnout I linked both turnouts and I selected to invert the second one. It worked perfectly so both turnouts are paired and when route is established at them goes straight and in the oposite position goes to another path. When I used the discover to establish the pairing signals all goes perfectly but when I tried to work always the signal is on danger. I forced to change aspect but it is not the correct way. When I analysed the signal mast Logic I released that turnouts aren't correctly. Both where considered as throw instead of one throw and the other closed to be active so it is not possible to link them. If I didn't put this link the pairing is correct with the Signal Mast Logic that is the way I did actually the configuration.

I am using JMRI on its 5.2 version so it is upgraded until last production version, is it a problem on this last version or it was also on previous versions?

Best Regards

颁é蝉补谤






 

颁é蝉补谤,

Try this crazy idea.

Remove Invert from the linked turnouts. ?Set the "Continuing Route Turnout State" for CanvV6V20 to Thrown. ?This makes the diverging leg be the Closed position.

Remove and re-discover the SML routes between the two turnouts. ?

See if this makes a difference after storing and re-starting.

Dave Sand


----- Original message -----
From: "Cesar Alcala via groups.io" <shegar81=[email protected]>
Subject: Re: [jmriusers] Signal Mast Logic #signalmasts #turnouts
Date: Friday, May 05, 2023 3:09 PM


Hi,

I will try to show it by images.

I have this layout. You can see the signals SAL2O( text above the signal) and S2/6 ( text next to the signal) that text is next to them. Also there is involved turnouts CanvV6V2O( turnoutbelow the text) and CanvV2V6O(turnout above the text)

Imagen en el mensaje

Configuration of turnout CanvV2V6O

Imagen en el mensaje

On signalMast logic this is what happens about the position on the turnouts.
Imagen en el mensaje
I tried to configure SignalMast Logic it without the link between turnouts and it works correctly even if I establish later the connection but when I start JMRI it happens this.

I hope it is clearer now with the images

Best Regards

颁é蝉补谤


En viernes, 5 de mayo de 2023, 21:38:44 CEST, Dave Sand <ds@...> escribió:


颁é蝉补谤,

We will need a least a picture of what you are trying to do. ?The best approach is to upload the xml file to the group's ProblemsBeingWorkedOn file folder.

Dave Sand

----- Original message -----
From: "Cesar Alcala via groups.io" <shegar81=[email protected]>
Subject: [jmriusers] Signal Mast Logic #signalmasts #turnouts
Date: Friday, May 05, 2023 2:29 PM

Hello,

I have detected and issue on the signal mast logic or at least I have the problem. It is related to turnouts that are connected. I have two turnouts that are directly connected one on closed position and the other on throw. On the configuration on the turnout I linked both turnouts and I selected to invert the second one. It worked perfectly so both turnouts are paired and when route is established at them goes straight and in the oposite position goes to another path. When I used the discover to establish the pairing signals all goes perfectly but when I tried to work always the signal is on danger. I forced to change aspect but it is not the correct way. When I analysed the signal mast Logic I released that turnouts aren't correctly. Both where considered as throw instead of one throw and the other closed to be active so it is not possible to link them. If I didn't put this link the pairing is correct with the Signal Mast Logic that is the way I did actually the configuration.

I am using JMRI on its 5.2 version so it is upgraded until last production version, is it a problem on this last version or it was also on previous versions?

Best Regards

颁é蝉补谤






Locked Re: logix vs logixNG #logix #logixng

 

They both end up with the same logic.
Logix is a traditional function configuration (like that which used to be used in Programmable Logic Controllers).
LogixNG is a language construct similar to Object Programming (new stuff).

It's like different human interface looking at the same thing.
Use whichever you're comfortable with.

I've used both. I'm an old dog that grew up with the functional configurations.

--
Ken
NYNH&H, Old Colony Division, Cape Cod Branch (1949-1959)
[DB150][PR3][QuadLN_S][JMRI 5.3.5]


 

For a new installation, is there any reason to use logix as opposed to logixng? It appears that NG is intended to (eventually) completely supplant logix, so probably the answer is no. However I suppose that there may be some straggling bits that haven't been redone yet or something like that.


 

Hi,

I will try to show it by images.

I have this layout. You can see the signals SAL2O( text above the signal) and S2/6 ( text next to the signal) that text is next to them. Also there is involved turnouts CanvV6V2O( turnoutbelow the text) and CanvV2V6O(turnout above the text)

Imagen en el mensaje

Configuration of turnout CanvV2V6O

Imagen en el mensaje

On signalMast logic this is what happens about the position on the turnouts.
Imagen en el mensaje
I tried to configure SignalMast Logic it without the link between turnouts and it works correctly even if I establish later the connection but when I start JMRI it happens this.

I hope it is clearer now with the images

Best Regards

颁é蝉补谤


En viernes, 5 de mayo de 2023, 21:38:44 CEST, Dave Sand <ds@...> escribió:


颁é蝉补谤,

We will need a least a picture of what you are trying to do. ?The best approach is to upload the xml file to the group's ProblemsBeingWorkedOn file folder.

Dave Sand

----- Original message -----
From: "Cesar Alcala via groups.io" <shegar81=[email protected]>
Subject: [jmriusers] Signal Mast Logic #signalmasts #turnouts
Date: Friday, May 05, 2023 2:29 PM

Hello,

I have detected and issue on the signal mast logic or at least I have the problem. It is related to turnouts that are connected. I have two turnouts that are directly connected one on closed position and the other on throw. On the configuration on the turnout I linked both turnouts and I selected to invert the second one. It worked perfectly so both turnouts are paired and when route is established at them goes straight and in the oposite position goes to another path. When I used the discover to establish the pairing signals all goes perfectly but when I tried to work always the signal is on danger. I forced to change aspect but it is not the correct way. When I analysed the signal mast Logic I released that turnouts aren't correctly. Both where considered as throw instead of one throw and the other closed to be active so it is not possible to link them. If I didn't put this link the pairing is correct with the Signal Mast Logic that is the way I did actually the configuration.

I am using JMRI on its 5.2 version so it is upgraded until last production version, is it a problem on this last version or it was also on previous versions?

Best Regards

颁é蝉补谤


 

颁é蝉补谤,

We will need a least a picture of what you are trying to do. ?The best approach is to upload the xml file to the group's ProblemsBeingWorkedOn file folder.

Dave Sand

----- Original message -----
From: "Cesar Alcala via groups.io" <shegar81=[email protected]>
Subject: [jmriusers] Signal Mast Logic #signalmasts #turnouts
Date: Friday, May 05, 2023 2:29 PM

Hello,

I have detected and issue on the signal mast logic or at least I have the problem. It is related to turnouts that are connected. I have two turnouts that are directly connected one on closed position and the other on throw. On the configuration on the turnout I linked both turnouts and I selected to invert the second one. It worked perfectly so both turnouts are paired and when route is established at them goes straight and in the oposite position goes to another path. When I used the discover to establish the pairing signals all goes perfectly but when I tried to work always the signal is on danger. I forced to change aspect but it is not the correct way. When I analysed the signal mast Logic I released that turnouts aren't correctly. Both where considered as throw instead of one throw and the other closed to be active so it is not possible to link them. If I didn't put this link the pairing is correct with the Signal Mast Logic that is the way I did actually the configuration.

I am using JMRI on its 5.2 version so it is upgraded until last production version, is it a problem on this last version or it was also on previous versions?

Best Regards

颁é蝉补谤


 

Hello,

I have detected and issue on the signal mast logic or at least I have the problem. It is related to turnouts that are connected. I have two turnouts that are directly connected one on closed position and the other on throw. On the configuration on the turnout I linked both turnouts and I selected to invert the second one. It worked perfectly so both turnouts are paired and when route is established at them goes straight and in the oposite position goes to another path. When I used the discover to establish the pairing signals all goes perfectly but when I tried to work always the signal is on danger. I forced to change aspect but it is not the correct way. When I analysed the signal mast Logic I released that turnouts aren't correctly. Both where considered as throw instead of one throw and the other closed to be active so it is not possible to link them. If I didn't put this link the pairing is correct with the Signal Mast Logic that is the way I did actually the configuration.

I am using JMRI on its 5.2 version so it is upgraded until last production version, is it a problem on this last version or it was also on previous versions?

Best Regards

颁é蝉补谤


Locked Re: RFID Connectivity #rfid

 

YAY my Ethernet shield showed up today!!……….now what? I have two groove 125khz sensors and an uno. I plan to buy more sensors in the near future. Can someone please provide a step per step for hooking it up, then programming followed by the required JMRI settings. Thank you?
Micheal (aka the computer, but eager dummy)?


Locked Re: SOUND DECODERS

 

On Fri, May 5, 2023 at 11:57 AM, Lawrence Varady wrote:
Are you saying decoder pro has no issues with ANY brand sound decoder?
Lawrence,

DecoderPro is basically a very smart throttle connected to your DCC (or other) system. What matters is whether your DCC system and the decoder in question will play nicely together. If, for example, your DCC system's programming track output isn't robust enough for a particular sound decoder, well, JMRI can't change that.

HTH,
Steve
"Breezlys"


Locked Re: restricting classification yards by location #operationspro

 

On Fri, May 5, 2023 at 02:16 PM, <jmri@...> wrote:
What I do find is that this restriction does reduce car movement, which is expected, because if a C/I track is full for a specific location, a car cannot be moved there with a final destination of that location, and cannot use another empty track due to an incorrect location.
You could simply "pool" all of your C/I tracks at that location.? Now if a certain destination C/I needs extra track space, it will steal it from the others.? This way your cars will be blocked by destination.



Dan


Locked restricting classification yards by location #operationspro

 

Hello again,

I currently have a yard where I have classification/interchange tracks set up by location, which works ok.? What I do find is that this restriction does reduce car movement, which is expected, because if a C/I track is full for a specific location, a car cannot be moved there with a final destination of that location, and cannot use another empty track due to an incorrect location.? I would like to make a change to get rid of the restriction of location on my C/I tracks, so that cars from any location can use any classification track.? Without these location restrictions, will OperationsPro attempt to block cars by final destination when sending cars to a C/I track when possible???

Thanks.
--
Tom


Locked Re: track doesn't accept custom loads even though track is configured to accept all loads #operationspro

 

Hi Dan/Pete,

Makes total sense now.? Thank you for your help.??
--
Tom


Locked Re: New user to JMRI Ops Pro requesting assistance #operationspro

 

couldn't he print the switch list without hitting the "move " button? I thought I printed a switch list just after I " built " the train. I can't test it now my computer is down and will be for a bit.


Locked Re: SOUND DECODERS

 

Are you saying decoder pro has no issues with ANY brand sound decoder?


Locked Re: M?rklin CS3 and DCC accessories #maerklin

S?ren Jacob Lauritsen
 

I had a look at the source code for turnout control (MarklinTurnout.java). Since my experience with the source code of JMRI is somewhat limited,?I?may?be missing something, it does, however, look as if the MarklinTurnout class is unintentionally hardcoded to the MM protocol.

Line 126 sets the protocol to "UNKNOWN":
126: int protocol = UNKNOWN;

The method in line 152 "getCANAddress" checks the protocol?and defaults to "MM" if set to anything but DCC.

? ? int getCANAddress() {
? ? ? ? switch (protocol) {
? ? ? ? ? ? case DCC:
? ? ? ? ? ? ? ? return _number + MarklinConstants.DCCACCSTART - 1;
? ? ? ? ? ? default:
? ? ? ? ? ? ? ? return _number + MarklinConstants.MM1ACCSTART - 1;
? ? ? ? }
? ? }

In line 164 it uses the above method to check what protocol it should be using:

? ? ? ? ? ?if (protocol == UNKNOWN) {?
? ? ? ? ? ? ? ?if (m.getAddress() == _number + MarklinConstants.MM1ACCSTART - 1) {
? ? ? ? ? ? ? ? ? ? protocol = MM2;
? ? ? ? ? ? ? ? } else if (m.getAddress() == _number + MarklinConstants.DCCACCSTART - 1) {
? ? ? ? ? ? ? ? ? ? protocol = DCC;
? ? ? ? ? ? ? ? } else {
? ? ? ? ? ? ? ? ? ? //Message is not for us.
? ? ? ? ? ? ? ? ? ? return;
? ? ? ? ? ? ? ? }
? ? ? ? ? ? }

It does this by looking at the output of the "getCANAddress". Since the "protocol" variable is never set to anything but UNKNOWN, JMRI will always use "MM" for M?rklin turnout protocols (given the result of the "getCANAddress" method).?

Since the Central Station supports both DCC and MM for turnouts, it should be possible to somehow change the protocol to DCC. Is there any way in the XML files or anywhere that I can insert some sort of property to work around this issue? It does not seem like it, but maybe someone with more knowledge of the source code can shed some light on this.

Best regards
S?ren


Den tors. 4. maj 2023 kl. 20.33 skrev S?ren Jacob Lauritsen via <m=[email protected]>:

Hi group,
?
I am struggling?with CS3 and DCC accessory decoders. I am using a CS3 (Central Station 3) which has the same Ethernet protocol as the CS2 (Central Station 2).
?
I cannot get accessories to work, so I checked the "Marklin Monitor" and noticed that JMRI sends out commands in the MM (Motorola) format for the CS3. As a test I created an MM based turnout and it switched just fine.
?
Is there any way to change accessory communication to DCC? CS3 supports both formats, and I mainly use DCC accessory decoders (that do not support MM).
?
Best regards
S?ren


Locked Re: Throwing turnouts from NCE throttle #nce

 

Andy,

Please clarify your question about working with signals. Normal case the
computer provides the logic to implement the signals so it knows what's
happening.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org