TDR Soil Moisture Sensor

I just want to water my plant, but cheap moisture sensors are pretty bad. Here I attempt to make a better one.

Public Chat
Similar projects worth following
This project is an attempt to create a moisture sensor based on Time Domain Reflectometry (TDR) instead of the more common capacitive or resistive sensors that often fail after prolonged contact with damp environments.
This ends up being an interesting exploration of high speed PCB design concepts and sub-nanosecond time measurements.

As I was trying to put together a simple automated plant watering solution, I figured that having the amount of water be driven by a soil sensor would be a good idea.  So I tried the default cheap capacitive moisture sensors, but had several of them fail on me after only a few weeks.  While looking for better solution I ran over a different technique call Time Domain Reflectometry that could be used to make that measurement.  How hard could it be to make one of those?

Many hours of debugging, a few failed designs later and I have a working prototype based on a Time of Flight sensor and a Raspberry Pi Pico W that can log to a central server.  

Using a PCB sensor that is inserted in to the soil of a plant, it is able to see the change in moisture content in the soil over time.  It's sensitive enough that it can see the change in moisture over a single day.  This allowed me to set a level that triggers watering and have small amount of water dispensed with a pump to keep the moisture level fairly consistent.  

This is a sensor log of a plant.  The green vertical lines are when watering was triggered and the red line is the average detected moisture level.  Each dose of water is pretty small, but shows up as a huge spice of moisture that then drops quickly as it spreads more evenly thru the plant pot.  

The test plant isn't dead after a few months, so by at least that metric, the project has achieved it's goal.  However, there are still some things that need to be done:

  • Design/create an enclosure
  • Finish rewrite to Rust
  • Create single PCB with integrated antenna

I'm going back and writing build logs to document some of the steps I did, which is really more of the point of this whole process.  But if you want to jump ahead and see some of the results the KiCad and RP2040 CircuitPython code can be found at:

  • 1 × 12V DC Dosing Pump Any 12 V pump would work
  • 1 × RaspberryPi Pico W

  • What are we actually measuring here?

    TheBlinkingMan05/05/2024 at 19:08 1 comment

    After all is said and done, the sensor measures about a 6 ns difference between a dry sensor and one dunked into about 4 inches of water.  That's certainly enough to measure since the sensor has a resolution to about 10ps with an accuracy of closer to 80ps (just rough guesses), but considering the reflection on the 7 inch dry trace in theory is only about 2ns, that difference is pretty large.  Looking at the relative permittivity of pure water, delays of that magnitude are theatrically possible since a wave traveling thru 7 inches of water would see about a 10.5ns reflection. However seeing a 6 ns change would require a huge shift in the effective dielectric constant of the probe in water, which seems unlikely.  So what is actually being measured here?

    Lets take a closer look at a fast step signal down the probe at a much higher time resolution.  While I would love to have a 10s of GHz bandwidth real time oscilloscope to do this, I don't have that kind of money, so instead I got access to some vintage hardware.  Using a sampling oscilloscope with a 20GHz sampling head and a 30ps step generator, we can take a look at what dunking the probe into water looks like:

    The white trace is the dry probe and the yellow trace is the probe in about 4 inches of water which cover about half the probe.  The transition from air to water happens at the first reflection after the step and where the two traces first diverge.  The cursor position show the time difference to when the voltage reaches it's peak, so what we are measuring with our sensor.  It's also about 6ns, which at least validates the basic operation.  

    However, the shape of the trace is interesting.  Unlike the white/dry trace, where there is a sharp edge at the end (ignore the secondary reflections after 3ns since that's after the signal has first reached the end of the trace), there is a lower section followed by a gentle slope up to the step voltage.  This indicates a capacitive termination instead of an open termination 

    Likely what is happening is there is an increase in the capacitance between the parallel traces in addition to the change in the dielectric constant due to the water.  The dielectric constant change is probably responsible for the extended lower reflection in the yellow trace and the capacitance is what is causing slope up to the final voltage.  Both of which contribute to the measured delay.  

    So, while the sensor is based on TDR techniques, what is actually being measured is a mix of effects, much of which is a result of a change in capacitance, similar to what is measured using other soil moisture sensors.  That being said, it's still effective and the probe has been robust (no failures in many months), so overall I'm still satisfied with the design.  

    P.S. Thanks for the comment that made me look into this more, since things are certainly more complex than it originally appeared.  

    Refs: -TDR Impedance Measurements: A Foundation for Signal Integrity

  • Simple Enclosure

    TheBlinkingMan01/23/2024 at 03:26 0 comments

    Integrating the PCB with a water reservoir and plant pot would be the best solution, but I haven't quite figured out how I wan to do that yet.  So lets just at least put the PCB into a simple enclosure to look a little better since there's been a bare board sitting around for a while now.  The board already has mounting holes in it, so I can export the STEP from KiCAD to a CAD program:

    I populated most of the footprints with 3D models mostly via DigiKey or the default models in KiCAD.  The only really important ones are the off board connectors so that I can put holes in the right place in CAD.  

    I also added a simple model for the OLED module I'm using.  This is to make sure I put the hole in the top at the right place and have clearance.  To make it look actually good, it would probably be best to actually attach the OLED module to the top and use a ribbon cable to connect it to the PCB, but these OLED modules are so cheap on ebay that I just keep a few around to use in these projects.   

    Under each mounting hole I put in a M3 heat set brass insert and these are easily installed with a soldering iron.  If you want a really secure way to hold on the top of the enclosure, use a threaded standoff instead of a screw and then use screw into the standoff to hold on the top.  However, a snap fit top will work here and make it easer to get to the adjustments if needed.  

    After the first iteration, I moved all the lugs/snaps to the lid so that I could drop the PCB in without having to slid it past things.  The snap is only .020" interference as the lid is pushed on and fits into a matching slot in the bottom so that it's not under strain after the lid is closed.  

    Also make sure to make the snaps fairly wide since 3D printed in this orientation isn't that strong.  

    An hour and a half later and the 3D print is done:

  • Fixing SPI with "weak" MISO

    TheBlinkingMan11/19/2023 at 21:19 0 comments

    I was having SPI issues that seemed to be exacerbated by setting a clock speed faster than 2MHz.  I was getting junk data from the TDC chip sometimes.  So, I kluged around this by discarding values that were outside a reasonable range, but I wanted to address the underlying issue.  So, lets dig into what is actually happening here.  

    Looking at the SPI transactions with a scope showed a "weak" MISO.  

    The magenta trace should be going to 3.3V but sometimes doesn't even manage to get to 1V.   Just as an aside, always remember to put in test points for signals.  The first revision didn't have easy places to probe and it was a massive pain to capture these traces on that board.  

    To make things even weirder, probing the traces cause more problems.  I could see better results when not probing.  Just as a test, if I set the clock speed to where it just barely worked, and then when I touched the TDC chip with my finger, it would fall apart.  The extra capacitance from the probe or my finger would degrade the signal enough that it would stop working.  This is a pretty short, well routed trace so it shouldn't be so borderline.   

    So does SPI need a pull-up to work? In theory no, but it sure seems like this chip could use some help.  But what value to pick? 10K did nothing, but using 3.3K did improve things:

    You can see the multiple slopes on the leading edge and no flat top.  The pull-up drags the MISO up to 3.3V, but it takes a few 100ns.  This is with a clock set to 5MHz (the RP2040 seems to not quite make it there).  But if we bump up the clock to the advertised 20MHz

    Here you can see the leading edge takes too long to rise up to the 3V level and the clock already gets to a falling edge where the measurement is made.  So, lets try a 1K pull-up.  

    Now at 20MHz (RP2040 only makes it to 15.6MHz), even the last single bit on MISO can make it up to about 2.7V in time for the falling clock edge.  You can also see the TDC starting to struggle in bring the low level down to 0V, but the 0.5V level seems to be good enough to be treated as logic low.  

    Things still aren't perfect.  The TDC should be able to drive the MISO from 0V to 3.3V without that 1K pull-up, but at least this gets it working at 15MHz without kluging around it in software, which is much faster than where it was before.  More importantly, it seems more stable, so board to board or chip to chip variations won't mess it up.  I've also seen a board that worked at one point start to fail after a few months with SPI errors.  Now if I could only figure out why the WiFi sometimes won't reconnect...

  • TOF Sensor CircuitPython Code

    TheBlinkingMan11/19/2023 at 01:18 0 comments

    In this revision of the PCB, I'm using a Seed XIAO RP2040, which is based on the RP2040.  It's supported by CircuitPython which offers lots of useful libraries, but not one for the TDC chip I'm using.  Generally I would say CircuitPython is pretty good for development, but does seem to have some stability issues when run for long periods of time.  However, just dropping the code on a USB drive is pretty nice. 

    We are using the Time of Flight chip TDC7200 to measure the time between when we send a pulse and when we see the final reflection from the other end of the line.  So the general flow is to setup everything by configuring the TDC and clock generation chip (a Si5351).  Then trigger a measurement and read the result back.  

    The TDC is accessed over SPI and data is read or written into registers.  So all the configuration looks like writing values to address with various bits set that indicate how the chip should be configured.  

    def config_tdc():
        calibration_periods = 1 # 1 = 10 periods
        calibration_shift = 6
        avg_cycles = 0b111 # 128 cycles
        avg_cycles_shift = 3
        reg_value = (calibration_periods << calibration_shift) | (avg_cycles << avg_cycles_shift)
        write_register(CONFIG2_ADDR, reg_value)

     Everything is set as the default except we can enable taking multiple measurements and averaging it together on the TDC before returning the result.  This ends up being much faster than doing the equivalent number of single measurements and doing the averaging on the RP2040 because it takes more time to do all the SPI interactions then it takes to do another measurement.  

    Another thing we need to setup is receiving the signal from the TDC to send a pulse.  There are many different ways to do this, but since we want to do this quickly to minimize the time between measurements, I used a simple PIO program to just wait for a signal and then send the pulse to the Schmitt trigger.

    # This will trigger a pulse whenever the TDC requests it
    trigger_pio = '''
    .program trigger
        wait 1 pin 0    ; wait for trigger pin to be set
        set pins, 1     ; send pulse 
        set pins, 0
        ; loop back to the beginning
    triggered_asm = adafruit_pioasm.assemble(trigger_pio)
    sm = rp2pio.StateMachine(triggered_asm,

    The reason I didn't just set the output of the TDC directly to the Schmitt Trigger is that there is a minimum delay between the TDC requesting a start pulse and the pulse actually happening.  The easiest way to add a delay is to have the RP2040 do it and then it can be adjustable too.  Turns out that the no extra delay was needed.    

    So now we can actually do a measurement:

    def do_measurement():
        "Time of flight in nanoseconds"
        start_measure = 0b1 # start measurement mode 1
        write_register(CONFIG1_ADDR, start_measure)
        # Wait for a measurement to be ready
        while done.value:
        time1 = read_register(TIME1_ADDR, reg_size=3) & TIME_MASK
        cal1 = read_register(CAL1_ADDR, reg_size=3) & CAL_MASK
        cal2 = read_register(CAL2_ADDR, reg_size=3) & CAL_MASK
        tof = calc_tof_mode1(clock, time1, cal1, cal2)
        # print("TOF = %s" % (tof*10**9))
        return tof * 10**9

     Setting the start measure bit in the CONFIG1 register will cause the TDC to send the start signal back to the RP2040, which via the PIO program will send a pulse to the Schmitt trigger, which will then send the pulse, and the START pin of the TDC.  Once that pulse reflection crosses the comparator level, a edge will be sent to STOP pin of the TDC.  

    This happens 128 times and when that is done, the done pin will be brought low, which indicates the RP2040 should read the result.  Three values are read and then we can calculate the actual value

    def calc_tof_mode1(clock, time, cal1, cal2):
        if time == 0 or cal1 == 0 or cal2 == 0:
            return -1
        freq = clock.clock_0.frequency
        period = 1/freq
        calCount = (cal2 - cal1)/9...
    Read more »

  • Time of Flight Sensor

    TheBlinkingMan11/10/2023 at 18:19 0 comments

    The TDC7200 Time-to-Digital Converter chip came to my attention and despite it not exactly intended for this application, the basic functionality seems to be exactly what I need.  It's intended to be used in something like a LIDAR system, where it measures the time between the outgoing pulse and the reflection.  But the measurement resolution of 55ps with a standard deviation of 35ps should be more than enough my application.  

    So what I need to do is create a start and stop signal to feed into this chip and then read out the time of flight.  The start pulse is easy, since I'm already generating that to feed into the Schmitt trigger to create the pulse, but the only twist is that the TDC requests the pulse instead of it just happening whenever.  So, I wait for that with the RP2040 and then send out the start pulse.  

    Where I want to stop measuring is at the final reflection from the end of the PCB antenna.  Since the TDC doesn't work off of voltage trigger level like an oscilloscope, I used a voltage divider to set the trigger level and a comparator to make a single step after that threshold is crossed.

    I picked a very fast comparator, but in theory this actually isn't required since the absolute time between the start and stop pulse isn't important since we are just comparing relative readings, not the absolute value.  So a cheaper chip is certainly possible as long as the rise time is less than 1ns and the delay is fixed.  

    The TDC also needs a clock, which I generated using Si5351 which gives me the ability to try out various frequencies, but in the end I just used the datasheet recommended frequency.  

    The board in action:

    The SMA connector goes to the PCB antenna just sitting on the desk.  I made a measurement that I saved to a ref (thin traces):

    The yellow trace is the start pulse that then causes the light blue pulse to go to the antenna.  The dark blue line is the comparator output and the magenta line is the trigger level.  The light green thin ref line is the pulse with the antenna on the desk, so there is no extra step from the change in medium as the pulse goes down the trace.  The comparator output with the antenna at that point is the orange ref line.  I then covered the end of the antenna with my hand, causing a new step in the pulse trace from my hand right where the trigger level trace intersects the trace.  This causes the comparator output to shift significantly.  The difference between the orange ref trace and the blue trace is the result of my hand being on the antenna trace or not.  

    You can see the delay between the trigger level being crossed and the comparator output is about 5ns, but that is acceptable for this application.  

    In the end the only two traces that are measured by the TDC are the yellow and dark blue traces for the start and stop pulses.  They are both clean edges for the TDC, unlike the mess that is the raw pulse trace. 

    Here's the reading from the TDC:

    TOF = 19.5382
    TOF = 19.554
    TOF = 19.6037
    TOF = 19.6216
    TOF = 21.7848        <-- Hand placed on trace
    TOF = 22.386
    TOF = 22.6032
    TOF = 22.7481
    TOF = 22.8489

     I'm reading the TDC reading via a serial console on the XIAO RP2040 and we can clearly see the jump in time of flight.  The change is roughly what we see in the o-scope trace too (they aren't from the same moment, so they don't line up exactly).

    Next time I'll go over the code needed for this.  

  • EDN TDR Sensor

    TheBlinkingMan10/30/2023 at 02:34 1 comment

    At this point we have something that at least proves out the concept of using TDR to measure soil moisture, but requires an oscilloscope to actually measure.  To make this project work, I'll need to make a self contained way to measure that timing difference and it also can't cost much.  So I want to avoid any ADC based based designs and instead focus on comparator and timing based designs.  

    The first design I attempted to replicate was from an EDN article.  There are some low res partial schematics in the article that I recreated:

    And also the PIC24F based digital section:

    Which resulted in the following layout:

    If you look closely, you may notice some unpopulated parts.  I didn't take a picture until after I had already harvested a few components for the next version.  There was a next version because this design ended up not having the resolution I needed to detect the differences between moist soil and slightly less moist soil.  In the end it could measure a delay change of about 500ps which wasn't enough to reliably detect the moisture difference over a day.  

    So even if it didn't work out, I learned a few things while working with the PIC microcontroller and the CTMU.  As mentioned in the article, the PIC has a current source it can start and stop charging a capacitor with.  It then can measure the voltage on that cap to determine how much time has passed.  Even with the current source set to the highest setting and using just the internal capacitance, the charge was too small to get an accurate reading.  Also, the documentation on how to set the flags to get the right charge range where incorrect and had to be determined experientially.  

    The code is pretty simple and mostly configuration, so I'm including it here for completeness.  

    #define RANGE_5_50uA 1 // 5.50uA
    void CtmuTimeConfig(unsigned int range, signed int trim)
        // Step 1 Configure the CTMU
        CTMUCON1 = 0x0000; // Disable CTMU
        CTMUCON1bits.TGEN = 0; // Disable Time Generation mode
        CTMUCON1bits.EDGEN = 1; // Edges are enabled
        CTMUCON1bits.EDGSEQEN = 1; // Edge sequence enable
        CTMUICONbits.ITRIM = trim; // Set trim
        CTMUCON1bits.CTTRIG = 1; // Trigger output enabled
        CTMUICONbits.IRNG = (range & 3); // Set range
        // This line does not apply to all devices
        //CTMUCON2bits.IRNGH = (range>>2); // set high bit of range
        CTMUCON2bits.EDG1MOD = 1; // Edge mode
        CTMUCON2bits.EDG1POL = 1; // 1 - rising edge 0 - falling edge
        CTMUCON2bits.EDG1SEL = 2; // 8 = CTED13 Pin 6 || 2 = CTED2 pin 15
        CTMUCON2bits.EDG2POL = 0; // 1 - rising edge 0 - falling edge
        CTMUCON2bits.EDG2MOD = 1; // Edge mode
        CTMUCON2bits.EDG2SEL = 8; // 8 = CTED13 Pin 6
    //    CTMUCON2bits.IRSTEN = 1; // enable reset by external trigger
    //    CTMUCON2bits.DSCHS = 4; // ADC end of conversion
        // Step 2 Configure the port Ports
        TRISBbits.TRISB12 = 1; // Configure RB12 as a input CTED2
        ANSBbits.ANSB12 = 0; // disable analog on RB12
        TRISBbits.TRISB2 = 1; // Configure RB2 as a input CTED13
        ANSBbits.ANSB2 = 0; // disable analog on RB2
        TRISAbits.TRISA0 = 1; // Configure RA0 as a input
        ANSAbits.ANSA0 = 1; // Configure AN0/RA0 as analog
        AD1CHSbits.CH0SA = 0 ; // Select AN0
        // Configure the cap drain output pin
        TRISAbits.TRISA3 = 0; // RA3 as output
        PORTAbits.RA3 = 0; // Set output low
        // Step 3 configure the ADC
        AD1CON1 = 0x0000; // Turn off ADC
        AD1CON1bits.SSRC = 0; // 4 - CTMU is the conversion trigger source 0 - manual
        AD1CON2 = 0x0000; // VR+ = AVDD, V- = AVSS, Don't scan,
        AD1CON3 = 0x0000; // ADC uses system clock
    //    AD1CON3bits.ADCS = 8; // conversion clock = 1xTcy
        AD1CON5 = 0x0000; // Auto-Scan disabled
        AD1CON1bits.ADON = 1; // Enable ADC
        AD1CON1bits.ASAM = 1; // Auto-sample
        // Clear CTMU Interrupt
        IFS4bits.CTMUIF = 0;
        // Step 4 - 6 Enable the current source and stop manual discharge
        CTMUCON2 &= ~0x0300; // clear the edge status bits
        CTMUCON1bits.CTMUEN = 1; // Enable the CTMU
    Read more »

  • TDR Antenna

    TheBlinkingMan10/16/2023 at 03:17 0 comments

    I have no idea what design parameters are needed to maximize the effect of whatever medium the TDR step has on the propagation speed.  So I started with just two stainless steel 2mm rods in parallel with ground on one rod and the pulse on the other.  This did work, but the connection between the rods and the copper clad PCB I had just cut two pads into with a knife was not great.  I ended up making another PCB for this.  

    There is no ground plane based on the thought that I want as much of the EM field to go through the surrounding medium instead of there being a short path to ground.  The impedance of this trace will be higher than 50ohms, so in theory that will cause some refections as it goes from the 50 ohm cable to the pcb, but we only care about the last reflection that goes all the way down the trace.  

    To test how well this works, we can measure the difference between air and fully immersed in water

    Which looks like this on the scope:

    The green trace is the antenna in open air and the magenta trace is fully immersed in water.  Most of the length of the step is the same, but at the 9ns the reflection starts coming from the antenna.  Each division is 10 nanoseconds, so the water reflection is about 5 ns slower than open air.  This is about the maximin difference we can expect to be able to detect.  

    So, lets stick it into some soil and see what it looks like.

    Here the difference between the two traces are when the soil is dry and freshly watered.  The antenna was not inserted as deep into the pot as it was into the water, so we can see the change is nearer the top of the step.  It is also smaller because the change in water content is not as large between the dry and moist soil.  In this case it is 3ns right after watering.  

    The difference in timing is only a few nanoseconds at best.  That's pretty small and I'd like to be able to differentiate between various levels of moisture content which will need sub-nanosecond resolution.  The good news is that it is a relative measurement.  My scope which can only measure a rise time of about 1ns can resolve differences much less than that.  

    The original TDR article on EDN has a design for measuring the difference in TDR pulses, so the plan is to build one and test if it has the resolution needed for this application.  

  • Pulse Generator

    TheBlinkingMan10/15/2023 at 17:41 0 comments

    There's already quite a few of builds of cheap pulse/step generators online, so I just picked one to base my build on:

    Even though something like a 555 timer could generate the start pulse to feed the Schmitt trigger, I ended up putting a XIAO RP2040 to just generate a pulse via PWM. 

    I put two edge launch SMA connectors so I could run one to whatever I was trying to test and one to my oscilloscope.  The theory behind simple TDR measurements assumes that there's only one transmission line involved and adding the second one to the scope would cause it's own set of reflections into the high impedance scope termination.  So I added a 50ohm termination at the scope, which I have to do with an external passthrough termination:

    The 50 ohm termination will load the signal, which will cause the magnitude of the signal to be decreased compared to when the scope isn't connected, but that doesn't matter in this case since it will only be used with something attached to make the reading.  

    This pulse has a rise time of a little more than 1ns into 50 ohms, which is about the limit of the bandwidth of my 350MHz scope.  

    Attaching different lengths of coax shows that the basic TDR measurements work.  

    Which results in the following trace:

    The orange ref trace is when nothing is connected.  The active trace is with a 2ft coax attached.  The green trace is with a much longer coax cable attached.  The different length of coax cause a step from the delayed reflection off the other end of the cable.  The length of that delay is proportional to the length of the cable.  That same delay is what I'm aiming to measure to in soil.  

    Now I need to make something to probe soil and see the TDR measurements.  

  • Initial Research

    TheBlinkingMan10/15/2023 at 04:35 0 comments

    First step of any of these DIY projects is to check if I can just buy the solution.  At first glance, the price jump between most capacitive sensors and low end TDR sensors is pretty big but some cheaper examples of TDR sensors exist at the $50 price point:

    More than I'd like to spend on each plant I want to water, so there's actually a chance it makes sense to create my own solution that will be cheaper if I need to make several. 

    Alright, so how does that actually work? Well, turns out there a pretty good background article on that too:

    The TLDR version is that the speed that a voltage step moves down a transmission line is related to the medium the electric fields pass thru.  In PCBs this is the typically FR4 fiberglass that makes up the board itself, not the copper of the traces itself.  This is true for cables and anything else too.  Also, an open or short circuit will cause that voltage step to be reflected back to the sender, it is possible to measure the time it reach the end of the transmission line and come back from the sending side by looking at the final voltage step.  

    So the basic concept is that by measuring that time, one can learn something about the medium the step is traveling thru.  For example, by dunking the line in water will cause the time to increase when compared to the time when the line is in open air.  

    More subtle differences, like that between dry soil and damp soil are also possible and that seems to be the working principle of these TDR soil moisture sensors.  

    But how subtle is that difference? I figured it would make sense to test this out first, so I will build a pulse generator I can use with my oscilloscope as a proof of concept.

View all 9 project logs

Enjoy this project?



Bruno Da Silva wrote 05/12/2024 at 12:34 point

Love this project!! I've been super interested in "better" soil moisture sensors ever since I've run into measurement inconsistencies with the the $2 capacitive ones I got off aliexpress. TDR/FDR always scared me because you start dealing with signaling and RF complexities that I've yet to learn.

I'm all for commodotizing better soil sensors that are more DIY and don't cost $300+ off a research-targeted site. I just want to know when to water my plants without killing them 😅

Data integrity is the bedrock of good automation!!

  Are you sure? yes | no

Brad Stewart wrote 04/17/2024 at 21:10 point

Not sure you are using a TDR method.  You are measuring more capacitive values at a higher frequency.  And for best results, you need to be above 10MHz as at those frequencies, the dielectric constant of the soil has less of an effect.   I design commercial TDR probes and you need a pulse of <300ps rise-time.  You need to send the pulse down a 15cm probe and measure the first reflection with at least 10ps of resolution using a delay line.  So this requires special h/w like PECL (postive emitter coupled logic) to achieve those speeds.  In the article cited in the comments, the method uses TDT which also yields good results, but does require very high frequency measurements.  Good news is that I used a PyBoard and micropython to take the measurements.

  Are you sure? yes | no

Bruno Da Silva wrote 05/12/2024 at 12:30 point

I'm limited in my understanding so far of TDR. I'm curious of your mentioning of a 15cm probe -- is that probe length a hard requirement? Why does probe length matter with TDR? I wouldn't imagine it changes the timing of the pulse. 

Perhaps... does it change how strong the pulse returns (ie voltage)? Does it significantly affect the capacitance between the probes? 

Love it when industry experts come in to drop knowledge in these threads. <3

  Are you sure? yes | no

babasolomon904 wrote 04/12/2024 at 21:14 point

It's interesting how long it took you to learn to do this... Cool, why are there so few comments here?  I also spent a long time learning, there was even a moment when I used to get through my university tasks. Honestly, I still confuse the TDR and TDT methods.

  Are you sure? yes | no

Kostas wrote 11/11/2023 at 08:45 point

You can check the following paper:

  Are you sure? yes | no

TheBlinkingMan wrote 11/12/2023 at 05:26 point

That's a good paper with an interesting solution to the same problem.  It's too bad the sensor design wasn't described more that just saying they used a very expensive software package to optimize it.  I think I can probably get my BOM cost below their $60 mark with acceptable performance.  I saw some commercially available solutions below that price point, but it's too expensive to use for a single potted plant.  

  Are you sure? yes | no

Similar Projects

Does this project spark your interest?

Become a member to follow this project and never miss any updates