¿ªÔÆÌåÓý

Locked Error while trying to run auto train under Dispatcher


 

Hi,
Working on automating trains with Dispatcher and am getting an error regarding a particular turnout:

2018-08-28 20:33:53,534 jmri.Section????????????????????????? ERROR - Unexpected error in getDirectionStandardTurnout when working with turnout NT14 [AWT-EventQueue-0]
2018-08-28 20:33:53,534 jmri.Section????????????????????????? ERROR - Unexpected error in getDirectionStandardTurnout when working with turnout NT14 [AWT-EventQueue-0]

Signals appear to be working as expected (but it has been quite a challenge to get this far). I am using the SSL type signaling. The turnout in question is "inside" a block, not sure if that is an issue. All blocks are contiguous. Another part of the same panel worked ok with Dispatcher so this seems localized.
Running:
JMRI 4.12
Linux Ubuntu 16.04
NCE

I have read the online help and searched the user messages (very helpful to get me this far btw) but could not find this problem.

Panel is in problem area folder: 'Allen House SSL Dispacter signal issue'

Any help appreciated.
Thanks,

Allen
Mtn RR


 

Allen,

The first thing that needs to be fixed are the Section direction sensors. You are currently using the neighboring block's occupancy sensors. The Section direction sensors are Internal sensors for the exclusive use of Dispatcher. I recommend names that are based on the section name such as sect_OL_8_Fwd and sect_OL_8_Rev.

If there are still issues, upload the updated panel xml file and the custom icons.


Dave Sand

On Aug 28, 2018, at 10:52 PM, ahouse3761 <trainmail1@...> wrote:

Hi,
Working on automating trains with Dispatcher and am getting an error regarding a particular turnout:

2018-08-28 20:33:53,534 jmri.Section ERROR - Unexpected error in getDirectionStandardTurnout when working with turnout NT14 [AWT-EventQueue-0]
2018-08-28 20:33:53,534 jmri.Section ERROR - Unexpected error in getDirectionStandardTurnout when working with turnout NT14 [AWT-EventQueue-0]

Signals appear to be working as expected (but it has been quite a challenge to get this far). I am using the SSL type signaling. The turnout in question is "inside" a block, not sure if that is an issue. All blocks are contiguous. Another part of the same panel worked ok with Dispatcher so this seems localized.
Running:
JMRI 4.12
Linux Ubuntu 16.04
NCE

I have read the online help and searched the user messages (very helpful to get me this far btw) but could not find this problem.

Panel is in problem area folder: 'Allen House SSL Dispacter signal issue'

Any help appreciated.
Thanks,

Allen
Mtn RR


 

Dave,
More errors now:

2018-08-29 17:45:04,821 dispatcher.DispatcherFrame??????????? DEBUG - trainID:WP583, tSource:1, startBlockName:IB1, startBlockSectionSequenceNumber:1, endBlockName:IB9, endBlockSectionSequenceNumber:9 [AWT-EventQueue-0]
2018-08-29 17:45:04,823 layoutEditor.ConnectivityUtil???????? ERROR - Error - could not add watched sensor to SSL for signal head LH5 because there is no room in the facing SSL diverging part. [AWT-EventQueue-0]
2018-08-29 17:45:04,823 layoutEditor.ConnectivityUtil???????? ERROR - Error - could not add watched sensor to SSL for signal head LH5 because there is no room in the facing SSL diverging part. [AWT-EventQueue-0]
2018-08-29 17:45:04,824 layoutEditor.ConnectivityUtil???????? ERROR - Error - could not add watched sensor to SSL for signal head LH7 because there is no room in the facing SSL continuing part. [AWT-EventQueue-0]
2018-08-29 17:45:04,825 layoutEditor.ConnectivityUtil???????? ERROR - Error - could not add watched sensor to SSL for signal head LH7 because there is no room in the facing SSL continuing part. [AWT-EventQueue-0]
2018-08-29 17:45:04,828 layoutEditor.ConnectivityUtil???????? ERROR - Error - could not add watched sensor to SSL for signal head LH78 because there is no room in the facing SSL diverging part. [AWT-EventQueue-0]
2018-08-29 17:45:04,828 layoutEditor.ConnectivityUtil???????? ERROR - Error - could not add watched sensor to SSL for signal head LH80 because there is no room in the facing SSL continuing part. [AWT-EventQueue-0]
2018-08-29 17:45:04,829 jmri.Section????????????????????????? ERROR - Unexpected error in getDirectionStandardTurnout when working with turnout NT14 [AWT-EventQueue-0]
2018-08-29 17:45:04,829 layoutEditor.ConnectivityUtil???????? ERROR - Error - could not add watched sensor to SSL for signal head LH78 because there is no room in the facing SSL diverging part. [AWT-EventQueue-0]
2018-08-29 17:45:04,829 layoutEditor.ConnectivityUtil???????? ERROR - Error - could not add watched sensor to SSL for signal head LH80 because there is no room in the facing SSL continuing part. [AWT-EventQueue-0]
2018-08-29 17:45:04,829 jmri.Section????????????????????????? ERROR - Unexpected error in getDirectionStandardTurnout when working with turnout NT14 [AWT-EventQueue-0]

The same two plus 8 new ones.
I'll upload this panel to the same directory.

Allen


 

I tried to upload the custom icon set to the files area but received an error that images could not be put there. Alternate?

Allen


 

Allen,

Try putting the icons in a zip file.?

Dave Sand?


----- Original message -----
From: ahouse3761 <trainmail1@...>
Subject: Re: [jmriusers] Error while trying to run auto train under Dispatcher
Date: Wed, 29 Aug 2018 17:55:57 -0700

I tried to upload the custom icon set to the files area but received an error that images could not be put there. Alternate?

Allen





 

Allen,

Disclaimer: I am not a SSL expert, what follows is my understanding.

The additional errors appear to be caused by SSL definitions that don¡¯t make sense. If you look at the SSL for 3R, part of it is protecting Block 3 and Block 4. Since Block 4 is beyond the protected signals, it does not need to be included.

Dispatcher is trying to add a direction sensor to the SSL. Since this is a ¡°facing point¡± SSL, there are only two sensor slots. By including Block 4, there are no slots available for the direction sensor. This appears to apply to all 8 new errors.


Dave Sand

On Aug 29, 2018, at 7:48 PM, ahouse3761 <trainmail1@...> wrote:

could not add watched sensor to SSL


 

Ok, I'll look at that logic. Do you think correcting that will also affect the NT14 issue?
Thanks,?
Allen


 

Allen,

It might fix the NT14 issue, but I doubt it. The other problems do get in the way of debugging what is happening with NT14. It is possible that the NT14 issue is caused by a series of unreported errors or configuration issues.


Dave Sand

On Aug 31, 2018, at 9:15 AM, ahouse3761 <trainmail1@...> wrote:

Ok, I'll look at that logic. Do you think correcting that will also affect the NT14 issue?
Thanks,
Allen


 

ok, fixed SSL logic issues and the 8 extraneous errors are gone. Original 2 on NT14 remain.
Panel icons loaded along with updated panel.

Allen


 

Allen,

I have identified the problem. ?

The section containing NT14 was missing the entry point for the stub track. ?I devised a quick fix for that and then several other turnouts had the same problem. ?I deleted the transits and sections and re-built them. ?Once that was done, I was able to virtually run a train around the outer loop.

Based on the symptoms, it appears that the stub track blocks were added after the sections had been created.

I am not able to provide an updated panel xml file since the following custom items were automatically deleted from the panel:
  • Photos_and_images/Turntable sky view 1000x561.png
  • panel _icons/*. [[ yes, there is a space in the folder name ]]
There are still problems with SSL. ?Each signal head needs to be reviewed to make sure that definition is correct.

Dave Sand



On Sep 1, 2018, at 12:50 AM, ahouse3761 <trainmail1@...> wrote:

ok, fixed SSL logic issues and the 8 extraneous errors are gone. Original 2 on NT14 remain.?
Panel icons loaded along with updated panel.

Allen


 

Dave,
Thanks for the analysis. I'm out of town this weekend and will duplicate your process when I return. I have to admit that during the learning sequence it has been difficult to keep the layering of elements straight. I recall I was not clear that the small spur tracks needed blocks. The number of virtual signals required was also surprising.?
For the SSL definitions, is there a reference to help me get the logic right? I think I need to step back a bit.
Allen?


 

Dave,
I tried deleting the transit and sections near NT14, recreating them, and I still get the same error. Your quick fix must be more than that?
I also uploaded more images/icons that appear to be necessary for all my panels. I have created them over a long period of time and did not know all the images would be needed to rebuild it. Hopefully that will allow a complete fix.

Allen


 

Allen,

I have uploaded a fixed file to your folder.

/g/jmriusers/files/ProblemsBeingWorkedOn/Allen%20House%20SSL%20Dispacter%20signal%20issue/Mtn_RR_215%20fix.xml

That should take care of the NT14 problem.


Dave Sand

On Sep 4, 2018, at 8:55 AM, ahouse3761 <trainmail1@...> wrote:

Dave,
I tried deleting the transit and sections near NT14, recreating them, and I still get the same error. Your quick fix must be more than that?
I also uploaded more images/icons that appear to be necessary for all my panels. I have created them over a long period of time and did not know all the images would be needed to rebuild it. Hopefully that will allow a complete fix.

Allen