- Feb 6View SourceHola:
Bluetooth Serial Port Profile? Not even close to it, since it's too low level and is transparent to me. On the robot I'm using a bluetooth module from dealExtreme.com ( http://dx.com/p/wireless-bluetooth-rs232-ttl-transceiver-module-80711 ) it's a BT to Serial converter. So effectively to the Android application the connection looks like an RS232 wired connection. The Android Basic interpreter (www.mintoris.com) App that I'm using, has simple commands to talk to the BT paired connection. It has the BTscan, BTpair, BTconnect, BTread and BTwrite... When I send a simple ASCII command to my robot I just use a simple Basic command, such as [ BTWrite 1, data$ + "\n" ] and I'm not burden with the low level details how the "command string" gets to the embedded controller via the BT transceiver module on the bot.
I still need to post the latest pics, since the ones that I posted sometime ago were just the start. The ones online are the course version.
That might be possible, both bots could be identical to make it fair, but each would have it's Cell an Android and the other the iPhone, So it would be a real Android vs iOS rock'em sock'em.Cesar
From: Cory Cross <crcross@...>
Sent: Thursday, February 6, 2014 1:06 AM
Subject: Re: [SeattleRobotics] Better robot chassis/system?
Interesting bot. Hope you build it a buddy using an iPhone and do a little rock'em sock'em robots and settle this whole iOS vs Android thing once and for all ;)
Are you using the Bluetooth Serial Port Profile (SPP)?
I'm not planning to do anything too fancy with machine vision, as the distance sensors should be sufficient to do SLAM. It's mostly for telepresence and maybe a color-following algorithm later.
On 02/05/2014 11:26 AM, robotMaker wrote:
This is my chassis for my autonomous carpet walkingBot ( http://www.flickr.com/photos/96504930@N02 ) that I mentioned in a previous post. I'm still not finished with it since these photos, but have added refinements to the chassis, and almost ready to bring together the software pieces. I'm using a used Android cell phone for the main controller or brains, and via BT I control a BabyUrangutan board (from pololu.com), that controls the motors (no servos for now), and audio IO and other simple IOs. I plan to use the camera built in the phone for "machine vision". I'm using a Basic Interpreter Android App available from googleplay.com. It has everything that I need to access the Android built in sensors, such as the accelerometer, compass, camera, audio output, wifi, gps and display. I've found that used Android Cell phones on the web can be found for $20 and up. For my Android control software in Basic, I plan to use an Event driven Deterministic Finite State Automata. At this time I'm not planning to use GPS or WIFI. The "getEvent" sub will do most of the work in getting the events to bump the State Machine states. For the vision part of the "getEvent" sub, I was planning on breaking up the image to a course 124x124 pixles, and using perhaps the Open Source code from the AVRcam software for image processing. But I'm sure that you're looking for a better performing image processing software that I'm using for navigation and other skills. Right?
From: Cory Cross <crcross@...>
To: "SeattleRobotics@yahoogroups.com" <SeattleRobotics@yahoogroups.com>
Sent: Wednesday, February 5, 2014 1:16 AM
Subject: [SeattleRobotics] Better robot chassis/system?
I want a small robot capable of SLAM; basic video capture, processing,
and transmitting; and following me, all for a low per-unit cost and
minimal time investment before I can program the desired behaviors. And
something I can use to collaborate and share software with others.
My plan is:
1. Android phone: available cheap used; has camera, wifi, and power
built-in; sufficient bandwidth to stream video to another device;
sufficient power for basic video algorithms and path planning;
sufficient memory & processing for SLAM; running ROS
2. Pre-made chassis w/ wheel encoders:
Plus four fixed-position IR distance sensor added on to assist SLAM &
four whiskers to sense collisions
(A future chassis would be roughly similar, but with better specs: more
accurate encoders, stronger & faster motors, etc)
Anything I've overlooked that would be better?
Visit the SRS Website at http://www.seattlerobotics.orgYahoo Groups Links
<*> To visit your group on the web, go to:
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo Groups is subject to: