new MIO led flashing

[ydna1979]

After I could not determine why the "IN" led on my MIO kept flashing(with nothing hooked up to any input) I bought a new one. The new on has the same issue. I have gone through all the guides and I cannot figure it out. I have 2 other MIO modules hooked up with no issue.

[stefanh]

Hi ydna1979,

In which color does the IN LED flash?

Description of the MIO module: The IN LED lights up green as soon as an input is used.
If the voltage at one of the inputs is above the defined value of 10 V, the LED flashes red.

Stefan
FAE | Support

[Arjen]

Hello,

I have exactly the same problem. Have a new MIO and IN LED keeps flashing red. No inputs attached.

Have you figured out a solution yet?

[nicolaiB]

Hi Arjen,

could you please share the output of `piTest -d` and `dmesg | grep piControl` ? Thanks.

Nicolai

[Arjen]

Hello Nicolai,

Thank you for your quick response.

piTest -d has output:

Code: Select all

Address: 0 module type: 95 (0x5f) RevPi Core V1.2
Module is present
     input offset: 0 length: 6
    output offset: 6 length: 5

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

dmesg | grep piControl output:

Code: Select all

[    2.893033] piControl: loading out-of-tree module taints kernel.
[    2.897255] piControl: built: Tue Nov 29 07:41:58 UTC 2022
[    2.897274] piControl: RevPi Core
[    2.897279] piControl: MAJOR-No.  : 242
[    2.897444] piControl: MAJOR-No.  : 242  MINOR-No.  : 0
[    2.906537] piControl: read file finished, f_pos=10128
[    2.906572] piControl: 2 devices found
[    2.906576] piControl: 116 entries in total
[    2.906676] piControl: MIO configured(addr:32, ent-cnt:108, conf-no:0, conf-base:61, dio hdr:0x3520,aio_i hdr:0x9320, aio_o hdr:0x9320)
[    2.906684] piControl: dio  :00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[    2.906689] piControl: aio-i:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01
[    2.906692] piControl: aio-o:01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[    2.906701] piControl: cl-comp:  0 addr  6  bit ff  len   8
[    2.906706] piControl: cl-comp:  1 addr 45  bit 0f  len   4
[    2.906709] piControl: cl-comp:  2 addr 46  bit 00  len  64
[    2.906713] piControl: cl-comp:  3 addr 56  bit 00  len 128
[    2.931497] piControl: serial device /dev/ttyAMA0 opened
[    2.931526] piControl: set priority of spi0 to 54
[    2.933215] piControl: piIO thread started
[    2.933227] piControl: RevPiDevice_init()
[    2.933231] piControl: Enter Init State
[    2.933564] piControl: PADS 0 = 0xffffffff   slew=1  hyst=1  drive=7
[    2.933571] piControl: PADS 1 = 0xffffffff   slew=1  hyst=1  drive=7
[    2.933575] piControl: PADS 2 = 0xffffffff   slew=1  hyst=1  drive=7
[    2.933585] piControl: piControlInit done
[    2.933841] piControl: Enter PresentSignalling1 State
[    2.972980] piControl: Enter InitialSlaveDetectionRight State
[    2.973518] piControl: Enter ConfigRightStart State
[    2.983539] piControl: Enter ConfigDialogueRight State
[    3.018114] piControl: GetDeviceInfo: Id 118
[    3.048779] piControl: found 2. device on right side. Moduletype 118. Designated address 32
[    3.048789] piControl: input offset     11  len  34
[    3.048792] piControl: output offset    45  len  27
[    3.049328] piControl: Enter SlaveDetectionRight State
[    3.060091] piControl: Enter InitialSlaveDetectionLeft State
[    3.060883] piControl: Enter EndOfConfig State
[    3.060888] piControl: Device  0: Addr  0 Type  95  Act 1  In   6 Out   5
[    3.060894] piControl:            input offset      0  len   6
[    3.060898] piControl:            output offset     6  len   5
[    3.060901] piControl:            serial number 1  version 1.2
[    3.060905] piControl: Device  1: Addr 32 Type 118  Act 1  In  34 Out  27
[    3.060915] piControl:            input offset     11  len  34
[    3.060919] piControl:            output offset    45  len  27
[    3.060922] piControl:            serial number 27002  version 1.0
[    3.060926] piControl:
[    3.060935] piControl: Adjust: base 0 in 0 out 6 conf 0
[    3.060939] piControl: Adjust: base 11 in 11 out 45 conf 72
[    3.060944] piControl: After Adjustment
[    3.060946] piControl: Device  0: Addr  0 Type  95  Act 1  In   6 Out   5
[    3.060950] piControl:            input offset      0  len   6
[    3.060953] piControl:            output offset     6  len   5
[    3.060956] piControl: Device  1: Addr 32 Type 118  Act 1  In  34 Out  27
[    3.060960] piControl:            input offset     11  len  34
[    3.060963] piControl:            output offset    45  len  27
[    3.060966] piControl:
[    3.178091] piControl: start data exchange
[    3.418111] piControl: MIO Initializing...(devno:1, addr:32, conf-base:61)
[    3.418121] piControl: search mio conf(index:0, addr:32)
[    3.421250] piControl: headers of mio:aio conf request: 0x3520, response:0x20a0
[    3.424195] piControl: headers of mio:aio_i conf request: 0x9320, response:0x80a0
[    3.427137] piControl: headers of mio:aio_o conf request: 0x9320, response:0x80a0
[    3.427146] piControl: MIO Initializing finished(devno:1, addr:32)
[    3.430727] piControl: headers of mio:dio data request: 0x 920, response:0x11a0
[    3.433631] piControl: headers of mio:aio data request: 0x4220, response:0x51a0
[    3.433638] piControl: set BridgeState to running
[   14.028204] piControl: recv len from pibridge err(got:0, exp:20)
[   14.028218] piControl: talk with mio for aio data error(addr:32, ret:-70)
[   18.468308] piControl: recv len from pibridge err(got:0, exp:20)
[   18.468319] piControl: talk with mio for dio data error(addr:32, ret:-70)
[   35.778083] piControl: recv len from pibridge err(got:0, exp:20)
[   35.778094] piControl: talk with mio for dio data error(addr:32, ret:-70)
[16827.817616] piControl: recv len from pibridge err(got:0, exp:20)
[16827.817627] piControl: talk with mio for dio data error(addr:32, ret:-70)
[19229.491438] piControl: recv len from pibridge err(got:0, exp:20)
[19229.491449] piControl: talk with mio for aio data error(addr:32, ret:-70)
[86177.964109] piControl: recv len from pibridge err(got:0, exp:20)
[86177.964121] piControl: talk with mio for dio data error(addr:32, ret:-70)

Seems there some error in the bridge, is that possible?

[Arjen]

If i try to read a value from the MIO with piTest, it seems to work as expected.

A signal conditioner on analog input 1 gives this output:

Code: Select all

2 Byte-Value of AnalogInput_1: 2644 dez (=0a54 hex)
2 Byte-Value of AnalogInput_1: 2644 dez (=0a54 hex)
2 Byte-Value of AnalogInput_1: 2649 dez (=0a59 hex)
2 Byte-Value of AnalogInput_1: 2657 dez (=0a61 hex)
2 Byte-Value of AnalogInput_1: 2674 dez (=0a72 hex)
2 Byte-Value of AnalogInput_1: 2695 dez (=0a87 hex)
2 Byte-Value of AnalogInput_1: 2717 dez (=0a9d hex)
2 Byte-Value of AnalogInput_1: 2749 dez (=0abd hex)
2 Byte-Value of AnalogInput_1: 2776 dez (=0ad8 hex)
2 Byte-Value of AnalogInput_1: 2805 dez (=0af5 hex)
2 Byte-Value of AnalogInput_1: 2841 dez (=0b19 hex)
2 Byte-Value of AnalogInput_1: 2864 dez (=0b30 hex)
2 Byte-Value of AnalogInput_1: 2887 dez (=0b47 hex)
2 Byte-Value of AnalogInput_1: 2913 dez (=0b61 hex)

etc.

But the input of analog input 2 (which is not connected), gives output:

Code: Select all

2 Byte-Value of AnalogInput_2: 10770 dez (=2a12 hex)
2 Byte-Value of AnalogInput_2: 10770 dez (=2a12 hex)
2 Byte-Value of AnalogInput_2: 10770 dez (=2a12 hex)
2 Byte-Value of AnalogInput_2: 10770 dez (=2a12 hex)
2 Byte-Value of AnalogInput_2: 10770 dez (=2a12 hex)

etc.

Why is it that the analogInput that doesnt have anything attached give a higher value than the one with a signal conditioning 0-10V output attached?

Could this be part of the red flashing LED error?

Hope this can help.