Error 6523 - Negative basic x coordinate (GRID 3) is illegal (Axisymmetric analysis)

Wesley Peijnenburg
Wesley Peijnenburg Altair Community Member
edited March 2023 in Community Q&A

 

In a 2D axisymmetric analysis I get the following error: "Error 6523 - Negative basic x coordinate (GRID 3) is illegal". But no geometry is defined in negative X in my model. 

 

What could be the cause, and how to solve that?

 

Tutorial OS-T 1394 was used for comparison; if I use the initial file "Ball_Joint_2D_Axisymmetry.hm" then everything is fine but if I start from scratch, this error keeps popping up? So it looks like I missed something. I tried both the XY and XZ system.

 

Best Answer

  • PaulAltair
    PaulAltair
    Altair Employee
    edited February 2023 Answer ✓

    As the original error states, GRID 3 has a negative X value (albeit a very very small one of -8.6e-17), if I make that 0.0, the model is able to run

    image

Answers

  • PaulAltair
    PaulAltair
    Altair Employee
    edited February 2023

    What are the coordinates of GRID 3? can you share your model?

  • Wesley Peijnenburg
    Wesley Peijnenburg Altair Community Member
    edited February 2023

    What are the coordinates of GRID 3? can you share your model?

    Yes, see attached:

    - The model from OS-T 1394 (works fine) and,

    - The model of a sphere against a wall which I'm currently working on

  • PaulAltair
    PaulAltair
    Altair Employee
    edited February 2023 Answer ✓

    As the original error states, GRID 3 has a negative X value (albeit a very very small one of -8.6e-17), if I make that 0.0, the model is able to run

    image

  • Wesley Peijnenburg
    Wesley Peijnenburg Altair Community Member
    edited February 2023

    As the original error states, GRID 3 has a negative X value (albeit a very very small one of -8.6e-17), if I make that 0.0, the model is able to run

    image

    Indeed, thank you!

  • Wesley Peijnenburg
    Wesley Peijnenburg Altair Community Member
    edited March 2023

     

    For anyone with the same error: Paul Sharp's solution could be automated with the below TCL code for this model. 

     

    # Loop over node coordinates and correct X<0 if needed:
    *createmark nodes 1 "all"
    foreach {nid} [hm_getmark nodes 1] {
        set coord_x [hm_getvalue nodes id=$nid dataname=x]
        set coord_y [hm_getvalue nodes id=$nid dataname=y]
        set coord_z [hm_getvalue nodes id=$nid dataname=z]

        if {$coord_x < 0} then {
          *setvalue nodes id=$nid localcoordinates={0 $coord_y $coord_z}
        }
    }