David,

When you add the turnout to the panel, you can change the icons.

If it is already on the panel, use "Edit Turnout Icon" from the pop-up menu.

JMRI generally does not know about left-hand/right-hand turnouts. ?The Turnouts table only has the state. ?SML discovery does know about LH/RH turnouts which is combined with the Continuing State. ?Manual SML relies on valid data being supplied.

I have a very simple rule: ?Switch machines are wired to set the turnout closed "route" when the JMRI turnout table entry is closed without using invert.

Dave Sand

David,

By "this" do you mean the continuing route setting? ?If so, that is a Layout Editor feature.

For Panel Editor and Control Panel Editor, you just swap the Closed and Thrown icons.

Dave Sand

Ok, thanks, Dave

?

I will keep working on the signals to make them work properly.

?

Best

KenF

Ecuador

Ken,

I have looked at the latest upload. ?It looks like the issue in this thread has been resolved.

Dave Sand

Good morning

I thought it might be helpful for you to know a little more about my layout.

It is a Kato Amherst 2005 modified by adding 3 additional feet because I wanted longer trains.

I have a passenger station between turnouts 22 and 14. The passenger train stops at turnout 26 to allow for passengers to board. I have a freight train that sometimes delivers cars to my grain mill in the center of the layout.?

Because I am new to the hobby some of my items on the layout are experimental like the sensors on the west side.?

I hope that helps to understand some of my ideas.

Best

Ken

?

?

Ken,

I don't know what your operating plans are, but the 23/27 crossover does appear to be redundant. ?

When you use two turnouts as a crossover, you do need a block boundary.? You do not need any signal masts.

Only one track segment is needed but I like to make the split obvious. ?Here I have color coded the blocks to make the block boundaries visible.

I have not explained the LT01(B) and LT01(C) issue very well. ?Maybe this will help.

LT01(B) is attached to the straight leg of LT1 which is the 812 block. ?LT01(C) is attached to the diverging leg which is the 806 block. ?Therefore the icon should be located next to the proper track.

Note: ?I like that you include the connection letter in the signal mast user name. ?I do the same thing. ?Many years ago I gave up on trying to use directions, such as east/west, left/right, etc., in signal mast user names.

Once you have made the changes for LT26/LT14 and made the same change for 23/27 or delete them and related signal masts, you need to delete all of the SML and do the Auto Generate Signaling Pairs.

Dave Sand

Good evening, Dave

I have some questions this time.?

1. Can I remove turnouts 23 & 27?

2. Can I remove block 817 also??

I am sending the file back.

I really appreciate your help.

Best?

KenF

Ecuador?

Ken,

The second try worked.

There are a few more changes.

I recommend that the turnout speeds be adjusted. ?The default speed for Thrown is Restricted. ?I normally used Medium. This is set using the "Speeds -> Defaults" menu item in the Turnout table.

This affects the signal mast logic when routes include thrown turnouts.

The "LT1" turnout table entry currently has "Inverted" enabled. ?I suspect that this was an attempt to make the diverging leg of LT1 to be the normal route. ?I don't use inverted. ?My rule is that if the JMRI Closed state is not the preferred route, the switch machine wiring is changed.

The image for LT1 has the wrong color (red). ?Right click LT1 and select Edit. ?Click on the "Create/Edit" block button. ?Set "Occupied Sense" to Active.

If the problem is with what LS57 is reporting, fix it instead of masking the problem using JMRI.?

The signal mast icons for LT01(B) and LT01(C) need to be flipped.

LT14 signal masts: ?LT14(C) is missing and LT14(B) is in the wrong location on the panel. ?Enable "Right Hand Side" for all 3 locations and click on Done. ?This will add/move the masts to the proper locations.

LT22 signal masts: ?Select LT22(C) for the 815 - 512 block boundary. ?Create SML for LT22(C). ?Delete and create SML for LT25(A).

LT23 signal masts: ?Add the masts to the panel.

------------------------------------

The LT26/LT14 and LT23/LT27 turnout pairs look like crossovers. ?If they behave as crossovers then trains will never stop between the turnouts. ?If that is true, then blocks 833 and 816 are not needed. ?And signal masts LT26(C) and LT14(B) are not needed.

------------------------------------

There is an error where occupancy sensor LS400 assigned to blocks 804 and 810.

------------------------------------

Note: ?The middle loop ( P14, etc.) has an interesting problem that will require more research. ?When the turnouts are lined for the loop, a SML loop occurs. ?When a signal mast aspect changes, the previous mast has to determine if its aspect needs to change. ?If so, it changes and when triggers the next previous mast. ?The method for propagating changes can go forever.

I think the problem is the number of signal masts in the loop. ?The outer loop does not have the problem.

Dave Sand

Good morning

Let me try again. I made all the changes you recommended so I don't know what happened.

Ken,

The file that you uploaded this morning does not have any of the changes that I recommended.

If you want, I can make the changes and upload an updated file for your review.

Dave Sand

Hi Dave

Thanks for your great analysis and suggestions, all of which I will follow.?

I used the 400 series for the blocks and the 50 series when I made the turnouts their own blocks.?

After I make all the corrections tomorrow I will send you another file.?

I am not clear on how and where to place cuts in the tracks or if I can use sensors somehow to make the signals react to the train movement.?

?

Have a good night and thanks again,?

?

KenF

Ecuador

Ken,

Your last upload was good. ?I have some initial comments.

LT1 is a left hand turnout, but you want the diverging leg to be the normal route. ?In Layout Editor this is done by using the Continuing Route Turnout State option.

By setting the option to Thrown, Layout Editor will show the diverging leg as the Closed position. ?

The Turnout table and related logic do not have left-hand or right-hand concepts. ?They deal with Closed and Thrown, whatever that means. ?My rule is that switch machines are wired so that the JMRI Closed state matches the expected physical turnout state. ?

You appear to have two groups of occupancy sensors, a low number range and a 400 number range. ?What are the differences?

Signal masts LT01(B) and LT01(C) are reversed on the panel. ?They are attached to block boundaries defined by the turnout legs, not the logical position as above.

The LT25 signal mast icons are not on the panel but they are attached to the block boundaries. ?This can be confusing. ?This is easily fixed by selecting Set Signal Masts for LT25 and selecting Right Hand Side for each mast and clicking on Done.

A lot of the signal mast logic is incorrect. ?I suspect this is causing the lack of signal response as a locomotive runs around the layout.

Whenever the block topology has been changed, the affected signal masts have to have the SML updated. ?Sometimes a small changed requires updates to the SML for several signal masts in either direction.

At this point I recommend running the GrandReset.py script. ?The script deletes the transits, sections, SML and block paths. ?After doing a store and quit, restart PanelPro and load the updated file. ?The first step is to go to the Signal Mast Logic table and do the Auto Generate Signaling Pairs. ?

At this point, I would not bother with Sections and Transits. ?The first goal is to get consistent signaling based on train movements.

Dave Sand

Hi Dave

?

There are 3 files on problems being worked on. All are not good?

?

I will send another file tonight or tomorrow morning.

?

Sorry for all this confusion.?

?

Best

KenF

Ken,

I don't see any new files. ?There are two bad ones from the 24th.

Dave Sand

Hi Dave

?

I uploaded again yesterday

Ok

Ken,

You need to upload your file again. ?The wrong file ended up in ProblemsBeingWorkedOn/Ken Fordham.

Dave Sand

I moved there this morning.

KenF