Editing Optimizing SimpleMotion V2 performance
Your changes will be displayed to readers once an authorized user accepts them. (help) |
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.
Latest revision | Your text | ||
Line 48: | Line 48: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
− | In the above example, the ''smExecuteCommandQueue'' is the only line where RS485 is being used thus generating only one write-read latency | + | In the above example, the ''smExecuteCommandQueue'' is the only line where RS485 is being used thus generating only one write-read latency. ''smAppendSetParamCommandToQueue'' and ''smGetQueuedSetParamReturnValue'' transfer data only inside SMV2 library buffers and are fast calls. |
====Queued size limit==== | ====Queued size limit==== | ||
Line 271: | Line 271: | ||
==See also== | ==See also== | ||
*[[Changing SimpleMotion baud rate]] | *[[Changing SimpleMotion baud rate]] | ||
− | |||
− |