Attached are two screenshots showing an error message I encountered while trying to create M# links for animating my model in ME Scope. The message indicates that around 50 points were not assigned M#'s, causing issues with the animation. Despite the fact that the M#'s in the data block are consistent with those that are functioning properly, I am confused by this error. I would greatly appreciate any assistance in resolving this issue. Thank you, KB.
Looking back on those memories, I remember the important steps to animate a structure. Firstly, you need to either draw or import a model of the structure. Secondly, import measurement data into a Data Block file or a Shape Table file. Lastly, assign M#'s in the data block or shape table to the Degrees of Freedom (DOF) of the model, such as points and directions. Have you completed step 3? If you need assistance, feel free to reach out to Vibrant Technology Tech Support. Regards, Jim P.
Hey Jim, I'm having some trouble with step 3 of my project. I'm attempting to create approximately 450 M# links, but when I run the animation equations, only around 150 are being generated and I'm getting an error message for the rest. I'm not sure where I'm going wrong, but I'll share the solution once I figure it out. Thanks, KB.
I have not encountered that particular error message in the jobs I have completed. Could the issue be related to a specific point number (94) or M# (97)? I am puzzled by this and would appreciate an update from you once you have more information. Good luck troubleshooting!
After some investigation, I discovered that the issue causing my animations to not work properly was due to unassigned data in the data block. Once I fixed this and ran interpolation calculations for each substructure, the animations started working perfectly. I'm so pleased with how they look now. Grateful for the troubleshooting process. Thank you, KB.
That's great to hear. Learning from mistakes is key to becoming "smarter." By consistently applying this principle, one can significantly improve their knowledge and skills. By the way, did the points or M#'s in question align with where the error code originated? J
Hi KB, I've encountered this issue before. It's possible that the unassigned M#'s come from the nodes in the FE model which don't perfectly coincide with the points in the geometry model. A good trick to solve this would be to run an automatic adding M# routine (which comes with the program), instead of assigning them manually. This should align your nodes accurately, and hopefully that eliminates the error message. Let me know if this helps!
It seems like you've already checked for inconsistency in M#'s, which is a common issue. However, since that's not the case, consider the possibility of M#'s not being assigned due to naming clashes or they might be already in use elsewhere. You might want to do a quick search to ensure no duplicate M#'s are present. Also, remember that M#'s assignment order matters, ensure they are assigned sequentially. Hope this helps, and don't hesitate to dive in further if more details are required.
Hey KB, this error usually occurs when there's a mismatch between the point IDs in your geometry and the response data. Double check to make sure that your data block's point IDs match perfectly with your geometry. Also, do check if you have any unused points in the model. Removing these could potentially fix the issue. If your issue persists, it might be a good idea to reach out to the ME Scope technical support for more specialized assistance. Best of luck!
Hi KB, it seems like you're facing a pretty peculiar issue. One potential cause of this error could be a mismatch between the source points and the modal points. Double-check if the points in your model and in your M# list corresponding to each other. If after syncing these you're still having the same problem, you might want to ensure that your model is fully defined and properly constrained. Another thing - be sure the software is up to date, as outdated versions can cause unexpected issues. If none of these resolve the issue, your best bet might be to contact ME Scope's technical support. They might be able to provide a solution more specific to your situation. Good luck!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: 1. Q: What does the error message about unassigned Ms in ME Scope mean? The error message indicates that some points in your model are missing M assignments, which can cause issues with animation in ME Scope.
Answer: Check that all points in your model have consistent and correct M assignments in the data block to ensure smooth animation functionality.
Answer: It's possible that there may be subtle differences or errors in the M assignments of those points causing the inconsistency, leading to the error message. Double-check the M assignments for accuracy.
Answer: Review and correct any missing or incorrect M assignments for the points in your model to ensure all points are properly linked for smooth animation.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.