Page 2 - Coding a hardware

Not necessarily geniuses, but they definately know there stuff. It's not likely you're going to find anything at your level right now, I've looked a while and the best I can get is explanations of what does what, not really how. If you're really interested in this Major in Computer Engineering in college and specialize in Microelectronics.

woah triple post! Please use the edit button next time, just leave a blank line inbetwwen your different ideas/subjects to people don't get confused at why you jump around. heres and example, it works pretty well.

I dunno about geniuses, they just when to college and got trained my Intel and along with a ton of other people they slowly develop the chips. If you were to ask an Intel engineer about overclocking an ATI 9800 they'd probably not have a clue. Its just they're really good in their field.

All devices that take input and give output have software, just like your desktop.

That software is embedded into the system that is being used. It is very likely that the software cannot be modified and is written in a low level language (like assembler) to directly interface with the hardware and stored in a ROM (read only memory) device. Again, like your computer, the software is executed by a chip on the device and takes inputs (like steering controls) and generates outputs (signals to the motors).

Again, implementation specifics I can't answer. I can explain concepts.

I think you are asking about hardwired programming... this is the kind of stuff that doesn't necessarily use software to run, because all the functionality is built into the device. For some servomotor systems, for example, the driver has an output (or several) to the motor(s) it drives, no software addressing is needed because the motor is directly wired to the driver.

Now, in an RC vehicle, there are typically a number of drivers. They receive input from a radio receiver which gets its signals from the remote control. I haven't worked on those types of circuits, so I can't tell exactly how the data is encoded or anything like, that, but I can give the theory behind it. The reciever in the vehicle will separate the different signals based on built-in logic and distribute the appropriate stimuli to the different drivers.

In networked devices, then the signal coming to the device will have some sort of addressing in it, commonly the first thing. Each device on the network has a unique address for it listens for. If the address header doesn't match, then the device ignores the data. If it does, then the device receives the data and performs the appropriate functions.

A common example of this would be the IDE bus your hard drive is on. Each IDE channel is an independant data bus the can accommodate two devices. The IDE controller sends an addressing signal down the bus and whichever device is being addressed will respond with an acknowledge signal (part of the "handshaking" process used for most bus communications). The controller then sends the commands and/or data intended for that device. The other device ignores this because it was not addressed. The devices are assigned their respective address by the master/slave straps or their position on the cable if they are cable addressed. If neither device is assigned the address sent then the controller times out with a fault (no acknowledge), if both are addressed, then the controller will get confused because there are too many acknowledgements.

not so real geniuses.... they do research at study (make try and errors)

They're not geniuses simply because what they handle is complex. They didn't invent the concept of microprocessors...the concept of microprocessors was arrived upon through a logical progression learning one thing and using it...learning another thing and using that in conjunction. Everything we have today existed at the beginning of time, in a more simple form. Humans are pretty good at manipulating what is already there, there is no real invention involved.

I think this thread has been necroed enough times. Thread closed.