Milker

Description, License, Development Status
Project: Milker. Description: Development of an autonomous milking ongoing robot (AMOR).
Keywords	milking robot; agriculture; automation; Landwirtschaft; Milchroboter
License	Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)
Status	inactive
Levels Achieved	prototype development
Communication
Contact	Jan R.B.-Wein <radagast@ciry.at>
Creators, Contributors	Please add creators or contributors
Discussion	OSEG Welcome Group on Telegram Forum (archive)
Developers' repositories	https://github.com/faerietree/autonomous_milking_ongoing_robot http://github.com/faerietree/manipulator (universal robotic manipulator)
Data
Avai­lable meta­data (OKH Meta-Data)	n.a.

Current focus

• Adhere to full modularity following complex conventions. (To establish this system is a long process but increases open source consistency, reusability drastically to the benefit of the entire eco system and targetting long time critics.)
• Shift resources towards the important module universal robotic manipulator which replaces several custom machine designs with one standard construction whose functionality changes depending on the program. Tribute to Jef Murray, a skilled artist that has left our case too early.

Reasons:

• Saving a lot of hardware + software development, documentation, testing, ...
• Open source projects are like milk readily available at a low price compared to drinking water and closed source products. Farms and ecological projects alike require an increase in efficiency to become independent from subsidies and donations respectively to the benefit of the entire community.
• The previous milking robotic manipulator design is not certain to work with a real animal due to the limited workspace and the difficult base construction which requires reattachment (thus remachining) if there are more sizes or kinds of animals to be milked, e.g. goat or sheep teats pointing sidewards previously were hard to dock to.

Motivation for an autonomous milking ongoing robot (AMOR)

An autonomous system results in the following dis-/advantages:

• + Indepence (no more need to be there to milk morning and evening, 7days/week)
• - Machine service increases.
• - Electricity and likely water bill increases.
• + Technical knowledge increases, hence perhaps some other good robot ideas may evolve.
• + Animals can decide themselves when to get milked.
• + Free decision of how often a day they are milked. (falsely labelled "interval" in DeLaval commercial milking system, milking frequency per day is the correct term though, because an interval is a time span).
• + => Increased milk yield
• + Concentrated feed can be delivered automatically and according to milk delivered (in realtime).
• + => Easier and more adapted feeding ... a cow that produces more milk, requires more food if the rest state (e.g. influenced by activity) is equal.
• - Animals' possible illness not realized early enough. => Action taken too late. => Animal could die.
• - Gathering at Milking robot leaves behind a lot of unusable muddy terrain at entrance (doors, feeding, water pits in general).
• - Higher complexity in separation of milk for calves, though of course possible if valves and cleaning system are integrated.
• + Driving out and in of cattle no longer necessary as animals can get milked outside.
• + Tough animals can be tied to the robot frame automatically (and freed just in time).
• + Less material required (much shorter vacuum and milk tubes as compared to conventional non-automated distributed [at cow/goat..] milking)
• ... and likely others.

An ongoing (uninterrupted, self-sustained) system results in the following (dis-)advantages:

• - Higher complexity (more modules and systems that interact).
• - Software more complicated because of the difficult interaction and the many modules that depend on each other and have to be monitored (e.g. if new food arrives, then the robot must realize it to open the gates (because the container needs weather protection) or be notified by the harvest robot).
• + Independence of any external supplies.

   ** Water (heavily dependent on environment)
   ** Power (Solar/Heat/Water/Microbial fuel cell replaces Grid)
   ** Food (requires the worlddevelopment eco harvest robot, high level inter-machine communication).

• - Redundancy of susceptible subsystems (Electronics, in general: The more complex the system the higher the vulnerability).
• + Less cabling (length), water pipe laying.
• + Less maintenance (if redundant and watchdog or error correction exists, one can wait for enough minor errors to accumulate before taking the system apart).
• ... and likely others.

High Level Overview

Separation in Subproblems & Technological Difficulties

AMOR of several submodules:

• MECHANICAL CONSTRUCTION
  • - Difficult to achieve a robust, lightweight (for truck to lift) & cheap system at the same time.
  • + Rain serves as a water supply and natural (ecologic) and self-sustained washing. -> So AMOR must be waterproof!
• VACUUM SYSTEM
  • - Difficult to be flexible in frequency (provide user settings) and keep it simple at the same time.
  • + Could be used for several other functionality than milking (doors, ...). => No hydraulics needed. Update: We have settled on keeping it all electric as it's much cheaper and we need electricity anyway.
  • Note: As the robotic manipulator should be flexible anyway as it could be hit by the cow, compressible air/vacuum could serve this purpose, too - but price of vacuum cylinders and the vulnerability to leakage remains a problem.
  • Vacuum pump: Any pump should do, as the required vacuum levels are low and we don't have a lot of volume to keep free of gases in a mobile system because there is not much piping.
• STORAGE CONSTRUCTION
  • Milk
  • Food
  • Water
  • Energy
  • Database for animals milk (amount, properties, ...)
  • Database for organization of the cow's fertile cycle, ...
• SENSORICS
  • Milk properties (flow rate, derivations of that, TODO)
  • Robotic manipulator (3D camera, washing mechanism)
  • Animal within milking construction => Door states.
• ELECTRONICS
  • Control of Doors.
  • Control of Feeding (derived from amount of milk), but also accept some user constraints (lower / upper bounds for each type of food respectively).
  • Control of Robotic manipulator (joints, gripper).
  • Collection & storage of the stored animal & product data.
• SOFTWARE
  • Microcontroller programs capable of controlling at least two AMOR system blocks (stacked next to each other).
  • compare ELECTRONICS.

Mechanic structure

The mechanic structure is free to choose. Builders might have their own preference of how to assemble a milking robot structure. Some may choose to bolt sqaure beams together, the others might prefer welding (Schweissen) steel or if they have a TIG (Tungsten) welder even aluminium.

For convenience I design and post my structure as a base and hope you give back your improvements to it by mentioning it in the forum, uploading to our repository or any other possibiity you see as appropriate.. http://www.youtube.com/watch?v=GawGF-8rVSY

Video of Prototyp 3 CAD

This video demonstrates how the robotic manipulator is about to work as well as the door mechanism:

Simulation of Milking robot

Vacuum System

Power system

Several ideas for autonomous power can be found in the forum. The easiest solution for now will be to attach a truck or emergency generator (UPS) or simply an extension cord. So we need a possibility to plug it into the grid (1-phase might be too low, but let's go for that first as the vacuum system needs by far less energy in a mobile robot than in a conventional one).