Meaning of spline id=-1 in .log file

c_sells
c_sells Altair Community Member
edited October 23 in Community Q&A

Hello, I'm curious if anyone knows what may cause a spline ID of -1 to be referenced in a "value out of range" warning in a motionsolve .log file. This doesn't appear to be a valid spline ID and I can't find any splines in my model with an xend = 80 either, so I'm guessing this is an auto-generated utility spline, possibly generated by the event. I'm just not sure how to debug without knowing what the spline is representing or where to find its definition.

image

Thanks

Tagged:

Answers

  • GTT Adam
    GTT Adam
    Altair Employee
    edited October 21

    Hi Chris Sells,

    You are correct in that this is a curve that is forced to extrapolate as it is looking for a value outside of a defined range. One thing you can try is to open the XML file using a text editor and search for anything that references a value of 80 to see what spline it may be referencing. The curve may also be from an AutoTire entity, SpringDamper, BumpStop, or ExtnesionStop entity so make sure to reference those for any values of 80 being used.

    It should be noted that this is not preventing the stimulation from running, however it may be outside of valid ranges.

     

    Hope this helps!

    Adam Reid

  • c_sells
    c_sells Altair Community Member
    edited October 21

    Hi Adam, thanks for the reply. Unfortunately, I did already complete a text find on the .xml and didn't come up with any values of 80 from splines in the model.

  • GTT Adam
    GTT Adam
    Altair Employee
    edited October 22

    Hi Chris Sells,

    Is there any way you can attach your model or an animation for review?

    Does this message appear at the beginning of the simulation or near the end?

    Can you please provide more information on the simulation? ie. full vehicle simulation trying to complete a double lane change, etc.

     

    Hope this helps!

    Adam Reid

  • c_sells
    c_sells Altair Community Member
    edited October 22

    Adam, I don't think I can attach the model here, but I can give some more details. It is a two-wheeler model built initially from the vehicle wizard with the rear suspension links modified, two flex-bodies, and the wizard defined deformable classic (non-inverted) fork model. I also have the detailed rider split up with torsion spring-dampers at the major joints, so the model is relatively complex for a two-wheeler.

    The event on the other hand is very simple, just a straight line coast down over a single cleat. The animation shows the model rolling forward and suddenly the solver stops without any visual deviation from path or unusual motion from the suspension so the animation isn't much use.

    The message appears in the middle of the dynamic portion of the simulation. I've also started getting warnings for the fork polybeam, though I haven't been able to pinpoint why as I haven't changed the layout from the wizard generated subsystem and all dimensions seem reasonable so I have more digging to do there as well.

    image

  • c_sells
    c_sells Altair Community Member
    edited October 22

    I should also note that I swapped in a non-deformable fork as a test and the QUISPL warning persisted, so it doesn't appear to be caused by something in the front fork subsystem.

  • GTT Adam
    GTT Adam
    Altair Employee
    edited October 23

    Hi Chris Sells,

    If you want to share this model, you can always create a Support Case to keep model information from the public.

    It looks as though the error message about the QUISPL function aligns with the point in which the simulation stops. So it looks to be a contributing factor to the simulation quitting.

    When you swapped for the rigid fork subsystem, did the warnings for Constraint_PTdCV/307001, which is a deformable curve, persist? 

    Have you tired this model performing any other events?

     

    Hope this helps!

    Adam Reid

Categories