Can I use REST API with standalone RIO

groov RIO
1

Hi,
In our project we are hoping to use groovRIOs (84) as standalone RIOs to read some analog I/O.

We need to integrate this into our current control system, which is JVM-based.

Is it possible to read/write a standalone RIO (no EPIC, MQTT or node-red) using a HTTP REST API?

This API is on the web site: (Swagger UI)

If this is the correct yaml file, what I’m not sure about is the device value and the module index for a standalone unit.

The data sheet says each RIO has a yaml file describing its API, but I’m not sure if the above is that yaml file.

Is it possible to use HTTP/REST to communicate with a standalone RIO?

If so, could someone send me the yaml file or a URL for the yaml file (assuming it is not the one above)?

If the above file is the correct yaml file. What should device and moduleIndex be for a standalone RIO?

Thank you for any help!

1 Like
2

Hi Kim. Welcome to the forums.

Yes. Every RIO has a RESTful server built in, so you can easily make calls to it and return your data and control its outputs.

Think of a RIO as a single-channel EPIC module.
EPIC modules are from 0 to a max of 15. Since a RIO is just one module, it is always module zero.
Every bit of code you write for a RIO will also work on an EPIC, just by changing the module index (unless of course, you only want to talk to the first EPIC module in its rack) and any code you write for an EPIC will work on a RIO, just change the module index to zero.

BTW, I’ve asked @torchard to add a word or three to the developer.opto site to make that super clear - RIO is always module index zero.

Hope that gets you up and running.
Should be a quick roll out.

2 Likes
3

Thanks @Beno! I was hoping that was the case.

Thank you very much for the quick response, and I will watch for any more information that gets posted.

1 Like