top of page

Why did we develop Modbus Modern API?

Three months ago we released our first SaaS product RoboMon to monitor the industrial robots Availability, Performance, and Condition from anywhere, anytime and any device. While we were developing we had to use Modbus programming interface to communicate to the industrial robots over Modbus protocol.



Three months ago we released our first SaaS product RoboMon to monitor the industrial robots Availability, Performance, and Condition from anywhere, anytime and any device. While we were developing we had to use Modbus programming interface to communicate to the industrial robots over Modbus protocol. We were looking for an Application Programming Interface (API) to communicate to the devices that support Modbus protocol.


Three months ago we released our first SaaS product RoboMon to monitor the industrial robots Availability, Performance, and Condition from anywhere, anytime and any device. While we were developing we had to use Modbus programming interface to communicate to the industrial robots over Modbus protocol. We were looking for an Application Programming Interface (API) to communicate to the devices that support Modbus protocol.

Our requirements are like the API

  1. should be very simple to use

  2. to provide response asynchronously for a given request

  3. to notify the application with response periodically for a request submitted once

We couldn't find such an API in both open source and commercial versions. And the API that are available in the market forces the developer to write more lines of code and doesn't fit well into our event driven architecture.

As RoboMon polls the robots as a Modbus client periodically, periodic poll is supported in an end product like OPC-UA Server and not at the API level.

We want the device communication to be clearly separated out from the application code so that the application can focus only on what to do with the data.

So, we quickly built device agnostic, vendor agnostic Modbus TCP Client API which helps RoboMon communicate to the Robots.

Since there is no such simple API available in the market, we released our 'Modbus Modern API' as a developer SDK for the developers who build industrial applications.

Modbus Modern API is built for the developers by the developers.

Now, two well-known R&D institutes have been using our Modbus SDK.

  1. Navy Research Lab, USA

  2. BHEL R&D division, India

We are happy that we are enabling the developers to focus on what to do with the data collected from the device.

And RoboMon also is running successfully on Cloud by receiving the robot's data collected by our DaacoX IoT Edge Software.


We have published the source code of our .NET based Modbus TCP Client API in GitHub under Apache-2.0 License. GitHub link

Comentários


bottom of page