by PaulL » Sat Jul 17, 2010 9:24 pm
by PaulL
Sat Jul 17, 2010 9:24 pm
Thanks I-Bot,
I downloaded the scode.asm file, and will have to dig a bit further to understand the Atmel code better, but it doesn't look too difficult.
My main goal with Roboard is to retain a good bit of the original capability of the MRC-3024 (if not enhanced just a bit..), and I'd like to keep the stock remote in the picture. It would be handy to be able to provide a drop-in approach to get an RN-1 operational and close to stock with a Roboard as a replacement for the MRC-3024, I think that would promote the RN-1 AND the Roboard. The fun will come in extending beyond the basic command / control of the remote, but I have to start somewhere.
Right now, I have an RN-1 (Ok, not quite a stock RN-1, but relatively close) that has a Roboard on him, and he hasn't even taken his first step with the Roboard. Sad, but true. So in evolving him, my path is to get the basic capabilities back up and running, then move beyond that. It will also help with testing code and such.
I'm thinking about fellow roboteers, other folks that might purchase a Roboard, and then think "What now?". If I can build something in software that could be downloaded for free to get him back to doing what he could do with his MRC-3024, that would inspire people, would keep others from spending months getting to that very same point.
Even when I have him at a point beyond what he could do with the MRC-3024, it would be cool to switch in his old moves and use the stock remote just to remind myself about the "good ole' days" and how far he's come.
Thanks again for pointing me to the .asm file!
Paul
Thanks I-Bot,
I downloaded the scode.asm file, and will have to dig a bit further to understand the Atmel code better, but it doesn't look too difficult.
My main goal with Roboard is to retain a good bit of the original capability of the MRC-3024 (if not enhanced just a bit..), and I'd like to keep the stock remote in the picture. It would be handy to be able to provide a drop-in approach to get an RN-1 operational and close to stock with a Roboard as a replacement for the MRC-3024, I think that would promote the RN-1 AND the Roboard. The fun will come in extending beyond the basic command / control of the remote, but I have to start somewhere.
Right now, I have an RN-1 (Ok, not quite a stock RN-1, but relatively close) that has a Roboard on him, and he hasn't even taken his first step with the Roboard. Sad, but true. So in evolving him, my path is to get the basic capabilities back up and running, then move beyond that. It will also help with testing code and such.
I'm thinking about fellow roboteers, other folks that might purchase a Roboard, and then think "What now?". If I can build something in software that could be downloaded for free to get him back to doing what he could do with his MRC-3024, that would inspire people, would keep others from spending months getting to that very same point.
Even when I have him at a point beyond what he could do with the MRC-3024, it would be cool to switch in his old moves and use the stock remote just to remind myself about the "good ole' days" and how far he's come.
Thanks again for pointing me to the .asm file!
Paul