The agrirouter© middleware was developed to have easier access to the functionality of the agrirouter. The agrirouter© middleware is an additional layer of abstraction and provides access to the agrirouter© without deep knowledge of the underlying processes. The agrirouter© middleware manages the connections and fetches messages from the agrirouter, based on the technical messages types registered. In addition, the agrirouter© middleware provides simple data conversion from ISOXML TaskData to EFDI Telemetry Data and provides searching operations for DDIs and other parts of the specification.
The release notes can be found within this repository, please have a look at the following document - Release Notes.
The functional documentation can be found within this repository, please have a look at the following document - Functional Documentation.
The project would not have been possible without strong partners for the idea and the development. The following companies have taken an active part during the development of the agrirouter© middleware.
The initial idea for the agrirouter© middleware has been developed by the Maschinenfabrik Bernard Krone GmbH & Co. KG. The main concept is based on the idea to make the agrirouter© connection easier for third party app providers.
The Holmer Maschinenbau GmBH joined the project after the development started and added the use case of sending machine data using the agrirouter© middleware. The agrirouter© middleware is part of the communication concept between their machines and the agrirouter© on the other side.
The LMIS AG is part of the agrirouter© universe since the beginning of the project and was chosen as implementation partner for the middleware. Using an agile development process the middleware was developed in 2021/2022 and will be maintained as long as the project is active.
Without the agrirouter there would not have been such a project. The easy way to connect machines, farming software and telemetry platforms is one essential step to a strong network of agricultural machines.
The LMIS AG is providing free hosting of the agrirouter© for development purpose. All you need to do is to send a request using the contact form on the website. The hosting on the QA environment is free and won’t be charged. If you need a hosting offer for production, please send out a request as well - there are reasonable packages for everyone.
There is a public Postman workspace available, which can be used to test the agrirouter© middleware. The workspace can be found here:
If there are any questions or issues regarding the workspace, please feel free to create an issue in the GitHub repository. Thanks for your support!
The agrirouter© middleware is an abstraction to the well-known interface of the agrirouter. The agrirouter© middleware uses the interface of the agrirouter© and provides an easy way to manage applications and endpoints, send and receive messages or handle the connection to the agrirouter.
The agrirouter© middleware provides a REST interface for endpoint management, sending messages and retrieving messages. On the other hand the connection to the agrirouter© is based on the faster MQTT protocol to have live telemetry data with real push notifications. The messages from the agrirouter© are fetched, confirmed and stored within an internal database. There is no need to implement the business process on your own.
The agrirouter© middleware is ready for certification. What does this mean? By using the agrirouter© middleware you are ready to speed up the certification process, since most of the requirements are already fulfilled by the middleware. To get an overview, please see the following table of certification criteria:
| Certification criteria | Status | Comment |
|---|---|---|
Secured Onboarding |
|
The agrirouter© middleware covers the whole onboarding process. You only need to integrate a button to call one of the endpoints and add the status checking. After this you are ready to go. |
Authorization |
|
The agrirouter© middleware ships customizable redirect pages and everything you need to connect to the agrirouter© and pass the certiciation. |
Verfication |
|
The agrirouter© middleware verifies the response from the agrirouter© and adds that extra bit of security. |
Revoking |
|
If the user wants to disconnect the endpoint, the agrirouter© brings all you need to add this functionality. |
Using / Updating router devices |
|
The agrirouter© middleware is ready to use router devices and provides an easy way to update the router device. |
VCU onboarding / off-boarding |
|
Using the agrirouter© middleware to run your telemetry platform you are able to register your machines as virtual endpoints. |
agrirouter© commands |
|
Since the agrirouter© middleware is based on the agrirouter© SDKs, all the commands are supported and implemented. |
Chunking |
|
Chunking is necessary for all formats that transport "non-telemetry" data (ISOXML, SHAPE, images, videos, …) and the agrirouter© middleware is capable of it. |
Encoding |
|
All messages are encoded correctly, therefore no need to worry. |
Message addressing |
|
The agrirouter© middleware supports direct addressing as well as publishing of messages. |
Merging chunks |
|
All messages are fetched from the agrirouter© and can be downloaded even if they are chunked. |
Push notifications |
|
By default, the agrirouter© middleware uses push notifications to receive messages directly from the agrirouter©. If one of the push notifications has been missed, there is a scheduled job to fetch pending messages. |
Clean you feed |
|
With the agrirouter© you can rely on a solid mechanism to fetch all messages from the agrirouter©. Nothing will be lost. |
Error handling |
|
Errors from the agrirouter© will be transformed into speaking business errors (if necessary). |
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent