Well I would really love to get it working on-board the hydra to keep everything consolidated if possible. I''ll do some more testing and see if I can figure something out. It really bugs me that the LEDs won't even light up. It has to be something simple we are overlooking. I'll fit the bill on an ethernet shield to test with if it comes to that. Who sells one like the hydra circuit for $20?
Good to know on the MAC address part, I was under the impression that microchip loaded the MAC address on the chip.
Yeah, my comment about getting the shield was purely for testing/comparison purposes, not as a permanent solution. When something doesn't work and I can't figure out why, I like to compare it to something similar that I know works.
Here are the commercial products I know of:
Jeelab's board is neat, but a pretty different approach. No onboard level shifting and some other component differences:
http://jeelabs.com/products/ether-card
nuelectronic's design, which was sort of the reference for the Hydra:
http://www.nuelectronics.com/estore/index.php?main_page=product_info&cPath=1&products_id=4
seeedstudio USED to sell one, but I can't find it now. I actually used their Eagle files to make the Hydra circuit, it's basically a direct copy of the nu shield. They have the PCB but it's sold out:
http://www.seeedstudio.com/depot/ethernet-shield-pcb-p-179.html?cPath=77
iteadstudio is a new kid on the block and looks like a seeedstudio knockoff (ha! a knockoff of a knockoff. How "China" is that):
http://iteadstudio.com/store/index.php?main_page=product_info&cPath=18&products_id=224
Thanks for the info , yeah I was looking at terhz makeshift breakout board for his relays, I saw he was using the chip with 8 outputs ill go for one with 16 just to be sure , 110 is more than enough yeah
There are restrictions on what address you can assign to certain chips. I2C chips come in one of three varieties, generally:
1) For chips that you'd typically only need one of on your bus (i.e. an RTC), the address is hard-coded. It MUST use that address, and you can't use that address for anything else.
2) For simple chips you might need a few of (i.e. the MCP23008), the address is partially hard coded (a "family" code) and partially set by hardware, by wiring certain pins on the chip high or low. This way, you can have a few on the same bus, provided to set the address pins correctly. But, you're stuck with the general range of addresses, and can't really use anything that has an overlapping range.
3) For more complex chips, i.e. microprocessors, the address is usually set in code. This is the case with the AVRs used as processors on the Hydra.
So, for instance, you can't put 110 MCP23008's on the same bus. But you can probably put more than you'll need. And if you still need more, you can use a different I2C port expander with a different default address range.
Cool , I'll wait for another batch, would be nice to get the ethernet shield issue fixed too first. Would be really nice to have that onboard.
It might be a while! We'll see.
