The Industrial Raspberry Pi Forum

Hi all,
I'm about to re-commission a RevPi Connect+ to a new project, so I figured I'd do a fresh firmware install, but I'm having some issues after having installed the latest stable Buster image (2022-01-19). When opening Pictory (after having worked around the password bug), I noticed that the RevPi Connect+ itself was missing, so I dropped in one, plus a virtual Modbus RTU master. After saving this configuration and rebooting, it seems I still have some issues with the driver – if I do for instance piTest -d or piTest -x, I get a "no such device" error. Obviously I can't get Modbus to work either, but I suppose that's because of the driver problem.

I think I entered the MAC and serial correctly after installing – the password did get set to the default printed on the label, which I suppose is a good sign?

For what it's worth, I noticed that the /dev/ttyRS485 symlink doesn't exist, not sure if that means anything.

I tried to search the forum for mentions of this kind of issue, but didn't find much of relevance. A missing config.rsc file could apparently be the cause, but I do have that file where it should be.

Any clues?

Hi,

looks like the connect overlays are not loaded. Could you please share /var/log/kern.log aswell as /boot/config.txt?

Nicolai

Here they are:
/boot/config.txt: https://cumulus.glod.studio/s/sY83FTF3ANXrETS
/var/log/kern.log: https://cumulus.glod.studio/s/irwnMBGTDfEtKaG

Hi,

thanks for the files. It looks like the factory reset was not performed and therefore the device overlay is not specified in /boot/config.txt. Without this configuration the driver is not able to work. The missing factory reset also explains "the password bug". Please run revpi-factory-reset as described in our tutorial and test again.

Nicolai

I did that yesterday, but I can try again and see if the outcome is different this time.

Could you please post the complete output of the factory reset command (redact password) and the /boot/config.txt after the factory reset?

Nicolai

There we go, now it worked! The terminal output was exactly the same as last time. Only difference is apparently I typed the letters in the MAC address in lowercase last time and uppercase now. Is it case sensitive?

No, it is not case-sensitive. I usually type the letters in lowercase too. Anyway, I'm glad to hear that it is working now

Nicolai