<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>Comments on: Servo motor driven laser projector</title>
	<atom:link href="http://openservodrive.com/servo-motor-driven-laser-projector/feed/" rel="self" type="application/rss+xml" />
	<link>http://openservodrive.com/servo-motor-driven-laser-projector/</link>
	<description>Cutting edge without Bleeding edge</description>
	<lastBuildDate>Thu, 15 May 2025 12:21:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.1.12</generator>
	<item>
		<title>By: Tero</title>
		<link>http://openservodrive.com/servo-motor-driven-laser-projector/#comment-386</link>
		<dc:creator><![CDATA[Tero]]></dc:creator>
		<pubDate>Sun, 22 Dec 2013 20:19:34 +0000</pubDate>
		<guid isPermaLink="false">http://openservodrive.com/?p=962#comment-386</guid>
		<description><![CDATA[Thanks and the best X-mas &amp; new year for you too!

Both drives have an internal FIFO buffer for SM commands and in this case buffers are filled by position setpoint commands. Drives are set to excecute commands from the buffer at 250 Hz rate and command execution clock between the drives is being sychronized over the bus. 

Most of the tracking error comes simply from servo overshooting as we&#039;re asking too high accelerations at sharp corners. We didn&#039;t calculate trajectories for all speeds separately so acceleration scales up same amount with speed (and that&#039;s why it starts overshooting). Trajectory is simply a large table of axis coordinates generated by gcodecompiler (EMC2/LinuxCNC based app).]]></description>
		<content:encoded><![CDATA[<p>Thanks and the best X-mas &#038; new year for you too!</p>
<p>Both drives have an internal FIFO buffer for SM commands and in this case buffers are filled by position setpoint commands. Drives are set to excecute commands from the buffer at 250 Hz rate and command execution clock between the drives is being sychronized over the bus. </p>
<p>Most of the tracking error comes simply from servo overshooting as we&#8217;re asking too high accelerations at sharp corners. We didn&#8217;t calculate trajectories for all speeds separately so acceleration scales up same amount with speed (and that&#8217;s why it starts overshooting). Trajectory is simply a large table of axis coordinates generated by gcodecompiler (EMC2/LinuxCNC based app).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lubchi</title>
		<link>http://openservodrive.com/servo-motor-driven-laser-projector/#comment-385</link>
		<dc:creator><![CDATA[lubchi]]></dc:creator>
		<pubDate>Sun, 22 Dec 2013 15:47:51 +0000</pubDate>
		<guid isPermaLink="false">http://openservodrive.com/?p=962#comment-385</guid>
		<description><![CDATA[Hi!
Great demo.Congratulations!
Do you have synchronized the actual position estimation of both drives? IF not, It could be the reason for the deviation between both axes at the periods with high velocity.

Happy holidays and a smooth start in 2014!!!]]></description>
		<content:encoded><![CDATA[<p>Hi!<br />
Great demo.Congratulations!<br />
Do you have synchronized the actual position estimation of both drives? IF not, It could be the reason for the deviation between both axes at the periods with high velocity.</p>
<p>Happy holidays and a smooth start in 2014!!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
