Page 1 of 1

Direct control of DIO module?

Posted: 12 Nov 2021, 16:56
by archi
Hi, we're currently using the RevPi because the form factor is so amazing for our customers.
On the software side we are using custom images based on Raspbian.

Now we'd like to offer our customers the option to trigger some specific action when a button is pressed; and maybe offer some visual feedback. For that the RevPi DIO module seems like a natural fit.
But due to the nature of our product we can not just install the default image and enable the pictory web service.

From the GitHub I could figure out that
1. you're using a custom kernel module to control the DIO boards and
2. I can talk to the .ko using either the python bindings (revpimodio2) or the C API (as the piTest does).
So that part seems pretty straightforward.
But from what I could gather, the actual hardware configuration seems to depend on pictory.
Is there a way to circumvent that?

E.g. could I configure a sample RevPi with pictory, export some configuration data and then just put that into our image? Or set the configuration from my program?

Best regards,
Sebastian

(Feel free to reply in either German or English; I just stuck to English so international users might find this more helpful :))

Re: Direct control of DIO module?

Posted: 12 Nov 2021, 17:13
by nicolaiB
Hi Sebastian,

Pictory is used to configure the device configuration and stores the configuration in json format. Our piControl driver looks for such configuration in /etc/revpi/config.rsc. Therefore it should be sufficient to generate the config once with pictory and just ship it with your custom image. You could also write this configuration by yourself. Just have a look into the json file.

Nicolai