Posted 17 January 2014 - 08:08 AM
Hey all.
I'm trying to write a "megaturtle" program, where 64 wireless mining turtles in a 4x4x4 pattern move together as one unit, the facing side digs, and advanced inventory management (using inner turtles for extra storage). Ideally, I'd like to have them simply run off of the startup program and listen to the rednet for instructions from a controller computer, or perhaps entering in commands from one of the turtles in the swarm and the command is then retransmitted to the rest. A "turnRight" would turn all the turtles but the "digging" turtles would change.
One brain-warping experience I'm having is the single startup program I'm writing will be run simultaneously by all turtles, including the one sending messages and (conceptually) receiving the same message simultaneously.
Right now I'm trying to get all the turtles to register themselves in the configuration so they know what part of the cube they are in and what direction they are facing). I'm realizing, I think, that I need a very robust messaging system that can receive, process, and relay rednet messages without overloading the "airspace" (e.g., preventing infinite loops of relayed messages).
I've never written anything like this before. Any suggestions or tips or URLs to helpful theory?
I'm trying to write a "megaturtle" program, where 64 wireless mining turtles in a 4x4x4 pattern move together as one unit, the facing side digs, and advanced inventory management (using inner turtles for extra storage). Ideally, I'd like to have them simply run off of the startup program and listen to the rednet for instructions from a controller computer, or perhaps entering in commands from one of the turtles in the swarm and the command is then retransmitted to the rest. A "turnRight" would turn all the turtles but the "digging" turtles would change.
One brain-warping experience I'm having is the single startup program I'm writing will be run simultaneously by all turtles, including the one sending messages and (conceptually) receiving the same message simultaneously.
Right now I'm trying to get all the turtles to register themselves in the configuration so they know what part of the cube they are in and what direction they are facing). I'm realizing, I think, that I need a very robust messaging system that can receive, process, and relay rednet messages without overloading the "airspace" (e.g., preventing infinite loops of relayed messages).
I've never written anything like this before. Any suggestions or tips or URLs to helpful theory?