[scottb613]

Hi Folks,

Fired up some old diesels (NALW FP-40's with the later Texture Upgrade) I haven't used in a while on the Cajon Pass (Marc's Upgraded Ver)... I get a TCS Emergency Brake application every five seconds... I've searched and read some previous posts on the subject here and it sounded like it was resolved... I'm not sure why I am getting it and here is what I have done:

• I started with a twin loco setup at first - then switched to a single loco.
  
• I tried different locations on the route.
  
• I tried several of the locomotives in the pack - all with the same result.
  
• I tried them in MSTS and they worked fine - no TCS Emergency Brake application.
  
• I found and removed the "Vigilance" line from the ENG files.
  
• I made sure the "Alerter" function was disabled in ORTS.
  
• I tested in "Explore Mode" - then went to "Manual" mode - no change - still trips the brakes.
  
• I built an activity and made the locos in question the "Player Consist".

ORTS - nothing works - brakes trip within 5 seconds of opening the throttle... MSTS the same locomotives work fine without issue...

. . . - - - . . .

ENG files attached:
 Amtrak400.zip (48.18K)
Number of downloads: 284

Regards,
Scott

[gpz]

Without testing the files actually, I see that you have the following entries in the .eng file:

VigilanceMonitor(
		MonitoringDeviceMonitorTimeLimit( -1 )
		MonitoringDeviceAlarmTimeLimit( 5 )
                ...
                ...
                ...
)

The second line sets the time between the last vigilance reset and the beginning of the new audible alert, the first line sets the time between the last reset and the emergency brake application, in seconds. Some more sensible values for these would be 66, 60, respectively. The value of -1 is really weird, the code might not be protected against feeding it with such a physically nonsense value. :bigboss:

[scottb613]

Hi Peter,

Thanks for looking - I kind of thought it was related to "Vigilance" - I had found and removed "Vigilance (0 1 0)" in all the files - I must have missed the additional occurrences - I'm assuming I can just removes these lines as well...

Diesels are not my forte...

Appreciate the help - sir !!!
:bigboss:

Regards,
Scott

[gpz]

Vigilance (0 1 0) line isn't used by OpenRails at all. :bigboss:

[markus_GE]

Having done loads of research also in that direction for my DPU program, I can say those -1 values are not exactly use over and over, but still occur frequent times. AFAICT they are used as some shortcut to make MSTS think the VigilanceMonitor is switched off.

Cheers, Markus

[ATW]

With
VigilanceMonitor(
MonitoringDeviceMonitorTimeLimit( 50 )
MonitoringDeviceAlarmTimeLimit( 30 )

I have 20 seconds to respond because the limit is set seconds between the two options.

BTW for some units like the default Acela or other units equipped these have not been implemented either:

DoesBrakeCutPower( 1 )
BrakeCutsPowerAtBrakeCylinderPressure( 15 )

MonitoringDeviceAppliesCutsPower( 1 )
MonitoringDeviceAppliesShutsDownEngine( 1 )