See I told you it exists
Jonathan McLean
27 February, 2007
  • transceivers
  • basic stamps
  • breadboards
  • pics

Some Pictures

Well readers, here are some pictures to prove that what I am working on does in fact exist and is not just a pipe dream within my head. I have gotten the little buggers to talk which is nice. Right now one Transceiver (TR/x) tells the other TR/x to kill some humans and the other responds by outputting its human kill count. If you don't get why I have robot brains talking about killing all humans, you do not read nearly enough science fiction. If you are going to keep reading this journal, you might want to get on that.

The pictures you see below are those of my lovely TR/x's: Righty and Lefty. I call them that so that in my testing I can always remember Righty Receives (get it?) and Lefty transmits (no alliteration there, sorry). The TR/x's are the large protruding boards and the little green chips are Parallax BASIC Stamp II microcontrollers...the brains. I think it's pretty cool atleast.

TR/x'x
TR/x'x
Up...and, well, just up for now.
Jonathan McLean
14 February, 2007
  • transceivers
  • basic stamps
  • breadboards

A love hate relationship

I would like to point out that I am in now way an electrical engineer, nor is my physics in relation to electricity worth even a dime. Thus, I was so very happy when Owen explained to me how my circuits were in fact not completed and that is why my LED was not lighting up. That knowledge really lit a lightulb, both of the metaphorical and the literal variety. This is extremely symbolic of my love hate relationship with the tools with which I work on this robotics project. Circuitry is cool and all because it makes what I want to happen happen, but at the same time I am approaching it like a four year old approaches an outlet with a fork: a bit naively, excited at all the shiny objects, and completely unaware if and when a shock might occur. I also have a fear of capacitors, having been more than a little shocked by a disposable camera flash capacitor when I was...hmm I don't remember how old I was; eleven, twelve? And breadboards. They are great for what they are, but they are often times the most unorganized mess of wires I have ever seen.

Progress

Despite all these fears and misgivings, progress is being made. Sorry, still no pictures. Maybe I will get some up later. We did in fact have 418 MHz Transceiver boards by Parallax lying around the lab, two in fact, so at least we did not need to wait for a shipment to come in. Also, because they are by parallax they work well with our BASIC stamps and the PBASIC language. I spent about 5 hours in the lab yesterday hooking them all up to the breadboards and the stamps.

The hookups did not go as smoothly as I would have liked, but I chalk it all up to lack of experience with breadboards and their layout. Eventually I will get the hang of it all and clean things up a bit. My second board looks better than my first. One problem I did create was with the layout of the pins for the network library stamp. The decision has been made to make the stamp a full-fledged transceiver control and network protocol library chip. As such it needs its pins to connect to both the transceiver and any brain stamp we concoct for a robot.

The transceiver can operate in two modes. Serial mode sends 9600 baud serial information with 15 millisecond spacing between bits between the TXD pin on one transceiver to the RXD pin on any other receiving device. There is also a TXFLO pin which can handle different rates and quicker using PBASIC's built in serializing function. This stream of bits is a good source of communication but requires work on both ends to ensure parity and accuracy of data.

The transceivers can also operate in switch mode, which can send 3 bits in parallel to any similarly-addressed board. Timing is different and it seems to be an easier means of communication. All that occurs is tha output pins on the receiving end mirror the state of the input pins on the transmitting device. If an IN pin is high, so is the corresponding OUT pin on the receiver. Seems just easier to program from my point of view. I may very well be eating those words at a later date.

So that is where I stand. I have two breadboards wired with a controller chip and transceiver each, and an increasingly clean work area. I have already started to lay claim to heaps of table space in the colony lab. Next step: get the transceivers talking to each other in switch mode. We shall see how it goes.

A Trans-whatter?
Jonathan McLean
7 February, 2007
  • goals
  • history

An Introduction

Welcome one and all to yet another robotics project. My name is Jonathan McLean, a Junior at Connecticut College. This is the homepage for my Computer Science 496 Spring Semester Seminar class that will most likely take more than just this spring semester. The goal of the seminar is to complete and individual research project and present it to the class at the end of the semester (or so I have been told considering I was abroad when this whole scam was concocted). Either way this is an Independent Study-style course. My topic of reasearch: inter-robot communication through microcontroller-controlled Radio Frequency (RF) transceivers. What does that all mean? Well, hopefully as I come to understand it, so will you, the reader (as long as you follow this website). This site will serve as a digital notepad/photo gallery/showcase for what I hope will become a network of flying robots.

My Faculty adviser for this project is Dr. Jana Iyengar. Together we have settled upon the following goals for the semester:

  1. Research RF transceiver technology with the notion of purchasing such a device. It must fit certain conditions:
    • be small enough to feasibly place on a potentially flying autonomous device
    • be able to integrate with existing BASIC Stamp II micro controllers so as to be adapted to Conn's pre-existing robots
    • low power consumption!
  2. Purchase two RF transceiver devices that fit the requirements above and establish that they can use PBASIC to initiate and sustain data transfer in a two way fashion
  3. Come up with primitives necessary for a general robot-to-robot communication. May need to look into literature a bit (send, broadcast, sendmany, recv, recvfrom, recvany)
  4. Information gathering, learning network (and topology?.
    • How do existing robots identify each other (RFID?)
    • How do robots establish reachability (heartbeats, ping?) and connectivity
    • How does a new entering robot learn about the network?
  5. Develop an abstracted code base and protocol layer to allow for data transmission between two transcievers
    • Develop modules for network comm.
    • Can we build libraries?
  6. Apply these techniques to flying autonomous robots to allow for information to be passed on positioning and coordination. If flying autonomous robots are not available, apply the techniques to preexisting Conn robots to allow for communication between them.

Pardon if sometimes the writing on this site is less than formal. Though this site will present the visitor with recent updates, it will mostly be in the form of my thoughts written down instead of manicured entries. As such not everything will make sense all the time, but hopefully the pictures will be pretty.