[Csantucci]

darwins, on 10 February 2020 - 05:03 AM, said:

Hi Geoff
Does the cab cvf file you are using having a working sunflower?

		CabSignalDisplay (
			Type ( ASPECT_DISPLAY CAB_SIGNAL_DISPLAY )
			Position ( 600 79 40 40 )
			Graphic ( aws.ACE )
		)

The AWS ace having the two states.
I ask because some cabs either do not include that part in the cvf file or do not include the graphic to go with it.
Also check Carlo's instructions - I think it is still in latest version of Monogame only.
Finally the sad news that at the moment it seems unable to apply vacuum brakes.

Hi, this type of display has indeed 8 states (frames), which correspond to the 8 signal aspects. The first seven frames usually show the sunflower, while the eighth hides it.

[Coolhand101]

Csantucci, on 10 February 2020 - 08:39 AM, said:

If you set
TrainStopBeforeRelease=true
you can reset only when the train has stopped AND the reset button is pressed.

I believe there is a slight bug. When the train has been brought to a stand. You cannot reset the TCS from "Full Service". Also for UK trains that have this method, the AWS warning sound can be cancelled before coming to a stop.

Csantucci, on 10 February 2020 - 08:39 AM, said:

Re your second question: can you try if they return active after having commented line
Include ( "AWS_eng.inc")
? I'm not sure it is the TCS script causing that.

Any more information about this?

Thanks

[Csantucci]

Coolhand101, on 10 February 2020 - 11:48 AM, said:

I believe there is a slight bug. When the train has been brought to a stand. You cannot reset the TCS from "Full Service". Also for UK trains that have this method, the AWS warning sound can be cancelled before coming to a stop.

After start of braking, reset of sound and of braking are managed in parallel. As of now no possibility to reset only one of them.

[Csantucci]

Here a new release of the script file, that solves the problem of the not working DoesBrakeCutPower()

File deleted because new release available.

[darwins]

Quote

Could you suggest a trainset with vacuum brakes where TCSFullServiceBraking works with the standard EmergencyStopMonitor? (by setting MonitoringDeviceAppliesFullBrake( 1 ) and MonitoringDeviceAppliesEmergencyBrake( 0 ).
Passing a signal at stop should trigger the automatic braking.

I will experiment by adding an emergency stop monitor to some vacuum braked trains and see if it stops any of them.

[Coolhand101]

Csantucci, on 10 February 2020 - 08:39 AM, said:

If you set
TrainStopBeforeRelease=true
you can reset only when the train has stopped AND the reset button is pressed.

Carlo, I'm afraid there is no way to reset the TCS with this method. The train has stopped, but the TCS is showing "Full Service", it is permanently on! I even tried using the Control+M keys for manual/Auto mode with the same results.
Can this be confirmed ?

Csantucci, on 10 February 2020 - 12:40 PM, said:

After start of braking, reset of sound and of braking are managed in parallel. As of now no possibility to reset only one of them.

Thanks for the explanation

Csantucci, on 10 February 2020 - 01:23 PM, said:

Here a new release of the script file, that solves the problem of the not working DoesBrakeCutPower()

Many thanks, works correctly again.

Thanks

[darwins]

Hi Carlo

Quote

Here a new release of the script file, that solves the problem of the not working DoesBrakeCutPower()

At present that will be needed for air brakes and EP brakes. DoesBrakeCutPower now works for vacuum brakes.

Hopefully the version the does not cut power will continue to be developed - this is the version needed for steam locos where power can not be cut. It can also now be used for vacuum brakes on diesel and electric where the brake will now cut power as it should.Air brakes should also cut power - but it may be more accurate to retain a TCS that does cut power for EP braked stock.

So on to brakes:

Quote

Could you suggest a trainset with vacuum brakes where TCSFullServiceBraking works with the standard EmergencyStopMonitor? (by setting MonitoringDeviceAppliesFullBrake( 1 ) and MonitoringDeviceAppliesEmergencyBrake( 0 ).
Passing a signal at stop should trigger the automatic braking.

The results depend on the type of vacuum brake being used.


In all cases the F5 HuD shows TCS Full Service Braking when the train SPADs.

If the OR vacuum brake token is TrainBrakesControllerVacuumContinuousServiceStart then the vacuum is destroyed and the brakes applied. (This token is used for BR standard steam locos and dual braked diesel and electric locos)

If the OR vacuum brake token is TrainBrakesControllerVacuumApplyContinuousServiceStart then the vacuum remains at 25 in or 21 in even though we have "TCS Full Service Braking" and so the brakes are not applied (This token is used for pre-nationalisation steam locos and also diesel and electric locos that have vacuum brake only).

This is perhaps something that Peter needs to look at in the development of braking.

On a different but related matter I did not realise before that the Emergency Stop Monitor responded to SPADs - I thought that it was only for locos that had an emergency stop button - such as the BR Class 90.
Is there a way that we can have a working emergency stop button that does not cause the brakes to be applied if the train SPADs?
(Although in the case of modern trains TPWS will do that anyway so it probably does not matter.)

If the AWS script is taking over the function of the TCS monitors in the eng file what happens about the following:
If the eng file has an Emergency stop monitor to respond to an emergency stop button in the cab?
If the eng file has an Emergency stop monitor to respond to SPADs. (TPWS)?
If the eng file has an Overspeed Monitor (TASS or ATP)?
If the eng file has a vigilance monitor?

I can imagine that more accurate TCS scripts might be written for TPWS, TASS or ATP like the AWS script we now have, but the presence or absence of a vigilance monitor or emergency stop button is more a function of a particular train than a system.

[Csantucci]

Hi Darwin,

darwins, on 10 February 2020 - 11:59 PM, said:

Hopefully the version the does not cut power will continue to be developed - this is the version needed for steam locos where power can not be cut. It can also now be used for vacuum brakes on diesel and electric where the brake will now cut power as it should.Air brakes should also cut power - but it may be more accurate to retain a TCS that does cut power for EP braked stock.

If it is desired that a locomotive does not cut power when braking due to AWS, it is enough not to insert the DoesBrakeCutPower or to insert it with argument 0 in the .eng file, and to set AppliesCutsPower=false in the AWS block of the .ini file.

When the AWS script is operating, the standard MSTS Monitors (Overspeed, Emergency and Speed) are not executed. However AWS emulates 1:1 the execution of such monitors: the parameters that it considers are the ones which are present in the .ini file. If you check such file, you will see that such parameters are the same of those present in the .eng file.
So no MSTS Monitors function is lost using the AWS script, provided the .eng parameters are replicated, with the different syntax, in the .ini file.

Re emergency braking I suppose that what you have noticed is true also when the AWS script is disabled (general option "Disable TCS scripts" selected), so, as you say, that might be something of interest for Peter.
As of now the AWS script can only generate a full service braking, and not an emergency braking for an AWS alarm.

[Csantucci]

This new release of the script solves the problem of the impossibility to release TCSFullServiceBraking even at zero speed when TrainStopBeforeRelease=true has been selected.
 TCS_AWS_UK.zip (5.12K)
Number of downloads: 332

[Coolhand101]

Csantucci, on 11 February 2020 - 01:14 AM, said:

This new release of the script solves the problem of the impossibility to release TCSFullServiceBraking even at zero speed when TrainStopBeforeRelease=true has been selected.

Many thanks. Half of my trainsets use these feature, so now have to be quick to reset, to avoid a complete stop! :)