VigilanceMonitor (Part2)

[Edward Keenan]

According to the last post under #1176894, any new issues are to be reported in a new bug report so here it goes. The locomotive in question does not have the VigilanceMonitor section, but it has the following below.

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

If you notice, all values are 0 which would mean either false or the numeric 0. At the start of the activity, as soon as the brakes are released and I start moving the train, I get the "Alerter:Acknowledge" message and the following message that the brakes are applied and they are applied. After tracing some of the code, I have found that for some reason VigilanceAlarm is set to true which should not be the case since the activity is just starting. I have experimented by putting values into the first 2 TimeLimit categories, but no change.

Edward K.

[Edward Keenan (edwardk)]

Note: I was using V1743 and I noticed a fix for the alerter under V1746 which I tested, but this issue still exists.

Edward K.

[Edward Keenan (edwardk)]

It seems that a few more tests need to be in place. Since the above block from the FP45 is all 0's, this means that there is no alerter system in place, but OR seems to want to put one in place. I removed the above block and the issue of course has been solved. What procedure is OR going to follow in regards to the alerter system?

Edward K.

[Edward Keenan (edwardk)]

If I run the compiled code for V1746 as is once downloaded with the above activity and locomotive, the alerter issue will come up as initially posted. I ran the code under Express 2008 and guess what, the issue is not present?? I ran it more than once to be sure this is the case and the issue was not present. Evidently the code needed to be recompiled before running so this was the only change to the code. I tried the above procedure with V1743 and I still experienced the issue so evidently this is only involving V1746.

Edward K.

[Edward Keenan (edwardk)]

Disregard my last post. I totally forgot I was testing using the command line method so the alerter option was not being utilized.

Edward K.

[Peter Gulyas (pzgulyas)]

Adjusted in r1751.

[Edward Keenan (edwardk)]

Peter,

Confirming that this issue has been fixed.

Edward K.