Help me please,my due date is next week.....

[hidayahramli27]

`Hye, Iam new users and currently I am doing a project about irrigation,it is possible for me to combine this two coding,,Im trying to make a coding when the moisture dry,the pump will trigger water and will automatically stop when the moisture wet.I am also trying to use Thing Speak to display the data but I don't know how......

Relay coding

Code: Select all

import RPi.GPIO as GPIO
import time

channel = 21

# GPIO setup
GPIO.setmode(GPIO.BCM)
GPIO.setup(channel, GPIO.OUT)


def motor_on(pin):
    GPIO.output(pin, GPIO.HIGH)  # Turn motor on


def motor_off(pin):
    GPIO.output(pin, GPIO.LOW)  # Turn motor off


if __name__ == '__main__':
    try:
        motor_on(channel)
        time.sleep(1)
        motor_off(channel)
        time.sleep(1)
        GPIO.cleanup()
    except KeyboardInterrupt:
        GPIO.cleanup()

Soil coding
#!/usr/bin/python
import RPi.GPIO as GPIO
import time
 
#GPIO SETUP
channel = 14
GPIO.setmode(GPIO.BCM)
GPIO.setup(channel,GPIO.IN)
 
def callback(channel):
        if GPIO.input(channel):
                print ("DRY SOIL")
        else:
                print ("WATERY SOIL")
 
GPIO.add_event_detect(channel, GPIO.BOTH, bouncetime=300)  # let us know when the pin goes HIGH or LOW
GPIO.add_event_callback(channel, callback)  # assign function to GPIO PIN, Run function on change
 
# infinite loop
while True:
        time.sleep(1)

THANK YOU for your help seniorr

[pcmanbob]

Hi.

So you have left things late and now you want us to do your home work for you

well I wont do it for you be I will give you some pointers.

In the first portion of your code, you define you gpio pin using channel but you then go on to try and use pin but you never define pin , I suggest you keep it simple just use the gpio number in each gpio line.

in the second portion of you code you again use channel to define the gpio to use , you can do that as you have already used channel in the first part of the code , so again keep it simple use the gpio number in each gpio line.

I very much doubt the dampness of the soil will change very fast so you might be better just using a simple while try loop to check for the moisture sensor to go dry and then if its dry , turn the pump on and if wet turn the pump off.

if you specifically need to use event detect for the project then have a read of this web page that explains how to use it.

https://sourceforge.net/p/raspberry-gpi ... ki/Inputs/

[danjperron]

I very much doubt the dampness of the soil will change very fast so you might be better just using a simple while try loop to check for the moisture sensor to go dry and then if its dry , turn the pump on and if wet turn the pump off.

I completely agree with pcmambob!


First you should try to figure out experimentally how much time you should turn the pump ON and what is the delay for the sensor to trigger after you wet the soil.

With those two parameters you only need to do a loop.

1 - Check if the soil is wet
2 - if is wet dry then turn the pump for n seconds
2.5 - Turn the pump off.
3- Wait n seconds to let the water sink into the soil
4- goto to step 1

** Update thanks rin67630

Code: Select all

import RPi.GPIO as GPIO
import time

# GPIO setup
GPIO.setmode(GPIO.BCM)


PumpGPIO= 21
SensorGPIO=14

GPIO.setup(PumpGPIO, GPIO.OUT)
GPIO.setup(SensorGPIO, GPIO.IN)


#time definition

#how long the pump needs to run
PumpTime = 60.0

#how long to wait  for the water to penetrate the soil
SoakTime = 300.0


def motor_on(pin=PumpGPIO):
    GPIO.output(pin, GPIO.HIGH)  # Turn motor on


def motor_off(pin=PumpGPIO):
    GPIO.output(pin, GPIO.LOW)  # Turn motor off




try:

    while True:

        #is sensor wet or dry
        if GPIO.input(SensorGPIO):
            print("sensor wet turn pump for {} seconds".format(PumpTime))
            motor_on()
            time.sleep(PumpTime)
        else:
            print("sensor wet!")
        motor_off()
        print("wait {} seconds  to test the probe".format(SoakTime))
        #wait to let the water soak the soil
        time.sleep(SoakTime)
except KeyboardInterrupt:
     pass

#be sure that the motor is off
motor_off()

This code uses time.sleep but if you want to add a display and be interactive you will need to use something else like the comparison with datetime to turn on the pump and set the cycle.

[echmain]

Congratulations on your new baby!

[6by9]

Congratulations on your new baby!

I'm glad I'm not the only one who had incorrectly interpreted the thread title

[DougieLawson]

Congratulations on your new baby!

I'm glad I'm not the only one who had incorrectly interpreted the thread title

It's "due date" that triggers the thought of the Maternity Dept - as it did for me. (Although, my two grandkids have been born 14,500Km away in Western Australia - so we missed most of the excitement - until the WhatsApp message arrived.)

These "Eternal September" threads never fail to amuse.

[gordon77]

Based on your original code...

Code: Select all

import RPi.GPIO as GPIO
import time

m_channel = 21
d_channel = 14

# GPIO setup
GPIO.setwarnings(False)
GPIO.setmode(GPIO.BCM)
GPIO.setup(m_channel, GPIO.OUT)
GPIO.setup(d_channel,GPIO.IN)

def callback(channel):
    while GPIO.input(channel):
        print ("DRY SOIL")
        motor_on(m_channel) 
        time.sleep(1)
        motor_off(m_channel)
        time.sleep(1)
    if not GPIO.input(channel):
        print ("WATERY SOIL")
 
GPIO.add_event_detect(d_channel, GPIO.BOTH, bouncetime=300)  # let us know when the pin goes HIGH or LOW
GPIO.add_event_callback(d_channel, callback)  # assign function to GPIO PIN, Run function on change

def motor_on(pin):
    GPIO.output(pin, GPIO.HIGH)  # Turn motor on

def motor_off(pin):
    GPIO.output(pin, GPIO.LOW)  # Turn motor off

if __name__ == '__main__':
    try:
        callback(d_channel) # initial test for DRY / WATERY SOIL
        while True:
            time.sleep(1)
        
    except KeyboardInterrupt:
        GPIO.cleanup()

[danjperron]

Gordon I don't think it is a good idea to start and stop a pump in 1 second interval.

[gordon77]

Maybe, but l simply used the OPs code and timing. They can change it as required from advice such as yours.

Maybe?

Code: Select all

print ("DRY SOIL")
motor_on(m_channel) 
time.sleep(10)
motor_off(m_channel)
time.sleep(30) 

I expect times will depend on pump size, flow rate etc.

[rin67630]

1 - Check if the soil is wet
2 - if is wet then turn the pump for n seconds
3- Wait n seconds to let the water sink into the soil
4- goto to step 1

Hmmm.
Step 2 ist wrong: if it is NOT wet...

Step 2.5 is missing: turn the pump off.

[W. H. Heydt]

These "Eternal September" threads never fail to amuse.

Someone else who dates himself by remembering the "Endless September".

[danjperron]

Step 2 ist wrong: if it is NOT wet...

Step 2.5 is missing: turn the pump off.

Good catch.

At least the code in python was ok!

[pfletch101]

Step 2 ist wrong: if it is NOT wet...

Step 2.5 is missing: turn the pump off.

Good catch.

At least the code in python was ok!

Good way to flood your basement!

To me, "turn the pump on for n seconds" fairly strongly implies turning it off after n seconds - otherwise, why specify a time at all?

[W. H. Heydt]

Note that there has been no response (or any other post) from the OP.

[gordon77]

Note that there has been no response (or any other post) from the OP.

I'd also noticed that, happens quite regularly on here. I wonder if they can't find their post again.

[B.Goode]

Note that there has been no response (or any other post) from the OP.

...too busy writing up the assignment for their forthcoming project submission!

They have been given the conundrum of wondering which one of 2 possible solutions to copy and paste into their project. Perhaps we should leave them to find any 'deliberate mistakes' or implementation errors for themselves so that they actually do some work on the project to earn the marks or other credit?

[davidcoton]

Maybe the assignment setter follows raspberrypi.org/forums too

[Andyroo]

Maybe the assignment setter follows raspberrypi.org/forums too

I would hope so.

Maybe give extra points if you can explain the problem clearly without using the actual question text (as no one actually seems to do)?

[echmain]

Note that there has been no response (or any other post) from the OP.

She probably went into labor.

[gordon77]

Well the week is nearly up and nothing heard from the OP ..

[pcmanbob]

Well the week is nearly up and nothing heard from the OP ..

Seems common on this forum , make one post asking for help and then never seen again....

[Andyroo]

Well at least this one did come back a few days after - not like a lot of the five minute visitors

[fruitoftheloom]

Note that there has been no response (or any other post) from the OP.

She probably went into labor.

Yes a brand new RPi 4B was born

[pcmanbob]

Well at least this one did come back a few days after - not like a lot of the five minute visitors

No OP only ever made 1 post , guess due date came earlier than expected

[B.Goode]

Well the week is nearly up and nothing heard from the OP ..

The OP had their homework done for them.

They can read that by browsing the forum anonymously.

Why would anyone expect to hear from them again?



Like @pcmanbob, I am happy to provide hints and guidance, but am reluctant to provide full answers to what look - to me - like 'assignment' questions. I wish that was a general policy for these forums, but I have to accept that most of us are volunteers who can take independent decisions about whom and how we help.