<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>robots.net blog for jc38654</title>
    <link>http://robots.net/person/jc38654/</link>
    <description>robots.net blog for jc38654</description>
    <language>en-us</language>
    <generator>mod_virgule</generator>
    <pubDate>Thu, 20 Jun 2013 09:37:36 GMT</pubDate>
    <item>
      <pubDate>Fri, 12 Sep 2008 19:45:18 GMT</pubDate>
      <title>12 Sep 2008</title>
      <link>http://robots.net/person/jc38654/diary.html?start=0</link>
      <guid>http://robots.net/person/jc38654/diary.html?start=0</guid>
      <description>Wow ! First blog entry and its about a real pain-in-the-&#xD;
butt problem.&#xD;
I have a VEX microcontroller and it just stopped working &#xD;
one day.  That is it just stopped working in the R/C mode.  &#xD;
That's right, just when you try to control the bot in R/C &#xD;
it will not work.  I can program a routine in easyC and the &#xD;
controller works just as it should.  It runs through the &#xD;
entire routine and.... oh well you get my drift.&#xD;
The head engineer/programer/owner ?, or whatever he was/is &#xD;
said, and I quote, "VEX microconrollers NEVER fail!".&#xD;
I was told to try and reload factory default firmware, &#xD;
master code and user code.  I tried this but to no avail.  &#xD;
As I am fairly new to modern microcontrollers (that's right &#xD;
I am an old man) I was wondering if anyone in this fine &#xD;
community has had a similar problem or anyone who might &#xD;
have a ready answer to what I believe to be a uController &#xD;
failure.&#xD;
Thanks a bunch-JC</description>
    </item>
  </channel>
</rss>
