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) Configuration of turnout CanvV2V6O On signalMast logic this is what happens about the position on the turnouts. 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 °ä¨¦²õ²¹°ù |