Editing Buffered motion stream in SimpleMotion V2

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

This page supports semantic in-text annotations (e.g. "[[Is specified as::World Heritage Site]]") to build structured and queryable content provided by Semantic MediaWiki. For a comprehensive description on how to use annotations or the #ask parser function, please have a look at the getting started, in-text annotation, or inline queries help page.

Latest revision Your text
Line 1: Line 1:
The buffered motion stream feature of [[SimpleMotion V2]] bus allows implementing multi-axis motion control applications without need of real-time host or motion controller. The principle behind this mode is two-way FIFO buffers inside the drives which allow buffering upcoming motion commands as well as return data (user selectable parameter to read/monitor during motion).
+
The buffered motion stream feature of [[SimpleMotion V2]] bus allows implementing multi-axis motion control applications without need of real-time host or motion controller. The principle behind this mode is two-way FIFO buffers inside the drives which allow bufferind upcoming motion commands as well as return data (user selectable parameter to read/monitor during motion).
  
==Buffered motion stream characteristics==
+
==Characteristics==
 
===Pros===
 
===Pros===
 
*Allow synchronizing multiple axes and running arbitrary motion paths
 
*Allow synchronizing multiple axes and running arbitrary motion paths
Line 23: Line 23:
 
==Data flow==
 
==Data flow==
 
Each sent [[setpoint]] value will produce a return data point. Return data is user selectable and may contain for example position feedback value. It should be noted that reception of return data is delayed and read after drive has executed the corresponding setpoint commands.
 
Each sent [[setpoint]] value will produce a return data point. Return data is user selectable and may contain for example position feedback value. It should be noted that reception of return data is delayed and read after drive has executed the corresponding setpoint commands.
{{picturebox|buffered data flow.png|caption=Data flow in buffered motion stream. Note: the sequential numbers represent the '''index''' of the setpoint/returned data points, not the actual values.}}
+
{{picturebox|buffered data flow.png|caption=Data flow in buffered motion stream}}
 
+
[[Category:CNC]]
+
[[Category:Development]]
+
[[Category:SimpleMotion]]
+
[[Category:Work_in_progress_pages]]
+

Please note that all contributions to Granite Devices Knowledge Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Granite Devices Knowledge Wiki:Copyrights for details). Do not submit copyrighted work without permission!

Select categories:

To edit this page, please answer the question that appears below (more info):

Cancel | Editing help (opens in new window)

Templates used on this page: