OK, now I had this really “great” idea of writing a blog post once a month in 2021. So, let’s stumble into this and see where we go.
I started by writing about message queues. Really interesting to see how data flows from one terminal to a cloud over an interface… OK, do I need to describe an interface? Well, that’s so off topic, might be an additional blog post? 🤔
OK, let’s start with an article on UIs. Many things to discuss about User Inter….. D’oh 🤦♂️
So, I think I’ll just start with the basics:
A simple view to the world
From an IT guys perspective, the world is just about 2 things: Objects and Interfaces. Objects have Inputs and Outputs, Interfaces describe the match between two Objects’ in- and outputs to transfer information (in general: force, material or data). Too nerdy? Indeed, let’s ag-lify* that.
(*ag-lify: Put something in the context of agriculture 😉)
Objects in ag
The best way to describe an object that I found is definitely this one:
Take information (worm protein), convert information ( …. no details here …), output information ( other form of protein).
For conversion, we can just say:
“A few inputs + some logic = A few outputs”
So, in general an object has inputs, some logic inside, which can be mathematical formulars or Conditional statements (“Output 1 = Input1 if Input 3 = 5, otherwise (else) Output1 = Input2”) and one or multiple outputs.
Let the blue box be an object and the orange dots be inputs (with the one inside the object being some fixed value/attribute without any influence from outside), then this “Mozart’s hair” (actually my first shot to draw a brain 😀 ) is the conversion and the green dots are outputs.
Need another example of an object? Here we go: Tractor
The tractor has many In- and Outputs: The PTO outputs power to an attached machine. The ISOBUS breakaway outputs AND inputs ISOBUS information. For the power output, you need to input fuel into the tractor. Not to forget: The wheels output force to the ground and move it under the tractor (as long as you’re not just digging that thing deeper into the mud ).
On a field, our tractor is a bit lonely, so let’s give him a friend, e.g. a sprayer.
Now they are standing here, our tractor starts to move and …. D’Oh, the sprayer stays where it is? Yep, because without a compatible coupling, the tractor cannot transfer the information (“move on, dude”) to the sprayer.
Let’s call this coupling an interface. It’s just the connection between two objects, where the output of one object (“Move on dude”) is the input for the other object (“Should I stay or should I go now?”).
In a real world, this “Stand by me” interface is just the ball hitch. It is one of multiple interfaces though that connect machine and implement.
We have the ball hitch, maybe a PTO, hydraulic cycles and electronic connections such as ISOBUS.
But is it just ISOBUS? THE ISOBUS? The one and only that we’ve heard of so much?
Onions, oh bloody layered onions
Well, I would say, it’s a Yeah….nope 😐
Of course, ISOBUS is standardized, so you can connect multiple ISOBUS devices to one ISOBUS without burning down your tractor. But ISOBUS – as most interfaces – has different layers (sidenote: The following is simplified; if you’re interested in a full list, see the OSI Model ):
- Physical: This one describes e.g. that an INCAB connector is round and has 3 by 3 pins
- Data Link layer: That one describes, how on-off-on-off is translated into bits and bytes
- PresentationLayer: That one describes, how bits and bytes are to be interpreted
- Application Layer: What to do with those data?
In ISOBUS, there are different Applications like TaskController (TC) and Universal Terminal (UT). Each of them needs a client (on machine side) and a server (on terminal side).
Connecting a machine that only provides TC with a Terminal only supporting UT is somehow like Opening a Website with your Email program. It just doesn’t work.
To check compatibility, the AEF Database is a good place to go.
Zoom, zoom, zoom, zoom….
Let’s now go a bit closer to our tractor. If we take a closer look, it’s not just a Tractor. It’s indeed a combination of different objects: It consists of wheels, an engine, a steering wheel and sometimes a nice carpet in the drivers cap. If taking all these smaller objects (that might consist of objects which might consist of objects, which might…. you get that) together, we can recognize it as a package in a detailed view. But for a high level view, a tractor is OK as an object. All the interfaces of a tractor are those interfaces, that are not connected to any other object within the tractor.
Somehow like that: 4 Inputs (e.g. Fuel, Oxygen, Steering wheel movement, sensor input), but the inner objects convert the input information to different 3 outputs (driving speed, rotating pto, ISOXML machine Data).
(let me know if you need an example of what I meant here)
May I introduce: Process chains
But wait: If we have interfaces between 2 objects and we can convert data of one input to another output, we can build a chain. 😲
Yes, that’s correct 😊 *
(*: Imagine this like a conversation. Since I’m in home office for a while, I can just say “I’m pretty sure, that’s how conversations with other people work”)
So, let’s do this: Lets add a terminal, a modem, a cloud and a laptop and here we go: Ag-IT in a nutshell:
We translate a physical environment status (e.g. a temperature) to a sensor signal to an ISOBUS information to an ISOXML or EFDI entry, package it in some modem signal that’s converted to a Cloud API where our data just hangs around for a while until some guy (or woman) with a laptop decides, it requests some information. Stopping the chain at the user interfaces (next blog post 😉 ), that’s a – very simplified – overview of digital farming already.
Onions, oh lovely layered onions
Agreed, this layer stuff in interfaces makes the description a bit more complicated, but it has a huge advantage: Sometimes, 2 incompatible interfaces are just incompatible in certain layers, so you just have to convert these layers. Need an example?
Imagine you’re in the fields with your laptop and want to google something:
- Your laptop only supports WiFi
- The transmission tower only supports 4G
- Your Smartphone supports both and can translate between those
The upper layers (HTTPS, IP etc.) are the same, but by adding your smartphone to the system, you can setup a hotspot to “convert” from WiFi to 4G.
Asking better questions
First things first: You made it through the article. Congratulations and thank you for taking the time. If you read this, I owe you a beer. (99 bottles of beer on the wall, 99 bottles of beeeeer….) Just hit me up on LinkedIn, Xing or via mail to blog@dev4Agriculture.de.
Now, what’s the essence of all of this. Why did I even write it? Because interoperability is about compatible interfaces, interfaces with different layers and information of different types. With the implementation of IoT on farms, there are more zoom levels: Intra-Machine, Intra-Field, Intra-Process Chain, Intra-Farm, Intra-Farming Community (e.g. contractors).
IoT offers big chances but has also a potential for big confusion.
I recently talked to someone working for a college with focus on farming technology. And I really liked his answer to the question “What’s the most important thing to teach about ag IT?”:
“The best would be if people learn to ask better questions”
So, with a view to all I’ve written above, we might come up with those questions:
- Which information do I want to transfer?
- What’s the source of my information?
- What’s the destination of (the need for) my information?
- Where do I have a mismatch in my interfaces? Is there a special layer to respect?
- Which object could be fit inbetween to convert between these incompatible interfaces?
Sure, it’s not the solution for all our problems (sorry about that 🙁), but I think it’s an interesting view worth sharing and I’ld really love any feedback.
I’m yet missing a good closing for my blog articles, some inspirational catch phrase.
Let’s try that one:
Thanks for reading, I really put my heard and soil into this…
OK, agreed, I’ll find a better one next time. Thanks for reading.