<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-gb">
<link rel="self" type="application/atom+xml" href="http://forum.robosavvy.com/feed.php?f=15&amp;t=7803" />

<title>RoboSavvy Forum</title>
<subtitle>Robosavvy Forum: The largest online community of Humanoid Robot Builders</subtitle>
<link href="http://forum.robosavvy.com/index.php" />
<updated>2012-02-23T20:04:45+01:00</updated>

<author><name><![CDATA[RoboSavvy Forum]]></name></author>
<id>http://forum.robosavvy.com/feed.php?f=15&amp;t=7803</id>
<entry>
<author><name><![CDATA[PedroR]]></name></author>
<updated>2012-02-23T20:04:45+01:00</updated>
<published>2012-02-23T20:04:45+01:00</published>
<id>http://forum.robosavvy.com/viewtopic.php?t=7803&amp;p=33744#p33744</id>
<link href="http://forum.robosavvy.com/viewtopic.php?t=7803&amp;p=33744#p33744"/>
<title type="html"><![CDATA[Reprogramming the Robobuilder BT Module: interestingfindings]]></title>

<content type="html" xml:base="http://forum.robosavvy.com/viewtopic.php?t=7803&amp;p=33744#p33744"><![CDATA[
Hi all<br /><br />We've been working hard on preparing 2 KHR 3Hvs for a custom project ( I know this is the Robobuilder forum, so please bear with me during the intro).<br /><br />Part of the project was designing a Wireless Remote Control System to feed commands from the PC to the KHR 3HV. <br />We decided to use the Robobuilder Bluetooth Module (it is a Parani ESD 200) as it creates a Transparent COMM port on the PC (the client software doesn't need to be aware that BT is even involved; it just sees a COMM port).<br /><br />There were (and still are) a number of challenges and tasks: we've documented the whole RCB4 protocol for playing motions, based on libkondo (we'll publish this later) and most importantly <span style="color: green">we've learned how to reprogram the Robobuilder BT module with an inexpensive USB to TTL Serial adapter</span>.<br />We needed to do this because the KHR 3HV controller uses 115 200 bps, 8 data bits and 1 stop bit like Robobuilder but KHR uses EVEN parity (Robobuilder uses No Parity so the module needed to be reconfigure to EVEN)<br /><br /><span style="color: green">Setting up:</span><br />We've used Sparkfun's excellent Breakout board for FT232RL <!-- m --><a class="postlink" href="http://robosavvy.com/store/product_info.php/products_id/545">http://robosavvy.com/store/product_info ... cts_id/545</a><!-- m --><br /><br />This is a Swiss knife for any developer.<br /><br />The connection Diagram is the following:<br />BT Vcc -&gt; USB2TTL +3.3V pin<br />BT Gnd-&gt; USB2TTL Gnd<br /><br />BT RX -&gt; USB2TTL TX<br />BT TX -&gt; USB2TTL RX<br /><br />BT CTS -&gt; USB2TTL RTS<br />BT RTS -&gt; USB2TTL CTS<br /><br />from our experience all other pins should be left unconnected (ie &quot;floating&quot;)<br /><br />The pinout for the Bluetooth module can be found here <!-- m --><a class="postlink" href="http://www.sena.com/download/datasheet/ds_parani_esd.pdf">http://www.sena.com/download/datasheet/ ... ni_esd.pdf</a><!-- m --><br />The pinout for the USB2TTL is actually printed on the board so it makes things easier <img src="http://forum.robosavvy.com/images/smilies/icon_smile.gif" alt=":)" title="Smile" /><br /><br />To read the pin number on the Parani you need to hold it with the pin headers facing down (ie the flat surface facing you).<br /><br /><span style="color: green">Get the Software:</span><br />You will need to download <span style="font-weight: bold">ParaniWin </span>from this website <!-- m --><a class="postlink" href="http://www.sena.com/support/downloads/">http://www.sena.com/support/downloads/</a><!-- m --> and install it on you computer.<br /><br />After everything all the Hardware is connected, run ParaniWIN<br /><br /><span style="color: green">Connect and Configure:</span><br />Once you run the software you'll need to connect to the module by indicating the connection settings.<br />If you're using it on Robobuilder, connection settings are 115200, 8 data bits, no parity, 1 stop bit but if you don't know these settings you can do a procedure to hard reset it to factory defaults (see bellow).<br /><br />You will immediately access a nice configuration Window where you can set a wide range of options: <br />- Connection speed<br />- connection settings (parity, data bits, stop bits)<br />- hardware flow control (which you typically want it to be OFF) <br />- the Bluetooth Pairing Mode <br />- the Module's name<br />- and a lot more<br /><br />With Robobuilder the module is set to Mode 3 (always discoverable and anyone can connect) and has &quot;Command Response&quot; set to OFF (otherwise the module may start trying to interpret what's passing through it against it's own AT command set).<br /><br />There is some magic in ParaniWin that somehow it detects command response is OFF, informs you of this and reverts the setting to ON so that you can use the software to configure the module.<br />Once you're done just remember to set &quot;Command Response&quot; to OFF again and Save.<br /><br /><br /><span style="color: green">Interesting Features:</span><br /><br />We noticed the module can be set to much higher Baud Rates (or so it seems on the software). This is particularly nice if you're using a custom firmware or if you're using the module with other devices.<br /><br />Another interesting thing is that you can configure a security passkey for the module (instead of the generic 1234).<br /><br /><br /><span style="color: green">Hardware Reset to Factory Defaults</span><br />Finally we wanted to leave a note about Hard resetting the module. We inadvertently Hard reset one of our modules leading us to believe we had killed it.<br /><br /><span style="color: green">After a Hard reset the module is not discoverable</span> by any BT device (it doesn't advertise itself), goes back to 9600bps and since it has no status LEDs <span style="color: green">it may seem &quot;dead&quot;</span>.<br /><br />We still don't know exactly how we did it but it seems we did it through the RESET pin.<br /><br />The instructions seem a bit contradictory (at least to me) but in practice the RESET pin should be left unconnected on day to day operation.<br /><br />If you need to hard reset the module to restore factory defaults, power the module (with Vcc and Gnd) and then apply +3.3V to the RESET pin for a couple of seconds.<br />This should reset it to factory defaults. You should then connect to it using ParaniWin to configure it. By default it goes back to 9600 bps and 8N1 setting I believe.<br /><br />Still, refer to the user manual regarding the Hard reset. Some parts of the manual seems suggest you need to connect RESET to GND to cause a Factory reset but I don't think that was what we did and that's also not our experience on day to day operation.<br /><br /><br />We're extremely busy these days with projects but I'll try and post back some images if I have the opportunity.<br /><br />There was a great sense of accomplishment when reprogramming these modules.<br /><br />I remember we had discussed this previously on some thread without any conclusion (just the &quot;maybe you need to get the official programming board&quot;).<br /><br />I hope this post shows an easy (and fairly inexpensive) way of reprogramming a Parani ESD 200 with the simple resources.<br /><br />Regards<br />Pedro.<p>Statistics: Posted by <a href="http://forum.robosavvy.com/memberlist.php?mode=viewprofile&amp;u=1061">PedroR</a> — Thu Feb 23, 2012 8:04 pm</p><hr />
]]></content>
</entry>
</feed>