takuya
Topic Author
Posts: 3
Joined: 13 Aug 2019, 05:55

DO module can't be connected

13 Aug 2019, 06:17

After using rpiboot and Win32DiskImager to rewrite the image that was in Core 3 at the time of purchase, Core 3 cannot be connected to the DO module. Until then, the connection was successful and the output from the module was correct.
Immediately after turning on the power, Core 3 was lit red, and the DO module was lit green. When the dmesg command was executed, the following error messages were displayed in large numbers.

[   37.168935] piControl: write error -5
[   37.168941] piControl: too many communication errors -> set inputs to default 0 255 0 0   0 0 0 0

The execution result of piTest -d is as follows.

Found 2 devices:

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

Address: 31 module type: 98 (0x62) RevPi DO V1.4
Module is present
     input offset: 0 length: 70
    output offset: 70 length: 18

Also, after setting correctly with piCtory, when piTest -x was executed, Core 3 was lit green and the DO module was lit red. This is the execution result of the dmesg command.

[   37.170000] piControl: write error -5
[   37.170007] piControl: too many communication errors -> set inputs to default 0 255 0 0   0 0 0 0
[   37.170254] piControl: Reset: BridgeState=2 
[   37.231772] piControl: stop data exchange
[   37.231782] piControl: write error -5
[   37.231786] piControl: dev all: send ioprotocol send error -1
[   37.231790] piControl: piIoComm_gotoGateProtocol returned 0
[   37.232975] piControl: kernel_read returned 0: b31b9e00, 5328
[   37.232999] piControl: 2 devices found
[   37.233002] piControl: 80 entries in total
[   37.233098] piControl: cl-comp:  0 addr 70  bit ff  len   8
[   37.233103] piControl: cl-comp:  1 addr 71  bit ff  len   8
[   37.233107] piControl: cl-comp:  2 addr 119  bit ff  len   8
[   37.233875] piControl: RevPiDevice_init()
[   37.233893] piControl: PADS 0 = 0x1b   slew=1  hyst=1  drive=3
[   37.233899] piControl: PADS 1 = 0x1b   slew=1  hyst=1  drive=3
[   37.233903] piControl: PADS 2 = 0x1b   slew=1  hyst=1  drive=3
[   37.233961] piControl: Enter Init State
[   37.234485] piControl: Enter PresentSignalling1 State
[   37.273343] piControl: Enter InitialSlaveDetectionRight State
[   37.273869] piControl: Enter InitialSlaveDetectionLeft State
[   37.274388] piControl: Enter ConfigLeftStart State
[   37.284668] piControl: Enter ConfigDialogueLeft State
[   37.284678] piControl: write error -5
[   37.311740] piControl: piIoComm_sendRS485Tel(GetDeviceInfo) failed 1
[   37.312271] piControl: write error -5
[   37.341754] piControl: piIoComm_sendRS485Tel(GetDeviceInfo) failed 1
[   37.342279] piControl: write error -5
[   37.371756] piControl: piIoComm_sendRS485Tel(GetDeviceInfo) failed 1
[   37.372291] piControl: write error -5
[   37.401744] piControl: piIoComm_sendRS485Tel(GetDeviceInfo) failed 1
[   37.402270] piControl: Enter EndOfConfig State

[   37.402278] piControl: Device  0: Addr  0 Type  95  Act 1  In   6 Out   5
[   37.402282] piControl:            input offset      0  len   6
[   37.402285] piControl:            output offset     6  len   5
[   37.402289] piControl:            serial number 1  version 1.2
[   37.402292] piControl: 
[   37.402303] piControl: Adjust: base 113 in 113 out 119 conf 0
[   37.402309] piControl: After Adjustment
[   37.402313] piControl: Device  0: Addr  0 Type  95  Act 1  In   6 Out   5
[   37.402317] piControl:            input offset    113  len   6
[   37.402320] piControl:            output offset   119  len   5
[   37.402325] piControl: Device  1: Addr 31 Type 32866  Act 0  In  70 Out  18
[   37.402329] piControl:            input offset      0  len  70
[   37.402332] piControl:            output offset    70  len  18
[   37.402335] piControl: 
[   37.521749] piControl: start data exchange
[   37.521759] piControl: write error -5
[   37.631742] piControl: piIoComm_sendRS485Tel(PiIoStartDataExchange) failed 1
[   37.761746] piControl: initialization of module not finished (1,0,4) -> retry
[   37.762272] piControl: Enter Initialization Retry
[   40.272893] piControl: RevPiDevice_init()
[   40.273414] piControl: Enter Init State
[   40.273938] piControl: Enter PresentSignalling1 State
[   40.313429] piControl: Enter InitialSlaveDetectionRight State
[   40.313953] piControl: Enter InitialSlaveDetectionLeft State
[   40.314472] piControl: Enter ConfigLeftStart State
[   40.324251] piControl: Enter ConfigDialogueLeft State
[   40.324260] piControl: write error -5
[   40.351740] piControl: piIoComm_sendRS485Tel(GetDeviceInfo) failed 1
[   40.352267] piControl: write error -5
[   40.381739] piControl: piIoComm_sendRS485Tel(GetDeviceInfo) failed 1
[   40.382265] piControl: write error -5
[   40.411739] piControl: piIoComm_sendRS485Tel(GetDeviceInfo) failed 1
[   40.412265] piControl: write error -5
[   40.441739] piControl: piIoComm_sendRS485Tel(GetDeviceInfo) failed 1
[   40.442262] piControl: Enter EndOfConfig State

[   40.442270] piControl: Device  0: Addr  0 Type  95  Act 1  In   6 Out   5
[   40.442273] piControl:            input offset      0  len   6
[   40.442277] piControl:            output offset     6  len   5
[   40.442281] piControl:            serial number 1  version 1.2
[   40.442284] piControl: 
[   40.442294] piControl: Adjust: base 113 in 113 out 119 conf 0
[   40.442299] piControl: After Adjustment
[   40.442304] piControl: Device  0: Addr  0 Type  95  Act 1  In   6 Out   5
[   40.442308] piControl:            input offset    113  len   6
[   40.442311] piControl:            output offset   119  len   5
[   40.442317] piControl: Device  1: Addr 31 Type 32866  Act 0  In  70 Out  18
[   40.442320] piControl:            input offset      0  len  70
[   40.442324] piControl:            output offset    70  len  18
[   40.442326] piControl: 
[   40.561742] piControl: start data exchange
[   40.561750] piControl: write error -5
[   40.671739] piControl: piIoComm_sendRS485Tel(PiIoStartDataExchange) failed 1
[   40.801742] piControl: set BridgeState to running

Execution result of piTest -d.

Found 2 devices:

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

Address: 31 module type: 32866 (0x8062) RevPi DO V0.0
Module is NOT present, data is NOT available!!!
     input offset: 0 length: 70
    output offset: 70 length: 18

Sorry for poor English using translation software. It would be helpful if you could give me advice.
 
Eduard
KUNBUS
Posts: 194
Joined: 18 Jun 2018, 16:16

Re: DO module can't be connected

13 Aug 2019, 11:20

Hello,
please query the RevPi version with "cat /etc/revpi/image-release".
 
takuya
Topic Author
Posts: 3
Joined: 13 Aug 2019, 05:55

Re: DO module can't be connected

14 Aug 2019, 06:01

Hello, Eduard.

This is the output.
2018-07-17-revpi-stretch.img
 
Eduard
KUNBUS
Posts: 194
Joined: 18 Jun 2018, 16:16

Re: DO module can't be connected

14 Aug 2019, 10:08

Can you please flash the latest image (2019-03-14)?
How this works can be found here.
 
takuya
Topic Author
Posts: 3
Joined: 13 Aug 2019, 05:55

Re: DO module can't be connected

16 Aug 2019, 08:32

I'm sorry for the late reply.
The image was updated to the latest one (2019-03-14-revpi-stretch.img), but the output of the piTest -d and dmesg commands was the same as before.
Is it a mechanical failure?

Who is online

Users browsing this forum: fzeta and 0 guests