Partial ICE model with torque input in Newton-metres.
Models that inherit from this:
- partialIceP that contains an in ternal loop so that the request from the exterior is now in power instead of torque
- IceP used when ICE must follow a Power request
- IceConnP used when ICE must follow a Power request through an expandable connector
- IceConnPOO used when ICE must follow a Power request through an expandable connector, and also ON/Off can be commanded from the outside
- IceT used when ICE must follow a Torque request
See their documentation for further details or Appendix 3 in EHPTexamples tutorial for the general taxonomy of ICE based models.
---
To make access to torque limit table from file more flexible, the speed measured on the system is first multiplied by tlSpeedFactor; the obtained torque is then multiplied by tlTorqueFactor.
For instance speeds in the table might be in rpm instead of the SI rad/s. In this case, instead of manuallly multiplying all values in the input table, which might be tedious and error-prone, I can just set:
tlSpeedFactor=60/(2*pi)
Another example of usage of factors is when I want to re-use a torque limit map for a different machine, having the same shape but different values, If for instance I have a machine that has limits twice the one present in the table I can use:
tlTorqueFactor=2.
Inputted parameters tlTorqueFactor and tlSpeedFactor are not used when torque limit data are not taken from a txt file.