Problem getting thing the HAH to work
17 December, 2011 - 12:42
Hi, I recently received my semi new Livebox and HAH PCB. The kit looks good, all packed and labeled very well. The PCB however was of a new design, so it now fits a 1 wire and has the 15v relocated next to the RJ11 gain.
I have been soldering the components on the PCB, the 1 wire on board has not been updated on the wiki. So when done I even restrained my self from hooking it up and truning it on directly, instead I followed the instructios. Hooked up the HAH and measured 5.0 volt no ATMega inserted. When inserted the voltage drops to 4.90V which I guess would be ok.
So now having my HAH board seamingly ok I wanted to test it from the webpage and toggle the relay. So turning it on it takes approx 10 minutes before it becomes online. As I don't have any experience with Liveboxes or HAH I am not sure if this is normal or not. It also does not matter having the HAH board plugged in or left out.
When turning the power on the middle led lights up, than the power led starts blinking while the middle led now and than lights up. By the time the middle led is on almost continuelsy the box goes online. So when I got the box online I toggled the relays, heard clicking sound so this was looking good. At least the Livebox is talking to my HAH board. The 1Wire did show ? no reading. Since the relays were working I assumed the HAH was working ok. Next hooking up the LCD. The LCD does show booting v3.4 but then nothing happens and it remains showing this line. Trying to set the LCD using the Web interface also doesn't change this.
So it looks like parts work and some don't. I did review all the soldered connections they all look ok, the 1 wire does not have a resistor like in the wiki, this might be the reason that it does not read. I did notice there is a diode depicted behind it, not sure what this is for.
Given the fact that the relay clicks it would look like the HAH works, however the clicking sound is not allways following the web interface, at least it does not always click when toggled. The LCD getting stuck in booting rahter than showing an IP indicates that something is wrong. Currently I have checked everthing and I am not sure what the problem is. The long booting time seems odd, did see in the middle of the board it is slightly discolored and getting pretty warm. I don't know if this is common for Liveboxes. It just an observation. However it appears to be working as expected and comes up with a web interface. Than the other component in the quotation is the ATMega 328. it would appear to work gets powered and seems to trigger relays. The hooked up LCD get information from it and show booting v3.4 could it be getting stuck after this?
I hope anyone with hands on experience can let me know if my observations are normal and hopefully point me in the right direction to get it up and running normally.
17 December, 2011 - 15:18
#3
A sample timing
Hmm, I'd assumed DHCP as that's what I ship out. However, static is fine. I've just set my HAH to static and timed from a power-cycle to the first xAP traffic appearing on xFx. 26 seconds.
Connecting up my HAH PCB and power-cycling again has the LCD initially showing 'Booting V3.4' and then changing to show the Static IP address after 25secs.
Changing back to 'Automatic - DHCP' mode, I get the 'Booting V3.4' as before for 25 secs, then 'Acquiring IP' until around 40secs, then the IP address.
Does your LCD ever show the IP address? Also, do power-cycle the Livebox (rather than use 'reboot' at the telnet prompt or pressing the web UI reboot button).
One thought, I'm running Beta release 298.5 . It might be worth upping your Livebox to this. Just telnet in, and at the # prompt, enter
/etc_ro_fs/update-dev hah-beta.dbzoo.com
As for some spots on the Livebox board running a little 'hot' ... this is normal. The voltage reg that gives 5V is working hard, but is within spec.
Hang in there ... we'll WILL get you up and running.
Derek.
17 December, 2011 - 16:57
#4
Response Time
Hi Robert,
Have you tried pinging you HAH when you boot it. What I would do is make sure your network cable is inserted into the yellow socket properly, then from a command prompt type ping -t <hah ip>, so my ip is 192.168.1.8, I'd use ping -t 192.168.1.8
This starts to check the network interface on the HAH, and should get a response when the network interface comes up, it might give you a better indication of how long it take to boot.
The beta the Derek recommend is quite stable, so don't be worried about trying it.
Karl
17 December, 2011 - 17:27
#5
About Beta's
I would not be upgrading to beta whilst you are trying to also sort out your system. Please stick to a known production release until you get your system running then you can consider moving to a beta (if you so desire). I make no promise that you can migrate from one beta to the next nor from a beta to a production release without manual changes, or by having to do a full firmware "clean" install first. I can think of a few occasions where this has been true.
Brett
17 December, 2011 - 18:12
#8
Debugging
To minimize things that could be causing problems disable ALL non essential services: telnetd, iserver, serial, plugboard, ftp. There is no point in running all this stuff on startup if you are having issues its just more chaff to try to unravel.
If the network start is coming up in 20-30 seconds buts its taking longer for the processes to start up then perhaps you have some sort of strange, dns resolution issue. Check /etc/resolv.conf see what is in there as it will have remnants of when you where setup for DHCP.
Also if you are running static IP then its up to you to setup /etc/hosts FAILURE to do this will result in strangeness as the hosts local IP won't be known AND/OR may be incorrect as was left over from DHCP as well.
This all sounds like some sort of networking issue to me.
One more thing: I'm betting its jamming on the NTPCLIENT as you have not got something setup incorrect for static ip mode. This process does take AGES to timeout if you have incorrect setting in your system. You can rety blanking out the NTP host setting via the webgui and see if it comes up quicker. This will effectively disable this feature.... although you want to get your network sorted so it can be enabled later on. This makes sense becasue util the TIME is synced the IP address of the unit is not displayed. I'll make a firmware tweak to display syncing NTP in the future to makethis easier to diagnose.
Brett
17 December, 2011 - 18:21
#9
I have flashed a few boxes before
But never had anything like this. As Derek says always boot up within a minute.
Is it worth forcing a clean reintall back to the current Production version?
I think ths command is
# /etc/init.d/update clean
EDIT: Forget this..Sounds like Brett's got it nailed
17 December, 2011 - 18:40
#11
Then the issue is DNS resolution
In that case the NTP timeout is being caused by one of two things
a) an incorrect /etc/resolv.conf
b) invalid default GW
Trying doing an NSLOOKUP from the command line now of "uk.pool.ntp.org" I bet is baulks. This is what you need to fix so you can put back NTP..... btw NTP is mandatory for anything that uses SSL that is; googlecal and twitter and SSH
SSL requries that you have no more then 2min of drift between clocks so that a key negotiation can occur.
Brett
17 December, 2011 - 19:17
#12
1wire on the board
This PCB is a newer revision from the one I have which does not have a PCB mounted 1-wire sensor. Do make sure that its correctly orientated and that the pullup resistor is inserted. Also did you SETUP the 1wire sensor on the Automation>Configure TAB? You must map a ROMID for it be correctly detected and used by the system.
I can see the documentation on the wiki around this area is a little fuzzy.
Brett
18 December, 2011 - 14:13
#13
Clicking relays
Note that when testing out the relays, it's a good idea to use a multimeter. Listening for 'clicks' isn't ideal as (for some strange reason) turning the relay on usually makes little or no 'click', yet turning it off again makes a noticeable 'click'.
This might lead to confusion.
Derek
27 December, 2011 - 14:37
#15
Pullup the 1-wire data line
Hi Robert,
Do fit R7 (the 1-wire bus pullup resistor). The bus operation may well be intermittent without this pullup in place.
The URF may seem challenging, but it is very flexible. It's worth taking the time to read the wiki and understand how the codes are formed.
Cheers,
Derek.
>So turning it on it takes approx 10 minutes before it becomes online. As I don't have any experience with Liveboxes or HAH I am not sure if this is normal or not. It also does not matter having the HAH board plugged in or left out.
The Livebox should bootup in around 40secs or so. As it boots, it goes looking on your network for a DHCP server (normally just your internet wifi router) and gets assigned an address. This, and the fact that the LCD doesn't show the IP address makes me wonder if there is perhaps an issue with DHCP.
So, I'd recommend that you unplug the PCB for now and work to get the HAH on your LAN and booting up in under a minute. If you install xFx viewer on a PC that is on the same subnet as your Livebox, you will be able to see the xAP traffic from the HAH.
Give this a try & let us know how it goes.
Derek.