OK I can see sort of what you are trying to do.
I have a question and a suggestion.
Question. Line #43 that controls the TIMER, Gndr_Tmr, uses the contact associated with the TIMER as part of the logic. It looks like you are trying to create some sort of Seal-in circuit. The issue is that the TIMER contact only does not go active until it times out. This would then keep Gndr_Tmr active until either the contact with Seq1:1 goes active of SW_High goes inactive. Is this what you want?
Can you simplify your program down to 2 or 3 lines and the problem still exists? This would be a lot easier for me to figure out.
Suggestion: The use of "_" in the names of the ladder logic elements used to work quite fine. Somewhere in the history of TRI they decided to allow attaching a comment to variable names in the TBASIC programming language that was added to PLCs after the T28. This idea was stupid and it breaks all sorts of things. Now in TBASIC the following are all references to the same thing, "A" "A_InputState", "A_A". Essentially anything including the "_" is ignored. If you use TBASIC and try to access INPUTs, OUTPUTs, RELAYs, TIMERs and such in TBASIC the "_?
" will be ignored.
If you never use TBASIC you can keep the "_" names. If you use TBASIC, then DO not use "_" in any name anywhere. The "_" breaks the parts of the i-TRiLOGI syntax highlighter, also.
TRI did come up with something that was a lot more powerful and I like a lot, the #define mechanism. This mechanism does give you useful names for things. However, they didn't get rid of the stupid "_" idea.
Gary Dickinson