Well, this brings back some memories.....from what I can recall, there are essentially 3 steps to animate the structure:

1. Draw or import model of structure

2. Import measurement data into a Data Block file or a Shape Table file

3. Assign M#'s in the data block or shape table to the DOF (i.e. points and directions) of the model.

Are you sure you preformed step 3?

If needed, you can always contact Vibrant Technology Tech Support

Regards

Jim P

Hi Jim,

   Yeah step 3 is my issue..... so I am trying to make somewhere around 450 M# links, but when I do perform the animation equations it only writes like 150 and tells me it cant write the rest.... not sure what I am doing wrong.

Will post the corrective action once I "discover" it.

Thanks man,

KB

Good luck....I don't recall having that error message in the few jobs I've done. Wondering if it occurring at that specific point number (94) or M# (97) has something to do with it??  I'm stumped, let us know when you do

JP

So I found out that this actually wasn't an error, and it wasn't killing my animations. I was bringing in data in the data block that was not assigned to a point.... this created the error message. When I ran my interpolation calculations for each substructure, everything worked out fine.

Animations looks great now.

Thanks,

KB

Good to hear. I've done that myself. I try to learn by my mistakes and, if that were true 100% of the time, I would be really "smahht" by now  

BTW - Did the points/M#'s in question start with where the error code began?

J

Hey Jim,

Yes... they matched.

I have actually modeled this installation in another ODS software (Clear Motion) before and now that I have an ME Scope license I only modeled a portion of the installation so I actually have more data than I need. By importing that extra data which didn't match any points, it created the error message. Was a good learning experience.

ME Scope software is so powerful.... amazing tool to have. Glad I have a license now.

Thanks and have a good weekend,

KB