m0dul-ethernet
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| m0dul-ethernet [2012/04/24 10:45] – created sec | m0dul-ethernet [2012/06/09 21:32] (current) – equinox | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| 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. | 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. | ||
| - | ====== Alternate Options | + | ===== Alternate Options ===== |
| There are of course other options to do this: | There are of course other options to do this: | ||
| Line 15: | Line 15: | ||
| * Wifi: Own Wlan would clash in crowded locations and might not reach far enough. Normal Participant wlan is possibly not stable enough. Also: running Wlan from r0ket sounds complicated unless there are all-in-one chips. | * Wifi: Own Wlan would clash in crowded locations and might not reach far enough. Normal Participant wlan is possibly not stable enough. Also: running Wlan from r0ket sounds complicated unless there are all-in-one chips. | ||
| - | ====== Ethernet Chip ====== | + | ====== Hardware ====== |
| + | Plans on how to do it on the hardware side. | ||
| + | |||
| + | ===== Ethernet Chip ===== | ||
| Two main options. | Two main options. | ||
| Line 22: | Line 25: | ||
| * Con: limited space means we will probably only get UDP, and maybe DHCP. Enough for our logging stuff, but difficult for other projects, only 10baseT | * Con: limited space means we will probably only get UDP, and maybe DHCP. Enough for our logging stuff, but difficult for other projects, only 10baseT | ||
| * [[https:// | * [[https:// | ||
| + | * Please do not use this chip. It's a pain to work with, doesn' | ||
| + | * [[http:// | ||
| + | * considerably simpler buffer/ | ||
| + | * supports 100base-TX & Autonegotiation | ||
| + | * supports Auto-MDIX (Crossover) | ||
| + | * QFN32 package | ||
| + | * ca. 3€ | ||
| Use a " | Use a " | ||
| Line 30: | Line 40: | ||
| -> So far it looks like the " | -> So far it looks like the " | ||
| - | ====== Power ====== | + | ===== Power ===== |
| It would be nice to be able to (optionally) power this via [[https:// | It would be nice to be able to (optionally) power this via [[https:// | ||
| Again two options here: | Again two options here: | ||
| - | " | + | * " |
| - | " | + | * **homegrown/ |
| + | * " | ||
| according to Wikipedia, the injector decides wether to provide power via the " | according to Wikipedia, the injector decides wether to provide power via the " | ||
| Line 44: | Line 55: | ||
| ===== RJ45 Connector ===== | ===== RJ45 Connector ===== | ||
| - | As far as I can tell, we *must* decouple the ethernet lines from our ciruit. Doing this sounds like no fun[tm]. | + | 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 " | There are RJ45 Connectors with " | ||
| Line 51: | Line 62: | ||
| " | " | ||
| + | |||
| + | -> Still unclear if there are no other options. | ||
| + | |||
| + | Discrete Magnetics: | ||
| + | * [[http:// | ||
| + | |||
| + | Recommended reading for magnetics selection: http:// | ||
| ===== Connection to r0ket ===== | ===== Connection to r0ket ===== | ||
| - | Over m0dulbus. | + | Over m0dulbus. |
| + | |||
| + | ====== Software ====== | ||
| + | Nothing done yet. Need to decide on the Hardware first | ||
| + | |||
| + | Please implement [[http:// | ||
| + | (Possible on all of the chips, simple ethernet protocol.) | ||
| + | |||
| + | ===== Openbeacon Reader ===== | ||
| + | The openbeacon reader protocol we want to emulate is fairly known. | ||
| + | Check [[tracking]] or [[tracking: | ||
m0dul-ethernet.1335257103.txt.gz · Last modified: by sec