Random Restart

[pyton]

I have the beta installed and I do not know if this is a beta issue or controller issue.

I upgraded to the beta when the post was put out by Curt. Everything has been running smooth until the other day. It seemed that every time I was looking at my tank the same Tunze was always running. I thought nothing of it and let it go for a couple more days. Sure enough it was like it was not switching.

So I issued a restart through the network set up through the web.
(Config - Network Setup - tick Reboot system after update)

Everything came back online but the Tunze was reversed. The Left in the programming (MainStreamL) controlled the right one and vice versa

Tried another restart from the head unit this time and same thing.

Changed the cable seemed like the easiest thing to do. That was two days ago.

Last night about 2am the controller restarted on it's own. I thought maybe it was a small spike. About 10 hours later I got an email saying my pH was < 6.00 and I checked the controller. It had rebooted again on it's own.

6pm Reboot

now it was been rebooting every 3 to 5 minutes for the last hour.

Any ideas? This controller is less than a month old.

 

[pyton]

Saw the post in the beta post to load the file from the 4.04 version and restart.
No such luck at all

Loaded the firmware 4.04_2B11 and load old file with the Tunze profiles
Adjusted the timer back to switch every hour and everything is back to normal.


Upgraded the the 4.05 beta restarted and the restarting started again.

Switching back to 4.04_2B11 and leaving it there.

I just hope someone can figure this one out.

 

[Deleted member 143833]

There is a chance that, depending on your network configuration the AquaServer being enabled is causing reboots, also check your email settings and disable email if you are not using it. Both settings are in network section from the display menu.

If this doesn't fix it (or even if it does) you should email Neptune about the issue; during reboots that can be a file saved to the Apex that will indicate cause and help them diagnose the issue and fix the bug. support@neptunesys.com in case you don't have the email near.

 

[pyton]

Great I will email them and get that set up.

I do use email features and network access outside my home using a Cisco 501 Pix.

Question I have now is in Outlet set up do I have to say

for LED lights:

Fallback OFF
Set OFF
If Power Apex Off 005 Then OFF
If Time 07:00 Then MorningB
If Time 11:50 Then DayB
If Time 18:30 Then EveningB
If Temp > 80.0 Then OFF


OR


Fallback OFF
Set OFF
If Power Apex Off 005 Then OFF
If Time 07:00 to 11:50 Then MorningB
If Time 11:50 to 18:30 Then DayB
If Time 18:30 to 23:00 Then EveningB
If Temp > 80.0 Then OFF

I do not have the LED fixture but I would like to set it up for it so I am ready to go.

Thank you for your help kenargo

 

[aquamanic]

This is what I would do:

Fallback ON
Set OFF
If Time 07:00 to 11:50 Then MorningB
If Time 11:50 to 18:30 Then DayB
If Time 18:30 to 23:00 Then EveningB
If Temp > 80.0 Then OFF
If Power Apex Off 005 Then OFF

 

[pyton]

Thank you

 

[pyton]

Update

Update

What a wonderful weekend.


Went back to the beta to help troubleshoot for Neptune System.
Installed a new EB4 for my lights.

Now every time my lights go off and the current through the EB4 is 0 so is my ORP readings. As soon as I turn on my MH the ORP readings go back to normal.


Anyone got a clue on this one?

Thanks

 

[aquamanic]

There's something strange happening with the 4.05 firmware between the energy bars and probes. Someone else was having a similar problem with their pH probe and their EB8. I'd email Curt and make sure he's aware but post back and let us know what's happening and any resolution.

 

[pyton]

Emailed curt everything and went back to 4.04 because the restarts came back again!

Turned the lights off and went to bed last night, ORP read 383 shut the Ozone off just in case
Woke up lights still off and it read 0

As soon as the lights turned on it jumped to 335

 

[pyton]

According to Curt at Neptune systems the EB4 has nothing to do with the ORP problem

He says I have a short in my base unit or my ORP probe.

Today I did some testing and found out this
When my EB4 USB cable is plugged in and the ORP is reading anything at all it reads 30 to 50 lower.

Example:
With cable plugged in
Reading: 335

With the cable unplugged
Reading: 383

Plug cable back in
Reading: 338

Seriously you can just unplug the USB cable walk back to the desk and wait for first refresh...
Is there an order that the EB's have to be plugged in via USB?

Curt asked me to open up my firewall so he could telnet in and run some tests when the ORP is 0. Since this only happens at night I dont think this will ever get resolved. Every time I call or email after 4pm PST no answer and no return email until the next day.

Sorry I am just venting right now because this is brand new within the last month or so and they don't seem to care something is wrong. I know it is not likely but what if this is the beginning of something big that causes my tank to run dry, get too cold overnight, or flood my floors? We never know unless someone take the time to care about their product and what it does to our tank!

 

[swearint]

If you can repeatedly demonstrate it as you indicate, then Curt should be able to figure it out. Keep working with him, he may just be tied up with other things. I have had him respond to emails well after business hours. He even called me and used telnet to confirm an issue I was having.

Todd

 

[aquamanic]

You're making a mistake in thinking this won't get resolved and publically venting on Curt for something he hasn't even NOT done yet. I know that Curt has worked with people at 9pm on a Sunday night. You've got a weird problem but he's the guy that can figure it out.

 

[pyton]

You're making a mistake in thinking this won't get resolved and publically venting on Curt for something he hasn't even NOT done yet. I know that Curt has worked with people at 9pm on a Sunday night. You've got a weird problem but he's the guy that can figure it out.

I am not venting directly at Curt, I have no issues with him personally. I am venting this controller is acting up so early from when I bought it and it seems no one cares.

I went back to all my emails over the last 3+ years to see if ANYONE from neptune systems has EVER emailed me after 4PM PST and the answer is NEVER.

Even when my basement was flooding repeatedly from the code they gave me for my Standard Aqua Controller. In short I was told it had to be something I had done because his equipment would never just fail like that. I swore then I was never going to buy another controller from them but decided to give them one more chance with this Apex. So far I am not impressed.