From: Chris B. <ch...@ba...> - 2006-03-27 10:31:33
|
Hi David, thanks for responding. I used the email that you sent out just before Christmas with the Roomba codes. Here's the result of me importing the MAX code and then sending it. I have added "\n" to show where the carriage returns appeared in the output. <QUOTE> 27/03/06 21:14:02 Importing device ROOMBA function MAX pronto 0000 0069 0000 0008 006F 0027 0024 0071 0023 0071 0023 0071 0023 0071 006C 0027 0024 0071 006C 02CF\n 27/03/06 21:14:51 Sending device ROOMBA function MAX\n USB_UIRT sending 36173f000000116f2724712371237123716c2724716c82cf97\n USB_UIRT: transmit_pronto returned 0x0\n </QUOTE> I got no response from my Roomba and even now, 15 minutes later, the red LED on the front of the unit is still on. Here's the 'strings' output of /home/mh/data/usb_uirt_codes.dbm: <QUOTE> [root@ha data]# strings usb_uirt_codes.dbm P00 0000 0069 0000 0008 006f 0027 0024 0071 0023 0071 0023 0071 0023 0071 006c 0027 0024 0071 006c 02cf\n ROOMBA\n P00 0000 0069 0000 0008 006f 0027 0024 0071 0023 0071 0023 0071 0023 0071 006c 0027 0024 0071 006c 02cf\n ROOMBA\n ROOMBA\n _dummy_\n _dummy_\n P00 0000 0073 0000 000c 0020 0021 0040 0021 0020 0021 0020 0021 0020 0021 0020 0021 0020 0021 0020 0021 0020 0041 0020 0021 0040 0021 0020 0cc2\n POWER\n <QUOTE> The "POWER" string is associated from a TV device that I've also been unable to get working. If I recall, the string was captured using Girder some time ago. Interestingly we can see "ROOMBA" (the device name) but not "MAX" (the button name) for the Roomba and "POWER" (the button name) but not "TV" (the device name) for the television. Any assistance would be greatly appreciated. Regards, Chris > -----Original Message----- > From: mis...@li... [mailto:misterhouse- > use...@li...] On Behalf Of David Norwood > Sent: Monday, 27 March 2006 6:58 PM > To: mis...@li... > Subject: Re: [mh] USB-UIRT and Linux - no go > > Your log entries indicate misterhouse is communicating with the usb-uirt > successfully. What problem are you having? > > David > > ----- Original Message ----- > From: "Chris Barrett" <ch...@ba...> > To: <mis...@li...> > Sent: Sunday, March 19, 2006 9:29 PM > Subject: [mh] USB-UIRT and Linux - no go > > > >I have had my USB-UIRT for over a year now (possibly 2?) and I don't > think > > I've ever been able to use it successfully under MH/Linux. > > > > Here's how I have it defined in my mh.private.ini: > > <QUOTE> > > usb_uirt_module=USB_UIRT > > usb_uirt_port=/dev/ttyUSB0 > > </QUOTE> > > > > And here's a sample from my console.log when MH first starts up: > > <QUOTE> > > - creating USB_UIRT object on port /dev/ttyUSB0 > > > > Getting UIRT Info... > > USB_UIRT sending 23dd > > USB_UIRT: get_version returned 0x0 > > USB_UIRT Protocol Version 1.1 > > USB_UIRT Firmware Version 5.4 Date 04/30/2003 > > > > Getting UIRT Config Info... > > USB_UIRT sending 3801c7 > > USB_UIRT: get_config returned 0x0 > > ** USB-UIRT Config: currently = 00000003 (LED_RX=1, LED_TX=1, > LEGACY_RX=0) > > </QUOTE> > > > > Could someone please give a run down on their *working* setup? > > |