Open Source Orchard

1. LoRaWAN Gateway Deployment 

To determine the optimal implementation of a LoRaWAN gateway (or multiple) in a commercial orchard setting, our initial assumption was to continue with our approach from the summer of 2022 where we set up a WisGate Edge Pro gateway on a tripod next to our shop, and simply move the entire unit on top of our roof to ensure greater farm-wide coverage. However, we had issues scheduling anyone who would be able to (safely) get on the 30' high roof to fasten the tripod down and we quickly realized if there was ever a need to provide maintenance to the gateway, it would be virtually impossible. We then began to reevaluate the overall agrosecurity of the system, and started by addressing questions such as "If something were to happen to a gateway, how easy would it be to replace that gateway, continue sensor data collection, and get everything back up and running?" Our new shop office was recently completed in the summer of 2024 and in the process, we installed a WisGate Edge Pro (V2) to the inside of the attic and routed a 12’ cable to an 8 dBi antenna mounted on the roof, with the base of the antenna 6’ (2 times the length of the antenna) above the top of the metal roof. The gateway inside has an Ethernet cable routed through the celling to an office room to a PoE injector to provide power, and another Ethernet cable runs from the injector to a Wi-Fi router. We began range testing by connecting four soil moisture sensors to ChirpStack and moved them incrementally further from the gateway location, collecting data on the SNR (Signal Noise Ratio), RSSI (Received Signal Strength Indication), and time intervals of sensor communication. The gateway was able to cover the entire farm, however there was significant signal loss beyond a locust grove that divides a section of our farm. The sensor just in front of the locust grove recorded an average RSSI of -110.915 dBm and average SNR of -2.795 dB for the month of July while the sensor just beyond the locust grove recorded an average RSSI of -113.07 dBm and average SNR of -12.649 dB, showing a notable degradation. This suggests that deploying an additional cellular-connected LoRaWAN gateway on a tripod beyond the locust grove may be necessary to strengthen reliable coverage, and can bolster resiliency of the system through working in a cluster. In the event one gateway is knocked out, sensor signals can still be picked up by other gateways within the network, allowing for data collection to continue even in worse-case scenarios. In addition, this means the second gateway on a tripod can be taken in during winter months when data collection isn't as necessary as during the growing season. For the server to manage the data pipeline, we've switched from a Raspberry Pi-based physical computer to cloud-based computing (virtual machine) via a managed service provider. This concept came from the question "How could a farm respond to cybersecurity threats and ensure operations can continue to run smoothly especially if automated devices are in use?" Using cloud computing instead of physical computing will mean maintenance of a separate computer is not necessary and farms will not be responsible for establishing intense cybersecurity measures on their own (the Raspberry Pi could be hacked if left unmaintained). If cybersecurity issues do occur, the managed service provider will act as a deterrent and work on the farm's behalf. The open source components of the IoT data pipeline, namely ChirpStack (the web-interface to manage the gateway and all devices connected to it), will reside in the cloud computing space for an affordable cost.

2. Irrigation Management 

Three “Drop Count” sensor systems were constructed during the summer of 2023 and the design involved a Watermark Soil Moisture Sensor (acting as a soil potential sensor) with a 15’ cable, Watermark Soil Moisture Sensor Voltage Adapter in a plastic utility box, Vegetronix Soil Moisture Sensor with a 2-meter cable, Watermark Soil Temperature Sensor with a 15’ cable, Dragino Waterproof Long Range Wireless LoRa Sensor Node, and a wooden stake to prop the system vertically. The systems were successfully assembled but proved to be tedious to assemble and far too bulky, especially since a 2x4 was needed to hold everything upright. In the winter of 2024, we initially considered a leaner design that included a Tektellic KIWI Agriculture Sensor, 2 Watermark Soil Moisture Sensors, and 2 soil temperature sensors. One pair of soil moisture sensors and soil temperature sensors would have been placed about 6" deep and the second pair about 18"-24" deep, the latter of which was suggested by a Cornell Cooperative Extension agent. The idea was to not only monitor surface level soil moisture but also soil moisture at the depth of roots as well. However, this system still would’ve required a degree of custom work and the use of 2 schedule 13.5 PVC pipes to ensure cables aren't exposed and mice can't chew on them, which might be more difficult to deploy. We also found out the Watermark Soil Moisture Sensors have a lifespan of only 2 years, and we’d prefer a lifespan of around 5. We originally hoped to stick with Tektellic Clover Agricultural Sensors given their simplicity in deployment, collecting 6” soil moisture, 6” soil temperature, ambient humidity, and ambient temperature or light intensity with battery lifespans of 5-10 years at low cost. Unfortunately, the readings proved to be too unreliable for use, and we had to turn to the only other soil moisture sensor we knew of at a similar cost point: the Dragino SE01-LS LoRaWAN Soil Moisture & EC Sensor. Although these sensors are from China, the U.S. distributor based in California, Choovio, was very easy to work with and helpful over phone calls and emails. Because the Dragino sensors have separate sensor and radio components, we used some schedule 40 PVC pipes to encase the cords connecting them to protect against environmental and animal damage. The cords were longer than 3m, so we used 10’ of PVC pipe, cut it at 9’, and then used a 90-degree elbow to connect the 1’ piece and the 9’ piece together. The idea was to mount the radio component higher against a trellis post for more stability while receiving more sunlight as the LS version of the sensor comes with a solar panel embedded in the radio, while at the same time following recommendations from Cornell researchers to position the sensor units 1’ deep in the ground, 1’ away from our drip lines. To site the locations of where to place the 8 soil moisture sensors (1 per zone), we worked with researchers from the Purdue OATS Center with experience in Geographic Information Systems (GIS). Utilizing QGIS, an open source geospatial analytics software, we imported U.S. Geological Survey (USGS) Digital Elevation Models (DEM) data for our area, and segmented it based on our farm boundaries. For this project’s location, we then used a Topographic Wetness Index model and classified the output into 5 classes, keeping the middle one as an average representation of the orchard block. We then added visual boundaries of where each irrigation subzone started and stopped. Locations for placing 1 sensor per subzone were then visually determined, aiming to place them in the relative centers of the subzones in representative TWI zones based on the middle class. We synced this data into QField as a mobile platform of our QGIS project and then using a smart phone to track our location relative to the soil sensor destinations to deploy them. On site, after ensuring the areas weren’t too rocky, holes were dug 1’ deep 1’ away from the irrigation drip lines near trellis posts. There was some difficulty sticking the sensors horizontally in the soil, especially as there were dry conditions at that point in the season (late July), but was manageable. We then monitored the data collected in Grafana over the course of 2 weeks at the end of irrigation season. Data proved to be inconsistent across the zones, making us question how we placed the sensors, the methods we used to determine the sites, and if prior calibration had been required. For the 2/8 sensors that did seem to provide relevant information, we were able to see how well the soil was holding water and how long it took for the VWC (volumetric water content) to settle back down after irrigation events, leading us to decide on switching from a 2 subzone per day cycle to a 3 subzone per day cycle given the weather patterns we were experiencing. The sensors were dug up after harvest in November, and they proved much easier to remove when the ground was wetter at the time.

A major focus of this grant was to use cost-effective sensors at scale for big picture data. However at this point, we think it’s better to invest a bit more in higher quality sensors that are reliable and have support in the U.S. At Purdue, we’ve also used GroPoint Profile sensors, which collect soil moisture and soil temperature data at multiple depths. We’ve connected Dragino Waterproof Long Range Wireless LoRa Sensor Nodes to their tops to report data and deployed the units with stakes. Sensors such as these might not be feasible to be deployed in every irrigation subzone, but could be used more to ground truth other irrigation scheduling models at a broader scale.

In addition to soil moisture sensing, a representative from the Wabash Heartland Innovation Network (WHIN) in Indiana informed of us of a LoRaWAN tree dendrometer from a company called ePlant out of California that collects data on tree growth in microns and other tree characteristics, as well as environmental temperature and humidity. We decided to get 4 of their Tree Tags and deployed them in the first 4/8 irrigation subzones next to the soil moisture sensors in those locations. One downside for us was we had to use the company’s LoRaWAN gateway to start, so we set it up on a tripod outside our shop building and had everything running, but faced several issues connecting the Tree Tags until confirming there was an issue stemming from the gateway company ePlant was working with. After fixing that, we were able to collect some data, but it wasn’t until after the irrigation season. We were still able to see the natural expansion and contraction of the tree trunks between night and day which was interesting, but would like to have another chance to evaluate them during rain and irrigation events. In the future we’ll be able to integrate the devices with our own gateway.

3. Irrigation Automation 

To automate turning irrigation zones on/off, our plan was to install Strega LoRaWAN Smart Valves with 10' cables for each submain to control them remotely from anywhere. We successfully acquired 10 smart valves in the summer of 2023 but faced great difficulty in doing so. Because 10 smart valves was a small order for Strega, they had us order the valves through their Chinese partner and the LoRaWAN transmitters through them. There were no issues when paying the Chinese company for the valves, but currency conversion issues came up when making bank transactions to Strega, a Belgian-based company. Then, the smart valves were packaged and shipped in a single box to us, but got stuck in customs in Memphis and an additional payment was required to finally get the package to us in NY. After receiving the smart valves, we were notified we'd need to make a firmware upgrade. Fortunately, the added wait gave us time to think more about the configuration of our submain boxes, which have been wooden to date and starting to fall apart. As part of an expansion project on another section of our farm, concrete submain boxes are being implemented as a more structurally sound alternative, and now we're planning on replacing our existing submain boxes with the same material. This will also allow for a more stable smart valve deployment and mitigate against flooding and damage concerns. When implementing, the valve portion of the smart valve replaced the previous manual valve at a pipe diameter size of DN50 or 2” and is high pressure rated at PN20. The wire to the actuator (the control and transmission portion) is run in 10’ schedule 40 PVC pipe up the nearest row post and secured with the end of the pipe to the post. This ensures data transmission/communication between the gateway and smart valve can be kept above ground and interference won’t occur with the zone box lid. In the summer of 2024, we successfully installed a new concrete zone box and smart valve in the irrigation zone closest to our gateway. A slight modification was made for the setup where an additional row post was added and the transmitter was fastened to the post facing inside the row to mitigate the risk of a tractor accidentally hitting it. The smart valve was turned on/off during our irrigation season through the use of a TagoIO dashboard for simplicity in testing since TagoIO (an IoT dashboard company) had an existing integration with Strega smart valves. Once the free data limit was reached, the smart valve’s physical backup mechanism was tested successfully for the tail end of the irrigation season to continue watering the zone. In the summer of 2025, we configured 7 more smart valves and installed them as we replaced old wooden submain boxes with concrete boxes. Significant verification was practiced to ensure everything was working, and the first few times we switched zones on/off from the app, we would manually check to make sure it had occurred. For the first week or so, things worked well and we were able to remotely change zones from anywhere, including 2 hours away in one instance, as long as our smart phones had internet connection. One issue we did face was we consistently exceeded the data limits for our TagoIO plan, even when we moved to a paid plan, due to the fact that we weren’t parsing payloads to remove unnecessary variables from being processed and stored. We also didn’t have time at that point in the season to deal with this, so we frequently had to keep bumping the limits up and paying a bit extra. Towards the end of the irrigation season, we found more issues with the valves themselves which were supplied by Strega’s valve manufacturing partner in China, including inconsistent/unreliable openings where valves didn’t always open/close fully, times where the valves’ motors would continue working after already being fully opened/closed, and times where they simply wouldn’t do anything even though downlink commands were properly sent and verified. After harvest and when all valves were opened for winterization, 4/8 of the valves didn’t respond to downlink commands, and they had only been in the ground for 6 months. Based on these results, we’ve decided if we were to continue with a LoRaWAN smart valve setup, we would use the Strega electronic boxes but an American company’s solenoid valves for more reliability and support if something went wrong.

4. Weather Data Collection 

Concerns earlier in the summer of 2023 arose when it appeared Davis weather stations didn't have a supportive LoRaWAN integration, and individual components for the only LoRaWAN-specific option we could find were ordered from a company based in China. However, once we acquired everything, we found out that we had to source the tripod mounting brackets ourselves, as the company in China only worked with local distributors for those parts and there weren’t any distributors in the US or anywhere else as far as we could tell. We considered the Davis Vantage Pro2 Weather Station as well since it’s widely used in the agricultural industry, however we felt that the weather stations that are part of the NEWA IPM program could provide us and other northeastern farms with an additional added value through being able to connect the weather stations to the NEWA website and run pest, disease, and crop models based on the local weather data collected, leading us to favor weather stations compatible with this integration. Therefore, to study weather differences near and away from Lake Ontario, in 2025 we were planning on doing a weather data study with a KestrelMet 6000 Weather Station. From talks with fellow growers, this weather station was recommended to us as the best option compatible with the NEWA system. The KestrelMet 6000 can be purchased either to upload data via Wi-Fi or cellular connection, and we’d hoped to use Wi-Fi to avoid the monthly cellular costs. However, we found out our Wi-Fi router could not be dual band in order to be compatible, which ours unfortunately are. Therefore, the company recommended the AgroMET & IP-100 Package, which comes with a unit that can be plugged into a Wi-Fi router and connects to the weather station up to 100 ft away. We set up the weather station with a mount post on our deer fence surrounding the orchard block associated with this grant with the solar panel facing south. We were able to collect data on an AmbientWeatherNet portal, but we noticed that no precipitation data was showing up, even after heavy rain events. We ended up working with the company over the course of several weeks to troubleshoot and swap various parts out to no avail. We decided to ship the unit back so it could be tested and have since received the unit from the company after verification that everything should be in order and will look to redeploy when the weather is nicer again. In our original grant submission we’d hoped to work with 2-3 other farms with already-established weather stations in the NEWA system to compare weather patterns over a period of time, but unfortunately the main weather station we’d hoped to get data from has since been retired. As an alternative, we’re considering fabricating some metal frames for the Chinese LoRaWAN weather station we’d ordered back in the summer of 2023 to fill this need.

5. Asset Tracking 

In early September 2025 at the beginning stages of harvest, we verified LoRaWAN coverage for a Digital Matter Oyster LoRaWAN GPS Tracker from our gateway location to Lake Ontario while driving a tractor. We then used Velcro tape to place 4 trackers on 4 harvest platforms to keep track of harvest progress. The platform locations were viewable on both the TagoIO mobile app and on laptops with the TagoIO online dashboard. The GPS trackers were used to view live locations of harvest platforms, check historical progress, and reference locations when driving out to harvest platforms to check on employees. The location accuracy was solid for these purposes but would not be something to use with precision implements. The devices worked well for about a week but then we noticed issues with the rate data was coming in. They’d been programmed to transmit data every 2-10 seconds but some were transmitting as little as once per hour, leading to inaccurate live locations. After discussing this with Purdue OATS Center researchers, it was determined the issue was likely due to battery limitations as the devices only use 3 AA batteries for power and the high data rate of 2-10 seconds was probably draining it too fast. We looked into other Digital Matter products but unfortunately the wired options that could be connected to equipment batteries or fuse boxes aren’t FCC compliant in the U.S. and therefore unavailable. We explored other vendor options as well such as those offered by Tektellic, but they don’t provide the level of positioning accuracy to see machinery locations within specific tree rows and are more used for transportation and logistics purposes. Therefore, our best option seems to be to reconfigure the devices for 5–10-minute transmissions instead. This won’t give us the same level of data that we’d hoped for in terms of closer live locations and speed tracking, but it will likely give us a better balance with battery power and reduce the number of times the batteries need to be swapped out.

6. Fuel Tank Monitoring 

After much searching, we were able to determine a suitable fuel tank level sensor that fits our needs. In the summer of 2023, two options that had been evaluated were Dragino’s LDDS20 LoRaWAN Liquid Level Sensor and IOT Factory’s Fuel-Water LoRaWAN Sensor (Ultrasonic). The issue we faced with the Dragino sensor was it requires a slightly flat surface at the bottom of a fuel tank, and in our case our tanks are perfect cylinders. For the IOT Factory sensor (and in general), we require LoRa products that can operate at the US frequency level (US915), but unfortunately IOT Factory doesn’t offer the US frequency for this specific product. We discussed options with a former extension agent from North Dakota State University who has published extension reports on LoRaWAN implementation on farms, however the recommended products couldn’t be used for our scenario. In the summer of 2025, we evaluated products offered by GAOTek, Daviteq, and finally settled on a product offered by Tekelek/Rochester Sensors that best fits our needs at a reasonable price. The distributor, Timitoo Tank Monitoring Solutions, provided us with TEK 888 LoRaWAN Ultrasonic Subband 2 915 fuel tank monitors with threading that we screwed onto the tops of our 2 diesel fuel tanks in place of some caps. We were successfully able to connect the devices to our ChirpStack server and get raw data into TagoIO. We have yet to complete payload parsing/decoding to read actual data from the devices. We may also have to adjust how far the sensors tighten into the tank, as we noticed during install that the threads on our tanks are less than on the sensor. The general recommendation from Timitoo was to check if the liquid in the tank can reach all the way to the top. If it does, then we’ll need to screw the sensor only as far down as the threads on the tank go so it doesn’t come in contact with the content of the tank. If there is plenty of distance, then we’ll need to screw the sensor in as far as it can go.

6a. Storage Temperature Monitoring

While not originally in the scope of our grant project, another application we discovered was using simple LoRaWAN temperature/humidity sensors for monitoring conditions in our cold storages remotely. After purchasing some Dragino LHT65N-E31F LoRaWAN Temperature & Humidity Sensors, we deployed 3 in 3 storages on the walls near the center entrances where we had digital monitors that had to be checked manually. The sensors were able to send data via LoRaWAN even though they were inside separate metal buildings. We were able to monitor the data and the data proved consistent from manual verification of the existing digital monitors. We’re now considering adding additional sensors in other facilities for maintenance purposes, and even adding more sensors in the cold storages to know the temperatures of different locations around bins of fruit that are stored there. While an unexpected avenue for the grant, it has actually shown some of the most promising results.

7. Dashboard Integration 

When starting the grant project, we’d hoped to utilize the free, open source dashboard Grafana to synthesize all data points collected to one location for ease of use for farmers, meaning all soil moisture sensor systems would be displayable as graphs live and over time, fuel tanks would show their levels, and the locations of vehicles would be shown on a map, for example, all in the same place. In the summer of 2024, an iteration of the Purdue OATS Center’s custom data pipeline, Avena, was implemented halfway for initial testing of a cloud-based data management system. Accessible from anywhere, the data pipeline components streamlined data flow and minimized cost for a cloud-based system. ChirpStack was primarily used within Avena to connect the gateway, the first smart valve, and four soil moisture sensors and then monitor the quality of data communications. In the summer of 2025, work was continued in this area with the support of researchers from the Purdue OATS Center. First, 8 Tektellic Clover Ag Sensors and the 8 Dragino soil moisture sensors were successfully added through the entire data pipeline and visualized in Grafana. The dashboard was made publicly available and data collected during this time was made available to IoT4Ag’s SPRING educational modules for students to have an opportunity to work with sensor data not just from Purdue’s ACRE research farm but also a commercial farm/orchard setting. As we attempted to move more systems to Grafana, limitations became apparent in that many features required for agricultural dashboards were not available unless external plugins were developed for their specific use cases. These include the ability to easily import updated basemap imagery, draw field boundary polygons and create irrigation schedules. In general, we hoped to simplify backend challenges in the data pipelie for applications such as sending downlink commands to smart valves to turn them on/off so if issues occurred, they’d be easier to solve. Plus, Grafana is not as mobile friendly to date, although dashboards can be accessed from any device with internet access. Therefore, we decided to focus exclusively on TagoIO, which we already had experience with from the smart valves. Some advantages of this new approach are it simplified our data pipeline (now only the default gateway manager, ChirpStack, and TagoIO need to be managed), the ability to parse payloads live with TagoIO’s features, create dashboards very quickly, automate devices out of the box, and now deploy them to mobile applications using TagoRUN. Some disadvantages are TagoIO has data retention limits (up to 9 years of storage), limits on the number of messages that can be sent per month (unless paying for more), and pricing tiers that can restrict the number of devices a farm can connect affordably. The data limits especially stress the importance of payload parsing, which is easier being able to do it live in the TagoIO platform, but still requires a level of coding. We were able to use ChatGPT and import sensor documentation into chats, add specifications on variables we wanted to save and how the data would be used, and get mostly correct payload parser scripts to copy/paste into TagoIO, but it wasn’t always the best. TagoIO does offer engineering services and users can pay a fee for payload parsers for each device they use, but it can be expensive if just used for a farm setting. Hybrid approaches to the data pipeline were explored as well, especially with an interest in being able to store historical data permanently, but nothing seemed comprehensive enough to work. While TagoIO enables you to export data to databases and in file formats, it would be ideal to be able to continue viewing all data collected in the same dashboard.

In the summer of 2025, we had room in our grant to get an inexpensive drone, the DJI Mini 4 Pro, and test if we could conduct orchard mapping and acquire updated basemap imagery at a more affordable cost. We were successfully able to fly the drone using maps generated from WaypointMap Premium, an affordable online tool for mapping autonomous missions for supported drones, including the DJI Mini series. Flights were tested at various heights above the ground, and we were able to get the most complete orchard maps when flying at the maximum allowed altitude (slightly under 400 ft) but got much better resolution when flying lower to the ground, such as 90 ft. The maps generated from WaypointMap glitched a bit for us, particularly when attempting to use hundreds of waypoints for lower altitude flights, leading us to consider whether it fully met our needs for large-scale farm mapping. Battery limitations were also an issue (40 minutes of flight time but really closer to 30 considering safety procedures), but it’s not an uncommon problem for drones. We were able to complete a full map of a small orchard section and stitch the images together using a free trial of Pix4D. However, when we overlayed the results in QGIS, there were some discrepancies. For those interested in large scale drone mapping, we suggest exploring higher-end drones equipped with RTK GPS for enhanced precision, along with more advanced autonomous drone software for efficient extensive area land coverage

Because of the nature of our project, experimentation and testing of each objective have been frequent and throughout the development process, reflective of a true R&D phase. To make the system more resilient, we’ve started with our focus on the closest block of orchard to our gateway and tested the system over longer periods to observe data collection and infrastructural stability, all while learning how to adapt our systems to the weather and environment of the Northeast.