This is an old revision of the document!
Ethernet m0dul. Makes the r0ket speak IP. Currently in planning.
Main reason to do this is to get the received Openbeacon data from the r0ket to a central location in a nice and easy way.
There are of course other options to do this:
We currently get the data off via USB-Serial, this requires one USB port per r0ket – due to the length limits of USB cables about one Computer (Dockstar/etc.) per 2 r0kets. This requires more Hardware and more configuration for roughly the same effect.
We could get the data off via rf - i.e. Wlan or Xbee.
Plans on how to do it on the hardware side.
Two main options.
Use a “simple”/“stupid” Ethernet chip, and do IP in the r0ket.
Use a “smart” Ethernet chip which has a full TCP/IP implementation.
→ So far it looks like the “smart” variant is the way to go.
It would be nice to be able to (optionally) power this via POE.
Again two options here:
according to Wikipedia, the injector decides wether to provide power via the “unused” or the “data” wires, which means more work for us…
→ Still undecided.
As far as I can tell, we must decouple the ethernet lines from our ciruit. Doing this sounds like no fun[tm].
There are RJ45 Connectors with “integrated magnectics” which do this for us. But they then need to be POE-Capable which appears to be quite expensive.
1-6605834-1 is 6,08€ at mouser (http://www.te.com/catalog/pn/en/1-6605834-1)
“simple” RJ45 Connectors appear to be at about 0,90€
→ Still unclear if there are no other options.
Over m0dulbus. All the Ethernet chips above do SPI.
Nothing done yet. Need to decide on the Hardware first
Please implement LLDP and you will make the NOC happy :) (Possible on all of the chips, simple ethernet protocol.)