- Joined
- May 14, 2018
- Messages
- 44
- Reaction score
- 67
After seeing all of the excellent reef-pi build threads, I took a shot at putting one together https://www.reef2reef.com/threads/red-sea-reefer-170-reef-pi-build.564715/#post-5783459
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.
:-) your call. worst case if it does not work, you have to play with the frequency. I dont see any point unless you have any issues with current setup, just wait for 3.0 and upgrade to that.I will probably skip this update for now since everything is working lol
Woohoo :-)After seeing all of the excellent reef-pi build threads, I took a shot at putting one together https://www.reef2reef.com/threads/red-sea-reefer-170-reef-pi-build.564715/#post-5783459
I have cut 2.3 release. It has only one change, bugfix for pca9685 driver, where pwm frequency settings were not working. Release builds can be found in usual location:
https://github.com/reef-pi/reef-pi/releases/tag/2.3
cheers
I really dont know, I'll let @theatrus or someone else who is more knowledgable on these things speak. All I can say is that now pca9685 will respond to frequency changes correctly (you have to reload reef-pi everytime you change it ).Question regarding the 2.3 pwm fix, my dosing pumps don't move fluid below 50% via the PCA 9685 at the default 1500 Hz, so if I run the update and drop the frequency to say 100 or 200 Hz if my theory is correct, I can expect the pump to work at lower speeds?
meanwhile... relocated the lepto![]()
![]()
I just confirmed similar behavior on a Pi3. My cheap meter reads 1.6 kHz regardless of the setting. I manually changed the frequency using a test script and was able to confirm a frequency change in the pca9685. However, it reverted back to 1.6 kHz after I reloaded reef-pi...Havent tried metering yet to check frequencies...but with 2.3 loaded, im seeing no behavior changes on the PWM for the pca9685...all settings of frequency from 10 to 1500 yield the same behavior like its stuck at 1500hz.
Checking with my meter confirms it stuck at 1500hz
I am on the latest raspbian
Pi zero w
Reef pi 2.3
I tried deleting the jacks and lights, reloaded then rebuilt them and reloaded.
Everything else about the pca9685 works, but the 100 percent setting bug is still present.
I even purged reef pi and reinstalled 2.3 with no luck although i did keep my reef pi database file.
To confirm its not related to my hardware if i switch a channel to a pi pwm pin set at 100hz, my lighting dims as its supposed to.
I just confirmed similar behavior on a Pi3. My cheap meter reads 1.6 kHz regardless of the setting. I manually changed the frequency using a test script and was able to confirm a frequency change in the pca9685. However, it reverted back to 1.6 kHz after I reloaded reef-pi...
I'm sure we're just overlooking something simple in the software, and I'm confident we'll get it sorted soon.
dang , let me look into this ASAP. I’ll re publish the builds soon. We know for sure this is fixed, let me check why it’s not working on 2.3Havent tried metering yet to check frequencies...but with 2.3 loaded, im seeing no behavior changes on the PWM for the pca9685...all settings of frequency from 10 to 1500 yield the same behavior like its stuck at 1500hz.
Checking with my meter confirms it stuck at 1500hz
I am on the latest raspbian
Pi zero w
Reef pi 2.3
I tried deleting the jacks and lights, reloaded then rebuilt them and reloaded.
Everything else about the pca9685 works, but the 100 percent setting bug is still present.
I even purged reef pi and reinstalled 2.3 with no luck although i did keep my reef pi database file.
To confirm its not related to my hardware if i switch a channel to a pi pwm pin set at 100hz, my lighting dims as its supposed to.
No problem, just reporting my findings with as much info as possible.dang , let me look into this ASAP. I’ll re publish the builds soon. We know for sure this is fixed, let me check why it’s not working on 2.3
Does this mean I can re-install 2.3 and test it out?Ok, i found out the issue. I didnt pull down the latest bug fixes before building the release.. just republished the builds now. I am also testing it out on one of my build as I write this post.
I tested, Its not working. I know we have fixed the code , but due to some glitch it’s not being picked up in 2.3 release build. I was looking into that .., but a different situation unfolded and got busy with thatDoes this mean I can re-install 2.3 and test it out?
Lol, I remember those situations, I have them with the grandkids now ;)I tested, Its not working. I know we have fixed the code , but due to some glitch it’s not being picked up in 2.3 release build. I was looking into that .., but a different situation unfolded and got busy with that![]()