<?xml version="1.0" encoding="UTF-8"?>
<!--Generated by Squarespace V5 Site Server v5.13.159 (http://www.squarespace.com) on Sat, 25 May 2013 16:04:00 GMT--><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><title>Journal</title><link>http://www.thecodebenders.com/journal/</link><description></description><lastBuildDate>Wed, 24 Apr 2013 20:49:43 +0000</lastBuildDate><copyright></copyright><language>en-US</language><generator>Squarespace V5 Site Server v5.13.159 (http://www.squarespace.com)</generator><item><title>AVR's and FreeRTOS</title><dc:creator>Matthias</dc:creator><pubDate>Wed, 24 Apr 2013 19:55:36 +0000</pubDate><link>http://www.thecodebenders.com/journal/2013/4/24/avrs-and-freertos.html</link><guid isPermaLink="false">317094:3313767:33430425</guid><description><![CDATA[<p>Lessons Learned:</p>
<p>attribue(__interrupt__) and attribute(__noinline__) may appear similar but the former will totally hose your stack pointer. &nbsp;Like to the point where you're executing out of SRAM. Bad news on a harvard machine. &nbsp;Only took a day to find that typo... yeesh.</p>]]></description><wfw:commentRss>http://www.thecodebenders.com/journal/rss-comments-entry-33430425.xml</wfw:commentRss></item><item><title>Just testing mobile posting.</title><dc:creator>Matthias</dc:creator><pubDate>Sat, 25 Feb 2012 14:09:04 +0000</pubDate><link>http://www.thecodebenders.com/journal/2012/2/25/just-testing-mobile-posting.html</link><guid isPermaLink="false">317094:3313767:15182118</guid><description><![CDATA[<p>Hopefully this will encourage more frequent posting.</p>]]></description><wfw:commentRss>http://www.thecodebenders.com/journal/rss-comments-entry-15182118.xml</wfw:commentRss></item><item><title>Day 5: The Sunday Surprise Run</title><dc:creator>Matthias</dc:creator><pubDate>Sun, 18 Jul 2010 16:15:36 +0000</pubDate><link>http://www.thecodebenders.com/journal/2010/7/18/day-5-the-sunday-surprise-run.html</link><guid isPermaLink="false">317094:3313767:8289900</guid><description><![CDATA[<p>We've been granted a final chance, which honestly, for the competition is a pretty awesome thing. &nbsp;It's drug all the teams (and robots) back to the pool nice and early on the final day of competition. &nbsp;Traditionally Sunday is pretty sparse, I mean, with no "real" reason to be there it's hard to drag college students out to stand around a pool all day bright and early.</p>
<p>We're currently gearing up for our dunk. &nbsp;We'll have a 15minute run at 11AM PST, and I'll be reporting back immediately after. &nbsp;We're hoping to be able to take first in the losers bracket as it stands now. &nbsp;Gate, Bouys, Hedge and a few Paths are what we're hoping for. &nbsp;Wish us luck!</p>
<p>Time to have fun, but I'll give you the results:</p>
<p>Our run didn't go so hot. &nbsp;We didn't make it under the gate, I think we still maintain our place from yesterday, more info coming tomorrow probably.</p>]]></description><wfw:commentRss>http://www.thecodebenders.com/journal/rss-comments-entry-8289900.xml</wfw:commentRss></item><item><title>Day 4: Damn it's early...</title><dc:creator>Matthias</dc:creator><pubDate>Sat, 17 Jul 2010 15:09:19 +0000</pubDate><link>http://www.thecodebenders.com/journal/2010/7/17/day-4-damn-its-early.html</link><guid isPermaLink="false">317094:3313767:8284591</guid><description><![CDATA[<p>We arrived at the pool at 6:30 this morning and sadly found ourselves 6th in line to hit the practice side. &nbsp;This meant the earliest we could hit the water without some help would be 10AM. &nbsp;A good hour and a half after our slotted qualifying time... At first it looked a little bleak, but thankfully due to an awesome gesture by Cornell we were in the water at 7:30. &nbsp;We found a bad camera cable was in use, critical knowledge before our qualifying run. &nbsp;Basically at this point, wish us luck, we need it.</p>
<p>After the vision guys performed some tweaking, we hit the water and prepared to see what all SeaWolf could do. &nbsp;After a few runs of being sent towards various sides of the gate, the diver finally gave us a good start towards the center. We veered a little to the left while we were covering the distance from the dock to the gate, which required a little gymnastics to align with path, but we managed it. &nbsp;Seawolf headed for the bouy's, bound directly for the red one. &nbsp;About 5 feet from the bouy, Seawolf went into a sweeping partern... sadly, something like as if it was looking for the next path marker. &nbsp;She slowly inched her way forward, sweeping from left to right. We were down to 2 minutes on the clock, no time to reset and were just praying for the bouy bounce. &nbsp;</p>
<p>With a minute left we saw the divers sign that we had hit red, but there was a little doubt which Seawolf saw fit to correct. &nbsp;After a few seconds of intermittent contact, Seawolf basically sat down on the bouy. &nbsp;Clearing up any remaining questions of her contact. 30 seconds left.... time. &nbsp;Seawolf III completed more of the course than she ever had before. That's enough to keep us pleased and as of the standings last night, it was enough to put us in the top 10.</p>
<p>We also opted to try to grab a few extra points yesterday by implementing JAUS, a DoD driven project that acts as a protocol for communicating with unmanned vehicles. &nbsp;Chris set to work shortly after we were out of the pool and managed to have us up and running to nearly complete state within 2 hours. &nbsp;The University of Florida had developed an opensource solution to JAUS called JAUS++ and with a little finagaling Chris managed to get it to compile against our own LibSeawolf making implementing the protocol near painless. &nbsp;In no time we were able to send data and let a JAUS sever connect with us properly, change states correctly, and most importantly, pass data out to the server. &nbsp;There was still one little bug preventing us from&nbsp;completing&nbsp;the Interop Challenge completely, but we'll have another shot between 8-10 on Sunday.</p>
<p>While the 9th place announcement was reason enough for excitement, Dave Novak had one last surprise for us. &nbsp;Sunday would play host not only to the finals which the top 7 teams would be competing in, but also to a wildcard round in the morning consisting on a single 15 minute run. &nbsp;There's a mystery check waiting for the team who is able to do the best, and with only one teams ranked above us by a thin margin so far, we're hoping for the best.</p><p><br/></p>]]></description><wfw:commentRss>http://www.thecodebenders.com/journal/rss-comments-entry-8284591.xml</wfw:commentRss></item><item><title>Day 3: Lets Compete!</title><dc:creator>Matthias</dc:creator><pubDate>Fri, 16 Jul 2010 20:36:35 +0000</pubDate><link>http://www.thecodebenders.com/journal/2010/7/16/day-3-lets-compete.html</link><guid isPermaLink="false">317094:3313767:8280592</guid><description><![CDATA[<p>Today marks the true start of the competition!  Last night we were able to choose which qualifying run time we wished to run based on our standings from last year.   By the time it got to us, 12:30 was the latest we were allowed to hit the pool but that gave us plenty of time for an early morning practice run and some debugging time if we needed it.</p>
<p>After a long night for the club 5:30 came early, a necessity after a long nights work if we were going to get everything packed up and make it to TRANSDEC early enough to get a nice early practice run in.  Thankfully everyone is pretty on task and we were making tracks for the pool by 7.  When we arrived we put in for the 8:30 pool test slot and Chris headed right out to start taking some accoustics measurements after some major retooling of how the correlation block was being executed on the blackfin.  Accoustics seems to be growing ever closer to that magical point of actually being able to drive Seawolf!  We're hearing pings loud and clear and are now just working on effectively measuring the delays between when the ping reaches Seawolfs four ears.  These delays will enable us to locate the pinger and hopefully track it down!</p>
<p>The 8:30 pool test wound up being more like a 9:15 pool test due to some delays at the pool and kind of dampened our hopes.  It turns out gatorade bottles don't exactly hold their shape when you fill them with air and submerge them 8 feet under water, meaning our ballasts stopped giving us much flotation.  Seawolfs a bit on the heavy side and losing boyancy was wreaking serious havok on our ability to accurately find and maintain a depth.  While this wasn't much of a problem for the gate mission it proved disastrous for trying to bump the bouy.  Our emergency breach code kept trying attack Micheal <br />(our diver for the time) after seawolf would start sinking at depth due to compression and our control code not ramping up quick enough to compensate.  Thanks to Maryland we've now replaced those pesky bottles with some pink foam that seems to be working well (if maybe not a little too well as we've now discovered).</p>
<p>While inspecting Seawolf after the test run, we noticed that one of our Fischer connectors (our class A waterproof connectors) was beginning to corrode.. readers from last year, this might sound a little familiar, and yes, Seawolf was once again performing chemistry experiments.  A solid round of testing by Rabbit found that the aluminum frame that holds Seawolf together was carrying a voltage! After a good deal of debugging we found that one of the connectors had a shield wire touching the outer casing.. we'd found our culprit, the source of our attempts to once again electroplate Seawolf.</p>
<p>After a bit more acoustics testing and some  buoyancy adjustments in the dolphin pool (small pools set up for teams to test in) 12:30 rolled around and it was time to see old Seawolf get into action.   Tetherless Kirk (resident Navy sailor dude for lack of a better description) lowered Seawolf into the water and after explaining our mission start/killswitch system to the diver, the swipe was made, the status light blinked and Seawolf dove.  It quickly became evident that we had overcompensated a bit in the boyancy department, even at when she was at depth you could still see the jets from the struggling thrusters breaching the surface. Due to a cross breeze there appeared to be a current in the Transdec pool, combined with the mistake of leaving her forward speed set a little low and the immense thrust the vertical thrusters were exhibiting Seawolf barely missed making it through the gate deciding to split the right side pole instead.  After two more attempts with various degrees of success and failure we yanked her our of the water, Michael plugged in the tether and corrected our speed issue.  We reset and tried again, this time succeeding in making the gate!  Sadly we never saw the path on the bottom of the pool and got a little hung up looking for it, forcing the restart once again.  We again managed to make the gate but path align failed again.</p>]]></description><wfw:commentRss>http://www.thecodebenders.com/journal/rss-comments-entry-8280592.xml</wfw:commentRss></item><item><title>Day 2: Bug Squashing</title><dc:creator>Matthias</dc:creator><pubDate>Thu, 15 Jul 2010 20:33:55 +0000</pubDate><link>http://www.thecodebenders.com/journal/2010/7/15/day-2-bug-squashing.html</link><guid isPermaLink="false">317094:3313767:8269142</guid><description><![CDATA[<p>After a long day at Transdec on Wednesday we headed out to find some food chosing the always popular Baja Fresh. &nbsp;The trip yielded &nbsp;some quality food, a reminder of last years adventures (looking at you VT) and an awkward trip around the Carl's Jr. while we had left poor Thunes behind at CVS. &nbsp;The remainder of the evening was pretty uneventful with the evening winding down&nbsp;uncharacteristically&nbsp;early for the NCSU URC.&nbsp;</p>
<p>We were greeted to day two of the competition once again by the delightful wakeup call/advertisement hotline the Kona Kai has opted to employ. &nbsp;I believe that they fail to realize that waking up to an advertisement is a sure fire way to leave a sour taste in my mouth for whatever it is they're trying to convince me to spend my money and &nbsp;"extra" time on while we're here.</p>
<p>We once again made it to TRASNDEC ahead of our 7:15 unload time and quickly registered for our first pool test of the day. &nbsp;That's about where things started falling apart. &nbsp;Once we were in the water we started losing communication with just about everything on random occasion... Our little honey moon with the new and predictable Seawolf was coming to a close and we were starting to see problems of old start creeping out on us. &nbsp;After a bit of debugging, it turns out, running thrusters and electronics on a single bank of batteries is either a project for grad students or worth avoiding by isolating your thrusters.</p>
<p>It turns out, big inductive loads, make equally big noise. &nbsp;This meant that from time to time, the USB hubs on Seawolf were eating some crazy voltage spikes, resulting in the IMU and our cameras freaking out in a rather spectacular fashion. &nbsp;Seawolf was regularly going blind deaf and dumb and worse than that, was having trouble putting it all back together once things had settled down. &nbsp;Sadly this little problem has cost us our brand new power board... but a quick reworking of our old harness and a DC-DC converter has given us legs to stay in the competition!</p>
<p>While this hasn't completely fixed the issue completely, we're banking on a few zener diodes on the last few points noise could work its way back up the lines to the USB hub.</p><p><br/></p>]]></description><wfw:commentRss>http://www.thecodebenders.com/journal/rss-comments-entry-8269142.xml</wfw:commentRss></item><item><title>Back in San Diego!</title><dc:creator>Matthias</dc:creator><pubDate>Wed, 14 Jul 2010 21:35:56 +0000</pubDate><link>http://www.thecodebenders.com/journal/2010/7/14/back-in-san-diego.html</link><guid isPermaLink="false">317094:3313767:8255713</guid><description><![CDATA[<p>It's that time of year again, time to let Seawolf do her thing! &nbsp;After an all night packing/organizing marathon the NCSU URC headed for the RDU Airport at the bright and early hour of 4:30 and began working our way through the maze that is modern airport security. &nbsp;You've never truly experienced the TSA until you've tried to take a robot and a labs worth of test equipment through an airport while in that foggy, not quite awake, haven't slept in the past 24 hours state.</p>
<p>I wish there was more to tell of the flights, and there probably is, I however managed to catch up on some much needed sleep over the course of the two flights being rattled from&nbsp;unconsciousness&nbsp;only when the&nbsp;passengers&nbsp;next to me required my movement. &nbsp;Pitfalls of the isle seat I suppose, but well worth it.</p>
<p>Once landed in San Diego we were glad to find SeaWolf, although&nbsp;throughly&nbsp;searched, was still in tact and all of our spray painted boxes had survived the hands of the "throwers" behind the scenes. &nbsp;Kevin and Dave set off quickly to locate out 15&nbsp;passenger&nbsp;van, which much to our&nbsp;surprise&nbsp;came back as a much more modest Kia Serento with seating for 7. &nbsp;A quick game of Tetris and we hit the road and headed for point Loma with a minor distraction of food planned along the way.</p>
<p>We made it to our favorite resort, the lovely Kona Kai, around 2 and just in time for our orientation. &nbsp;Orientation consisted of the typical, "You're on a navy base, in California, there are plenty of ways to get hurt, please avoid them and don't tell all of our secrets" followed by an unusually short round of Q and A time with Dave as engineers from competing schools grilled him on the specifics of how the course was going to be set up, missions were to be run, and a fair share of questions that didn't need to be asked. &nbsp;We stayed quiet for the most part, I believe our stance on such issues as course lay out would be more aptly described as reactionary&nbsp;than proactive.</p>
<p>Following orientation, a quick check-in and we were on to assembling our craft. &nbsp;Thankfully, and much to our amazement, even with the reduced load, there were no major missing components, nothing severely damaged, and other than a utility knife (which.. in reality we had, it was just in hiding) no missing tools! &nbsp;With assembly and some work on our new cable hiding skirts, Seawolf was ready for action and looking the best she has since we've moved on from SeaWolf II.</p>
<p>The remainder of the evening was spent tooling around for a few parts to complete our new powerboard, finding some food for dinner, and finally locating some much needed sleep with wake up calls coming at 6AM.</p>
<p>This morning certainly came quickly, but thanks to that wonderful 3 hour west coast lag we were all up and moving fairly quickly. After removing a few thrusters from Seawolf to get her to fit in the trunk, we did the impossible (note: this may mean the end of the world is in fact upon us) and showed up to Transdec 5 minutes ahead of our 7:15 unload time.</p>
<p>A quick unload and some short tuning had us up and running well enough to hit the water for the first time this year. &nbsp;Our first brush with fabled Dave Novak gave us the 8:15am testing slot in the practice half of the pool. Following Cornell we were the 3rd team in the water. &nbsp;While it wasn't all that visually impressive of a run due to a small bug, we couldn't be happier with the way SeaWolf was performing. &nbsp;Long gone are the days of futile attempts at making her go in a straight line! (now replaced with less futile attempts to make her dive... but at least it was much more resolvable) &nbsp;A short retooling period following the first test led up to our second. &nbsp;Again, while not that impressive to those watching, we collected good data on what the objects we're trying to see actually "look" like to SeaWolf. &nbsp;After having some navy divers drug her around for a bit we pulled her out and have set out on giving her her last major upgrade of the season, a brand new power board designed by Kevin Wolf and Byron Beddingfield. &nbsp;A few short reworks of some bad parts and a few load tests later we're all ready to see the days of the famed rats nest we call our wiring harness come to a close and the introduction of a sleek and clean power solution make that last step toward a clean and managed case</p>
<p>Once again AUVSI has managed to fail to provide reliable internet at Transdec, and while not particularly&nbsp;surprising, (I see how providing internet to an outdoor secured navy testing pool could provide some challenges) is&nbsp;atrociously&nbsp;annoying at a robotics competition. &nbsp;This blog post has been the result of a quick trip back to the Kona Kai for some parts orders and some the need for some&nbsp;datasheets.</p>
<p>I'm sure we'll be in the water at least one more time over the afternoon and hopefully we'll start collecting data for our accoustics system! &nbsp;I'm planning to update this once a day, but you may also want to check out robosub.org for more up to date information and video recaps starting on Friday!</p>
<p>Thanks for reading,</p>
<p>Matthias Welsh</p>]]></description><wfw:commentRss>http://www.thecodebenders.com/journal/rss-comments-entry-8255713.xml</wfw:commentRss></item><item><title>SeaWolf Updates</title><dc:creator>Matthias</dc:creator><pubDate>Tue, 30 Mar 2010 01:30:32 +0000</pubDate><link>http://www.thecodebenders.com/journal/2010/3/29/seawolf-updates.html</link><guid isPermaLink="false">317094:3313767:7180017</guid><description><![CDATA[<p>Ah finally, reviving my blog.  Things have been a bit dead, but now we're beginning to crank along.  Hopefully I'll have time to update my other projects too, but we'll see.</p>
<p> </p>
<p>So SeaWolf... It's that time of the year again when we can feel San Diego beginning to lurk around the corner and everyone starts ramping up their efforts.  We currently have 3 major projects under development. We're testing vision pretty handily, all the time finding out that our PIDs and control systems weren't quite tuned or working as we had intended but luckily we're discovering this now and not at Transdec this year.  We'll take it.   A couple of minor things we're currently looking to rework vision wise</p>
<p> </p>
<ol>
<li>Wide angle lense. This is hurting us.. vision keeps losing site of our target far before we get there leaving us in a dead reckoning state.  If I remember correctly.. our test gate is a little smaller than the real gate, meaning this problem will only compound during competition.</li>
<li>Better cameras.  Our current cameras are webcams in fancy waterproof enclosures.  While this is convenient in some aspects, in others it's a bit of an annoyance.  A complete lack of control over auto-gain, auto-whitebalance and auto contrast can wreak havok on the image we're getting back.  This boils down to the fact that off the shelf webcams weren't intended to deal with underwater lighting conditions, surprise surprise.  We're looking for cameras currently that will allow for more fine grained control under linux, if you have any reccomendations, please shoot me an email (contact stuff in the side bar).</li>
</ol>
<p> </p>
<p>One of our members, Kevin Wolf is hard at work on a new power-board for SeaWolf.  The current "power-squid-thing" is functional (loosely defined) but is easy to mis connect, looks like hell and generally needs to be cleaned up.  In addition to tidying things up quite a bit Kevin is also preparing out switch to some form of modern battery technology.  Currently we're in the process of investigating LiPoly as they seem to be the balance between energy density and explosiveness (li-ion being equated to placing incendiary grenades in our case with the pins pulled and hoping for the best) especially due to the high-current pull of our thrusters.</p>
<p>Finally, I've currently taken on the objective of ripping out a new motorboard for Seawolf.  There's a few quirks in the current board that make it a bit difficult to deal with.  The design objectives for this project are to reduce the USB cable count (we were going to try to cut down on the number of controllers... but this works for now).  We're planning to achieve this through one of these guys, <a href="http://www.ftdichip.com/Products/FT4232H.htm">FT4232H by FTDI</a>. This will allow us to communicate with 4 Arduinos.  3 will be used for motor control and a 4th will be broken out for use with sensors or anything else we decide we need (status lights etc).  The current plan for the breakout (both analog and digital) is to provide:</p>
<p>signal1    voltage    ground</p>
<p>signal2    voltage    ground</p>
<p>This allows for 3 pin headers to be slapped in instead of having to run individual wires all over the place.  A few fuses to protect our controllers and call it a day.</p>]]></description><wfw:commentRss>http://www.thecodebenders.com/journal/rss-comments-entry-7180017.xml</wfw:commentRss></item><item><title>Final Recap</title><dc:creator>Matthias</dc:creator><pubDate>Fri, 07 Aug 2009 04:09:28 +0000</pubDate><link>http://www.thecodebenders.com/journal/2009/8/7/final-recap.html</link><guid isPermaLink="false">317094:3313767:4837392</guid><description><![CDATA[<p>Well, I know this is a bit late but it's been hard to find the time to sit down and acutally finish a post about what went on.&nbsp; Firstly I just want to say it's been a pleasure being a member of the team this year.&nbsp; From start to finish we've had 10 months to design a water tight robot that can see, hear, and is aware of it's surroudings.&nbsp; Too all who have finished major projects this year, congratuations, namely, Baird Hendrix with his work on our acoustics system, Micheal and Jeffery with their work on vision, and Chris with his work on SeaSQL and libSeaWolf.&nbsp; Thanks also to Tim Capo for the time put into creating the hardware that allowed us to get this far, the time and materials spent on our dropper, camera cases, torpedo launcher and movable brackets have been invaluable to us.&nbsp; Finally, to our sponsors, thank you, we're hoping to grow your ranks in the next year with our vastly improved position and brand new robot!</p>
<p>So lets start with the practice run, which was largely an impressive success, due to tether length issues we were only able to complete the gate mission but after looking back over the logs we were able to see that Seawolf indentified both the bouy and orange marker pointing to the bouy.&nbsp; After seeing Seawolf do something totally intelligent, we headed back to our tent with high hopes and ready for our next chance at qualifying.&nbsp; In large we decided to leave Seawolf as she was, fixing a few funky bugs that Chris found but nothing major.&nbsp; When he time came we quickly headed to the pool, ready to make the most of our last chance.&nbsp; Once she was on the crane we all crossed our fingers and hoped for the best as a culmination of ten very short months and four very long days was about to hit the water for the final run.&nbsp; We instructed the diver, blue RFID card to blue tape to start and kill in the event of a restart, red magnet to red tape in the event of a system failure.&nbsp; Once in the water, the diver swept blue, and Seawolf sprung to life, but with no forward motion, she aligned to the gate, sank to depth, but refused to go for it.&nbsp; After sitting for a few seconds she began to drift backwards and attempted to pin our poor diver under the dock, and we signaled to kill. After being dragged out from beneath the dock we quicky grabbed a hold of the crane operator Kirk, and hoisted SeaWolf onto the dock.&nbsp; Throwing our teather down to Brooks, Chris plugged in and started debugging.&nbsp; After 10 long minutes of bug hunting he stumbled on a bug he had corrected early which was adding an offset to the yaw directional thrusters and pushing Seawolf forward!&nbsp; After a quick fix we dropped her back in the water and hoped for the best, the driver once again swiped blue and once again she saw the gate, aligned herself, sunk to depth and with only a minute to spare took off toward the gate. B-lining directly through the gate she make a small course correction to align with the orange plank sending us to the bouy, and headed for it.&nbsp; Sadly, we shortly detoured and missed our target and after some debugging work later we found that a single line of code had left us stuck in the "search for path" mission.&nbsp; After all we had accomplished this year, that was the least of our worries, we have a working platform from which to build on last year, and we had sucessfully qualified this year, placing us somewhere in the middle of the pack for this years competiton.</p>
<p>More to come.. but I'm too tired right now.&nbsp; Hope you've enjoyed following us and I look forward to blogging our design process and competition again in the following year!&nbsp; Thanks to everyone who's shown an interest in SeaWolf and please continue to, we're only going up from here!</p>]]></description><wfw:commentRss>http://www.thecodebenders.com/journal/rss-comments-entry-4837392.xml</wfw:commentRss></item><item><title>Another day...</title><dc:creator>Matthias</dc:creator><pubDate>Sat, 01 Aug 2009 15:37:15 +0000</pubDate><link>http://www.thecodebenders.com/journal/2009/8/1/another-day.html</link><guid isPermaLink="false">317094:3313767:4800184</guid><description><![CDATA[<p>Well, we didn't quite make it under the gate to qualify yesterday sadly but we've got another shot today which we're much better prepared for.&nbsp; We've currently got a practice run scheduled for 10:20 and we're expecting good results.&nbsp; We spent a late night last night outside the pool at the Kona Kai getting things ready and we're confident going forward that we've at least got a shot of breaking the top 10.</p>
<p>I'll start with yesterday thought, kind of a frustrating day for us.&nbsp; Seawolf was having bugs creep up that were about as off the wall as they come.&nbsp; During our qualification run Seawolf was having trouble doing anything but spinning in circles and trying to attack our poor diver.&nbsp; It's quickly become apparent that when Seawolf goes into a spin the extruded aluminum coming off the rear of our craft acts as a rather scary weapon in addition to the handles they were intended.&nbsp; The divers are nimble though and averted any injury but after trying to take him out a few times, we pulled our ornery bot out of the water and set to debugging.&nbsp; While we're not 100% sure what was causing the problem it appears it was related to attempting to use our magnetic kill switch as a mission start.&nbsp; Surprise, surprise, electronics + magnets = problems.</p>
<p>We quickly scheduled a practice run and sadly... we found similar results.&nbsp; Seawolf was in a mood to fight and little else.&nbsp; After a bit of messing around and some debugging at TRANSDEC we headed out in somewhat low spirits.&nbsp; On our way out of Point Loma we happned to see another van, and it was on.&nbsp; After the necessary egging on back and forth, we found that it was virginia tech, both in our 15 person rental vans.&nbsp; We took off and they followed suit.&nbsp; With engines roaring (a rather impressive sound, not that that translated to much in terms of speed) we barreled through San Diego.&nbsp; We have the superior craft when it comes to vans though and we were eventually forced off the road as our destination approached, but there's nothing like a roaring engine (regardless of speed.. and with loaded vans there wasn't much of that) to introduce a little injection of some much needed fun into the evening.&nbsp;</p>
<p>After grabbing a bite a Baha Fresh we headed back to the Kona Kai only to discover a full scale Luau taking place right outside our door. We took in some sights and sounds for a few minutes before packing up Seawolf and heading to the pool to correct our rather disabled craft.&nbsp; After returning to our RFID card mission start system we found some improvement, at least now all of our motots were staying on, we still had some issues to debug with our yaw PID (control code).&nbsp; Chris started correcting problems one by one and pretty soon, SeaWolf knew what straight was again.&nbsp; With our problems solved we moved onto testing our vision bouy bumping code.</p>
<p>Because of the lighting in the pool, the orange bouys were showing up white, not something we were prepared to deal with, however due to Micheal and Jeffery's hard work on vision and interesintg "find the closest thing to what color we're looking for" code the red on my swim trunks quickly became a suitable target.&nbsp; Torro, torro, torro!.&nbsp; After some minor corrections we were quickly heading the right direction and with good time.</p>
<p>After all of Chris's contributions for the day he took the chance to grab some sleep while our vision guys were hard at work, but once they were done it was time to mix our "go straight" and "find the gate" code.&nbsp; After waking Chris we attempted to re-test the "go straight" code with scary results, again seawolf was lost, and going in circles.&nbsp; Frustrated, cold from being in the water and beat Kevin and I hopped into the hot tub to relax for a few minutes.&nbsp; I was quickly requested back in the pool, and in no time, seawolf was once again on the right track.</p>
<p>So here we are, back at transdec, with our practice run coming in less than an hour.&nbsp; We're currently mixing the vision and go straight code hoping for the best results.&nbsp; Wish us luck, and we'll be back shortly!</p>]]></description><wfw:commentRss>http://www.thecodebenders.com/journal/rss-comments-entry-4800184.xml</wfw:commentRss></item></channel></rss>