Writing to RevPiLED doesn't work

MaltarLED · Post by **MaltarLED** » 16 Jan 2023, 16:32

Hello,

I came across a problem when writing to a RevPiLED register from Codesys. For example, when I set the Bit3 and Bit7, the piTest reads value 1 on RevPiLED register, also the A2 LED doesn't turn red nor the WD is reset. Is there something regarding the using of the Revolution Pi Connect IO Mapping that I should be aware about?

Best regards.

Post by **u.biakoup** » 17 Jan 2023, 13:13

Hello MaltarLED,

To be able to operate the LEDs on RevPi connect, it is necessary to know the arrangement of the bits corresponding to each LED. The following articles explain how it works:

https://revolutionpi.com/tutorials/soft ... i-connect/

https://revolutionpi.com/tutorials/stat ... verwenden/

Best Regards

Ulrich Kouatang Biakoup | Technical Support

MaltarLED · Post by **MaltarLED** » 19 Jan 2023, 10:39

Hello Ulrich,

thank you for your response. I will try to explain my problem in details.

I am using RevPi Connect S model with CODESYS Control for Raspberry Pi SL. In my program code, I oscillate bit4 every 1 second and bit7 every 8 seconds (LED A3 green and Watchdog as described here: LED A3 green) of the byte in RevPiLED in RevPi Connect device.

On the device I see a A3 LED flickering green (not oscillating every one second), and the watchdog is not reset.
Using the piTest -r RevPiLED, the value read corresponds to the one seen in Codesys.

The same Codesys program ran on the RevPi Connect+ feat. CODESYS controller behaves as expected.

Post by **giuseppe** » 16 Feb 2023, 10:27

Hello MaltarLED,

I made a test setup for this and unfortunately could not control the LEDs except for A2 via Codesys.
I have created a bug report for this.

Best regards
Giuseppe Pagano

MaltarLED · Post by **MaltarLED** » 06 Mar 2023, 11:06

Hello Giuseppe,

thanks for the info. Please update me when the bug gets fixed.

Best regards.

Post by **giuseppe** » 06 Apr 2023, 14:42

Hello MaltarLED,

I found the solution to the problem in a forum post.
You simply have to deactivate GPIO_A_B in the Codesys device tree.

Take a look at the following post.
RevPi CONNECT+, CODESYS, RevPiLED doesn't work as expected

Best regards
Giuseppe Pagano

MaltarLED · Post by **MaltarLED** » 27 Apr 2023, 09:35

Thank you for the answer.