Configured the FireFly Rootooth as an DUN device and now cannot access the Command prompt to perform a factory reset. How does one reset the FireFly Rootooth that is connected to a 5XX model Roomba, optioned as an DUN modem ?
Updating the original question with some additional info. Using the pinout assignments for the RN-41 chip I soldered a 30 gauge wire to pin 11 (VDD 3.3 Vdc) another wire to pin 22 (PIO4) wired the two leads to a normally closed switch. Powered up the Rootooth, toggled the switch 3 times and then tested for the factory reset. No reset occurred, the same profile is still in the chip. Anyone have a clue as to what else to attempt ?
Not sure if this helps as I don’t know if your device is like the bluesmirf.
I couldn’t get mine in command mode via BT, so,
I connected the TX/RX lines via a serial cable and Max232 to a terminal program, (on a pocket pc), and put the unit in command mode $$$,
then issued the SF,1 command (Factory reset), then —.
It reset it 
Thanks for the reply, I do have a USB to DB9 cable and software somewhere around. I may have to play a bit with a 2.1 shifter from Sparkfun and a USB driver or two.
I’m not sure of the Rootooth, but the Firely (or RN41 module) needs PIO4 high at power up and then toggle PIO3 three times for the hardware reset. I know that this works as I am currently using the RN41 module.
That is very helpful info since the PDF doc does not provide that amount of detail on how to reset.
This is what is stated :
Factory Reset 1 PIO 4 OFF (0V) = disabled, ON (3V) = ARMED
Auto Discovery/Pairing 2 PIO 3 OFF(0V) = disabled, ON(3V) = enabled
Factory Reset- Set this switch/PIO4 on powerup. This arms the reset function. Then toggle the switch/PIO 3 times and all settings in the device (other than the Bluetooth name) will return to defaults.
So, did that work for you? I made the same mistake. I turned the reader on, then I set PIO4 high and toggled PIO3. But, I didn’t realize that PIO4 must be high at power up.
I strapped pin 11 (3.3vdc) and pin 22 (PIO4) together. My thought was at powerup this would put PIO4 High. Then with an additional lead off of the strapped connection I placed it on pin 20 (PIO3) three times. Nothing happened. I removed the extra lead going to pin 20, connected the Rootooth FireFly to the Roomba, ran the Discovery on the PC and could not find the Firefly. Disconnected the jumper between pins 11 and 22 and then discovery would work but the unit did not reset.
That sounds like what I did, except I used a pullup resistor instead of direct connection to 3.3V to be safe. Anyway, it should have worked. Unless the firmware in the Rootooth is somehow different. I dunno.
I had a thought. After a hardware reset, the baud rate defaults to either 115200 if PIO7 is low, or 9600 if PIO7 is high. Possibly you really did do a reset and the baud rate is incorrect.
What was the value of your drop down resistor ? I think the RN41-1 is the same as your unit. Mine has the antenna with it mounted on the PCB and that may be the only difference.
I will try the reset again with a drop down resistor.
I used a 4.7K resistor. Also, check the baud rate as I edited in my last post.
OK, baud rate noted. Looking for my 1/4 watt resistors. BTW if the reset had worked the DUN profile would have gone away and when running the services I should have seen SPP instead of the dial up networking.
Found the resistor, connected the leads toggled pin 20 3 times, no go, back to the drawing board. Thanks for the help.
Here is an Edit update on this thread:
Finally able to communicate with the Firefly bluetooth by providing 9 volts dc to the input side of the 3.3v regulator chip onboard the PCB. Access via Procomm was worthless, could not get the command prompt using $$$. Downloaded RealTerm from Sourceforge and was finally able to establish a connection, obtain the command prompt and send the SF, 1 command to reset the Firefly back to the factory defaults. This version of Bluetooth (FireFly) is not very stable with the new Windows Vista OS.