Embodiments described herein generally relate to systems and methods for managing nutrient dosages for a grow pod and, more specifically, to providing nutrients containing water to plants in moving carts based on nutrient dosages.
While crop growth technologies have advanced over the years, there are still many problems in the farming and crop industry today. As an example, while technological advances have increased efficiency and production of various crops, many factors may affect a harvest, such as weather, disease, infestation, and the like. Additionally, while the United States currently has suitable farmland to adequately provide food for the U.S. population, other countries and future populations may not have enough farmland to provide the appropriate amount of food.
Controlled environment growing systems may mitigate many of the negative factors affecting traditional harvests. These controlled environment growing systems may include a predetermined nutrient dosage to be applied to plant matter within the growing system, a predetermined amount of light to be provided to the plant matter within the growing system, and the like. However, this may not account for conditions particular to some the controlled environment growing systems, which may reduce crop yields and/or increase operating costs. Accordingly, a need exists for improved systems and methods for managing sustenance dosages in a controlled environment growing system and collecting improved growing procedures.
In one embodiment, a system for implementing modified recipes in a plurality of grow pods includes a remote computing device communicatively coupled to the assembly line grow pod, the remote computing device including a processor and a computer readable and executable instruction set, which when executed, causes the processor to receive a first recipe associated with a first physical parameter, receive a request from the assembly line grow pod for a recipe, determine whether the assembly line grow pod includes the first physical parameter, in response to determining that the assembly line grow pod includes the first physical parameter, implement the first recipe at the assembly line grow pod, in response to determining that the assembly line grow pod does not include the first physical parameter, determine a physical parameter of the assembly line grow pod, modify at least one characteristic of the first recipe to create a modified recipe based at least in part on the determined physical parameter of the assembly line grow pod, and implement the modified recipe at the assembly line grow pod.
In another embodiment, a method for applying recipes in a plurality of assembly line grow pods includes receiving a first modified recipe from a first assembly line grow pod, the first assembly line grow pod including a first physical parameter, receiving a second modified recipe from a second assembly line grow pod, the second assembly line grow pod including a second physical parameter that is different than the first physical parameter, receiving a request from a third assembly line grow pod for a modified recipe, determining that the third assembly line grow pod includes the first physical parameter or the second physical parameter, in response to determining that the third assembly line grow pod includes the first physical parameter, implementing the first modified recipe at the third assembly line grow pod, and in response to determining that the third assembly line grow pod includes the second physical parameter, implementing the second modified recipe at the third assembly line grow pod.
In yet another embodiment, a a method for implementing a recipe within an assembly line grow pod includes identifying a type of plant matter to be grown within the assembly line grow pod, retrieving a stored recipe from a remote computing device based at least in part on the type of plant matter, modifying at least one characteristic of the stored recipe to create a modified recipe based at least in part on a physical parameter of the assembly line grow pod, dispensing nutrients to at least one cart in accordance with the modified recipe, detecting an output of plant matter on the at least one cart from dispensing the modified recipe, determining that the output of plant matter from dispensing the modified recipe exceeds a predetermined threshold, in response to determining that the output of plant matter from dispensing the modified recipe exceeds the predetermined threshold, storing the modified recipe on the remote computing device, and dispensing nutrients to a second plurality of carts in accordance with the stored modified recipe.
The embodiments set forth in the drawings are illustrative and exemplary in nature and not intended to limit the disclosure. The following detailed description of the illustrative embodiments can be understood when read in conjunction with the following drawings, where like structure is indicated with like reference numerals and in which:
Embodiments disclosed herein include multiple assembly line grow pods communicatively coupled to one another via a central computing entity. The multiple assembly line grow pods may include a first set of grow pods having tracks of a first length and a second set of grow pods having tracks of a second length. In other embodiments, the multiple assembly line grow pods may have different numbers of water manifolds and/or different overall sizes of the assembly line grow pod. The central computing entity is configured to receive a modified recipe from a grow pod of the first set, associate the modified recipe with the first set of grow pods, and provide the modified recipe to the first set of grow pods for use in future harvests. In this way, improved recipes may be shared among grow pods with similar characteristics. The systems and methods for managing nutrient dosage for a grow pod incorporating the same will be described in more detail below.
As used herein, the term “plant matter” may encompass any type of plant and/or seed material at any stage of growth, for example and without limitation, seeds, germinating seeds, vegetative plants, and plants at a reproductive stage.
Referring initially to
Referring to
The connection portion 102c generally connects the track 102 at the ascending portion 102a to the track 102 at the descending portion 102b. The track 102 at the connection portion 102c may be generally level, such that the track 102 at the connection portion 102c does not move upward or downward in the vertical direction (e.g., in the +/−y-direction as depicted in the coordinate axes of
The track 102 at the descending portion 102b moves downward in the vertical direction (e.g., in the −y-direction as depicted in the coordinate axes of
Referring particularly to
The lighting system 206 includes one or more electromagnetic sources to provide light waves in one or more predetermined wavelengths that may facilitate plant growth. Electromagnetic sources of the lighting system 206 may generally be positioned on the underside of the track 102 such that the electromagnetic sources can illuminate plant matter in the carts 104 on the track 102. The assembly line grow pod 100 may also include one or more sensors (not depicted) positioned on the underside of the track 102 to detect growth and/or fruit output of plant matter positioned within carts 104 on the track 102, and the one or more sensors may assist in determining when plant matter positioned within the carts 104 is ready for harvest.
The harvester system 208 generally includes mechanisms suitable for removing and harvesting plant matter from carts 104 positioned on the track 102. For example, the harvester system 208 may include one or more blades, separators, or the like configured to harvest plant matter. In some embodiments, when a cart 104 enters the harvesting region 209, the harvester system 208 may cut plant matter within the cart 104 at a predetermined height. In some embodiments, a tray of the cart 104 may be overturned to remove the plant matter within the cart 104 and into a processing container for chopping, mashing, juicing, etc. In some embodiments, plant matter may be grown in the carts 104 without the use of soil, such as by a hydroponic process or the like. In these configurations, minimal or no washing of the plant matter may be necessary prior to processing at the harvester system 208. In some embodiments, the harvester system 208 may be configured to automatically separate fruit from plant matter within a cart 104, such as via shaking, combing, etc. In embodiments, plant matter remaining on the cart 104 after harvesting may be reused in subsequent growing processes. If the plant matter is not to be reused, the plant matter within the cart 104 may be removed from the cart 104 for processing, disposal, or the like. In embodiments, different assembly line grow pods may have a different length of track 102 evaluated between the seeding region 109 and the harvesting region 209. The length of the track 102 between the seeding region 109 and the harvesting region 209 may generally be indicative of the overall size of the assembly line grow pod 100, and affects the length of time for a cart 104 to move between the seeding region 109 and the harvesting region 209. For example, the longer the track 102, the longer it may take the cart to move from the seeding region 109 to the harvesting region 209. Accordingly, nutrient recipes may be modified to accommodate longer or shorter grow times for assembly line grow pods having longer or shorter tracks 102, as described in greater detail herein.
After the plant matter within the cart 104 is harvested by the harvester system 208, the cart 104 moves to the sanitizer system 210. In embodiments in which remaining plant matter in the cart 104 after harvesting is not to be reused, the sanitizer system 210 is configured to remove the plant matter and/or other particulate matter remaining on the cart 104. The sanitizer system 210 may include any one or combination of different washing mechanisms, and may apply high pressure water, high temperature water, and/or other solutions for cleaning the cart 104 as the cart 104 passes through the sanitizer system 210. Once the remaining particulate and/or plant matter is removed in the cart 104, the cart 104 moves into the seeding region 109, where the seeder system 108 deposits seeds within the cart 104 for a subsequent growing process, as described in greater detail herein.
Referring again to
In embodiments, the assembly line grow pod 100 includes the master controller 106 that is communicatively coupled to one or more of the seeder system 108, the harvester system 208 (
In embodiments, the assembly line grow pod includes the watering system 107 that generally includes one or more water lines 110, which distribute water and/or nutrients to carts 104 at predetermined areas of the assembly line grow pod 100. For example, in the embodiment depicted in
Referring to
In
The assembly line grow pod 100 includes a nutrient doser 420 in fluid communication with at least one of the vertical water lines 110a through a nutrient channel 430. The nutrient doser 420 is configured to dispense nutrients into the vertical water line 110a to form a nutrient/water mixture that passes through the vertical water line 110a. The nutrient/water mixture may pass through the vertical water line 110a to the horizontal water lines 110b, and is dispensed from the horizontal water lines 110b to plant matter within the carts 104a-h. While the embodiment depicted in
The nutrient doser 420 is communicatively coupled to the master controller 106. In some embodiments, the nutrient doser 420 communicates with the master controller 106 through a wired connection. In other embodiments, the nutrient doser 420 includes network interface hardware such that the nutrient doser 420 wirelessly communicates with the master controller 106 through the network 850. The operations of the nutrient doser 420 may be controlled by the master controller 106. For example, the master controller 106 sends an instruction to the nutrient doser 420 for mixing certain amount of nutrients with water, in some embodiments.
Each of the horizontal water lines 110b is coupled to one of a plurality of water manifolds 410a-410h. Each of the water manifolds 410a-410h includes a plurality of water outlets 412 that output water into a cart, such as one of carts 104a-104h, placed under the corresponding water manifold 410a-410h. While
Each of the water manifolds 410a-410h include one or more valves 411 for opening or closing the water outlets 412. Each of the water manifolds 410a-410h may output certain amount of water and/or nutrients into the carts 104a-104h passing under each of the water manifolds 410a-410h through the selective opening and closing of the one or more valves 411.
The water manifolds 410a-410h may be communicatively coupled to the master controller 106. In some embodiments, the water manifolds 410a-410h communicate with the master controller 106 through a wired connection. In other embodiments, the water manifolds 410a-410h includes network interface hardware such that the water manifolds 410a-410h wirelessly communicate with the master controller 106 through the network 850. The operation of the one or more valves 411 may be controlled by the master controller 106. For example, the master controller 106 sends an instruction to the water manifold 410a for output certain amount of nutrients containing water into the cart 104a.
In embodiments, the master controller 106 stores nutrient dosages for various plants, and instructs the water manifolds 410a-410h and the nutrient doser 420 to output a specific water/nutrient mixture to plant matter on the carts 104a-104h. The nutrient dosages stored in the master controller may include nutrient dosages associated with a type of plant matter and nutrient concentration in water. Exemplary nutrient dosages are shown in the Table 1 below.
The master controller 106 may include a computing device 130. The computing device 130 may include a memory component 840, which stores systems logic 844a and plant logic 844b. As described in more detail below, the systems logic 844a may monitor and control operations of the assembly line grow pod 100. For example, the systems logic 844a may monitor and control operations of the nutrient doser 420 as well as the water manifolds 410a through 410h. The plant logic 844b may be configured to determine and/or receive a recipe for plant growth and may facilitate implementation of the recipe via the systems logic 844a. For example, a recipe for a plant determined by the plant logic 844b includes predetermined nutrient dosages, and the systems logic 844a may instruct the nutrient doser 420 to mix water with nutrients based on the nutrients dosages.
Additionally, the master controller 106 is coupled to a network 850. The network 850 may include the internet or other wide area network, a local network, such as a local area network, a near field network, such as Bluetooth or a near field communication (NFC) network. The water manifolds 410a-410h and/or the nutrient doser 420 may be coupled to the network 850. The network 850 is also coupled to a user computing device 352 and/or a remote computing device 354. The user computing device 352 may include a personal computer, laptop, mobile device, tablet, server, etc. and may be utilized as an interface with a user. As an example, a user may send nutrient dosages to the master controller 106 for implementation by the assembly line grow pod 100.
Similarly, the remote computing device 354 may include a server, personal computer, tablet, mobile device, etc. and may be utilized for machine to machine communications. As an example, if the master controller 106 determines a type of seed being used (and/or other information, such as ambient conditions), the master controller 106 may communicate with the remote computing device 354 to retrieve a previously stored recipe for those conditions. As such, some embodiments may utilize an application program interface (API) to facilitate this or other computer-to-computer communications.
The master controller 106 may identify the plants (e.g., as one of the types of plant matter A-D as shown in Table 1 above) in the carts 104a-104h. For example, the master controller 106 may communicate with the carts 104a-104h and receive information about the plant matter in the carts 104a-104h. As another example, the information about the plant matter in the carts 104a-104h may be pre-stored in the master controller 106 when the seeder system 108 (
Once the identification of plant matter in the carts 104a-104h is determined, the master controller 106 instructs the nutrient doser 420 to mix water with nutrients based on nutrient dosages. As one example, the master controller 106 may determine that each of the carts 104a-104h carry plant matter A, as identified above in Table 1. Then, the master controller 106 instructs the nutrient doser 420 to mix water with nutrients to make water having 100 ppm of Nitrogen, 6 ppm of Phosphorus, and 70 ppm of Potassium based on the nutrient dosage for plant A, as shown in the Table 1 above. As another example, if the master controller 106 determines that the carts 104a-104h carry plant matter B, the master controller 106 instructs the nutrient doser 420 to mix water with nutrients to make water having 200 ppm of Nitrogen, 11 ppm of Phosphorus, 130 ppm of Potassium based on the nutrient dosage for plant matter B as shown in the Table 1 above. The nutrient doser 420 may change the nutrient concentration of water provided to the vertical water line 110a, in real-time according to the identification of plants being carried in the carts 104a-104h.
In embodiments, the nutrient dosages for plants may be updated based on information on harvested plants. For example, if the harvested plant matter A is generally smaller in size than an ideal plant matter A, the nutrient dosages for plant matter A may be adjusted to raise the concentration of Nitrogen, such as via a user input into the user computing device 352. As for another example, if the fruits of the harvested plant matter B are not as big as ideal fruits for the plant matter B, the nutrient dosages for plant matter B may be adjusted to raise the concentration of Phosphorus.
The memory component 840 may store operating logic 942, the systems logic 844a, and the plant logic 844b. The systems logic 844a and the plant logic 844b may each include a plurality of different pieces of logic, each of which may be embodied as a computer program, firmware, and/or hardware, as an example. A local interface 946 is also included in
The processor 930 may include any processing component operable to receive and execute instructions (such as from a data storage component 936 and/or the memory component 840). The input/output hardware 932 may include and/or be configured to interface with microphones, speakers, a display, and/or other hardware.
The network interface hardware 934 may include and/or be configured for communicating with any wired or wireless networking hardware, including an antenna, a modem, LAN port, wireless fidelity (Wi-Fi) card, WiMax card, ZigBee card, Bluetooth chip, USB card, mobile communications hardware, and/or other hardware for communicating with other networks and/or devices. From this connection, communication may be facilitated between the computing device 130 and other computing devices, such as the user computing device 352 and/or remote computing device 354.
The operating logic 942 may include an operating system and/or other software for managing components of the computing device 130. As also discussed above, systems logic 844a and the plant logic 844b may reside in the memory component 840 and may be configured to perform the functionality described herein.
It should be understood that while the components in
Additionally, while the computing device 130 is illustrated with the systems logic 844a and the plant logic 844b as separate logical components, this is also an example. In some embodiments, a single piece of logic (and/or or several linked modules) may cause the computing device 130 to provide the described functionality.
Referring now to
The memory component 340b may store operating logic 642, the analysis logic 344c, and the communication logic 344d. The analysis logic 344c and the communication logic 344d may each include a plurality of different pieces of logic, each of which may be embodied as a computer program, firmware, and/or hardware, as an example. A local interface 646 is also included in the remote computing device 354, and may be implemented as a bus or other communication interface to facilitate communication among the components of the remote computing device 354.
The processor 630 may include any processing component operable to receive and execute instructions (such as from a data storage component 636 and/or the memory component 340). The input/output hardware 632 may include and/or be configured to interface with microphones, speakers, a display, and/or other hardware.
The network interface hardware 634 may include and/or be configured for communicating with any wired or wireless networking hardware, including an antenna, a modem, LAN port, wireless fidelity (Wi-Fi) card, WiMax card, ZigBee card, Bluetooth chip, USB card, mobile communications hardware, and/or other hardware for communicating with other networks and/or devices. From this connection, communication may be facilitated between the remote computing device 354 and other computing devices, such as the user computing device 352 and/or computing device 130.
The operating logic 642 may include an operating system and/or other software for managing components of the remote computing device 354. As also discussed above, analysis logic 344c and the communication logic 344d may reside in the memory component 340b and may be configured to perform the functionality, as described herein.
It should be understood that while the components in
Additionally, while the remote computing device 354 is illustrated with the analysis logic 344c and the communication logic 344d as separate logical components, this is merely exemplary. In some embodiments, a single piece of logic (and/or or several linked modules) may cause the remote computing device 354 to provide the described functionality.
Referring to
Recipes and improved recipes may be communicated between the remote computing device 354, the user computing device 352, the assembly line grow pod 100 and the second and third assembly line grow pods 300, 400 via the network 850. For example, the remote computing device 354 may send a recipe to the computing device 130 for implementation by the assembly line grow pod 100.
In some embodiments, the analysis logic 344c of the remote computing device 354 may be configured to receive a recipe, an update to a recipe, and/or an upgrade to a recipe such as from the user computing device 352. The analysis logic 344c may then determine differences between the received recipe and a stored recipe that is stored by the remote computing device 354. If the differences satisfy a predetermined threshold, the remote computing device 354 may alter the stored recipe and/or save the received recipe for communicating the update and/or upgrade to the grow pods 100, 300, 400 via the communication logic 344d. In embodiments, the predetermined threshold may include a configurable threshold that is selected to achieve a desired increase in crop yield or other measurable output of the assembly line grow pods 100, 300, 400, as described in greater detail herein. Additionally, the analysis logic 344c may be configured to determine a compensation mechanism for the user based on the changes made to the recipe and/or assembly line grow pod 100 and facilitate payment of the determined compensation. As such, the remote computing device 354 may include and/or be coupled with an invoicing server, a payments server, and/or other computing device for actually making and/or accounting for the compensation to be paid to the user.
Various methods for modifying recipes and identifying modified recipes for growing plant matter within an assembly line grow pod, such as the assembly line grow pod 100 are described below.
Referring collectively to
It should be understood that blocks 802-810 may be performed by a suitable computing device, such as the computing device 130, the remote computing device 354, and/or the user computing device 352. As described above, a recipe may be utilized to facilitate growth of plant matter within an assembly line grow pod, such as the assembly line grow pods 100, 300, 400. The recipe may include nutrient doses to be applied to plant matter within carts 104 in the assembly line grow pods 100, 300, 400, such as via the nutrient doser 420. In some embodiments, the recipe may include other parameters, such as an amount of light provided by the lighting system 206, a preferred temperature of the grow pod (as may be maintained by the airflow system 111 depicted in
In embodiments, the first physical parameter of the first assembly line grow pod 100 may include a length of the track 102 evaluated between the harvesting region 209 and the seeding region 108 of the first assembly line grow pod 100. In general, the length of the track 102 of the first assembly line grow pod 100 may be indicative of the overall size of the assembly line grow pod 100, and may be related a grow time of plant matter grown in the assembly line grow pod 100. For example, the longer the distance between the seeding region 108 and the harvesting region 209, the longer it may take a cart 104 to move from the seeding region 108 to the harvesting region 209, resulting in a longer grow time. Accordingly, recipes suitable for an assembly line grow pods with comparatively long tracks 102 (evaluated between the seeding region 108 and the harvesting region 209) may not be suitable for assembly line grow pods having comparatively shorter tracks 102.
In other embodiments the first physical parameter may include other physical features of the assembly line grow pod 100 that may have an impact on the effectiveness of a recipe. For example and without limitation, the first physical parameter may include an area occupied by the assembly line grow pod 100, an overall height of the assembly line grow pod 100 evaluated in the vertical direction (e.g., in the +/−y-direction of the coordinate axes depicted in
By confirming that the assembly line grow pods 100, 300 both comprise the same first physical feature, the system (e.g., the computing device 130, the remote computing device 354, and/or the user computing device 352) may ensure that the first modified recipe is appropriate for use in the second assembly line grow pod 300. If the assembly line grow pods 100, 300 do not comprise the same first physical feature, as described above, a stored recipe may be implemented at the second assembly line grow pod 300. For example, the stored recipe may be appropriate for a physical feature (e.g., a length of the track, an overall size, an overall height, etc.) of the second assembly line grow pod 300. Alternatively, the second assembly line grow pod 300 may implement a modified recipe from another assembly line grow pod comprising the second physical feature if the assembly line grow pods 100, 300 do not comprise the same first physical feature.
Referring collectively to
It should be understood that blocks 902-910 may be performed by a suitable computing device, such as the computing device 130, the remote computing device 354, and/or the user computing device 352. Furthermore the method depicted in
Referring collectively to
It should be understood that blocks 1002-1012 may be performed by a suitable computing device, such as the computing device 130, the remote computing device 354, and/or the user computing device 352. Furthermore the method depicted in
In some embodiments, the stored modified recipe 1012 may be evaluated by the system (e.g., the computing device 130, the remote computing device 354, and/or the user computing device 352) to determine the nature of the improvement of the stored modified recipe 1012. For example, the system (e.g., the computing device 130, the remote computing device 354, and/or the user computing device 352) may compare the stored modified recipe with other stored recipes to isolate and identify the characteristic or characteristics contributing to the improved output of the stored modified recipe. More particularly, the system (e.g., the computing device 130, the remote computing device 354, and/or the user computing device 352) may identify a parameter of the stored modified recipe that exceeds a corresponding characteristic of other stored recipes. As one example, the stored modified recipe may include a comparatively higher amount of potassium as compared to other stored recipes. In that example, the higher amount of potassium may be identified as the cause and/or one of the causes of the improved results of the stored modified recipe. By identifying the characteristic or characteristics contributing to the improved output of the stored modified recipe, other stored recipes may be modified to obtain improved results.
Referring collectively to
It should be understood that blocks 1102-1114 may be performed by a suitable computing device, such as the computing device 130, the remote computing device 354, and/or the user computing device 352. Furthermore the method depicted in
In embodiments, the first physical parameter of the first assembly line grow pod 100 may include a length of the track 102 evaluated between the harvesting region 209 and the seeding region 108 of the first assembly line grow pod 100. In general, the length of the track 102 of the first assembly line grow pod 100 may be indicative of the overall size of the assembly line grow pod 100, and may be related a grow time of plant matter grown in the assembly line grow pod 100. For example, the longer the distance between the seeding region 108 and the harvesting region 209, the longer it may take a cart 104 to move from the seeding region 108 to the harvesting region 209, resulting in a longer grow time. Accordingly, recipes suitable for an assembly line grow pods with comparatively long tracks 102 (evaluated between the seeding region 108 and the harvesting region 209) may not be suitable for assembly line grow pods having comparatively shorter tracks 102.
In other embodiments the first physical parameter may include other physical features of the assembly line grow pod 100 that may have an impact on the effectiveness of a recipe. For example and without limitation, the first physical parameter may include an area occupied by the assembly line grow pod 100, an overall height of the assembly line grow pod 100 evaluated in the vertical direction (e.g., in the +/−y-direction of the coordinate axes depicted in
By confirming that the assembly line grow pods 100, 300 both comprise the same first physical feature, the system (e.g., the computing device 130, the remote computing device 354, and/or the user computing device 352) may ensure that the first recipe is appropriate for use in the second assembly line grow pod 300. If the assembly line grow pods 100, 300 do not comprise the same first physical feature, as described above, the physical parameters of the second assembly line grow pod 300 may be determined, and at least one parameter of the first recipe is modified. As one example, if the second assembly line grow pod 300 has a longer track 102 than the first assembly line grow pod 100, then a concentration of nutrients to be applied to the carts 104 on the second assembly line grow pod 300 may be reduced. For example, the ppm concentration of nitrogen, phosphorus, and/or potassium may be reduced in the modified recipe to accommodate the comparatively longer grow time of plant matter in the second assembly line grow pod 300 owing to the comparatively longer track 102. As another example, if the second assembly line grow pod includes fewer water manifolds 410a-h than the first assembly line grow pod 100, then the ppm concentration of nitrogen, phosphorus, and/or potassium may be increased in the modified recipe to accommodate the comparatively fewer opportunities for the carts 104 on the second assembly line grow pod 300 to receive a dose of nutrient(s).
In some embodiments, subsequent to implementing the modified recipe at the second assembly line grow pod 300, the output of the second assembly line grow pod 300 may be detected and compared to a predetermined threshold, and stored, as described above with respect to blocks 1008-1012 of
In some embodiments, the first recipe may be received from a testing chamber 500 at block 1102. In these embodiments, as the testing chamber 500 would not comprise the same physical parameters as the second assembly line grow pod, the system (e.g., the computing device 130, the remote computing device 354, and/or the user computing device 352) would proceed through blocks 1110 and 1112, determining the physical parameters of the second assembly line grow pod 300 and modifying at least one parameter of the first recipe received from the testing chamber 500.
As illustrated above, various embodiments for managing nutrient dosages for a grow pod are disclosed. The embodiments include systems and methods for receiving modified recipes and for modifying recipes based at least in part on physical parameters of the assembly line grow pod. By modifying the recipes and/or providing modified recipes based on physical parameters of the assembly line grow pod, the recipes may be modified to optimize plant matter output. These embodiments create a quick growing, small footprint, chemical free, low labor solution to growing microgreens and other plants for harvesting. These embodiments may create recipes and/or receive recipes that dictate the timing and wavelength of light, pressure, temperature, watering, nutrients, molecular atmosphere, and/or other variables the optimize plant growth and output. The recipe may be implemented strictly and/or modified based on results of a particular plant, tray, or crop. Furthermore by modifying the recipes and/or providing modified recipes based on physical parameters of different assembly line grow pods, similar crop outputs may be maintained across different assembly line grow pods.
While particular embodiments and aspects of the present disclosure have been illustrated and described herein, various other changes and modifications can be made without departing from the spirit and scope of the disclosure. Moreover, although various aspects have been described herein, such aspects need not be utilized in combination. Accordingly, it is therefore intended that the appended claims cover all such changes and modifications that are within the scope of the embodiments shown and described herein.
It should now be understood that embodiments disclosed herein includes systems, methods, and non-transitory computer-readable mediums for managing nutrient dosages for a grow pod. It should also be understood that these embodiments are merely exemplary and are not intended to limit the scope of this disclosure.
This application claims the benefit of U.S. Provisional Application Ser. No. 62/519,346 filed on Jun. 14, 2017 and entitled “Systems and Methods for Collecting Improved Growing Procedures from a Grow Pod,” and U.S. Provisional Application Ser. No. 62/519,633 filed on Jun. 14, 2017 and entitled “Systems and Methods for Managing Nutrient Dosage for a Grow Pod,” the contents each of which are hereby incorporated by reference in their entirety.
Number | Date | Country | |
---|---|---|---|
62519346 | Jun 2017 | US | |
62519633 | Jun 2017 | US |