reef-pi :: An opensource reef tank controller based on Raspberry Pi.

[Ranjib]

dashboard update button color issue if fixed: https://github.com/reef-pi/reef-pi/pull/368

I am in process of upgrading the AIO build, once done, i;ll run some more tests with it, and then cut a release (next week, probably on thursday)

Ranjib I don't understand its still not being able to perform timer based actions

None of the timer is working as expected or only one /two?
Lets start simple. Can you explain one use case. Like the reef light one. Following is an example where I am setting a timer name reef light, this timer kicks in every day (*) of the month, at 6 am, 1st minute, 5th second (6:01:05), the action will be against the equipment "Bozeman-A80", and we are also asking reef-pi to revert the action (checkbox), after 28800 seconds (which is 8 hours). reef-pi will trigger on action at the 6 am, and off action at 4 pm.

You are using individual timers to turn on and off. Make sure to not use the revert feature (uncheck).
The hour value is in 24 hours format. So 1 indicates 1 am at night (turn off light),

 

[Greg456]

Any luck on doser scheduling for the raspberry pi zero?

 

[Ranjib]

Any luck on doser scheduling for the raspberry pi zero?

Sorry , I was busy with the aio build upgrade. I’ll look into it tonight

 

[Ranjib]

Just finished upgrading my aio build with db9 connector for adj power strip control

It turned out ok. Basic tests across outlets, light, temperature , ato all are working as expected. This is the first pi 3 based post 1.0 build . I’ll run it for few weeks and report back the results. I am particularly interested in the cpu usage and power usage.

 

[Erica-Renee]

Just finished upgrading my aio build with db9 connector for adj power strip control

It turned out ok. Basic tests across outlets, light, temperature , ato all are working as expected. This is the first pi 3 based post 1.0 build . I’ll run it for few weeks and report back the results. I am particularly interested in the cpu usage and power usage.

So on the relay bar you only have 7 switched relays? It looks like one of the pins is being used as a power or is that ground ?

 

[janos]

Thank you for your replay.To me only PH and Temp would be important part and the relays.

 

[Ranjib]

So on the relay bar you only have 7 switched relays? It looks like one of the pins is being used as a power or is that ground ?

Spot on. It was my mistake to go with uln2003 instead of 2803. I was hoping for a uln2003 will be source current type darlington transistor ic instead of sink current type, which is 2803. But i was wrong they are both sink current type (thats is why i have wire the power to GND) and works in opposite fashion. Not only I misjudged that part, uln2003 is also a 7 channel IC. ULN2803 has 8 channel.
Anyway,, 7 channels are all working fine, which is more than enough for me (my pico actually needs only 4 outlets).
Does that make sense? The positive power to GND db9 pin is as expected , due to the IC being sink type. While the 7 channel is a limitation of the IC (relay pack has 8 channel), if you use ULN2803 , like my other power controller build, you should be able to use all 8 channels.

 

[Ranjib]

Thank you for your replay.To me only PH and Temp would be important part and the relays.

Then you dont need the tentacle board. Just get ezo ph circuit, bnc breakout board, instead.

 

[Erica-Renee]

Spot on. It was my mistake to go with uln2003 instead of 2803. I was hoping for a uln2003 will be source current type darlington transistor ic instead of sink current type, which is 2803. But i was wrong they are both sink current type (thats is why i have wire the power to GND) and works in opposite fashion. Not only I misjudged that part, uln2003 is also a 7 channel IC. ULN2803 has 8 channel.
Anyway,, 7 channels are all working fine, which is more than enough for me (my pico actually needs only 4 outlets).
Does that make sense? The positive power to GND db9 pin is as expected , due to the IC being sink type. While the 7 channel is a limitation of the IC (relay pack has 8 channel), if you use ULN2803 , like my other power controller build, you should be able to use all 8 channels.

yes i am using uln2803 the pin 9 is common ground... The relay is powered by its own power supply with ground shared on that pin 9 back to the uln 2803 and also shared with pi... But i agree for a pico or small tank you prob have more then enough relay channels.. I need at least 8 over sump area and another 7 over the tank in living room.

 

[binay]

Ranjib none of the timer based relays working . They can be manually switched on/off and the relays connected to sensors work just fine. I have done exactly the way you said.

 

[Erica-Renee]

Ranjib none of the timer based relays working . They can be manually switched on/off and the relays connected to sensors work just fine. I have done exactly the way you said.

I will test this right now on my build this will let you know if its a build issue or bug......

 

[Erica-Renee]

I will test this right now on my build this will let you know if its a build issue or bug......

Ok I set a new timer to come on second 3 of every minute for 3 seconds..
Meaning counting seconds.. 1,2,3 (Light on) 4,5,6, (LIGHT OFF) , 7,8,9,10- 59 still off.. new minute 1,2,3 (light on) I also have a few other timers more complicated and they work well.

Remember the no red update or delete bug is present in timers as well as configuration (just noticed this..) if you delete a timer it will not show it gone but refresh browser and it will be gone ..
screen shot

 

[Erica-Renee]

ohh and no looking at my cluttered desktop....... This computer is for work , play and REEF-PI NOW...

 

[Greg456]

no rush, just checking in. still got a way to go on my build.

 

[Ranjib]

no rush, just checking in. still got a way to go on my build.

Whoa . That’s a sweet build , you made my day

 

[Ranjib]

Ok I set a new timer to come on second 3 of every minute for 3 seconds..
Meaning counting seconds.. 1,2,3 (Light on) 4,5,6, (LIGHT OFF) , 7,8,9,10- 59 still off.. new minute 1,2,3 (light on) I also have a few other timers more complicated and they work well.

Remember the no red update or delete bug is present in timers as well as configuration (just noticed this..) if you delete a timer it will not show it gone but refresh browser and it will be gone ..
screen shot

Something is wrong then. For me if I delete a timer it’s gone instantly , no refresh required.

 

[Ranjib]

Ranjib none of the timer based relays working . They can be manually switched on/off and the relays connected to sensors work just fine. I have done exactly the way you said.

Can you explain in words a specific use case, and then share the screenshot of your timer configuration when you create it, same screen shot as I shared. We are going back and forth on this, but I am not able to reproduce any error on my side, neither is very clear what you are trying to do. Your timer configuration looks incorrect. So , let’s take baby steps, delete the existing timers, explain us one use case and then let’s create that.

 

[Erica-Renee]

Something is wrong then. For me if I delete a timer it’s gone instantly , no refresh required.

ok i just deleted the test i created above and it went away... Maybe it was lag between this computer (on wifi) and the pi computer on a wired network on a different switch ... (might need to look into that ) Yes I am toooooo geeky for my own good.. But remember my skills are in building things..Today i was swinging nail gun most of the day...

 

[Erica-Renee]

no rush, just checking in. still got a way to go on my build.

I am jealous... and that takes a lot for me to be

 

[Ranjib]

ok i just deleted the test i created above and it went away... Maybe it was lag between this computer (on wifi) and the pi computer on a wired network on a different switch ... (might need to look into that ) Yes I am toooooo geeky for my own good.. But remember my skills are in building things..Today i was swinging nail gun most of the day...

Thanks for validating. The delete button triggers api , and the the timer subjected to deletion goes away only when that API responds successfully, so behind the scene there are some plumbing going on which takes some time. I can see a couple of seconds delay at worts cases. I am working on the dosing schedule update button color fix. If you spot anything UI inconsistencies, do let me know. I'll squash those bugs one by one.