Apex programming for pmup

[Wantsomemora Acrapora]

Hey all, happy reefing. I have a pmup to keep my dKH line rinsed. My current programming is: Fallback OFF
OSC 000:00/001:00/180:00 Then ON.
This programming does not work but I was wondering, is there programming that would kick the pmup on after every dose for like 5 seconds. Dosing is done through a Neptune Dose. Thank you all in advance.

 

[BrokenReefer]

You would likely need to create a virtual outlet that tracks the state change on the DOS pump.

VO_DOS_Delay (name this whatever)

Fallback OFF
Set OFF
If Output [DOS_Head_Name] = ON Then ON
Defer 000:01 Then ON

VO_DOS_Start (again name this whatever)

Fallback OFF
Set OFF
If Output [DOS_Head_Name] = ON Then ON
If Output VO_DOS_Delay = ON Then OFF

PMUP_Prog

Fallback OFF
Set OFF
If Output VO_DOS_Start = ON Then ON
Min Time 000:05 Then ON

I would wire this up and then run a test to make sure the state changes happen as expected. I’ve had virtual outlets work and then stop. So I always caution and run the automation with lines disconnected to make sure things fire as intended.

 

[Sisterlimonpot]

This is a tough one. I, for one, don't see a path to have an outlet follow the dos internal programming.

It would be possible if you knew when it turned on and off. But the TDATA schedule isn't something we can predict.

It seems the osc code is about as good as you can get it. Do you know how often your dos dispenses? You can get a rough estimate of that and tailor your osc to get close.

Im curious to see if anyone has a clever solution.

You would likely need to create a virtual outlet that tracks the state change on the DOS pump.

Does the [dos head] outlet toggle ON / OFF in accordance with dos operations when set to AUTO.

If so, this should work.

 

[BrokenReefer]

This is a tough one. I, for one, don't see a path to have an outlet follow the dos internal programming.

It would be possible if you knew when it turned on and off. But the TDATA schedule isn't something we can predict.

It seems the osc code is about as good as you can get it. Do you know how often your dos dispenses? You can get a rough estimate of that and tailor your osc to get close.

Im curious to see if anyone has a clever solution.




Does the [dos head] outlet toggle ON / OFF in accordance with dos operations when set to AUTO.

If so, this should work.

I fully agree with you - that's why the suggestion to use the STATE change was made, it *should* work but as always try with dry lines first.

 

[Wantsomemora Acrapora]

You would likely need to create a virtual outlet that tracks the state change on the DOS pump.

VO_DOS_Delay (name this whatever)

Fallback OFF
Set OFF
If Output [DOS_Head_Name] = ON Then ON
Defer 000:01 Then ON

VO_DOS_Start (again name this whatever)

Fallback OFF
Set OFF
If Output [DOS_Head_Name] = ON Then ON
If Output VO_DOS_Delay = ON Then OFF

PMUP_Prog

Fallback OFF
Set OFF
If Output VO_DOS_Start = ON Then ON
Min Time 000:05 Then ON

I would wire this up and then run a test to make sure the state changes happen as expected. I’ve had virtual outlets work and then stop. So I always caution and run the automation with lines disconnected to make sure things fire as intended.

Ok, this might fry my brain but I’ll give it a shot when I can monitor things for a time. Thank you for putting effort into this solution

 

[Sisterlimonpot]

I fully agree with you - that's why the suggestion to use the STATE change was made, it *should* work but as always try with dry lines first.

I took my dos' off line and have very little experience with their nuances.

I was under the impression that the outlet didn't relay "on/off" status. But then again why wouldn't they? And if so, then you can definitely take advantage of that with a defer ON statement.