I have been looking at the instructions on Adafruit and for each part of the project, you need a raspberry pi hat. Are you able to fit multiple hats onto the raspberry pi or do you need a new raspberry pi every time you build a part of it?
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I put all of my wiring on a single hat. Its a bit cluttered but I did every module except lighting. Alternatives are pre-built hats that members here offer (e.x. leviathan)I have been looking at the instructions on Adafruit and for each part of the project, you need a raspberry pi hat. Are you able to fit multiple hats onto the raspberry pi or do you need a new raspberry pi every time you build a part of it?
I don't like stuff being cluttered, so I was wondering if multiple reef pi hats can be stacked on top of each other.I put all of my wiring on a single hat. Its a bit cluttered but I did every module except lighting. Alternatives are pre-built hats that members here offer (e.x. leviathan)
Yup as long as you check your wiring you can do it that way.I don't like stuff being cluttered, so I was wondering if multiple reef pi hats can be stacked on top of each other.
I also do not want to use pre-built hats because I want the DIY experience.
As you have noticed, reef-pi does not have straight forward way to configure stepper, in ways that you can control the precise pwm life cycle. The % value stands for duty_cycle. 100% means the entire duty_cycle,Is there any good documentation for the "Reef Pi PWM Frequency" setting, and the Dosing "Speed" setting? Things aren't working as I'd expect - and I'm trying to figure out what I don't understand.
Basically, I've got the PWM frequency set to 100, and I've got a stepper motor with 1.8 degrees step angle/200 steps (A4988 driver) . I've got the driver set to full steps.
My expectation was that at 100hz, and 200 steps needed, a revolution would take 2 seconds. Its running way faster than that (several revolutions per second). I'm also not 100% sure what the speed setting is doing - it won't run at 100%, but will run at anything else and as far as I can tell speed isn't varying visibly.
Alrighty - so it makes sense that the speed setting didn't make a difference - the stepper control works on the rising cycle and that's not changing.As you have noticed, reef-pi does not have straight forward way to configure stepper, in ways that you can control the precise pwm life cycle. The % value stands for duty_cycle. 100% means the entire duty_cycle,
get an appropriate meanwell driver and connect pi pwm to that, and let meanwell supply the current to led,Is it possible to use reefpi to PWM control a 20 VDC lighting system? If so do you recommend circuitry that includes an optical isolator to prevent the 20 from hitting the pi?
hzAlrighty - so it makes sense that the speed setting didn't make a difference - the stepper control works on the rising cycle and that's not changing.
Is the raspberry pi pwm frequency in the main configuration page actually hz? Or is it something else ?
Thanks for the help - figured out my issue. The Dosing pumps are running of the pca9685 - not the pi itself - so I adjusted the frequency in the driver for that - and now they're running at a speed that makes more sense.
Nothing to do... I tried :80 and :8080.HTTPS://<pi>:80
Try that, just specify port 80 explicitly (with the colon ), along with https
That is the last resort. But if you are comfortable with there are many workaround that does not involve resetting database. for example, you can stop reef-pi and runNothing to do... I tried :80 and :8080.
At this point I think I have to connect by ssh and reset the reef-pi datatbese!!! :-(
Is it right?
reef-pi db show reef-pi settings
This is expected. Kessil does not dim till 0. In my experience below 13 pwm values (0-100) my A80, A360 etc will start blinking. This is the reason we introduced "min" value for individual channels early on. that tells reef-pi to set the channel value to 0 when the computed value (From profile) is below the minimum value.Hey Reef-Pi people,
I am having issues controlling my Kessil A160WE. I am able to manually adjust the two channels with the slider, and channel 1 is white and channel 2 is blue. My problem is that if I lower channel 2 below 10, both channels turn off? Channel 1 can go to zero and the channel 2 blue lights will stay on at what ever intensity its set to. Is this by design? Can you have White light without blue?
Additionally, I am wondering if anyone can speak to the TRRS adapter that came with my light? Is it required? Is there any benefit to using a TRRS cable and jack at the reef-pi?
TIA
I connected by ssh and wrote the commands you suggested.That is the last resort. But if you are comfortable with there are many workaround that does not involve resetting database. for example, you can stop reef-pi and run
Code:reef-pi db show reef-pi settings
that will show reef-pi settings which will include a field named "address", that has ip and port reef-pi is using
Ouch.. its looks like the port is set to blank and as a result, reef-pi is crashing. You can save the settings in a file, change the address to include :443 , i.e "0.0.0.0:443" and then reupload it, start reef-pi back,.I connected by ssh and wrote the commands you suggested.
This is the output... port is not showed (it should be :80 by default).
pi@raspberrypi:~ $ sudo systemctl stop reef-pi.service
pi@raspberrypi:~ $ sudo reef-pi db show reef-pi settings
{"name":"Freccialata's Aquarium","interface":"wlan0","address":"0.0.0.0","display":false,"notification":true,"capabilities":{"dev_mode":false,"dashboard":true,"health_check":true,"equipment":true,"timers":false,"lighting":false,"temperature":true,"ato":false,"camera":false,"doser":false,"ph":true,"macro":false,"configuration":true,"journal":false},"health_check":{"enable":true,"max_memory":500,"max_cpu":2},"https":true,"pprof":false,"rpi_pwm_freq":100,"prometheus":false}
pi@raspberrypi:~ $ sudo systemctl start reef-pi.service
I aslo tried to open chromium-browser by terminal...
pi@raspberrypi:~ $ chromium-browser http://192.168.178.230
--disable-quic --enable-tcp-fast-open --ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so --ppapi-flash-args=enable_stagevideo_auto=0 --ppapi-flash-version=
libEGL warning: DRI2: failed to authenticate
[4304:4304:1122/090203.048757:ERROR:sandbox_linux.cc(369)] InitializeSandbox() called with multiple threads in process gpu-process.
[4252:4437:1122/090203.726939:ERROR:eek:bject_proxy.cc(632)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[4252:4437:1122/090203.727980:ERROR:eek:bject_proxy.cc(632)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[4252:4437:1122/090203.728991:ERROR:eek:bject_proxy.cc(632)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
Fontconfig error: Cannot load default config file
I tried the follow commands too:
chromium-browser http://192.168.178.230:80
chromium-browser http://192.168.178.230:8080
chromium-browser https://192.168.178.230:80
chromium-browser https://192.168.178.230:8080
Any other suggestion?
sudo reef-pi db show reef-pi settings > s.json
# edit the s.json file to change address and include port 443 in it.
sudo reef-pi db update reef-pi settings -input s.json
pi@raspberrypi:~ $ sudo systemctl stop reef-pi.serviceOuch.. its looks like the port is set to blank and as a result, reef-pi is crashing. You can save the settings in a file, change the address to include :443 , i.e "0.0.0.0:443" and then reupload it, start reef-pi back,.
Code:sudo reef-pi db show reef-pi settings > s.json # edit the s.json file to change address and include port 443 in it. sudo reef-pi db update reef-pi settings -input s.json
And start reef-pi again . After this you should. E able to access reef pi just as https://ip , because 443 is default port for https