Hello Ranjib
i dont understand what you want us to do with wiring pi?
Well, I'm keeping a few things open and because I still have so much from the radio-controlled sockets. have would not be soo important. You already do a lot of my respect for your commitment.
I have been looking for this myself, but since I didn't find too much, I started building one myself. Not sure if that's what you meant, but it seems like a standard nickel plated audio jack has something like K=5.
yes.. i have like 5-10 i think. Let me know if you need.
I could use 2 of them
Dm me your address. And I’ll send two . @robsworld78 should i send a couple in your way as well ?
I am thinking about 6.0 release and what are the major features I want to see. I want to work on docs, but its almost 2nd priority compared to the core controller software.
On the software side, i want to integrate esp32 based capabilities. This is triggered by the shortage of raspberry pi, their cost and ability to augment the capabilities across multiple controller hardware. In that regards, i was tinkering with esp32 recently. As of now I think i am quite comfortable with getting a dumb wifi based controller capable of relay control, pwm output and temperature sensors reading. Over the past two weeks i got an end to end prototype woriking capable of doing all of those three via http api. I dont know if I'll have the time to integrate ph IC , but if not we'll address that in next following minor release. Other than the esp32 controller software, we need a reef-pi driver counter part that will use the api to read temperature/ato sensor value from esp32 and then control relay (or other driver based outlets). Finally we want the changes to be able to run reef-pi in non-pi, x86(intel mini pc) architectures, without devmode. It should be possible to run reef-pi in orange pi or something similar (since pi specific dependencies will be made optional), but I'll only release builds for x86 and test on that, other than Pi.
I started with the docs, because as i am doing this i realized this will entail significant documentation requirement for any users (who are already not familiar with reef-pi), not making incremental upgrade. There is no way I can catch up on existing docs lag, do the new software coding and also add docs for the new software/hardware changes coming. At the same time, i think documentation is getting to a place that its hurting the project.
So here is what i am thinking, i am planning to make the documentation process continuous, instead of trying to catch up on the lag, i'll start creating place holder documentation here in the sub-forum, make them sticky and we'll setup some convention to continuously update them. Because we can not have multiple person editing the same post, all of these threads first post will be from me. You all can tag me in different threads or comment there to suggest, ask and collectively improve it from there on. If not immediately, i can regularly go through the requests weekly , or monthly and incorporate those feedback. I think it will make the documentation process sustainable.
What you all think? makes sense? or bad idea? Irrespective of what happens on the documentation side, I am bit excited about the esp32 integrations. At 6$ a piece they bring lot of bangs for the bucks. It also paves the way for easier analog sensor integration, lower power consumption, more pwm outputs ... lots of potential. I dont know how the reliability will be , in terms of hardware, wifi etc. It will be interesting. Given its so popular in IoT devices , im not too worried, I'm more curious about long term performance of ds18b20 etc. wifi reliability, ability to multiple concurrent logic etc. But we'll deal with those later.. and start small,. a dumb wifi controllable driver will be the starting point, along with a set of tested hardware, like:
esp32 board: Amazon product
ds18b20 as temperature sensor, sainsmart relay as relay mechanism,
pwm based power mosfet controller for led,dc motor (peristaltic pump) control: Amazon product
A wonderful side effect of this will be i'll free up a bunch of pi zero that im using for different type of sensor reading across house and garden
transform text filed takes any expression compatible to goevaluate and with a variable `v` representing the raw probe value.,
2*vThanks for helping out Ranjib and thanks for the offer but I'm ok.
You can use an output from the PCA9685, connect it to your circuit where the GPIO would go. The K1 probe should be good.
i use multiple a single central prometheus server running on mini pc to scrape multile reef-pi metrics and more(node exporter ) ,
- job_name: 'ryan-reef-pi-app'
metrics_path: '/x/metrics'
static_configs:
- targets: ['192.168.86.143']
