RESOLVED e682 Issue - Boots Up In Test Mode - Can't Access It

[derektoews]

I've emailed Jim, but I know it's a busy season right now so not sure how long it would take for him to get back to me on this one...

I received the controller from Jim a few months ago, already with Version 5 firmware on it, and changed the IP, configured it, all that stuff. Everything was great. I just went to set it up outside today, hooked it up, and as soon as I powered it on, I noticed the green light was flashing really fast, like it was in a test mode. It's controlling a megatree, and only 4 strips seemed to be "obeying" if you will, that test mode, which means my config must have been erased as well. No big deal. However, I go to type in the IP to Chrome and it won't pull it up. But if I search in the Terminal for all IP's on my network, the IP shows up... it just won't pull up on a browser.

I tried a different power supply (and metered it), checked fuses,  I tried a different switch, direct connection to the computer, different ethernet cables (even made 2 brand new ones)... but it's something with the controller in that it's booting up in a test mode. I know I can hold program down and force a temp IP address... I've done that a few times, but that still won't allow me to gain access to the controller through the web browser... is there any kind of hard reset? Any ideas? I've done about everything I know to do.

[derektoews]

This has been resolved... here's what we (with Jim's help) did to fix it in case someone else has this issue.

I directly hooked the e682 up to my PC, (NO ROUTER, NO SWITCHES) disabled the Wireless, set the LAN to DHCP (well, it already). I rebooted the computer so it got the 169.xxx.xxx.xxx address. Then tried Override 4 on the controller but still nothing when I went to 169.254.74.73 on a web browser. So I did Override 1 then Override 4. Then I tried to find it on the web browser but again, still nothing. So I randomly tried Override 1, then 6, then 4, and it worked. why? I have no idea. But it did, and it’s acting completely normal. I then changed the IP, changed all the config settings, and hooked it back into my normal network switch and it's running great, just like the others.

Typically you should only have to do override 4 in this situation. Not really sure why this controller was acting like this but hey, it's working now...