Dear All, I am trying to update the firmware of a MIO module, but it fails consistently. What am I doing wrong, please? $ piTest -f update firmware fail Here is the context, the MIO Module is the only one connected. $ piTest -d Found 2 devices: Address: 0 module type: 105 (0x69) RevPi Connect V1.0 M...

Just a side note: That page has a broken image link. That makes it look like it is no longer valid.

Dear Mats-Olov, It does indeed redirect. The IT guys at your customer site are right. So you options are: 1) On the firewalls of your VPN, open port 41080 too. This is the path you chose and It is a good one. Some IT departments may be reluctant to comply, though. 2) Reconfigure the web server runni...

Dear Nicolai, Thank you for the welcome. Happy to make detailed reports, of course. I do need this fixed. :-) I did some more troubleshooting today and I got things to work, but I still need help understanding the logic of the way the configuration works. But first, the good news: when I enable both...

Dear EcoMan,

Your kernel log seems to have a few ominous messages about `/etc/fstab`. Can you please post the contents of that file for us to look at? Have you considered file system corruption?

Kees Jan

Dear All, After reading the code for `revpypiload` I traced the problem to https://github.com/naruxde/revpipyload/blob/master/revpipyload/revpipyload.py. The issue is that it instantiates both an MQTT server and a something called the `procimgserver`. My theory is that if you enable MQTT writing (li...

Dear All, I dug a little deeper into this and found that the MQTT server creates its own instance of `RevPiModIO()`. That got me thinking that perhaps these instances might be overwriting one another's IO output list. Does anyone have a working example? I'd love to learn what I am doing wrong. Anyon...

Dear All, I enabled MQTT write in the revpipyload configuration. Publishing a value of 1024 to /revpi000/set/PwmDutycycle_1 causes the PWM output to go to 1024 for one cycle only, then it falls back to 0. I checked the logs: no errors. I checked that no other processes are active on /dev/PiControl0 ...