Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
livebox:ethrelay [2013/11/18 11:49] – minerva9 | livebox:ethrelay [2015/06/01 06:15] (current) – Change SRC URL brett | ||
---|---|---|---|
Line 7: | Line 7: | ||
The main board requires DC power (7.5V .. 9V). The onboard 7805 regulator gives us the power for the micro and the relays. A 3.3V regulator keeps the ethernet module happy. The use of four-way DuPont female to female cables for hooking up the relay & ethernet module allows flexibility when mounting these parts in an enclosure. A red LED indicates that the unit is powered. A reset button is provided. | The main board requires DC power (7.5V .. 9V). The onboard 7805 regulator gives us the power for the micro and the relays. A 3.3V regulator keeps the ethernet module happy. The use of four-way DuPont female to female cables for hooking up the relay & ethernet module allows flexibility when mounting these parts in an enclosure. A red LED indicates that the unit is powered. A reset button is provided. | ||
- | The relay board has a couple of opto-isolated relays. Each rated at 10A for 250V. Be sure to [[http:// | + | The relay board has a couple of opto-isolated relays. Each rated at 10A for 250V. Be sure to [[http:// |
There are two versions of firmware for this unit | There are two versions of firmware for this unit | ||
Line 13: | Line 13: | ||
* xAP enabled. | * xAP enabled. | ||
- | The source code for both versions can be found in the HAH google | + | The source code for both versions can be found in the HAH Google |
- | http://livebox-hah.googlecode.com/svn/trunk/ | + | https://github.com/dbzoo/hah/ |
The only dependency is the [[http:// | The only dependency is the [[http:// | ||
- | |||
===== Web Enabled ===== | ===== Web Enabled ===== | ||
Line 49: | Line 48: | ||
**Technical explanation why this does not work** | **Technical explanation why this does not work** | ||
The problem is the receive ethernet buffer is also used for sending as we are tight on RAM. So after the 1st relay WRITES its response into the buffer and transmits the 2nd relay when it goes to look inside for the incoming xAP frame that triggered processing it'll only find the outbound message and all the xAP parse states are messed up. | The problem is the receive ethernet buffer is also used for sending as we are tight on RAM. So after the 1st relay WRITES its response into the buffer and transmits the 2nd relay when it goes to look inside for the incoming xAP frame that triggered processing it'll only find the outbound message and all the xAP parse states are messed up. | ||
- | Given this is the case there is no wildcard | + | Given this is the case there is no wildcard |
Apart from that it's fully xAPBSC compliant. | Apart from that it's fully xAPBSC compliant. |