The Industrial Raspberry Pi Forum

Posted: **09 Jan 2024, 17:48**

Hello,

I am new to Raspberry Pi and I’ve recently encountered some issues while trying to connect the RevPi Connect+ with the DIO module.

I have configured all modules using PiCtory, following the PiCtory Checklist and the Video Tutorials on YouTube. However, I’ve noticed that the power LEDs on both the DIO and RevPi Connect+ modules are still red, even though the other signal LEDs are green.

I have also checked the status and connection of the modules using a command via SSH and the results are like this:

Code: Select all

pi@RevPi-SPKT:~ $ piTest -r RevPiStatus,b
1 Byte-Value of RevPiStatus: 00000001

pi@RevPi-SPKT:~ $ piTest -r Status,b
2 Byte-Value of Status: 00000000 00000000

pi@RevPi-SPKT:~ $ piTest -r Output_Status,b
2 Byte-Value of Output_Status: 00000000 00000000

And

Code: Select all

pi@RevPi-SPKT:~ $ piTest -d
Found 2 devices:

Address: 0 module type: 105 (0x69) RevPi Connect V1.0
Module is present
     input offset: 113 length: 6
    output offset: 119 length: 5

Address: 31 module type: 96 (0x60) RevPi DIO V1.4
Module is present
     input offset: 0 length: 70
    output offset: 70 length: 18

I’ve seen some topics about the problem, but I still can’t fix it.
I’m currently stuck and any help would be greatly appreciated. Thank you in advance!

Best Regards, alenken

Posted: **10 Jan 2024, 12:12**

alenken, Firstly, thank you very much for the information you have collected. This is really helpful and gives me a good overview.
The value 1 in the variable RevPiSatatus means that at least one IO module is connected which has not been configured with PiCtory. See here:
https://revolutionpi.com/tutorials/soft ... rect=en-US

This contrasts with the output of "piTest -d". I would have expected an error to occur here. So it is questionable what is really not working in the system.

Anyway, I recommend updating your system using the following checklist and restoring it to factory settings.
https://kunbus-gmbh.atlassian.net/servi ... /836468748

If you are interested in tracing this error, I recommend that you make a backup beforehand.

Posted: **10 Jan 2024, 15:36**

Hello!

Please correct me if I'm wrong but this is bit 0 that is blinking, which means "picontrol running", so everything seems in order.

When I had the exact same issue it was because I messed up the X4 connections as described here:
https://revolutionpi.com/tutorials/uebe ... en-connect
and here:
https://revolutionpi.com/tutorials/over ... wer-supply

I don't remember what went wrong back then.

Posted: **11 Jan 2024, 02:27**

Thank you very much! The RevPi Connect+ is running properly now! The versions of the extension modules have been updated to newer versions than before, which are V1.4 of DIO and V1.3 of AIO.

I’m not sure if I set up some environment variables that conflict with the system, or if the old versions just can’t perform correctly. Previously, I only installed librealsense2 from the IntelRealsense source and set up some Python virtual environments. Could you explain to me what might have happened here?

Based on this experiment, I think I should try installing all the equipment with RevPi before installing anything else on it

Code: Select all

pi@RevPi44885:~ $ piTest -d
Found 3 devices:

Address: 0 module type: 105 (0x69) RevPi Connect V1.0
Module is present
     input offset: 202 length: 6
    output offset: 208 length: 5

Address: 31 module type: 96 (0x60) RevPi DIO V1.5
Module is present
     input offset: 89 length: 70
    output offset: 159 length: 18

Address: 30 module type: 103 (0x67) RevPi AIO V1.5
Module is present
     input offset: 0 length: 20
    output offset: 20 length: 4

Best Regards, alenken

Posted: **11 Jan 2024, 13:36**

Hi alenken, thank you for your positive feedback and good luck with the products and the Revolution Pi community!

The Industrial Raspberry Pi Forum

Status-LEDs

Status-LEDs

Re: Status-LEDs

Re: Status-LEDs

Re: Status-LEDs

Re: Status-LEDs