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

[DirtDiggler2823]

start with checking if you can signin

curl -c cookie.txt -X POST -d '{"user":"reef-pi", "password":"reef-pi"}' http://IP/auth/signin

Change IP , user/password as necessary. And let us know if that works, if it works then go for calibration, else lets fix this first

Just to be clear, I'm using login information for the reef-pi UI, or the pi itself? Also, should I be using this login information with the IP of the PC, or the reef-pi UI?

 

[DirtDiggler2823]

start with checking if you can signin

curl -c cookie.txt -X POST -d '{"user":"reef-pi", "password":"reef-pi"}' http://IP/auth/signin

Change IP , user/password as necessary. And let us know if that works, if it works then go for calibration, else lets fix this first

Running into the same issues no matter what login information I use. Using 127.0.0.1 as the IP, or the reef-pi IP of 192.168.3.187 results in null. Attempting to connect to the PC's IP of 168.192.3.229 results in a failure to connect over port 80. Connection timed out.

 

[Ranjib]

Null is ok . That’s not errror, you should see some text with cookie details in the cookie.txt file

 

[DirtDiggler2823]

Null is ok . That’s not errror, you should see some text with cookie details in the cookie.txt file

Where is that file located?

 

[Ranjib]

Where is that file located?

Same place from where you are invoking the command

 

[Ranjib]

Same place from where you are invoking the command

And then you should be able to run the calibration command using same ip

 

[DirtDiggler2823]

And then you should be able to run the calibration command using same ip

I'm using putty to get to the CLI in the reef-pi (x.x.3.187) itself, so the commands im inputting are going directly to the reef-pi. The json files are located on the desktop of my PC (x.x.3.229), as well as the download folder in the reef-pi. Any commands from the reef-pi to the reef-pi result in the CLI returning with null. Any commands to the PC result in a connection failure due to timeout over port 80. I'm missing something here, and I can't figure it out. Should I be executing these commands from the desktop of the reef-pi? I did do a full OS load on it, so it does have a desktop. Should the json files be placed somewhere specific in the reef-pi or my PC? If anyone besides @Ranjib knows how to do this, please let me know. @theatrus, how did you go about calibrating your probes for testing? What am I missing?

 

[trackerit]

@theatrus


Nevermind, I was able to get it working......:oops:

which is the address? I tried with 72 and 75 and I have the same error

 

[Ranjib]

I'm using putty to get to the CLI in the reef-pi (x.x.3.187) itself, so the commands im inputting are going directly to the reef-pi. The json files are located on the desktop of my PC (x.x.3.229), as well as the download folder in the reef-pi. Any commands from the reef-pi to the reef-pi result in the CLI returning with null. Any commands to the PC result in a connection failure due to timeout over port 80. I'm missing something here, and I can't figure it out. Should I be executing these commands from the desktop of the reef-pi? I did do a full OS load on it, so it does have a desktop. Should the json files be placed somewhere specific in the reef-pi or my PC? If anyone besides @Ranjib knows how to do this, please let me know. @theatrus, how did you go about calibrating your probes for testing? What am I missing?

CLI returning null is ok and as expected . It means it’s working

 

[Ranjib]

Last night spend some time fixing couple of bad bugs. Namely the 0 and 100% pwm issue , and ato disable based on threshold . I ll cut a new 3.0 alpha release tonight if things go as expected

I like my new workspace/garage , it’s pretty sophisticated with all the testing gears I need (multi meter , oscilloscope ) and with ample additional builds :-)

 

[That Crusso Kid]

Last night spend some time fixing couple of bad bugs. Namely the 0 and 100% pwm issue , and ato disable based on threshold . I ll cut a new 3.0 alpha release tonight if things go as expected

I like my new workspace/garage , it’s pretty sophisticated with all the testing gears I need (multi meter , oscilloscope ) and with ample additional builds :)

It needs more gadgetry! And where is your little helper/director? ;)

 

[trackerit]

I could not add the ph of my picoboard, i get the following error.

 

[DirtDiggler2823]

I could not add the ph of my picoboard, i get the following error.

even if its selected, you have to choose it again, and the same when you go to set up the probe.

 

[T-MIKE]

You got this running? I am curious how you think about this feature. Its not very popular use case, I had built it to see my tank images during vacation, when Im out of home. Looking at how complex this for new users, I am thinking if its worth keeping this in 3.0. Users can setup the drive based upload as separate cron job, outside reef-pi,

No, it kept getting the cannot find executable problem.

I think if you can get streaming video working it would be pretty useful but the thing is who is going to have reef-pi in a position to live stream the tank and control everything? Right now I just have pi cam control running alongside reef-pi and it’s working fine. It is web based so it may be easier just to integrate pi cam control into reef-pi. It was easy to install too. You would just need to load http://loacalhost/min.php in reef-pi.

My Pi Zero is inside the light so I can have the camera come out and point downwards but I think most people are not doing it this way and the reef-pi box is probably hiding behind somewhere.

https://elinux.org/RPi-Cam-Web-Interface

 

[T-MIKE]

I’m usi

what user you have configured as? reef-pi runs as root,

I’m using user “pi” normally.

 

[T-MIKE]

You can usually fix this problem with a pull down resistor (for each channel). That would be some high value resistor between your signal pin and ground. That way, if the signal is left floating while reef-pi is booting or otherwise disconnected, the light would see ground as the signal and stay off. Once reef-pi starts sending a signal, it would be much stronger than the pull down resistor.

Let me look into this, thanks for the tip. The PWM pin is connected to a FET and the gate is already pulled to ground with a resistor but I’ll have to measure the status of the gate to see what’s going on.

 

[trackerit]

even if its selected, you have to choose it again, and the same when you go to set up the probe.

if exactly that is the solution, but it must be taken as a bug, I think

 

[T-MIKE]

This is my CPU and memory usage with reef-pi and Pi Cam Control running at the same time. It is recording video 24/7.

 

[Ranjib]

if exactly that is the solution, but it must be taken as a bug, I think

yes, its a bad UX /UI bug :-(

 

[Bigtrout]

Last night spend some time fixing couple of bad bugs. Namely the 0 and 100% pwm issue , and ato disable based on threshold . I ll cut a new 3.0 alpha release tonight if things go as expected

I like my new workspace/garage , it’s pretty sophisticated with all the testing gears I need (multi meter , oscilloscope ) and with ample additional builds :)

Nice workspace, so was the pca9685 100 and zero percent bug fix in the code I identified?