redesign the cbpi4-Flowmeter plugin?

[avollkopf]

          Hello, Alexander. Off topic, but I don't know where else to post. Can you help me redesign the cbpi4-Flowmeter plugin? I don't know python myself. I constantly have an error with the volume of water, since the speed of the water is not constant. Is it possible to change the code or add to the code the ability to calculate the volume of water by the number of pulses per liter, and not by frequency? The documentation says that there are 450 pulses per liter. Well, so that you can change the number of pulses in the settings. The author of the plugin does not get in touch. I tried this with an arduino. It turns out high accuracy to measure the amount of water, regardless of the flow rate.

Originally posted by @dimontau in PiBrewing/craftbeerpi4#108 (comment)

[avollkopf]

@dimontau I won't be able to support this as I just ported the original plugin, where it was extremely hard to test a sensor for me. This needs support from somebody else who is really having a sensor and can adapt the plugin if feasible.

[dimontau]

I can help with plugin testing

[prash3r]

@dimontau i added a very simple VolumeSensor to this Plugin. I hope you are using a Volume sensor via GPIO and not MQTT?

If thats the case here is how you can test my modifications:

• you need command line access on your Pi
• deinstall the Flowmeter Plugin you currently have installed: pip uninstall cbpi4-Flowmeter
• check if the deinstall was successful with pip list it should not be in the list anymore
• install my modified version: sudo pip3 install https://github.com/prash3r/cbpi4-Flowmeter/archive/VolumeSensor.zip
• now check if the install was successfull with pip list where you should find the flowmeter again but now version 0.0.6

Then you can test. To revert to official pypi release you can just pip uninstall cbpi4-Flowmeter && pip install cbpi4-Flowmeter and you should be running the official release version 0.0.4 again.

[dimontau]

prash3r Thank you. I tried. But everything is unchanged. The volume changes with the pressure in the tap.

[prash3r]

@dimontau i am sorry, my instructions were incomplete. I added a new hardware config sensor. you should be able to select the VolumeSensor in the hardware config and use that instead of the sensor you are currently using.

I didnt want to mess with people using the existing logic so i added completely new logic.

Is the VolumeSensor available in the hardware config? (you may need to remove the existing config and remember the RPi Pin used so the configs dont mess with each other but i am unsure).

The VolumeSensor should only be counting impulses from your hardware. if this changes with pressure in the tap then your problem seems to be hardware related. It could also be software but i cant test.

[dimontau]

prash3r. I used VolumeSensor. But when I ask to pour one liter of water, each time I get a different volume. from 0.7 liters to 1.4 liters

[dimontau]

Over the weekend I will reinstall the system so that there are no leftovers from the old plugin and try again.

[prash3r]

I need you to be more specific.

• is the volume displayed correctly on the dashboard (does it show the wanted volume or does it show the actual wrong volume)
• is the volume reset correctly on start (and end)
• does the volume count before the flow step is started and thus resetting the previously filled value and starts counting from 0 again?

I assume you are using the FlowStep and i am testing this with this and the fake impulse action i added to the sensor. the only error that should be added by the software is a one second delay for closing the valve. one second shouldnt be a problem right? This logic belongs to the existing FlowStep. I can implement a simpler VolumeStep, but i dont see a problem here as it works when im testing it.

Your sensor is connected directly to a GPIO pin, correct? what hardware are you using exactly?

You wouldnt need to reinstall everything on the Pi. you can just check which plugin Version is installed with

pip list | grep "cbpi4-Flowmeter"

• 0.0.6 is my Version and the VolumeSensor is available
• any other (lower) version and the VolumeSensor should not be available

If you see the VolumeSensor when you shouldnt be able to or the other way around then try to reload the webpage or delete the browser cache. If the 0.0.6 is listed then everything is set up correctly

The interference I was talking about was that you should make sure that no other Hardware element is using this GPIO pin - so when you replace the existing config you need to delete the old sensor from the hardware config so you dont have 2 sensors using the same GPIO pin

Edited:
additional info about my testing

My testing demo is setup to stop the first step on 0.05L volume and the second on 0.02L volume. I didnt stop clicking the fake impulses when the volume targets were reached so the 1 second delay causes it to trigger and finish at 0.06L (instead of 0.04L) and 0.04 (instead of 0.02L). On the second step i was clicking faster so the one second delay resulted in 0.02L overshoot instead of 0.01L like in the first step.

In a real world scenario one second delay should not be a problem - if this is the problem let me know and ill implement a separate VolumeStep.

[dimontau]

Thanks for the help. Checked everything today. Everything works as it should.

[dimontau]

The sensor I use is YF-S201. Connected directly to gpio.

[louzano]

eu uso a configuração "200" no volume sensor e funciona normalmente pra mim. tenho cerca de 1,8BAR de pressão na minha linha, e o YF-S201 está ligado na saída do filtro de água, porém há uma torneira após o YF-S201 pela qual regulo o fluxo de filtragem, mantendo em cerca de 10 a 20 ml/s. A única falha que vejo é não conseguir usar na dashboard os valores de volume total e fluxo, pois somente a ultima configurada recebe a leitura