Clarisea Mod For Apex Control With Optical Sensor

stacksoner

Well-Known Member
View Badges
Joined
Jul 29, 2018
Messages
810
Reaction score
1,165
Rating - 0%
0   0   0
So I got tired of the Clarisea controller beeping and being annoying so I decided to cut it off and directly wire it into the power adapter it came with. Lo and behold, the roller turns on when plugged in which makes it a great fit for the Apex!

My current program turns on the fleece roller for 4 seconds every 25 minutes:

Fallback OFF
OSC 000:00/000:04/025:00 Then ON


I was interested in adding in an optical sensor here to turn on for 4 seconds if the sensor is closed and wait 15 mins between times that its allowed to turn on again. Does this code look kosher to ya'll?

Fallback OFF
Set OFF
OSC 000:00/000:04/025:00 Then ON
If OS1 CLOSED Then ON
If OS1 OPEN Then OFF
Defer 000:04 Then OFF
Min Time 015:00 Then OFF
 

SuncrestReef

That Apex guy
View Badges
Joined
Jan 18, 2018
Messages
4,214
Reaction score
9,251
Location
Oregon
Rating - 0%
0   0   0
There are two problems with your code:

1. If the OS1 sensor is closed and that turns on the Clarisea, there's no guarantee it will only run for 4 seconds. The motor will run for however long it takes until OS1 is open, then it will run for the additional 4 seconds from the Defer timer.

2. When the OSC tries to turn it on for 4 seconds every 25 minutes, if the OS1 sensor is open, that will override the OSC command, so it won't run at all.

To achieve what you're proposing, it's going to require a couple of virtual outputs. One will monitor the OS1 status, and the other will act as a 4 second timer:

[OS1_Control] -- virtual output
Set OFF
If OS1 CLOSED Then ON
If Output OS1_Limit = ON Then OFF
Min Time 015:00 Then OFF

[OS1_Limit] -- virtual output
Set OFF
If OS1 CLOSED Then ON
Defer 000:04 Then ON

[Clarisea]
Fallback OFF
OSC 000:00/000:04/025:00 Then ON
If Output OS1_Control = ON Then ON
Min Time 015:00 Then OFF

With this code, OSC will continue to turn on for 4 seconds every 25 minutes. At any time during that cycle, if OS1 is closed, it will turn on for 4 seconds, but at most every 15 minutes.

If you're not familiar with virtual outputs, see my tutorial here:
 
OP
OP
stacksoner

stacksoner

Well-Known Member
View Badges
Joined
Jul 29, 2018
Messages
810
Reaction score
1,165
Rating - 0%
0   0   0
There are two problems with your code:

1. If the OS1 sensor is closed and that turns on the Clarisea, there's no guarantee it will only run for 4 seconds. The motor will run for however long it takes until OS1 is open, then it will run for the additional 4 seconds from the Defer timer.

2. When the OSC tries to turn it on for 4 seconds every 25 minutes, if the OS1 sensor is open, that will override the OSC command, so it won't run at all.

To achieve what you're proposing, it's going to require a couple of virtual outputs. One will monitor the OS1 status, and the other will act as a 4 second timer:

[OS1_Control] -- virtual output
Set OFF
If OS1 CLOSED Then ON
If Output OS1_Limit = ON Then OFF
Min Time 015:00 Then OFF

[OS1_Limit] -- virtual output
Set OFF
If OS1 CLOSED Then ON
Defer 000:04 Then ON

[Clarisea]
Fallback OFF
OSC 000:00/000:04/025:00 Then ON
If Output OS1_Control = ON Then ON
Min Time 015:00 Then OFF

With this code, OSC will continue to turn on for 4 seconds every 25 minutes. At any time during that cycle, if OS1 is closed, it will turn on for 4 seconds, but at most every 15 minutes.

If you're not familiar with virtual outputs, see my tutorial here:
Thank you so much for the thoughtful and well articulated reply. I really appreciate your input here!!
 

infinite0180

Valuable Member
View Badges
Joined
Apr 25, 2018
Messages
1,821
Reaction score
1,100
Rating - 100%
1   0   0
I want to do this exact same thing with my klir filter. I think it will be way more efficient this way. It prevents the fleece from getting too heavy and stretching!
 

infinite0180

Valuable Member
View Badges
Joined
Apr 25, 2018
Messages
1,821
Reaction score
1,100
Rating - 100%
1   0   0
There are two problems with your code:

1. If the OS1 sensor is closed and that turns on the Clarisea, there's no guarantee it will only run for 4 seconds. The motor will run for however long it takes until OS1 is open, then it will run for the additional 4 seconds from the Defer timer.

2. When the OSC tries to turn it on for 4 seconds every 25 minutes, if the OS1 sensor is open, that will override the OSC command, so it won't run at all.

To achieve what you're proposing, it's going to require a couple of virtual outputs. One will monitor the OS1 status, and the other will act as a 4 second timer:

[OS1_Control] -- virtual output
Set OFF
If OS1 CLOSED Then ON
If Output OS1_Limit = ON Then OFF
Min Time 015:00 Then OFF

[OS1_Limit] -- virtual output
Set OFF
If OS1 CLOSED Then ON
Defer 000:04 Then ON

[Clarisea]
Fallback OFF
OSC 000:00/000:04/025:00 Then ON
If Output OS1_Control = ON Then ON
Min Time 015:00 Then OFF

With this code, OSC will continue to turn on for 4 seconds every 25 minutes. At any time during that cycle, if OS1 is closed, it will turn on for 4 seconds, but at most every 15 minutes.

If you're not familiar with virtual outputs, see my tutorial here:
Hey Suncrest,

whats the osc code to turn mine on for 5 sec every hour and have it be the same time everyday?

here is what i came up with. Hows this look? I want to be able to predict when it spins.
E24166EB-12F7-450E-99BD-B45A0D21027E.png
 
Last edited:

SuncrestReef

That Apex guy
View Badges
Joined
Jan 18, 2018
Messages
4,214
Reaction score
9,251
Location
Oregon
Rating - 0%
0   0   0
Hey Suncrest,

whats the osc code to turn mine on for 5 sec every hour and have it be the same time everyday?

here is what i came up with. Hows this look? I want to be able to predict when it spins.
E24166EB-12F7-450E-99BD-B45A0D21027E.png
Your OSC code will turn it on for 5 seconds at the top of the hour, 24 hours per day:

00:00 - 00:05
01:00 - 01:05
02:00 - 02:05, etc.
 

infinite0180

Valuable Member
View Badges
Joined
Apr 25, 2018
Messages
1,821
Reaction score
1,100
Rating - 100%
1   0   0
Your OSC code will turn it on for 5 seconds at the top of the hour, 24 hours per day:

00:00 - 00:05
01:00 - 01:05
02:00 - 02:05, etc.
Fantastic. Quick question for you. Based on previous observation, running the Klir default controller, the filter spun way less from midnight till my lights came on. Fish are sleeping and not much is being stirred up into the water. Is there a way to utilize two different OSC commands for different times of day. Say once every two hours when lights are off and once every hour when on, or something to that effect...
 

SuncrestReef

That Apex guy
View Badges
Joined
Jan 18, 2018
Messages
4,214
Reaction score
9,251
Location
Oregon
Rating - 0%
0   0   0
Fantastic. Quick question for you. Based on previous observation, running the Klir default controller, the filter spun way less from midnight till my lights came on. Fish are sleeping and not much is being stirred up into the water. Is there a way to utilize two different OSC commands for different times of day. Say once every two hours when lights are off and once every hour when on, or something to that effect...
You'd need to use virtual outputs for each OSC and disable the OSC using If Time commands, then on the physical output have it turn on and off based on the virtual outputs:

[Day_OSC]
OSC 000:00/000:05/059:55 Then ON (every hour)
If Time 18:01 to 07:00 Then OFF

[Night_OSC]
OSC 000:00/000:05/119:55 Then ON (every two hours)
If Time 07:01 to 18:00 Then OFF

[Klir]
Fallback OFF
Set OFF
If Output Day_OSC = ON Then ON
If Output Night_OSC = ON Then ON

If Output ReturnPump = OFF Then OFF

Just adjust the times on the Day_OSC and Night_OSC to match your lighting schedule.
 

infinite0180

Valuable Member
View Badges
Joined
Apr 25, 2018
Messages
1,821
Reaction score
1,100
Rating - 100%
1   0   0
You'd need to use virtual outputs for each OSC and disable the OSC using If Time commands, then on the physical output have it turn on and off based on the virtual outputs:

[Day_OSC]
OSC 000:00/000:05/059:55 Then ON (every hour)
If Time 18:01 to 07:00 Then OFF

[Night_OSC]
OSC 000:00/000:05/119:55 Then ON (every two hours)
If Time 07:01 to 18:00 Then OFF

[Klir]
Fallback OFF
Set OFF
If Output Day_OSC = ON Then ON
If Output Night_OSC = ON Then ON

If Output ReturnPump = OFF Then OFF

Just adjust the times on the Day_OSC and Night_OSC to match your lighting schedule.
Awesome! Thank you soo much!
 

infinite0180

Valuable Member
View Badges
Joined
Apr 25, 2018
Messages
1,821
Reaction score
1,100
Rating - 100%
1   0   0
You'd need to use virtual outputs for each OSC and disable the OSC using If Time commands, then on the physical output have it turn on and off based on the virtual outputs:

[Day_OSC]
OSC 000:00/000:05/059:55 Then ON (every hour)
If Time 18:01 to 07:00 Then OFF

[Night_OSC]
OSC 000:00/000:05/119:55 Then ON (every two hours)
If Time 07:01 to 18:00 Then OFF

[Klir]
Fallback OFF
Set OFF
If Output Day_OSC = ON Then ON
If Output Night_OSC = ON Then ON

If Output ReturnPump = OFF Then OFF

Just adjust the times on the Day_OSC and Night_OSC to match your lighting schedule.
One more, i promise!
Best way to use a feed button to turn it for 5 sec...
 

infinite0180

Valuable Member
View Badges
Joined
Apr 25, 2018
Messages
1,821
Reaction score
1,100
Rating - 100%
1   0   0
There are two problems with your code:

1. If the OS1 sensor is closed and that turns on the Clarisea, there's no guarantee it will only run for 4 seconds. The motor will run for however long it takes until OS1 is open, then it will run for the additional 4 seconds from the Defer timer.

2. When the OSC tries to turn it on for 4 seconds every 25 minutes, if the OS1 sensor is open, that will override the OSC command, so it won't run at all.

To achieve what you're proposing, it's going to require a couple of virtual outputs. One will monitor the OS1 status, and the other will act as a 4 second timer:

[OS1_Control] -- virtual output
Set OFF
If OS1 CLOSED Then ON
If Output OS1_Limit = ON Then OFF
Min Time 015:00 Then OFF

[OS1_Limit] -- virtual output
Set OFF
If OS1 CLOSED Then ON
Defer 000:04 Then ON

[Clarisea]
Fallback OFF
OSC 000:00/000:04/025:00 Then ON
If Output OS1_Control = ON Then ON
Min Time 015:00 Then OFF

With this code, OSC will continue to turn on for 4 seconds every 25 minutes. At any time during that cycle, if OS1 is closed, it will turn on for 4 seconds, but at most every 15 minutes.

If you're not familiar with virtual outputs, see my tutorial here:
Suncrest,

i just installed a float switch and implemented this coding as well. My only issue is that everytime the float is tripped it does not keep the outlet on. Instead, as soon as the float trips the water level begins to fall and instead of it running the 4 sec i want it to it shuts right off. If i lift the float and keep it suspended then it works correctly, but in real world scenario, atleast in my sump, it short cycles the motor and only spins for a sec. i really want to keep that motor turning for 4 sec everytime the float lifts, is that possible?
 

SuncrestReef

That Apex guy
View Badges
Joined
Jan 18, 2018
Messages
4,214
Reaction score
9,251
Location
Oregon
Rating - 0%
0   0   0
Suncrest,

i just installed a float switch and implemented this coding as well. My only issue is that everytime the float is tripped it does not keep the outlet on. Instead, as soon as the float trips the water level begins to fall and instead of it running the 4 sec i want it to it shuts right off. If i lift the float and keep it suspended then it works correctly, but in real world scenario, atleast in my sump, it short cycles the motor and only spins for a sec. i really want to keep that motor turning for 4 sec everytime the float lifts, is that possible?
Please post the programming for the Clarisea and any additional virtual outputs you are using. Be sure to include the output names before each list of program code.
 

infinite0180

Valuable Member
View Badges
Joined
Apr 25, 2018
Messages
1,821
Reaction score
1,100
Rating - 100%
1   0   0
Please post the programming for the Clarisea and any additional virtual outputs you are using. Be sure to include the output names before each list of program code.
Sorry, here you go:

[KlirControl] -- VO
Set OFF
If S_KLIR CLOSED Then ON
If Output KlirLimit = ON Then OFF
Min Time 001:00 Then OFF

[KlirLimit] -- VO
Set OFF
If S_KLIR CLOSED Then ON
Defer 000:04 Then ON

[Klir]
Fallback OFF
OSC 000:00/000:04/239:56 Then ON
If Output KlirControl = ON Then ON
Min Time 001:00 Then OFF
If Output ReturnPump = OFF Then OFF
 

SuncrestReef

That Apex guy
View Badges
Joined
Jan 18, 2018
Messages
4,214
Reaction score
9,251
Location
Oregon
Rating - 0%
0   0   0
@SuncrestReef do i just need another min time statement somewhere in there?
The original code I wrote for this was meant to prevent the Clarisea from running longer than 4 seconds at a time, but never accounted for the sensor closing before 4 seconds had elapsed and turning it off prematurely. To do that, modify the code to add another 4 second Min Time delay:

[KlirControl] -- VO
Set OFF
If S_KLIR CLOSED Then ON
If Output KlirLimit = ON Then OFF
Min Time 001:00 Then OFF

[KlirLimit] -- VO
Set OFF
If S_KLIR CLOSED Then ON
Defer 000:04 Then ON

[Klir]
Fallback OFF
OSC 000:00/000:04/239:56 Then ON
If Output KlirControl = ON Then ON
Min Time 000:04 Then ON
Min Time 001:00 Then OFF
If Output ReturnPump = OFF Then OFF
 

infinite0180

Valuable Member
View Badges
Joined
Apr 25, 2018
Messages
1,821
Reaction score
1,100
Rating - 100%
1   0   0
The original code I wrote for this was meant to prevent the Clarisea from running longer than 4 seconds at a time, but never accounted for the sensor closing before 4 seconds had elapsed and turning it off prematurely. To do that, modify the code to add another 4 second Min Time delay:

[KlirControl] -- VO
Set OFF
If S_KLIR CLOSED Then ON
If Output KlirLimit = ON Then OFF
Min Time 001:00 Then OFF

[KlirLimit] -- VO
Set OFF
If S_KLIR CLOSED Then ON
Defer 000:04 Then ON

[Klir]
Fallback OFF
OSC 000:00/000:04/239:56 Then ON
If Output KlirControl = ON Then ON
Min Time 000:04 Then ON
Min Time 001:00 Then OFF
If Output ReturnPump = OFF Then OFF
Fantastic! Thank you soo much.
 

Sandersonville

Community Member
View Badges
Joined
Jul 30, 2020
Messages
37
Reaction score
40
Location
California
Rating - 0%
0   0   0
Would love to see manufactures like Clarisea work with Neptune to offer supported out of the box integrations like this!
 

infinite0180

Valuable Member
View Badges
Joined
Apr 25, 2018
Messages
1,821
Reaction score
1,100
Rating - 100%
1   0   0
The original code I wrote for this was meant to prevent the Clarisea from running longer than 4 seconds at a time, but never accounted for the sensor closing before 4 seconds had elapsed and turning it off prematurely. To do that, modify the code to add another 4 second Min Time delay:

[KlirControl] -- VO
Set OFF
If S_KLIR CLOSED Then ON
If Output KlirLimit = ON Then OFF
Min Time 001:00 Then OFF

[KlirLimit] -- VO
Set OFF
If S_KLIR CLOSED Then ON
Defer 000:04 Then ON

[Klir]
Fallback OFF
OSC 000:00/000:04/239:56 Then ON
If Output KlirControl = ON Then ON
Min Time 000:04 Then ON
Min Time 001:00 Then OFF
If Output ReturnPump = OFF Then OFF
@SuncrestReef

is the min time off statement necessary in both
Klir and Klircontrol? I recently changed the timing on both of those statements to 15 minutes. Today i had a strange situation where the osc function spun the motor but for some reason within 15 min the float tripped and the klirlimit switched on and stayed on but because the float remained up it never shut off and therefor did not roll again. I think it might have had something to do with the defer timing so i increased that. Im also going to change the min time to 5 minutes but want to clean it up if i dont need it in both...
 
Back
Top