All the test were with ORTSTractionCharacteristics.
Having no MaxContinuousForce in the ENG file, there is no power loss, the same has having Max and Continuous force with the same figures.
When i first starting using the curves, i was getting different balancing speeds on the same grades. I had no ideal then, that the motors weaken over time.
Infact, on my test route, running uphill for 5 mins. i lost 1.7 mph of my balancing speed with the default ORTSContinuousForceTimeFactor.
Without the power lost option, or setting the ORTSContinuousForceTimeFactor to a higher setting, the power loss after 5 mins uphill, was negligible.
So what i will do, is set the max continuous force 10% lower than max force. And set the ORTSContinuousForceTimeFactor to 3600, to give the motors a 1 hour rating.
I always thought the ORTSContinuousForceTimeFactor, was the time allowed before the motors weaken. That would make sense as most DC motors power performance, are based on a 1 hour rating.
Thanks
Having no MaxContinuousForce in the ENG file, there is no power loss, the same has having Max and Continuous force with the same figures.
When i first starting using the curves, i was getting different balancing speeds on the same grades. I had no ideal then, that the motors weaken over time.
Infact, on my test route, running uphill for 5 mins. i lost 1.7 mph of my balancing speed with the default ORTSContinuousForceTimeFactor.
Without the power lost option, or setting the ORTSContinuousForceTimeFactor to a higher setting, the power loss after 5 mins uphill, was negligible.
So what i will do, is set the max continuous force 10% lower than max force. And set the ORTSContinuousForceTimeFactor to 3600, to give the motors a 1 hour rating.
I always thought the ORTSContinuousForceTimeFactor, was the time allowed before the motors weaken. That would make sense as most DC motors power performance, are based on a 1 hour rating.
Thanks
Comment