Multistep - axle data
Summary
An axle data meant for city application, hence max inputSpeed is limited to value corresponding to 90kph.
However, in the first stage of the multistep simulations speed ranges for all duty cycles are being validated/run, where there's a couch cycle with 100kph Vmax, which is beyond the axles data range. requesting new rig tests just for the portion of the data which will never be used in final product calculations seems to be undue and expensive.
inputSpeed needs to be extended from 2775rpm to 3300rpm, just to pass data validation for coach cycle.
Can chassis builders extrapolate the certificate data so that it passes the data validation and rehash it?
Or, should the axle supplier, who initially provided the xml (as per product specifications), do the extrapolation and rehashing the certificate?
BTW, didn't we once discussed on laxities the VECTO should allow in multistep simulations as some chassis were too weak for some duty cycles and loadings? Hence, I would presume such one off failures could be forgiven in the chassis data validation.
Thanks
BR
Sanatjon Gofurov
VBC
Component(s) involved
axle
Data & steps to reproduce
Versions affected:
- Windows version(s): Win10
- VECTO versions(s): 4.0.3.3330
- .NET version(s): ...