AJS Station 1x50s

chili46

Member
I have a route that has 8 passenger depots and I have been using AJS Station to control loading and unloading of passengers. There's a little problem -it doesn't always work. Some would and some wouldn't. It has been driving me nuts. The train would approach the station and, if it was working correctly, would stop and do its thing. If it wasn't working correct, the train would slow down, creep along, and then take off without clearing the download command.

Well, I finally figured it out. The asset is directional. If it is approached going against the direction arrows, it wouldn't work. Approaching in the direction of the arrows - works fine. Now these depots are all bi-directional. In the course of a day they will be approached from both directions.

I discovered that if I direct the train to a depot and wait for 10 seconds and then continue on with the unload command, everything works just great and consistently works. So there's the answer: a short pause before trying to unload.:D

I lied. It isn't working 100% all the time. Back to the drawing board. :confused:
 
Last edited:
"Navigate to"/"drive to" a station and use HALT TRAIN

Loading will start automaticly.

Don't use the Load/Unload command.

 
Not on my setup. The passenger train just rolls right through the depot and continues on to the next station. It Has to have the unload command. It doesn't necessarily need load/unload, but at least one of them.
 
I haven't tried it yet. I did see the notes on it and got it from DLS, but haven't played around with it yet. The "hack" I'm using seems to work just fine so for now I'll just stick with it. The intent of the post was more as "for your information" in case someone else was having the problem and wanted a simple way to make it work. :)
 
I have a route that has 8 passenger depots and I have been using AJS Station to control loading and unloading of passengers. There's a little problem -it doesn't always work. Some would and some wouldn't. It has been driving me nuts. The train would approach the station and, if it was working correctly, would stop and do its thing. If it wasn't working correct, the train would slow down, creep along, and then take off without clearing the download command.

Well, I finally figured it out. The asset is directional. If it is approached going against the direction arrows, it wouldn't work. Approaching in the direction of the arrows - works fine. Now these depots are all bi-directional. In the course of a day they will be approached from both directions.

I discovered that if I direct the train to a depot and wait for 10 seconds and then continue on with the unload command, everything works just great and consistently works. So there's the answer: a short pause before trying to unload.:D

I lied. It isn't working 100% all the time. Back to the drawing board. :confused:

First, what do you mean with "Direction arrows"? This asset, as all industries have two arrows at each end. Arrows that I thought where there to indicate the actual end of loading area. So, here is the thing: I use it extensively. Some stations do exactly what you describe, and I have not been able to fix the problem. Interesting is that before the latest upgrades, it was working perfectly. Is being said that on the latest oncoming fix, this anomaly will be corrected (system is being returned to what was before, not an actual fix), and to me it is related to the consist overshooting trackmarks, or the end result is he same. Bottom line: Why being it the exact same asset, it works in some places, and not the others? It does not matter if you use the "load", "call at", or that interesting "load passenger" that opens doors and allows selecting the side of the consist for door actions. When it fails, the train overshoots. Note that it is visible to AI, because when you direct the consist to go to XX station, by "drive to" or "navigate to", it does normally. But when it gets there, it does not execute the loading/unloading command and the consist goes to oblivion. I have even tried to "drive to" a trackmark located right over the station, and the train overshoots!
 
First, what do you mean with "Direction arrows"? This asset, as all industries have two arrows at each end. Arrows that I thought where there to indicate the actual end of loading area. So, here is the thing: I use it extensively. Some stations do exactly what you describe, and I have not been able to fix the problem. Interesting is that before the latest upgrades, it was working perfectly. Is being said that on the latest oncoming fix, this anomaly will be corrected (system is being returned to what was before, not an actual fix), and to me it is related to the consist overshooting trackmarks, or the end result is he same. Bottom line: Why being it the exact same asset, it works in some places, and not the others? It does not matter if you use the "load", "call at", or that interesting "load passenger" that opens doors and allows selecting the side of the consist for door actions. When it fails, the train overshoots. Note that it is visible to AI, because when you direct the consist to go to XX station, by "drive to" or "navigate to", it does normally. But when it gets there, it does not execute the loading/unloading command and the consist goes to oblivion. I have even tried to "drive to" a trackmark located right over the station, and the train overshoots!
I believe thearrow reference is to the default track on these assets, AJS Track Eraser <kuid2:122285:1003:2>.
 
So I tried the "call at" option and that seems to work pretty good. But I have discovered another "issue". I have two passenger consists: ATSF Santa Fe using 1950's style engines and rolling stock and a more modern Amtrak one. The Santa Fe consist works pretty much the way I want it too and fairly consistently. The Amtrak is a horse of another color. It will go to the station and do the unload/load functions. But then on departing the station it runs backwards for a few hundred yards and then switches directions and heads to the next station - if I'm lucky. It seems like it thinks it is at a terminal and has to back out of it, but all the platforms are set to be standard station, not terminal and the fact that the same engineer's schedule is used tells me that it has something to do with the consist (I simply switch which engine Kenny will be driving in driver setup).

Being a perfectionist has its drawbacks.
 
Update.

I have tested, retested, and tested again. The bottom line is that the Amtrak F40PH loco is doing something in the background that prevents it from following a schedule. I haven't tried any of the other Amtrak locos on DLS because I don't like their looks. The F40PH is cool looking and that's the one I wanted to use.

Test parameters:

2 Consists, 1 ATSF rolling stock and 1 Amtrak rolling stock
2 Engines, 1 ATSF F7A and B, 1 Amtrak F40PH (there are about 5 or 6 on DLS, tested all of them)
2 Schedules - 1 with Navigate to and load, the other Call at
1 Driver - Kenny

The results:

Using the ATSF F7A/B loco, either consist with either schedule works fine.
Using the Amtrak F40PH loco, neither consist with either schedule will work.

Tried the P42DC and it is working correctly. Not my first choice for a prime mover, but it's not too bad looking. ;)
 
Last edited:
Back
Top