|
|
|
|
|
#1
04-27-2014, 09:50 PM
|
|||||
|
|||||
One of the fail safe's I thought I saw, predetermined when a socket could be available. So say I wanted to start dosing at 8 am for 3 min. I could lock out the socket from doing anything if it wasn't, say 7:59 - 8:05. If that first condition was met (the clock read anywhere from 7:59 to 8:05), then it could move onto the actual program. If something went wrong with the program, the worst case scenario is I'd dose for 6 min (7:59-805 when that first condition shut the socket down) instead of an hour or more or, eek until the bottle was empty - thus killing the tank.
Maybe what I was looking at was overly complicated or I totally didn't understand it, lol. 
|
|
#2
04-27-2014, 10:11 PM
|
||||
|
||||
|
Not sure as to why you would need a Time statement to limit the time it could be run, as your OSC statement is just a much more advanced version of TIME.
Starting at Midnight SET OFF for 480 minutes, The turn on for 3 minutes, then back off 237 minutes REPEAT... So it repeats waiting for 480 minutes in off, then turns on for 3 minutes then OFF again for 237 minutes and Resets the OSC command at Midnight to run the pattern again. Even with that said off the top of my head I don't think you could have the redundancy that you are talking about using both the TIME and the OSC function together, but I could be completely wrong about that! =)
|
|
#3
04-27-2014, 10:24 PM
|
|||||
|
|||||
|
Cool, I didn't see the need for it either, but I did see it on other people's program's and I was wondering if it was necessary. I'm totally new to Apex so wanted to make sure I wasn't missing anything I shouldn't.
Next... my heaters...
|
|
#4
04-27-2014, 10:37 PM
|
||||
|
||||
|
Fallback OFF
Set OFF If 180Tmp < RT+0.5 Then ON If 180Tmp > RT+1.0 Then OFF Defer 000:05 Then ON Defer 000:05 Then OFF If FeedA 000 Then OFF Thats what I use for my heaters, using the seasonal tables, this is set for freshwater tank, not salt but I'm sure the temperature might be around the same anyways. The defer statements make the program wait instead of instantly turning the heaters on/off to verify that the temperature actually requires something to be done instead of possibly turning on/off/on/off a bunch of times in a row if temperature is real close to the set points. If the temperature is 1 degree F over the Seasonable table, turn OFF If the temperature is 0.5 degree F over the Seasonable table, turn ON Yes I only let my tank change in the range of .5 degrees before turning on/off In my 37g tank this turns the heater on for 20 minutes every 3-4 hours
|
|
#5
04-28-2014, 03:09 AM
|
|||||
|
|||||
|
Just linked in with Apex Fusion. One of the reasons I hadn't done much with the unit was I was a bit daunted by network setup and email notifications. WOW, am I glad fusion came out. Easy peasy!
|
|
#6
04-28-2014, 03:52 AM
|
||||
|
||||
|
Yes fusion is nice, but honestly it lacks the control that you have within the apex itself. I was all excited when the open beta opened up, took me 10 days to get in, and logged in, looked and besides the graphs I much prefer the actual control panel through the apex
|
|
#7
04-28-2014, 04:11 AM
|
|||||
|
|||||
|
I've been watching the BRS video series on the Apex and I can see how for a newbie like me it's much easier to get started. But I can also see how I will be modifying the code in advanced mode once I'm more comfortable with the programming language and the effects of certain commands like the OSC feature.
|
Hybrid Mode
