04-03-2015 04:36 PM
Hi-
I'm using a 73xx series board for a 3D system and would like to use the Motion Assitant VIs to allow path planning in the applicaiton, but can't seem to figure out how to use the result of the MA VIs for the 73xx motion.
I've attached a simple VI that shows how to use MA VIs to create a helical arc, and the equivalent VIs for 73xx native.
Thing I'm really after is the ability to show the path after creating (MA: Get Profile) prior to running it in hardware - the 73xx stuff doesn't allow that (that I know of) and it seems odd to create the path in MA and not be able to use it afterward?
04-03-2015 06:05 PM
Should add that I read through the following links (from a seperate thread) and I couldn't find anything WRT the issue posted..
Motion Assistant:
http://sine.ni.com/psp/app/doc/p/id/psp-489/lang/en
Fundamentals of Motion Control:
http://www.ni.com/white-paper/3367/en/
04-07-2015 09:43 AM
Hello Jef_A,
You could try merging both. For example using an "unbundle by name" function to extract the values from the "Arc Move Properties" cluster (i.e the radius, start angle, travel angle) and use those values as the source of the inputs of the "Load Helical Arc.flx" VI.
Regards,
>>Daniel C.
04-07-2015 01:46 PM
Thanks, that is my current plan - but need to blend seperate motions (linear, arc, more linear's, more arc's) and I'm concerned that the path created by using the 73xx VI's won't match what's generated by the MA Vi's.
Really trying to understand the purpose of the MA VI's - what are you supposed to do with them exactly? - They seem great at creating paths, but not implementing them?
04-09-2015 12:06 PM
Hey Jeff_A!
I've been looking deeper into your point: "Really trying to understand the purpose of the MA VI's - what are you supposed to do with them exactly?"
Basically, these VIs are used just for prototyping moves and their effects.
You can understand this better by opening the examples that uses these VIs. Find those examples right here:
C:\Program Files (x86)\National Instruments\LabVIEW 2014\examples\MotionAssistant
You will see these functions are used just for modeling the move, they are not focused on implementing it with a controller.
I hope this can be helpful to better understand the MA VIs on LabVIEW.
Best regards!
>>Daniel C.