Hello everyone,
I am working on a gear contact simulation in MotionSolve using a user-defined CNFSUB. According to the documentation, the arrays LOCI/LOCJ should provide the coordinates of the contact point on the two bodies (expressed in the local marker coordinates).
However, in my case they consistently return meaningless values, usually very close to zero (e.g. 1e-310) or sometimes extremely large numbers. For the first few iterations I might get some values, but they do not correspond to the actual gear contact point.
I saw in another thread that this behavior has already been reported and a workaround with GAP was suggested. Unfortunately, in my application the GAP value alone does not help, since I specifically need the coordinates of the contact point for further calculations inside the CNFSUB.
My questions are:
- Has anyone managed to get valid LOCI/LOCJ values in recent versions of MotionSolve?
- Does the same issue occur in other programming interfaces (e.g. C or MATLAB), or is it specific to the Python CNFSUB implementation?
- Is there any workaround that still provides the actual contact point coordinates without having to reconstruct them geometrically?
Any guidance or confirmation would be greatly appreciated.
Best regards,
Nefeli
