Quote:
Originally Posted by Mark McLeod
Sorry, we've been racing robots all night. They're having a pushing contest now.
Probably need to attach or email your whole project to look at.
It's hard to guess what serial port resource conflict you might have. There are too many answers.
|
Definitely zip up the project, there are a number of people out here on "the internets" who will take a look and give you a hand. Not being able to debug over the serial port leaves you with few options. The "Red Light of Doom" is typically caused by the same things that would cause a Windows-type program to either crash, or it went into an infinite/extremely long loop somewhere. The infinite/long loop would be the first thing I'd carefully check for in your code, it's easier to do than you'd think.
If you are indeed the lone programmer for your team (poor guy
) you might want to force some code versioning on yourself. Things like CVS or SVN (check out wikipedia or google it yourself) CAN AND WILL SAVE YOUR BACON! It'll allow you to easily step back in time before you screwed something up, and will also provide an easier time of multiple people working on the project at once. This way you can try training an interested freshman without fear of him making changes you can't get rid of when your team leader asks you "is autonomous mode done yet?"
It takes some work to understand, but I promise (and every other user of some code versioning system will promise) it will be worth the effort.
--Eric