I am trying to do full vehicle mbd with electric powertrain. I have used the fmu and property files for the 100 KW motor that are available by default. I tried to run an npost shaker event but got the following errors.

SHRIKAR WADADARE
SHRIKAR WADADARE Altair Community Member
edited October 2023 in Community Q&A

"ERROR" "MotionView" "Unknown symbol sys_r_driveline.b_carrier...Error resolving entity Differential for torque output under Model-Electric Powertrain (FMU). [General]" 
"ERROR" "MotionView" "Unknown symbol sys_instrumentation.sv_vx...Error resolving entity Vehicle long. vel. under Model-Electric Powertrain (FMU). [General]" 
"ERROR" "MotionView" "Unknown symbol "arg_veh_long_vel.VARVAL" in expression:...arg_veh_long_vel.VARVAL...Templex error evaluating Engine/Motor (FMU) Inputs-f3_expr under Model-Electric Powertrain (FMU)-Motor (FMU). [General]" 
"ERROR" "MotionView" "Unknown symbol "arg_veh_long_vel.VARVAL" in expression:...arg_veh_long_vel.VARVAL...Templex error evaluating FMU Motor/Engine-inputs-sv_2-value-expr under Model-Electric Powertrain (FMU)-Motor (FMU). [General]" 

Tagged:

Best Answer

  • GTT Adam
    GTT Adam
    Altair Employee
    edited October 2023 Answer ✓
    SHRIKAR WADADARE said:

    image

    This is what I can see. I can't find the Altair driver here. But it is there in my model.

    image

    Hi Shrikar,

    I see now that you are using v2022.2. I was showing a snapshot from v2023, which I would suggest you upgrade to as well. The classic interface you are using is no longer supported and is also behind the upgrades made originally in 2022.3.

    Another way to see if the entities exist is by examining the .XML. Try to export an XML by File >> Export >> Solver Deck. If I open the .XML in a text editor like Notepad, I can search for "m_gyro_body" and it pulls up the entity:

    image

    So I can confirm that this entity is not the issue. Continue with this method until you find which entity is missing.

    Or, since we know all of the 'missing' entities are from the Altair Driver Model, delete it and reinsert it.

    Lastly, you can try the "Update Model" option, through the Vehicle Tools ribbon. This may repair some damage you accidentally did when inserting the Altair Driver Model.

     

    Hope this helps!

     

    Adam Reid

Answers

  • GTT Adam
    GTT Adam
    Altair Employee
    edited October 2023

    Hi Shrikar,

    Since the electric powertrain is not necessary for an N-Post event, you could always deactivate it for this event to make these errors disappear. However, it looks like there are 4 issues within your model that need to be resolved:

    1. There is an output with a label named "Differential for torque output" that is trying to reference a body with a varname of "sys_r_driveline.b_carrier". Based on your assembly modifications, you may have removed this body, likely named "Carrier". You can update the output expression to no longer use this body, update the body it is referencing in the expression to a new one, or suppress the output altogether if you do not need it. 
    2. There is an output with a label named "Vehicle long. vel." that is trying to reference a solver variable with a varname of "sys_instrumentation.sv_vx". You can update the output expression to no longer use this solver variable, update the solver variable it is referencing in the expression to a different one, or suppress the output altogether if you do not need it. 
    3. There is an input to your FMU that is trying to use "arg_veh_long_vel.VARVAL" in the expression, however since it is not working (#2 above) is it not able to use the expression. If you fix #2, this should go away.
    4. Same as #3.

    Hope this helps!

     

    Adam Reid

  • SHRIKAR WADADARE
    SHRIKAR WADADARE Altair Community Member
    edited October 2023
    Adam Reid_21142 said:

    Hi Shrikar,

    Since the electric powertrain is not necessary for an N-Post event, you could always deactivate it for this event to make these errors disappear. However, it looks like there are 4 issues within your model that need to be resolved:

    1. There is an output with a label named "Differential for torque output" that is trying to reference a body with a varname of "sys_r_driveline.b_carrier". Based on your assembly modifications, you may have removed this body, likely named "Carrier". You can update the output expression to no longer use this body, update the body it is referencing in the expression to a new one, or suppress the output altogether if you do not need it. 
    2. There is an output with a label named "Vehicle long. vel." that is trying to reference a solver variable with a varname of "sys_instrumentation.sv_vx". You can update the output expression to no longer use this solver variable, update the solver variable it is referencing in the expression to a different one, or suppress the output altogether if you do not need it. 
    3. There is an input to your FMU that is trying to use "arg_veh_long_vel.VARVAL" in the expression, however since it is not working (#2 above) is it not able to use the expression. If you fix #2, this should go away.
    4. Same as #3.

    Hope this helps!

     

    Adam Reid

    Thanks this cleared most of the things and I ran the npost event but now when I try to run any other dynamic events it shows some errors and I can't seem to figure out anything .

    "17:38:37" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline3-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline3-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline3-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline4-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline4-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline4-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline5-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline5-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline5-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline6-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline6-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline6-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline7-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline7-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline7-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline8-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline8-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline8-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline9-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline9-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline9-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline10-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline10-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline10-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline11-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline11-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline11-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline12-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline12-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline12-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Unknown symbol altair_driver.sys_gyro.m_gyro_body...Error resolving entity Attachment att_veh_IC under Model-DoubleLaneChange 0-Altair Driver. [General]" 
    "17:38:38" "ERROR" "MotionView" "Unknown symbol "att_veh_IC.id" in expression:...att_veh_IC.id...Templex error evaluating text under Model-DoubleLaneChange 0-Altair Driver. [General]" 

  • GTT Adam
    GTT Adam
    Altair Employee
    edited October 2023
    SHRIKAR WADADARE said:

    Thanks this cleared most of the things and I ran the npost event but now when I try to run any other dynamic events it shows some errors and I can't seem to figure out anything .

    "17:38:37" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline3-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline3-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline3-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline4-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline4-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline4-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline5-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline5-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline5-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline6-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline6-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline6-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline7-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline7-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline7-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline8-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline8-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline8-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline9-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline9-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline9-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline10-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline10-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline10-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline11-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline11-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline11-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline12-x under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline12-y under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Argument 2 must be a Templex vector, or a Point, or a Marker, or a Vector...Math parser error evaluating Path Outline12-z under Model-DoubleLaneChange 0-Lane Graphics. [General]" 
    "17:38:38" "ERROR" "MotionView" "Unknown symbol altair_driver.sys_gyro.m_gyro_body...Error resolving entity Attachment att_veh_IC under Model-DoubleLaneChange 0-Altair Driver. [General]" 
    "17:38:38" "ERROR" "MotionView" "Unknown symbol "att_veh_IC.id" in expression:...att_veh_IC.id...Templex error evaluating text under Model-DoubleLaneChange 0-Altair Driver. [General]" 

    Hi Shrikar,

    It looks like the event you are trying next is the NATO double lane change. It uses graphics for cones to show where the gates are for the entrance, recovery, and exit are located. The "Path Outline" is trying to reference these cones to determine the event dimensions, and it is not able to do so. If you deactivated the cones or the event attachments are not defined properly, this may be the cause of your issue.

    Hope this helps!

     

    Adam Reid

  • SHRIKAR WADADARE
    SHRIKAR WADADARE Altair Community Member
    edited October 2023
    Adam Reid_21142 said:

    Hi Shrikar,

    It looks like the event you are trying next is the NATO double lane change. It uses graphics for cones to show where the gates are for the entrance, recovery, and exit are located. The "Path Outline" is trying to reference these cones to determine the event dimensions, and it is not able to do so. If you deactivated the cones or the event attachments are not defined properly, this may be the cause of your issue.

    Hope this helps!

     

    Adam Reid

    So, I did not deactivate anything. I just added the event from the analysis section and tried to run it on default settings without altering anything but looks like it is facing an error evaluating the path outline but I can't figure out why. For the last two errors, I am not able to find the expression only where att_veh_IC has been used under Model-DoubleLaneChange 0-Altair Driver. Following is one of the set of equations for a path outline:

    path outline 5
    loc_along_dir( altair_driver.m_ref_path.origin, altair_driver.m_veh_orientation.xaxis, ( ds.length_section1.value + ds.length_section2.value)*1000 )[0]
    loc_along_dir( altair_driver.m_ref_path.origin, altair_driver.m_veh_orientation.yaxis, 500*ds.path_width.value + (ds.turn_direction.value == "Right" ? -1 : 1) * ds.lateral_offset.value*1000 )[1]
    loc_along_dir( altair_driver.m_ref_path.origin, altair_driver.m_veh_orientation.zaxis, 0.0 )[2]

     

  • SHRIKAR WADADARE
    SHRIKAR WADADARE Altair Community Member
    edited October 2023
    Adam Reid_21142 said:

    Hi Shrikar,

    It looks like the event you are trying next is the NATO double lane change. It uses graphics for cones to show where the gates are for the entrance, recovery, and exit are located. The "Path Outline" is trying to reference these cones to determine the event dimensions, and it is not able to do so. If you deactivated the cones or the event attachments are not defined properly, this may be the cause of your issue.

    Hope this helps!

     

    Adam Reid

    Also if it helps, what I have done is I built my model using FSAE libraries and then imported only the electric powertrain FMU system from the small car model.   

  • GTT Adam
    GTT Adam
    Altair Employee
    edited October 2023
    SHRIKAR WADADARE said:

    Also if it helps, what I have done is I built my model using FSAE libraries and then imported only the electric powertrain FMU system from the small car model.   

    Hi Shrikar,

    Did you also insert the Altair Driver Model? If you constructed the model without the use of the Assembly Wizard or without starting from an example model from the Vehicle Tools extension, then you might have not the Driver Model inserted or attached properly. Can you confirm that you have a system named Altair Driver and that the attachments do not show any are unresolved?

    Hope this helps!

     

    Adam Reid

  • SHRIKAR WADADARE
    SHRIKAR WADADARE Altair Community Member
    edited October 2023
    Adam Reid_21142 said:

    Hi Shrikar,

    Did you also insert the Altair Driver Model? If you constructed the model without the use of the Assembly Wizard or without starting from an example model from the Vehicle Tools extension, then you might have not the Driver Model inserted or attached properly. Can you confirm that you have a system named Altair Driver and that the attachments do not show any are unresolved?

    Hope this helps!

     

    Adam Reid

    Yes,image I have the Altair driver imported as well and none of the attachments are unresolved.

  • GTT Adam
    GTT Adam
    Altair Employee
    edited October 2023
    SHRIKAR WADADARE said:

    Yes,image I have the Altair driver imported as well and none of the attachments are unresolved.

    Hi Shrikar,

    Can you confirm that a default vehicle will complete the double lane change? That way, we can be certain that your installation is functioning and that this issue is localized to your model only. Start a new session, and create the Sedan 1 model from Vehicle Tools >> Example Models. Next, add the double lane change event from Analysis >> Task Wizard. If the simulation completes, you can use this as a template to help diagnose what might be missing in your model.

    Hope this helps!

     

    Adam Reid

  • SHRIKAR WADADARE
    SHRIKAR WADADARE Altair Community Member
    edited October 2023
    Adam Reid_21142 said:

    Hi Shrikar,

    Can you confirm that a default vehicle will complete the double lane change? That way, we can be certain that your installation is functioning and that this issue is localized to your model only. Start a new session, and create the Sedan 1 model from Vehicle Tools >> Example Models. Next, add the double lane change event from Analysis >> Task Wizard. If the simulation completes, you can use this as a template to help diagnose what might be missing in your model.

    Hope this helps!

     

    Adam Reid

    Yeah, I tried it, but the only thing I could figure out was the path outline error but not how that would be solved. image

     

     

    image

    So, there are four things that are unresolved which I can't seem to find :

    altair_driver.sys_gyro.m_gyro_body

    att_veh_IC.id

    altair_driver.m_ref_path.origin

    altair_driver.m_veh_orientation.xaxis (y and z axis as well)

    The issue is I can't find these anywhere in my model. 

  • GTT Adam
    GTT Adam
    Altair Employee
    edited October 2023
    SHRIKAR WADADARE said:

    Yeah, I tried it, but the only thing I could figure out was the path outline error but not how that would be solved. image

     

     

    image

    So, there are four things that are unresolved which I can't seem to find :

    altair_driver.sys_gyro.m_gyro_body

    att_veh_IC.id

    altair_driver.m_ref_path.origin

    altair_driver.m_veh_orientation.xaxis (y and z axis as well)

    The issue is I can't find these anywhere in my model. 

    Hi Shrikar,

    You are going to have to determine if those entities exist in your model or not. To do so, open the Expression Builder for any entity and navigate through the hierarchy until you locate it. If they do not exist, you have likely implemented your Altair Driver Model incorrectly. For example, if we wanted to find the altair_driver.m_ref_path.origin marker, you can see how I found it using the Expression Builder in the attached picture:

    image

    Hope this helps!

     

    Adam Reid

  • SHRIKAR WADADARE
    SHRIKAR WADADARE Altair Community Member
    edited October 2023
    Adam Reid_21142 said:

    Hi Shrikar,

    You are going to have to determine if those entities exist in your model or not. To do so, open the Expression Builder for any entity and navigate through the hierarchy until you locate it. If they do not exist, you have likely implemented your Altair Driver Model incorrectly. For example, if we wanted to find the altair_driver.m_ref_path.origin marker, you can see how I found it using the Expression Builder in the attached picture:

    image

    Hope this helps!

     

    Adam Reid

    image

    This is what I can see. I can't find the Altair driver here. But it is there in my model.

    image

  • GTT Adam
    GTT Adam
    Altair Employee
    edited October 2023 Answer ✓
    SHRIKAR WADADARE said:

    image

    This is what I can see. I can't find the Altair driver here. But it is there in my model.

    image

    Hi Shrikar,

    I see now that you are using v2022.2. I was showing a snapshot from v2023, which I would suggest you upgrade to as well. The classic interface you are using is no longer supported and is also behind the upgrades made originally in 2022.3.

    Another way to see if the entities exist is by examining the .XML. Try to export an XML by File >> Export >> Solver Deck. If I open the .XML in a text editor like Notepad, I can search for "m_gyro_body" and it pulls up the entity:

    image

    So I can confirm that this entity is not the issue. Continue with this method until you find which entity is missing.

    Or, since we know all of the 'missing' entities are from the Altair Driver Model, delete it and reinsert it.

    Lastly, you can try the "Update Model" option, through the Vehicle Tools ribbon. This may repair some damage you accidentally did when inserting the Altair Driver Model.

     

    Hope this helps!

     

    Adam Reid

  • SHRIKAR WADADARE
    SHRIKAR WADADARE Altair Community Member
    edited October 2023
    Adam Reid_21142 said:

    Hi Shrikar,

    I see now that you are using v2022.2. I was showing a snapshot from v2023, which I would suggest you upgrade to as well. The classic interface you are using is no longer supported and is also behind the upgrades made originally in 2022.3.

    Another way to see if the entities exist is by examining the .XML. Try to export an XML by File >> Export >> Solver Deck. If I open the .XML in a text editor like Notepad, I can search for "m_gyro_body" and it pulls up the entity:

    image

    So I can confirm that this entity is not the issue. Continue with this method until you find which entity is missing.

    Or, since we know all of the 'missing' entities are from the Altair Driver Model, delete it and reinsert it.

    Lastly, you can try the "Update Model" option, through the Vehicle Tools ribbon. This may repair some damage you accidentally did when inserting the Altair Driver Model.

     

    Hope this helps!

     

    Adam Reid

    First of all, huge thanks for your help – without your help, I doubt I would have been able to move my car. But now, it's on an adventure of its own. 

    It's showing behavior that's got me scratching my head a bit. ????‍♂️

    I'd love to pick your brain about this new quirkiness. Thanks again for all your previous assistance,

    watch this

    Thank you,

    Shrikar

  • GTT Adam
    GTT Adam
    Altair Employee
    edited October 2023
    SHRIKAR WADADARE said:

    First of all, huge thanks for your help – without your help, I doubt I would have been able to move my car. But now, it's on an adventure of its own. 

    It's showing behavior that's got me scratching my head a bit. ????‍♂️

    I'd love to pick your brain about this new quirkiness. Thanks again for all your previous assistance,

    watch this

    Thank you,

    Shrikar

    Hi Shrikar,

    Not a problem. I'm glad we were able to get your model running, and hopefully with a little modification we can get it performing as intended.

    Would you mind creating a new thread for this new troubleshooting request?

     

    Adam Reid

  • SHRIKAR WADADARE
    SHRIKAR WADADARE Altair Community Member
    edited October 2023
    Adam Reid_21142 said:

    Hi Shrikar,

    Not a problem. I'm glad we were able to get your model running, and hopefully with a little modification we can get it performing as intended.

    Would you mind creating a new thread for this new troubleshooting request?

     

    Adam Reid

    Sure. Thanks a lot again.

     

Categories