Team Four/Journal

From Maslab 2014
Revision as of 01:30, 8 January 2014 by Atw (Talk | contribs)
Jump to: navigation, search

Day One

No batteries ;( What do? Zzz Going over lecture = going over competition. HEY LETS GO FOR COLLECTING BALLS YES? :D

1526197 10152102423785700 389387801 n.jpg 1512679 10152102539610700 311967234 n.jpg

IMG 20140106 211640.jpg IMG 20140106 211648.jpg

No electronics hooked up yet, but kitbot base mechanically works.

Ubuntu has been force fed onto our slate, opencv 2.4.8 compiled, and the CV stuff we have already is running on it with the on-board rear camera.

No work on actual electronics yet.

screenshot from slate


Day Two

2/3 team sick, 1/3 busy. We got a battery and made most of the connectors we need for kitbot. We have the Maple IDE working on two of our computers, and we're trying to get the maple libraries to work for our own makefiles, instead of the stupidly complicated ones that ship with libmaple.

Being sick is really not helping things.

Connecting to botclient is unbelievably simple. We'll probably spin off a process for every image we want to save, so the main system won't be hung up by the client or disk writes, if any are needed. It might be worth spinning off a process that writes out the image, then having a python daemon pick it up for simplicity (C and json is a bit of a pain). A ramdisk is easily fast enough to be used for passing images between processes, the SSD in the tablet might be too.

Reading sensor data for tomorrow's checkoff will probably be pretty trivial with the Maple IDE or libmaple toolchain, but it'd be nice to have sensors working outside of those two things, since both are a pain.

Personal tools