MIO / DIO / AIO connection issues

[mpandos]

Hello,
I am having the below format (attached as well)
AIO|MIO|DIO|Connect+SE (16GB)
and I am receiving the below error:

Jan 20 11:34:15 RevPi84278 kernel: piControl: recv len from pibridge err(got:0, exp:20)
Jan 20 11:34:15 RevPi84278 kernel: piControl: talk with mio for dio data error(addr:30, ret:-70)


Nothing is wired in I/O and I have energized only DIO's module output

I changed the bridge connectors, just in case one of them was faulty. In the first place I received an error between MIO|DIO, I swapped bridges and then I received an error in AIO|MIO then I took off completely the connector between AIO|MIO and replaced it with a new one, then I took an error again in MIO|DIO.

Please advise

Thanks in advance

[dirk]

Hi, could you send us a SOS-Report via SUP-5688?

[mpandos]

Thanks I will!

[dirk]

Hi I have made a test setup and can give you the following feedback
- check your PiCtory configuration and swap the modules accordingly
- change the RevPi Connect to RevPi Connect SE
The (cryptic) error from the kern.log means that piControl tries to communicate with the wrong module

Code: Select all

[  502.144748] piControl: ## address 30: incorrect module type 103 != 118
[  502.144753] piControl: ## address 29: incorrect module type 118 != 103

[mpandos]

Thanks for the reply.

So I just need to change the revpi edition to Connect SE, in address 0 and reload revpi?
I changed it!
I keep getting the same error
I am attaching the pictory config as well

[dirk]

Hello mpandos,
thank you for the SOS Report you provided via E-Mail. I have seen the errors in kern.log again. Well then I see that "piTest -d" outputs no error - OK:

Code: Select all

dirk@KUN-NB-045:~$ cat /tmp/sosreport-RevPi84278-20230125145741/sos_commands/revpi/piTest_-d
Found 4 devices:

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

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

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

Address: 29 module type: 118 (0x76) RevPi MIO V1.0
Module is present
     input offset: 0 length: 34
    output offset: 34 length: 27

Here the module configuration deviates from the one of your image.

Can you please do a fresh PiCtory configuation and pick the modules according to the hardware configuration?

Thank you & BR

[mpandos]

Thats my setup now, after updating each module one by one following your guide (https://revolutionpi.com/tutorials/imag ... re-update/)


pi@RevPi84278:~ $ piTest -d
Found 4 devices:

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

Address: 31 module type: 118 (0x76) RevPi MIO V1.0
Module is present
input offset: 202 length: 34
output offset: 236 length: 27

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

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

Here is my pictory setup.
I keep getting the same mistake

Jan 27 09:51:30 RevPi84278 kernel: piControl: recv len from pibridge err(got:0, exp:20)
Jan 27 09:51:30 RevPi84278 kernel: piControl: talk with mio for aio data error(addr:31, ret:-70)
Jan 27 09:52:44 RevPi84278 kernel: piControl: recv len from pibridge err(got:0, exp:20)
Jan 27 09:52:44 RevPi84278 kernel: piControl: talk with mio for aio data error(addr:31, ret:-70)
Jan 27 09:54:08 RevPi84278 kernel: piControl: recv len from pibridge err(got:0, exp:20)
Jan 27 09:54:08 RevPi84278 kernel: piControl: talk with mio for dio data error(addr:31, ret:-70)

[mpandos]

I finally changed all the modules. I followed the updated procedure and everything worked like a charm. So I guess there are some issues with the 1st set of modules.

[mpandos]

Hello again,

The problem is not solved after all. Tell me what kind of info you need in order to make a step-by-step debugging!

thanks

[dirk]

Hello mpandos,
good that you have more modules available and therefore the cause is on the hardware level. Unfortunately, there is no way around an RMA.
I will clarify the further steps with you in the support ticket.