Armstrong Powerhouse Class 356 Alarms

[Hipper]

I've used the class 356 that comes with the East Coast Mainline London to Peterborough and had no issues with warning alarms - if they went off when approaching a yellow light I pressed Q, or the Alert button on Raildriver, acted appropriately with braking and all was well.

With the Armstrong Powerhouse, using the scenario from Hitchin to Kings Cross for example, there are yellow lights when approaching Welwyn North. The alarm goes off, I press Q (correct in AP too) but the train straight away goes into emergency braking (EB). I've tried pressing Q and E (the Driver Vigilance Device) as well but it still goes into EB.

I thought when you see a yellow you slow down to around 40mph on the assumption that the next signal is red. If the next signal is definitely red you slow down to 20mph.

What am I doing wrong?

[749006]

The Class 365 is no different to the other Emus in the way you drive it

If you are waiting until you pass the Yellow Signal Magnet before applying the brakes you are going too fast.
The Signals on the route have TPWS which may consider you are going too fast at a single yellow to stop at the red

[Hipper]

I'm travelling at the existing speed limit - 70 mph I think. I can just about see the yellow but the alarm goes off at the same time. I immediately press Q and start to brake but it's too late. Emergency Braking is applied.

Unless I'm doing something wrong, I can't see what I can do.

[749006]

If you are using the Raildriver to drive the AP version that might be your problem

It says on their page
Please note, this pack is NOT compatible with any external controllers such as the XBOX or RailDriver.

Peter

[Hipper]

Actually it does work with Raildriver and CobraOne's T2017 Interface. The Alerter, Q key and using the mouse on the AWS button in the cab, all work.

Nevertheless I tried the scenario using only keyboard and mouse (Raildriver was disconnected and the T2017 Interface exited). The same thing happens. As soon as the alarm goes off, even when I turn it off, Emergency Braking is engaged. This happens even if I'm travelling at less then 40mph with brakes engaged. It happened with a flashing yellow and a fixed one.

I suppose I should contact Armstrong Powerhouse.

[749006]

Actually it does work with Raildriver and CobraOne's T2017 Interface. The Alerter, Q key and using the mouse on the AWS button in the cab, all work.

Nevertheless I tried the scenario using only keyboard and mouse (Raildriver was disconnected and the T2017 Interface exited). The same thing happens. As soon as the alarm goes off, even when I turn it off, Emergency Braking is engaged. This happens even if I'm travelling at less then 40mph with brakes engaged. It happened with a flashing yellow and a fixed one.

I suppose I should contact Armstrong Powerhouse.

You could try reinstalling the Class 365 pack as something might have got changed?
I presume the default 365 that comes with L2P does not have this problem?

If all else fails then contacting AP is a good idea as they are very quick to respond to a request for help.

[Hipper]

I contacted AP yesterday and sent a video today.

You may be right about reinstalling but it's a bit of a pain with AP products as I use Raildriver and the TS2017 interface which means it's not just a simple click and install.

I'll report what AP say - I hope it's not something I'll be embarrassed about!

[Hipper]

I discussed this with AP who have been very responsive.

It turns out I'm just a poor driver!

The AWS alarm response times on the AP 356 allow about two seconds to respond otherwise the emergency brake kicks in. On the ECML South 356 I get four seconds.

Back to driver training school!

[theorganist]

I discussed this with AP who have been very responsive.

It turns out I'm just a poor driver!

The AWS alarm response times on the AP 356 allow about two seconds to respond otherwise the emergency brake kicks in. On the ECML South 356 I get four seconds.

Back to driver training school!

I found with the AP class 158 on the Welsh Marches route, yesterday, that you have to be very quick, and managed to trigger the emergency brakes a few times

I got the hang of it in the end!

Peter

[Hipper]

We learn all the time.

What I've done is started using the mouse wheel more often to move the cab view forward or backward. Backward allows me to see the various door buttons etc., forward allows me a better view of the signals. I can now see the more visible ones between .3 and .4 miles away. This plus learning the route allows better preparation for when yellow signals are likely to occur.

I've just successfully completed the Hitchin to Kings Cross scenario and caught all the AWS alarms in time, including outside Welwyn North and quite a few as you approach KX. A very satisfying achievement.

[749006]

If I'm approaching a signal which is not Green I watch out for the AWS ramp in the track as you know when the Alerter will sound.

Hold your finger over the button as press as it sounds

[gptech]

Hold your finger over the button as press as it sounds

Don't the AP sounds work along the lines of having a short delay before the alarm sounds after passing over an AWS ramp, rather than only giving you only 2 seconds in which to respond?

From the 365 enhancement manual:

1 second delay between train passing over AWS magnet and AWS warning sound occurring. The F3/F4 HUD will show the warning immediately so you must wait 1 second before trying to cancel it.

[749006]

Hold your finger over the button as press as it sounds

Don't the AP sounds work along the lines of having a short delay before the alarm sounds after passing over an AWS ramp, rather than only giving you only 2 seconds in which to respond?

From the 365 enhancement manual:

1 second delay between train passing over AWS magnet and AWS warning sound occurring. The F3/F4 HUD will show the warning immediately so you must wait 1 second before trying to cancel it.

I still hold my finger over the Q and press it as it sounds

[Deano55]

That's right, there is a small delay but with signals its easy to keep your finger on the button because you can see the signals coming and know you need to press that button when you go over the AWS in front of it, so why would you wait longer when you can see it is coming.
The tricky one is the AP version of the DSD,DVD, Dead mans pedal or whatever you like to call it. That little monkey just leaps out of nowhere and always catches you unaware, and so often at the same time as AWS warning, speed reduction and track change.
It's like it knows when you will be flustered and strikes as you are already all fingers and thumbs trying to drive your train and gives you 2-3 seconds to find that other key too before it slams on the brakes making you scream "For Gods Sake you must be Fe*?@: joking" as your train comes to a halt just as you were about to pull in to the station only 30 seconds late.
DAM YOU Andrew P....

[Hipper]

Deano55 - there should be a like button on this forum!