Current DIO Firmware source code

[Projektraum]

Hi,
we are currently facing some problems with the piControl process (too many communication errors), and seems that it could be related to the use of newer Core3 images with old DIO firmware.
To develop our product, we used the IODeviceExample (https://github.com/RevolutionPi/IODeviceExample) as base code and modified it to have some extra features.
Unfortunately, we checked today the RevolutionPi repository, and the project seems to be exactly the one we used few years ago.

Short description of the problem:
We have a python script, which uses the revpimodio2 to control the DIO inputs and outputs, running on a Core3 with image 2020-03-02-revpi-stretch.img
After some random time, the piControl reports the error "too many communication errors". We already checked the electrical part, but there is nothing that may cause
a big disturbance on the piBridge. kern and daemon logs also does not show any relevant information about what triggered the error.

An old topic from the forum (viewtopic.php?t=909) mentions something regarding older and new firmware instability, that's why we want
to update our custom firmware.

Questions:
a) If we do a firmware update using the "piTest -f" command, all our modifications will be lost, correct?
b) In case the answer from previous question was yes, is the current DIO Firmware source code available somewhere? Or an up-to-date version of the IODeviceExample project, containing the last communication fixes/improvements?
c) Is there a way to use the "piTest -f" command with the firmware file path? This would be helpful to update remotely the firmware of all RevPis that we have at costumers.

Many thanks in advance!
Nathan Nyland

[dirk]

Hi, it seems like you are using an outdated image. Please use the Checklist to update your device.
https://kunbus-gmbh.atlassian.net/servi ... 1095710293
Updating the firmware of your IO-devices can help, but maybe your problems will already disappear by running the checklist.

The IO Device example is related to the communication between the devices that are connected via the PiBridge.
So this is running on the other side of the PiBridge inside the piControl driver. So you can update the firmware without loosing your canges.
Have a look here how a firmware update works:
https://revolutionpi.com/tutorials/imag ... re-update/

[Projektraum]

Hi dirk,

thanks for your reply!
I will try to follow your instructions and do some tests.
In case I cannot bring it to run or I have problems, I will write here again.

Many thanks!
Nathan