Client:Microcontroller - Server:PC

This isn't really the place for this, but /prog/ is the most technologically knowledgeable place on 4chan, so I'll ask here.

Say that someone wanted to automate various tasks using microcontrollers. For example, if he wanted to do some automated brewing and distilling, he could have a microcontroller that is set up to check temperatures, decide when a batch is ready, etc. Other microcontrollers could be used for other tasks, like turning lights on at specific times, or anything you can imagine. Now, to keep track of these microcontrollers, record their readings, and update their routines when necessary, one would need a server to connect them too. Any run-of-the-mill x86 PC would do here.

My question is, what would one use to connect the server to the microcontrollers without increasing cost or needlessly complicating things? Ethernet is possible, and would allow one to connect to many devices, but would greatly complicate both the hardware and software of the microcontroller. Serial or parallel ports could work, but the average PC only has one of each of those. Can /prog/ think of a connection solution here?

You can get a microcontroller with builtin USB for like $2.

wiki zigbee

Anonymous likes this.

>>1
use REAL microcontrollers faggots.

>>5
Why not just use mexicans?

>>5
What's the matter, too COMPLEX for you?

The solution is Ethernet. Get a micro with a built in TCP/IP stack, problem solved.

>>8
This. Very this.

These are cheap and well documented now.

>>7
It is not enough to be merely RATIONAL.

I²C bus or 1wire.

>>10
Get REAL.

>>12
Your bluntness, sir, CUTS like DEDEKIND.

Use the parallel port, it's the easiest method; you basically get 13 output pins and 5 input pins per port, and if you need more than that, PCI-E parallel port cards (which emulate a standard LPT port, i/o addresses and everything) are like 10-15 bucks each. Less latency, and more importantly, less software overhead than USB by far. For example, to output a byte to the low 8 bits of the output pins, you'd just write:

outb(0x378, data);

Where outb is just some inline assembly for the x86 out opcode.

>>14 here, forgot something.

You actually don't even need more parallel ports, if 13 outputs and 5 inputs (might be 4 inputs, I'm not certain) isn't enough; just get some multiplexers or shift registers, and some latch ICs (the 74HC series works well), and you've basically got infinite i/o pins, with only a slight performance hit.

I2C

Are you GAY?
Are you a NIGGER?
Are you a GAY NIGGER?

If you answered "Yes" to all of the above questions, then GNAA (GAY NIGGER ASSOCIATION OF AMERICA) might be exactly what you've been looking for!

20 Name: Anonymous 2013-01-18 22:51

/prog/ will be spammed continuously until further notice. we apologize for any inconvenience this may cause.