<?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: Argon firmware 1.0.2 released!</title>
	<atom:link href="http://openservodrive.com/argon-firmware-1-0-2-released/feed/" rel="self" type="application/rss+xml" />
	<link>http://openservodrive.com/argon-firmware-1-0-2-released/</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/argon-firmware-1-0-2-released/#comment-359</link>
		<dc:creator><![CDATA[Tero]]></dc:creator>
		<pubDate>Sat, 21 Sep 2013 17:02:41 +0000</pubDate>
		<guid isPermaLink="false">http://openservodrive.com/?p=828#comment-359</guid>
		<description><![CDATA[A good point there! 

Granity already supports older FW&#039;s if FW is fully compatible with the version Granity is designed for (for example Granity 1.0.2 can connect to FW 1.0.3 because no parameters are different). But it&#039;s true there is no &quot;compatibility mode&quot; that would work with &quot;too old&quot; FW version.

Luckily, the compatibility breaking updates should cease once all pending features are implemented in firmware. So the problem should be only temporary.]]></description>
		<content:encoded><![CDATA[<p>A good point there! </p>
<p>Granity already supports older FW&#8217;s if FW is fully compatible with the version Granity is designed for (for example Granity 1.0.2 can connect to FW 1.0.3 because no parameters are different). But it&#8217;s true there is no &#8220;compatibility mode&#8221; that would work with &#8220;too old&#8221; FW version.</p>
<p>Luckily, the compatibility breaking updates should cease once all pending features are implemented in firmware. So the problem should be only temporary.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johann</title>
		<link>http://openservodrive.com/argon-firmware-1-0-2-released/#comment-357</link>
		<dc:creator><![CDATA[Johann]]></dc:creator>
		<pubDate>Fri, 20 Sep 2013 11:33:54 +0000</pubDate>
		<guid isPermaLink="false">http://openservodrive.com/?p=828#comment-357</guid>
		<description><![CDATA[hi
I noticed a potential downside to the compatibility of comunication with diferente verssion firmware / software Granity
example:
Granity software version 1.0.2 is not connected by a 1.0.1 or older fimware
in instalation driver in a machine for a company, it will be good for a technician that can communicate / set with the latest software Granity on an old firmware
it could him avoids loss of time in search of Compatible Granity software with firmware
it can also make a backup of the settings before eventual updates

Thanks]]></description>
		<content:encoded><![CDATA[<p>hi<br />
I noticed a potential downside to the compatibility of comunication with diferente verssion firmware / software Granity<br />
example:<br />
Granity software version 1.0.2 is not connected by a 1.0.1 or older fimware<br />
in instalation driver in a machine for a company, it will be good for a technician that can communicate / set with the latest software Granity on an old firmware<br />
it could him avoids loss of time in search of Compatible Granity software with firmware<br />
it can also make a backup of the settings before eventual updates</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
</channel>
</rss>
