[elvasleis]

Hi,
Some diesel locos are going into TCS Emergency braking with Open rails versions after X3606.
This loco JV1 Jet Test Vehicle available here http://www.christrai..._v1.0_setup.exe is an example.

Fault Tested on the USA1 route and at speed in explore the route mode.
Disable TCS scripts is ticked
Attached is the log.
Some others are some of the Russian M62 locos.


Regards Geoff.

Attached File(s)

•  OpenRails WIN10 JET TRAIN.txt (11.37K)
  Number of downloads: 194

[Kazareh]

Having this problem as well, annoyingly with some trains where they go a few km/h over the speed limit and it TCS Emergency BRakes, be it in activity mode, or explore. Rather unacceptable in explore mode, but also it's not picky about era of vehicle either. While TCS Braking may apply nicely for say, a Amtrak P42DC, it does NOT apply for a steam engine in-era, Milwaukee Electrics, etc etc.

Very annoying 'feature'

[vince]

 Kazareh, on 31 August 2016 - 08:23 AM, said:

............................ snip....................................Very annoying 'feature'

As I recall, there is a time delay setting in the engine file between the warning and brake application.
Here is a clip from the Acela of the sections that apply. What follows are not the default settings but my own. As you can see, I just zero'd most everything out but some selective altering may get you what you want.
I think one of the Route_Riter utilities is able alter these parameters globally.

EmergencyStopMonitor(
		MonitoringDeviceMonitorTimeLimit( 0 )
		MonitoringDeviceAlarmTimeLimit( 0 )
		MonitoringDevicePenaltyTimeLimit( 0 )
		MonitoringDeviceCriticalLevel( 0 )
		MonitoringDeviceResetLevel( 0 )
		MonitoringDeviceAppliesFullBrake( 0 )
		MonitoringDeviceAppliesEmergencyBrake( 0 )
		MonitoringDeviceAppliesCutsPower( 1 )
		MonitoringDeviceAppliesShutsDownEngine( 0 )
		)

	VigilanceMonitor(
		MonitoringDeviceMonitorTimeLimit( 45 )
		MonitoringDeviceAlarmTimeLimit( 37 )
		MonitoringDevicePenaltyTimeLimit( 0 )
		MonitoringDeviceCriticalLevel( 0 )
		MonitoringDeviceResetLevel( 0 )
		MonitoringDeviceAppliesFullBrake( 0 )
		MonitoringDeviceAppliesEmergencyBrake( 0 )
		MonitoringDeviceAppliesCutsPower( 0 )
		MonitoringDeviceAppliesShutsDownEngine( 0 )
		)

	OverspeedMonitor(
		MonitoringDeviceMonitorTimeLimit( 0 )
		MonitoringDeviceAlarmTimeLimit( 5 )
		MonitoringDevicePenaltyTimeLimit( 0 )
		MonitoringDeviceCriticalLevel( 151 )
		MonitoringDeviceResetLevel( 0 )
		MonitoringDeviceAppliesFullBrake( 0 )
		MonitoringDeviceAppliesEmergencyBrake( 0 )
		MonitoringDeviceAppliesCutsPower( 0 )
		MonitoringDeviceAppliesShutsDownEngine( 0 )
		MonitoringDeviceTriggerOnTrackOverspeed( 0 )
		MonitoringDeviceTriggerOnTrackOverspeedMargin( 2 )
		MonitoringDeviceResetOnZeroSpeed( 1 ) 
		MonitoringDeviceResetOnResetButton( 0 )
		)

Tweak these puppies and I think you will be pleased with the result. Just one engine at first tho' until you get it right.
regards,vince

[elvasleis]

Yes but something must have changed in the OR code since X3606 since the locos eng files have not changed.

[steamer_ctn]

 elvasleis, on 31 August 2016 - 10:00 PM, said:

Yes but something must have changed in the OR code since X3606 since the locos eng files have not changed.

Can you please recheck your test results, as my testing suggests that the change occurred when #3610 was introduced.

This would make more sense, as the change log indicates that a number of changes were made to the Train Control System of which the OverSpeedMonoitor is part of.

From #3610 onwards it appears that OR ignores the "TCS Script Disable" box in the Option Menu.

[elvasleis]

 steamer_ctn, on 31 August 2016 - 11:17 PM, said:

Can you please recheck your test results, as my testing suggests that the change occurred when #3610 was introduced.

This would make more sense, as the change log indicates that a number of changes were made to the Train Control System of which the OverSpeedMonoitor is part of.

From #3610 onwards it appears that OR ignores the "TCS Script Disable" box in the Option Menu.

Hi Peter,
You are correct in that the problem occurs in X3610 and onwards.

Regards Geoff

[Kazareh]

That's when it started for me as well, with X3610.

[Serana]

The previous code of the OverspeedMonitor was a mess in the previous versions. The code has been rewritten.
I may have forgotten some conditions. I will check that.

[steamer_ctn]

 Serana, on 01 September 2016 - 06:55 PM, said:

The previous code of the OverspeedMonitor was a mess in the previous versions. The code has been rewritten.
I may have forgotten some conditions. I will check that.

No problems.

Working on the code is sometimes like playing Russian roulette, so a good tidy up is welcomed.

[Jovet]

 steamer_ctn, on 02 September 2016 - 03:18 AM, said:

Working on the code is sometimes like playing Russian roulette, so a good tidy up is welcomed.

Refactoring code takes a lot of concentration and sometimes some planning. Starting with this and trying to make it neater and more flexible/sensible isn't always easy and straightforward.