I was finally able to get a BT connection to the Rootooth (RT) on COM 4 using Windows Vista BT drivers. I factory reset the RT (SD,1) and set the baud rate to 57600 (SU,57). The RT "D" command shows the baudrate at 57,600. But I got no data out of the Roomba via RealTerm, Roomba Status, or SCITester. The programs connect to the COM port, but don't read any Roomba data and commands are ignored.
When I put the RT on my Scooba, I was seeing garbage via Realterm, so I figured wrong baud rate. I tried every baud rate there was, but none worked.
So I used an alternative RT speed command "U,57.6,N" and that got the communications working. I was happy to see the battery charging status messages Vic talked about.
I was going to try and figure out why the RT didn't change the baud rate using the SU command, and why it doesn't remember the changed baud rate between connections. But now I can't get a BT connection to the RT anymore, so it's going back to Sparkfun.
Were previous RT modems "AT" command based? All the docs I've read refer to the AT command set for programming the RT. My Rootooth does not respond to AT-style commands and is based on Roving Network's Firefly.
What's the difference between Roomba Status "serial cable" and "Rootooth" modes?
Thanks for everyone help and suggestions.