Negative tractive force values within ORTSMaxTractiveForceCurves aren't considered

Bug #1751067 reported by Carlo Santucci on 2018-02-22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Open Rails
Carlo Santucci

Bug Description

OR moves to zero any calculated tractive force value < 0.
However there are cases where negative tractive force values exist. E.g. in old triphase locomotives equipped with asynchronous motors, when the speed becomes higher than the sync speed (usually when running downhill), the motors start braking, acting as generators, and therefore their tractive force is negative.

Changed in or:
assignee: nobody → Carlo Santucci (carlosanit1)
status: New → In Progress
Carlo Santucci (carlosanit1) wrote :

Fixed in x.4079. If there are negative tractive force values within ORTSMaxTractiveForceCurves and the computed tractive force is negative, the latter is not clamped to 0.

Changed in or:
status: In Progress → Fix Committed
James Ross (twpol) on 2018-06-24
Changed in or:
importance: Undecided → Medium
milestone: none → 1.3
James Ross (twpol) on 2018-11-30
Changed in or:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers