OMSimulator -r=ModelicaTest_3.2.1_ModelicaTest.MultiBody.Joints.JointUSP2_res.mat --tempDir=temp_ModelicaTest_3_2_1_ModelicaTest_MultiBody_Joints_JointUSP2_fmu --startTime=0 --stopTime=4 --timeout=50 --tolerance=1e-06 ModelicaTest_3_2_1_ModelicaTest_MultiBody_Joints_JointUSP2.fmu info: Set temp directory to "/tmp/omsimulator" info: Set working directory to "." info: New temp directory has been created: "temp_ModelicaTest_3_2_1_ModelicaTest_MultiBody_Joints_JointUSP2_fmu" info: Set temp directory to "/var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelicaLibraryTesting/ModelicaTest_3.2.1_ModelicaTest.MultiBody.Joints.JointUSP2/temp_ModelicaTest_3_2_1_ModelicaTest_MultiBody_Joints_JointUSP2_fmu" info: Set working directory to "/var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelicaLibraryTesting/ModelicaTest_3.2.1_ModelicaTest.MultiBody.Joints.JointUSP2" info: New model "model" with corresponding temp directory "/var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelicaLibraryTesting/ModelicaTest_3.2.1_ModelicaTest.MultiBody.Joints.JointUSP2/temp_ModelicaTest_3_2_1_ModelicaTest_MultiBody_Joints_JointUSP2_fmu/model-xmhyyaks" info: maximum step size for 'model.root': 0.100000 info: No result file will be created stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.020202. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.303030. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 2.505051. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.151515. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.151515. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.232323. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.232323. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.232323. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.232323. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.232323. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.232323. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.232323. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.232323. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.232323. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.272727. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.313131. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.313131. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.313131. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.313131. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.313131. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.313131. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.353535. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.353535. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.353535. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.353535. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.353535. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.353535. That might raise performance issues, for more information use -lv LOG_LS. stdout | warning | The default linear solver fails, the fallback solver with total pivoting is started at time 3.353535. That might raise performance issues, for more information use -lv LOG_LS. warning: fmu (logStatusWarning): /var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelica/OMCompiler/build/lib/omlibrary/Modelica 3.2.1/Mechanics/MultiBody/Joints.mo:8428: The following assertion has been violated at time 3.353535 noEvent(jointUSP.prismatic.k1a > 1e-10) assert | error | | | | | Singular position of loop (either no or two analytic solutions; | | | | the mechanism has lost one-degree-of freedom in this position). | | | | Try first to use another Modelica.Mechanics.MultiBody.Joints.Assemblies.JointXXX component. | | | | If this also lead to singular positions, it could be that this | | | | kinematic loop cannot be solved analytically with a fixed state | | | | selection. In this case you have to build up the loop with | | | | basic joints (NO aggregation JointXXX components) and rely on | | | | dynamic state selection, i.e., during simulation the states will | | | | be dynamically selected in such a way that in no position a | | | | degree of freedom is lost. error: [fmi2logger] fmu (logFmi2Call): fmi2CompletedIntegratorStep: terminated by an assertion. error: [stepUntil] fmi2_import_completed_integrator_step failed for FMU "model.root.fmu" warning: fmu (logStatusWarning): /var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelica/OMCompiler/build/lib/omlibrary/Modelica 3.2.1/Mechanics/MultiBody/Joints.mo:8428: The following assertion has been violated at time 3.393939 noEvent(jointUSP.prismatic.k1a > 1e-10) assert | error | | | | | Singular position of loop (either no or two analytic solutions; | | | | the mechanism has lost one-degree-of freedom in this position). | | | | Try first to use another Modelica.Mechanics.MultiBody.Joints.Assemblies.JointXXX component. | | | | If this also lead to singular positions, it could be that this | | | | kinematic loop cannot be solved analytically with a fixed state | | | | selection. In this case you have to build up the loop with | | | | basic joints (NO aggregation JointXXX components) and rely on | | | | dynamic state selection, i.e., during simulation the states will | | | | be dynamically selected in such a way that in no position a | | | | degree of freedom is lost. error: [fmi2logger] fmu (logFmi2Call): fmi2CompletedIntegratorStep: terminated by an assertion. error: [stepUntil] fmi2_import_completed_integrator_step failed for FMU "model.root.fmu" warning: fmu (logStatusWarning): /var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelica/OMCompiler/build/lib/omlibrary/Modelica 3.2.1/Mechanics/MultiBody/Joints.mo:8428: The following assertion has been violated at time 3.434343 noEvent(jointUSP.prismatic.k1a > 1e-10) assert | error | | | | | Singular position of loop (either no or two analytic solutions; | | | | the mechanism has lost one-degree-of freedom in this position). | | | | Try first to use another Modelica.Mechanics.MultiBody.Joints.Assemblies.JointXXX component. | | | | If this also lead to singular positions, it could be that this | | | | kinematic loop cannot be solved analytically with a fixed state | | | | selection. In this case you have to build up the loop with | | | | basic joints (NO aggregation JointXXX components) and rely on | | | | dynamic state selection, i.e., during simulation the states will | | | | be dynamically selected in such a way that in no position a | | | | degree of freedom is lost. error: [fmi2logger] fmu (logFmi2Call): fmi2CompletedIntegratorStep: terminated by an assertion. error: [stepUntil] fmi2_import_completed_integrator_step failed for FMU "model.root.fmu" warning: fmu (logStatusWarning): /var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelica/OMCompiler/build/lib/omlibrary/Modelica 3.2.1/Mechanics/MultiBody/Joints.mo:8428: The following assertion has been violated at time 3.474747 noEvent(jointUSP.prismatic.k1a > 1e-10) assert | error | | | | | Singular position of loop (either no or two analytic solutions; | | | | the mechanism has lost one-degree-of freedom in this position). | | | | Try first to use another Modelica.Mechanics.MultiBody.Joints.Assemblies.JointXXX component. | | | | If this also lead to singular positions, it could be that this | | | | kinematic loop cannot be solved analytically with a fixed state | | | | selection. In this case you have to build up the loop with | | | | basic joints (NO aggregation JointXXX components) and rely on | | | | dynamic state selection, i.e., during simulation the states will | | | | be dynamically selected in such a way that in no position a | | | | degree of freedom is lost. error: [fmi2logger] fmu (logFmi2Call): fmi2CompletedIntegratorStep: terminated by an assertion. error: [stepUntil] fmi2_import_completed_integrator_step failed for FMU "model.root.fmu" warning: fmu (logStatusWarning): /var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelica/OMCompiler/build/lib/omlibrary/Modelica 3.2.1/Mechanics/MultiBody/Joints.mo:8428: The following assertion has been violated at time 3.515152 noEvent(jointUSP.prismatic.k1a > 1e-10) assert | error | | | | | Singular position of loop (either no or two analytic solutions; | | | | the mechanism has lost one-degree-of freedom in this position). | | | | Try first to use another Modelica.Mechanics.MultiBody.Joints.Assemblies.JointXXX component. | | | | If this also lead to singular positions, it could be that this | | | | kinematic loop cannot be solved analytically with a fixed state | | | | selection. In this case you have to build up the loop with | | | | basic joints (NO aggregation JointXXX components) and rely on | | | | dynamic state selection, i.e., during simulation the states will | | | | be dynamically selected in such a way that in no position a | | | | degree of freedom is lost. error: [fmi2logger] fmu (logFmi2Call): fmi2CompletedIntegratorStep: terminated by an assertion. error: [stepUntil] fmi2_import_completed_integrator_step failed for FMU "model.root.fmu" warning: fmu (logStatusWarning): /var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelica/OMCompiler/build/lib/omlibrary/Modelica 3.2.1/Mechanics/MultiBody/Joints.mo:8428: The following assertion has been violated at time 3.595960 noEvent(jointUSP.prismatic.k1a > 1e-10) assert | error | | | | | Singular position of loop (either no or two analytic solutions; | | | | the mechanism has lost one-degree-of freedom in this position). | | | | Try first to use another Modelica.Mechanics.MultiBody.Joints.Assemblies.JointXXX component. | | | | If this also lead to singular positions, it could be that this | | | | kinematic loop cannot be solved analytically with a fixed state | | | | selection. In this case you have to build up the loop with | | | | basic joints (NO aggregation JointXXX components) and rely on | | | | dynamic state selection, i.e., during simulation the states will | | | | be dynamically selected in such a way that in no position a | | | | degree of freedom is lost. error: [fmi2logger] fmu (logFmi2Call): fmi2CompletedIntegratorStep: terminated by an assertion. error: [stepUntil] fmi2_import_completed_integrator_step failed for FMU "model.root.fmu" warning: fmu (logStatusWarning): /var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelica/OMCompiler/build/lib/omlibrary/Modelica 3.2.1/Mechanics/MultiBody/Joints.mo:8428: The following assertion has been violated at time 3.636364 noEvent(jointUSP.prismatic.k1a > 1e-10) assert | error | | | | | Singular position of loop (either no or two analytic solutions; | | | | the mechanism has lost one-degree-of freedom in this position). | | | | Try first to use another Modelica.Mechanics.MultiBody.Joints.Assemblies.JointXXX component. | | | | If this also lead to singular positions, it could be that this | | | | kinematic loop cannot be solved analytically with a fixed state | | | | selection. In this case you have to build up the loop with | | | | basic joints (NO aggregation JointXXX components) and rely on | | | | dynamic state selection, i.e., during simulation the states will | | | | be dynamically selected in such a way that in no position a | | | | degree of freedom is lost. error: [fmi2logger] fmu (logFmi2Call): fmi2CompletedIntegratorStep: terminated by an assertion. error: [stepUntil] fmi2_import_completed_integrator_step failed for FMU "model.root.fmu" warning: fmu (logStatusWarning): /var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelica/OMCompiler/build/lib/omlibrary/Modelica 3.2.1/Mechanics/MultiBody/Joints.mo:8428: The following assertion has been violated at time 3.676768 noEvent(jointUSP.prismatic.k1a > 1e-10) assert | error | | | | | Singular position of loop (either no or two analytic solutions; | | | | the mechanism has lost one-degree-of freedom in this position). | | | | Try first to use another Modelica.Mechanics.MultiBody.Joints.Assemblies.JointXXX component. | | | | If this also lead to singular positions, it could be that this | | | | kinematic loop cannot be solved analytically with a fixed state | | | | selection. In this case you have to build up the loop with | | | | basic joints (NO aggregation JointXXX components) and rely on | | | | dynamic state selection, i.e., during simulation the states will | | | | be dynamically selected in such a way that in no position a | | | | degree of freedom is lost. error: [fmi2logger] fmu (logFmi2Call): fmi2CompletedIntegratorStep: terminated by an assertion. error: [stepUntil] fmi2_import_completed_integrator_step failed for FMU "model.root.fmu" warning: fmu (logStatusWarning): /var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelica/OMCompiler/build/lib/omlibrary/Modelica 3.2.1/Mechanics/MultiBody/Joints.mo:8428: The following assertion has been violated at time 3.717172 noEvent(jointUSP.prismatic.k1a > 1e-10) assert | error | | | | | Singular position of loop (either no or two analytic solutions; | | | | the mechanism has lost one-degree-of freedom in this position). | | | | Try first to use another Modelica.Mechanics.MultiBody.Joints.Assemblies.JointXXX component. | | | | If this also lead to singular positions, it could be that this | | | | kinematic loop cannot be solved analytically with a fixed state | | | | selection. In this case you have to build up the loop with | | | | basic joints (NO aggregation JointXXX components) and rely on | | | | dynamic state selection, i.e., during simulation the states will | | | | be dynamically selected in such a way that in no position a | | | | degree of freedom is lost. error: [fmi2logger] fmu (logFmi2Call): fmi2CompletedIntegratorStep: terminated by an assertion. error: [stepUntil] fmi2_import_completed_integrator_step failed for FMU "model.root.fmu" warning: fmu (logStatusWarning): /var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelica/OMCompiler/build/lib/omlibrary/Modelica 3.2.1/Mechanics/MultiBody/Joints.mo:8428: The following assertion has been violated at time 3.757576 noEvent(jointUSP.prismatic.k1a > 1e-10) assert | error | | | | | Singular position of loop (either no or two analytic solutions; | | | | the mechanism has lost one-degree-of freedom in this position). | | | | Try first to use another Modelica.Mechanics.MultiBody.Joints.Assemblies.JointXXX component. | | | | If this also lead to singular positions, it could be that this | | | | kinematic loop cannot be solved analytically with a fixed state | | | | selection. In this case you have to build up the loop with | | | | basic joints (NO aggregation JointXXX components) and rely on | | | | dynamic state selection, i.e., during simulation the states will | | | | be dynamically selected in such a way that in no position a | | | | degree of freedom is lost. error: [fmi2logger] fmu (logFmi2Call): fmi2CompletedIntegratorStep: terminated by an assertion. error: [stepUntil] fmi2_import_completed_integrator_step failed for FMU "model.root.fmu" warning: fmu (logStatusWarning): /var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelica/OMCompiler/build/lib/omlibrary/Modelica 3.2.1/Mechanics/MultiBody/Joints.mo:8428: The following assertion has been violated at time 3.797980 noEvent(jointUSP.prismatic.k1a > 1e-10) assert | error | | | | | Singular position of loop (either no or two analytic solutions; | | | | the mechanism has lost one-degree-of freedom in this position). | | | | Try first to use another Modelica.Mechanics.MultiBody.Joints.Assemblies.JointXXX component. | | | | If this also lead to singular positions, it could be that this | | | | kinematic loop cannot be solved analytically with a fixed state | | | | selection. In this case you have to build up the loop with | | | | basic joints (NO aggregation JointXXX components) and rely on | | | | dynamic state selection, i.e., during simulation the states will | | | | be dynamically selected in such a way that in no position a | | | | degree of freedom is lost. error: [fmi2logger] fmu (logFmi2Call): fmi2CompletedIntegratorStep: terminated by an assertion. error: [stepUntil] fmi2_import_completed_integrator_step failed for FMU "model.root.fmu" warning: fmu (logStatusWarning): /var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelica/OMCompiler/build/lib/omlibrary/Modelica 3.2.1/Mechanics/MultiBody/Joints.mo:8428: The following assertion has been violated at time 3.838384 noEvent(jointUSP.prismatic.k1a > 1e-10) assert | error | | | | | Singular position of loop (either no or two analytic solutions; | | | | the mechanism has lost one-degree-of freedom in this position). | | | | Try first to use another Modelica.Mechanics.MultiBody.Joints.Assemblies.JointXXX component. | | | | If this also lead to singular positions, it could be that this | | | | kinematic loop cannot be solved analytically with a fixed state | | | | selection. In this case you have to build up the loop with | | | | basic joints (NO aggregation JointXXX components) and rely on | | | | dynamic state selection, i.e., during simulation the states will | | | | be dynamically selected in such a way that in no position a | | | | degree of freedom is lost. error: [fmi2logger] fmu (logFmi2Call): fmi2CompletedIntegratorStep: terminated by an assertion. error: [stepUntil] fmi2_import_completed_integrator_step failed for FMU "model.root.fmu" warning: fmu (logStatusWarning): /var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelica/OMCompiler/build/lib/omlibrary/Modelica 3.2.1/Mechanics/MultiBody/Joints.mo:8428: The following assertion has been violated at time 3.878788 noEvent(jointUSP.prismatic.k1a > 1e-10) assert | error | | | | | Singular position of loop (either no or two analytic solutions; | | | | the mechanism has lost one-degree-of freedom in this position). | | | | Try first to use another Modelica.Mechanics.MultiBody.Joints.Assemblies.JointXXX component. | | | | If this also lead to singular positions, it could be that this | | | | kinematic loop cannot be solved analytically with a fixed state | | | | selection. In this case you have to build up the loop with | | | | basic joints (NO aggregation JointXXX components) and rely on | | | | dynamic state selection, i.e., during simulation the states will | | | | be dynamically selected in such a way that in no position a | | | | degree of freedom is lost. error: [fmi2logger] fmu (logFmi2Call): fmi2CompletedIntegratorStep: terminated by an assertion. error: [stepUntil] fmi2_import_completed_integrator_step failed for FMU "model.root.fmu" warning: fmu (logStatusWarning): /var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelica/OMCompiler/build/lib/omlibrary/Modelica 3.2.1/Mechanics/MultiBody/Joints.mo:8428: The following assertion has been violated at time 3.919192 noEvent(jointUSP.prismatic.k1a > 1e-10) assert | error | | | | | Singular position of loop (either no or two analytic solutions; | | | | the mechanism has lost one-degree-of freedom in this position). | | | | Try first to use another Modelica.Mechanics.MultiBody.Joints.Assemblies.JointXXX component. | | | | If this also lead to singular positions, it could be that this | | | | kinematic loop cannot be solved analytically with a fixed state | | | | selection. In this case you have to build up the loop with | | | | basic joints (NO aggregation JointXXX components) and rely on | | | | dynamic state selection, i.e., during simulation the states will | | | | be dynamically selected in such a way that in no position a | | | | degree of freedom is lost. error: [fmi2logger] fmu (logFmi2Call): fmi2CompletedIntegratorStep: terminated by an assertion. error: [stepUntil] fmi2_import_completed_integrator_step failed for FMU "model.root.fmu" warning: fmu (logStatusWarning): /var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelica/OMCompiler/build/lib/omlibrary/Modelica 3.2.1/Mechanics/MultiBody/Joints.mo:8428: The following assertion has been violated at time 3.959596 noEvent(jointUSP.prismatic.k1a > 1e-10) assert | error | | | | | Singular position of loop (either no or two analytic solutions; | | | | the mechanism has lost one-degree-of freedom in this position). | | | | Try first to use another Modelica.Mechanics.MultiBody.Joints.Assemblies.JointXXX component. | | | | If this also lead to singular positions, it could be that this | | | | kinematic loop cannot be solved analytically with a fixed state | | | | selection. In this case you have to build up the loop with | | | | basic joints (NO aggregation JointXXX components) and rely on | | | | dynamic state selection, i.e., during simulation the states will | | | | be dynamically selected in such a way that in no position a | | | | degree of freedom is lost. error: [fmi2logger] fmu (logFmi2Call): fmi2CompletedIntegratorStep: terminated by an assertion. error: [stepUntil] fmi2_import_completed_integrator_step failed for FMU "model.root.fmu" warning: fmu (logStatusWarning): /var/lib/jenkins/ws/OpenModelicaLibraryTestingWork/OpenModelica/OMCompiler/build/lib/omlibrary/Modelica 3.2.1/Mechanics/MultiBody/Joints.mo:8428: The following assertion has been violated at time 4.000000 noEvent(jointUSP.prismatic.k1a > 1e-10) assert | error | | | | | Singular position of loop (either no or two analytic solutions; | | | | the mechanism has lost one-degree-of freedom in this position). | | | | Try first to use another Modelica.Mechanics.MultiBody.Joints.Assemblies.JointXXX component. | | | | If this also lead to singular positions, it could be that this | | | | kinematic loop cannot be solved analytically with a fixed state | | | | selection. In this case you have to build up the loop with | | | | basic joints (NO aggregation JointXXX components) and rely on | | | | dynamic state selection, i.e., during simulation the states will | | | | be dynamically selected in such a way that in no position a | | | | degree of freedom is lost. error: [fmi2logger] fmu (logFmi2Call): fmi2CompletedIntegratorStep: terminated by an assertion. error: [stepUntil] fmi2_import_completed_integrator_step failed for FMU "model.root.fmu" info: Final Statistics for 'model.root': NumSteps = 2253 NumRhsEvals = 4275 NumLinSolvSetups = 609 NumNonlinSolvIters = 4273 NumNonlinSolvConvFails = 10 NumErrTestFails = 212 info: 16 warnings info: 32 errors