Mittleres Modul nach Neustart nicht gefunden

Rund um die Hardware des Revolution Pi
User avatar
nicolaiB
KUNBUS
Posts: 869
Joined: 21 Jun 2018, 10:33
Answers: 7
Location: Berlin
Contact:

Mittleres Modul nach Neustart nicht gefunden

Post by nicolaiB »

Hallo zusammen,

seit den letzten Updates beobachten wir vermehrt folgendes Phänomen, dass nach einem Neustart des RevPi das DIO Modul nicht mehr erkannt wird. Erst ein spannungsfrei machen aller Komponenten behebt den Fehlerzustand. Unser Aufbau schaut wie folgt aus:

Code: Select all

GW-PN | DIO | RevPi C3 (Stretch) | GW-PN

Die beiden Gateways übertragen die Daten ohne Probleme ins Prozessabbild, sodass ich nicht von einem Problem mit der physikalischen Verbindung der PiBridge ausgehe.

Ist das Problem vielleicht woanders schon mal aufgetreten oder hat jemand eine Idee was die Ursache sein könnte?

Code: Select all

$ cat /etc/revpi/image-release 
2019-03-14-revpi-stretch.img

Code: Select all

$ piTest -d
Found 4 devices:

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

Address: 30 module type: 79 (0x4f) Gateway Profinet IRT V1.2
Module is present
     input offset: 0 length: 512
    output offset: 512 length: 512

Address: 31 module type: 32864 (0x8060) RevPi DIO V0.0
Module is NOT present, data is NOT available!!!
     input offset: 1024 length: 70
    output offset: 1094 length: 18

Address: 32 module type: 79 (0x4f) Gateway Profinet IRT V1.2
Module is present
     input offset: 1148 length: 512
    output offset: 1660 length: 512

Gruß Nicolai
User avatar
dirk
KUNBUS
Posts: 1926
Joined: 15 Dec 2016, 13:19
Answers: 4

Re: Mittleres Modul nach Neustart nicht gefunden

Post by dirk »

Hi Nicolai, kannst Du uns bitte das kern.log schicken?
User avatar
nicolaiB
KUNBUS
Posts: 869
Joined: 21 Jun 2018, 10:33
Answers: 7
Location: Berlin
Contact:

Re: Mittleres Modul nach Neustart nicht gefunden

Post by nicolaiB »

Hallo Dirk,

ich habe dir das Log an die Supportaddresse geschickt.

Gruß Nicolai
User avatar
dirk
KUNBUS
Posts: 1926
Joined: 15 Dec 2016, 13:19
Answers: 4

Re: Mittleres Modul nach Neustart nicht gefunden

Post by dirk »

Danke wir haben es erhalten und sind dran.
Eduard
KUNBUS
Posts: 209
Joined: 18 Jun 2018, 16:16
Answers: 0

Re: Mittleres Modul nach Neustart nicht gefunden

Post by Eduard »

Hallo Nicolai,

wann tritt dieses Problem auf, nach einem Kaltstart(Spannung aus und Spannung an des kompletten Aufbaus) oder nach einem Warmstart(reboot des RevPi)?

Gruß Eduard
User avatar
nicolaiB
KUNBUS
Posts: 869
Joined: 21 Jun 2018, 10:33
Answers: 7
Location: Berlin
Contact:

Re: Mittleres Modul nach Neustart nicht gefunden

Post by nicolaiB »

Hallo Eduard,

Das Problem tritt in beiden Fällen auf. Wir haben einige Anlagen beobachtet, wo das Modul irgendwann nicht mehr gefunden wurde (nur Updates mit Neustart), aber auch Anlagen wo es nach dem Kaltstart nicht wieder kam. In beiden Fällen hilft es das ganze System spannungsfrei zu machen (mehr als ein paar Sekunden).

Die Netzteile (Weidmüller) sind passend dimensioniert (Nur RevPi, Module und Teltonika Router).

Gruß Nicolai
Eduard
KUNBUS
Posts: 209
Joined: 18 Jun 2018, 16:16
Answers: 0

Re: Mittleres Modul nach Neustart nicht gefunden

Post by Eduard »

Wie ist der Zustand der LEDs vom RevPi?
Leuchtet die Power LED grün obwohl der DIO nicht gefunden wird?
User avatar
nicolaiB
KUNBUS
Posts: 869
Joined: 21 Jun 2018, 10:33
Answers: 7
Location: Berlin
Contact:

Re: Mittleres Modul nach Neustart nicht gefunden

Post by nicolaiB »

Hallo Eduard,

da zwischen mir und den Anlagen mehrere hundert Kilometer liegen kann ich das nicht mit Sicherheit sagen. Neulich war aber auf einer Anlage ein Techniker vor Ort, der mir versicherte, dass die RevPi Power LED grün war. Den Kaltstart führen wir aus der Ferne per Relais durch.

Gruß Nicolai
User avatar
RR4711
Posts: 228
Joined: 22 Feb 2018, 13:28
Answers: 0

Re: Mittleres Modul nach Neustart nicht gefunden

Post by RR4711 »

Ich hab hier ähnliche Effekte mit einem Connect+ 32GB und einem einzelnen AIO Modul. Bilde mir ein, daß das in Pictory richtig konfiguriert ist, bekomme aber bei piTest -d folgendes:

Code: Select all

pi@sulfurpi:~ $ piTest -d
Found 2 devices:

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

Address: 31 module type: 32871 (0x8067) RevPi AIO V0.0
Module is NOT present, data is NOT available!!!
     input offset: 0 length: 20
    output offset: 20 length: 4
Kernel log (fehlen paar Zeilen am Anfang, dürfte aber nicht relevant sein):

Code: Select all

[    2.361773] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    2.370493] ip_tables: (C) 2000-2006 Netfilter Core Team
[    2.397396] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[    2.407296] systemd[1]: Detected architecture arm.
[    2.427268] systemd[1]: Set hostname to <sulfurpi>.
[    2.492427] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
[    2.495758] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.509276] smsc95xx v1.0.5
[    2.608311] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, c8:3e:a7:01:2e:55
[    2.711785] usb 1-1.5: new high-speed USB device number 4 using dwc_otg
[    2.842299] usb 1-1.5: New USB device found, idVendor=0424, idProduct=9512
[    2.845471] usb 1-1.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.852833] hub 1-1.5:1.0: USB hub found
[    2.856083] hub 1-1.5:1.0: 3 ports detected
[    2.952685] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    2.963476] systemd[1]: Listening on Journal Socket (/dev/log).
[    2.971825] systemd[1]: Created slice System Slice.
[    2.983009] systemd[1]: Mounting RPC Pipe File System...
[    2.991480] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[    2.999959] systemd[1]: Listening on udev Control Socket.
[    3.007674] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[    3.171821] usb 1-1.5.1: new high-speed USB device number 5 using dwc_otg
[    3.233232] i2c /dev entries driver
[    3.302635] usb 1-1.5.1: New USB device found, idVendor=0424, idProduct=ec00
[    3.305644] usb 1-1.5.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.322602] smsc95xx v1.0.5
[    3.334081] spi0.1 supply vdd-io not found, using dummy regulator
[    3.337217] spi0.1 supply vdd not found, using dummy regulator
[    3.419267] smsc95xx 1-1.5.1:1.0 eth1: register 'smsc95xx' at usb-3f980000.usb-1.5.1, smsc95xx USB 2.0 Ethernet, c8:3e:a7:01:2e:56
[    3.431952] ks8851 spi0.1: message enable is 0
[    3.441935] ks8851 spi0.1 pieth0: revision 1, MAC 46:58:22:3d:27:31, IRQ 174, no EEPROM
[    3.521830] usb 1-1.5.2: new full-speed USB device number 6 using dwc_otg
[    3.613304] piControl: loading out-of-tree module taints kernel.
[    3.621493] piControl: built: Tue Mar 12 15:40:55 CET 2019
[    3.625184] piControl: RevPi Connect
[    3.628306] piControl: MAJOR-No.  : 244
[    3.632240] piControl: MAJOR-No.  : 244  MINOR-No.  : 0
[    3.657141] piControl: kernel_read returned 0: b9265f00, 5378
[    3.660732] piControl: 2 devices found
[    3.664006] piControl: 65 entries in total
[    3.667424] piControl: cl-comp:  0 addr 20  bit 00  len  32
[    3.670700] piControl: cl-comp:  1 addr 95  bit ff  len   8
[    3.676692] uart-pl011 3f201000.serial: no DMA platform data
[    3.679824] piControl: filp_open -1188667904
[    3.683192] piControl: set priority of spi0 to 54
[    3.686107] usb 1-1.5.2: New USB device found, idVendor=0403, idProduct=6001
[    3.688933] usb 1-1.5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.694645] usb 1-1.5.2: Product: FT232R USB UART
[    3.697449] usb 1-1.5.2: Manufacturer: FTDI
[    3.699441] piControl: piIO thread started
[    3.699446] piControl: RevPiDevice_init()
[    3.699452] piControl: Enter Init State
[    3.699614] piControl: PADS 0 = 0x1b   slew=1  hyst=1  drive=3
[    3.699621] piControl: PADS 1 = 0x1b   slew=1  hyst=1  drive=3
[    3.699640] piControl: PADS 2 = 0x1b   slew=1  hyst=1  drive=3
[    3.699641] piControl: piControlInit done
[    3.700121] piControl: Enter PresentSignalling1 State
[    3.720189] usb 1-1.5.2: SerialNumber: AL04PERG
[    3.726828] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    3.739347] piControl: Enter InitialSlaveDetectionLeft State
[    3.742196] piControl: Enter EndOfConfig State

[    3.746697] piControl: Device  0: Addr  0 Type 105  Act 1  In   6 Out   5
[    3.749195] piControl:            input offset      0  len   6
[    3.751557] piControl:            output offset     6  len   5
[    3.754020] piControl:            serial number 1  version 1.0
[    3.756410] piControl:
[    3.758672] piControl: Adjust: base 89 in 89 out 95 conf 0
[    3.761130] piControl: After Adjustment
[    3.763569] piControl: Device  0: Addr  0 Type 105  Act 1  In   6 Out   5
[    3.765965] piControl:            input offset     89  len   6
[    3.768421] piControl:            output offset    95  len   5
[    3.770758] piControl: Device  1: Addr 31 Type 32871  Act 0  In  20 Out   4
[    3.773219] piControl:            input offset      0  len  20
[    3.775661] piControl:            output offset    20  len   4
[    3.778080] piControl:
[    3.891808] piControl: start data exchange
[    3.944986] usb 1-1.5.3: new full-speed USB device number 7 using dwc_otg
[    4.100247] usb 1-1.5.3: New USB device found, idVendor=0403, idProduct=6001
[    4.100268] usb 1-1.5.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    4.100278] usb 1-1.5.3: Product: FT232R USB UART
[    4.100287] usb 1-1.5.3: Manufacturer: FTDI
[    4.100297] usb 1-1.5.3: SerialNumber: AL04PERF
[    4.131834] piControl: initialization of module not finished (0,0,4) -> retry
[    4.132421] piControl: Enter Initialization Retry
[    4.361531] systemd-journald[153]: Received request to flush runtime journal from PID 1
[    5.796638] ks8851 spi0.1 pileft: renamed from pieth0
[    6.739217] piControl: RevPiDevice_init()
[    6.739803] piControl: Enter Init State
[    6.740403] piControl: Enter PresentSignalling1 State
[    6.779405] piControl: Enter InitialSlaveDetectionLeft State
[    6.779961] piControl: Enter EndOfConfig State

[    6.779979] piControl: Device  0: Addr  0 Type 105  Act 1  In   6 Out   5
[    6.779988] piControl:            input offset      0  len   6
[    6.779995] piControl:            output offset     6  len   5
[    6.780003] piControl:            serial number 1  version 1.0
[    6.780008] piControl:
[    6.780033] piControl: Adjust: base 89 in 89 out 95 conf 0
[    6.780051] piControl: After Adjustment
[    6.780066] piControl: Device  0: Addr  0 Type 105  Act 1  In   6 Out   5
[    6.780073] piControl:            input offset     89  len   6
[    6.780090] piControl:            output offset    95  len   5
[    6.780113] piControl: Device  1: Addr 31 Type 32871  Act 0  In  20 Out   4
[    6.780126] piControl:            input offset      0  len  20
[    6.780143] piControl:            output offset    20  len   4
[    6.780155] piControl:
[    6.891774] piControl: start data exchange
[    6.949416] usbcore: registered new interface driver usbserial
[    6.950837] usbcore: registered new interface driver usbserial_generic
[    6.954018] usbserial: USB Serial support registered for generic
[    6.973617] usbcore: registered new interface driver ftdi_sio
[    6.973761] usbserial: USB Serial support registered for FTDI USB Serial Device
[    6.974411] ftdi_sio 1-1.5.2:1.0: FTDI USB Serial Device converter detected
[    6.985153] usb 1-1.5.2: Detected FT232RL
[    6.988928] usb 1-1.5.2: FTDI USB Serial Device converter now attached to ttyUSB0
[    6.990115] ftdi_sio 1-1.5.3:1.0: FTDI USB Serial Device converter detected
[    6.994842] usb 1-1.5.3: Detected FT232RL
[    7.001194] usb 1-1.5.3: FTDI USB Serial Device converter now attached to ttyUSB1
[    7.131765] piControl: set BridgeState to running
[    8.164270] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[   14.078143] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   14.167962] smsc95xx 1-1.5.1:1.0 eth1: hardware isn't capable of remote wakeup
[   14.179994] IPv6: ADDRCONF(NETDEV_UP): pileft: link is not ready
[   15.626966] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1
[   15.652613] smsc95xx 1-1.5.1:1.0 eth1: link up, 100Mbps, full-duplex, lpa 0xC1E1
[  176.197627] piControl: Reset: BridgeState=2
[  176.261908] piControl: stop data exchange
[  176.261938] piControl: piIoComm_gotoGateProtocol returned 0
[  176.262910] piControl: kernel_read returned 0: b61a5c00, 5378
[  176.262936] piControl: 2 devices found
[  176.262940] piControl: 65 entries in total
[  176.263024] piControl: cl-comp:  0 addr 20  bit 00  len  32
[  176.263029] piControl: cl-comp:  1 addr 95  bit ff  len   8
[  176.263632] piControl: RevPiDevice_init()
[  176.263649] piControl: PADS 0 = 0x1b   slew=1  hyst=1  drive=3
[  176.263655] piControl: PADS 1 = 0x1b   slew=1  hyst=1  drive=3
[  176.263659] piControl: PADS 2 = 0x1b   slew=1  hyst=1  drive=3
[  176.264030] piControl: Enter Init State
[  176.264555] piControl: Enter PresentSignalling1 State
[  176.303383] piControl: Enter InitialSlaveDetectionLeft State
[  176.303904] piControl: Enter EndOfConfig State

[  176.303912] piControl: Device  0: Addr  0 Type 105  Act 1  In   6 Out   5
[  176.303916] piControl:            input offset      0  len   6
[  176.303919] piControl:            output offset     6  len   5
[  176.303923] piControl:            serial number 1  version 1.0
[  176.303926] piControl:
[  176.303934] piControl: Adjust: base 89 in 89 out 95 conf 0
[  176.303939] piControl: After Adjustment
[  176.303944] piControl: Device  0: Addr  0 Type 105  Act 1  In   6 Out   5
[  176.303947] piControl:            input offset     89  len   6
[  176.303950] piControl:            output offset    95  len   5
[  176.303955] piControl: Device  1: Addr 31 Type 32871  Act 0  In  20 Out   4
[  176.303959] piControl:            input offset      0  len  20
[  176.303962] piControl:            output offset    20  len   4
[  176.303964] piControl:
[  176.421876] piControl: start data exchange
[  176.661888] piControl: initialization of module not finished (0,0,4) -> retry
[  176.662416] piControl: Enter Initialization Retry
[  179.303268] piControl: RevPiDevice_init()
[  179.303790] piControl: Enter Init State
[  179.304313] piControl: Enter PresentSignalling1 State
[  179.343743] piControl: Enter InitialSlaveDetectionLeft State
[  179.344263] piControl: Enter EndOfConfig State

[  179.344271] piControl: Device  0: Addr  0 Type 105  Act 1  In   6 Out   5
[  179.344275] piControl:            input offset      0  len   6
[  179.344278] piControl:            output offset     6  len   5
[  179.344282] piControl:            serial number 1  version 1.0
[  179.344285] piControl:
[  179.344295] piControl: Adjust: base 89 in 89 out 95 conf 0
[  179.344300] piControl: After Adjustment
[  179.344304] piControl: Device  0: Addr  0 Type 105  Act 1  In   6 Out   5
[  179.344308] piControl:            input offset     89  len   6
[  179.344311] piControl:            output offset    95  len   5
[  179.344316] piControl: Device  1: Addr 31 Type 32871  Act 0  In  20 Out   4
[  179.344320] piControl:            input offset      0  len  20
[  179.344323] piControl:            output offset    20  len   4
[  179.344325] piControl:
[  179.461881] piControl: start data exchange
[  179.701888] piControl: set BridgeState to running
[  269.350916] piControl: Reset: BridgeState=2
[  269.402025] piControl: stop data exchange
[  269.402051] piControl: piIoComm_gotoGateProtocol returned 0
[  269.403059] piControl: kernel_read returned 0: b792ee00, 5378
[  269.403080] piControl: 2 devices found
[  269.403083] piControl: 65 entries in total
[  269.403184] piControl: cl-comp:  0 addr 20  bit 00  len  32
[  269.403189] piControl: cl-comp:  1 addr 95  bit ff  len   8
[  269.403806] piControl: RevPiDevice_init()
[  269.403824] piControl: PADS 0 = 0x1b   slew=1  hyst=1  drive=3
[  269.403829] piControl: PADS 1 = 0x1b   slew=1  hyst=1  drive=3
[  269.403834] piControl: PADS 2 = 0x1b   slew=1  hyst=1  drive=3
[  269.404134] piControl: Enter Init State
[  269.404658] piControl: Enter PresentSignalling1 State
[  269.443677] piControl: Enter InitialSlaveDetectionLeft State
[  269.444199] piControl: Enter EndOfConfig State

[  269.444206] piControl: Device  0: Addr  0 Type 105  Act 1  In   6 Out   5
[  269.444210] piControl:            input offset      0  len   6
[  269.444213] piControl:            output offset     6  len   5
[  269.444217] piControl:            serial number 1  version 1.0
[  269.444220] piControl:
[  269.444228] piControl: Adjust: base 89 in 89 out 95 conf 0
[  269.444233] piControl: After Adjustment
[  269.444238] piControl: Device  0: Addr  0 Type 105  Act 1  In   6 Out   5
[  269.444241] piControl:            input offset     89  len   6
[  269.444244] piControl:            output offset    95  len   5
[  269.444249] piControl: Device  1: Addr 31 Type 32871  Act 0  In  20 Out   4
[  269.444253] piControl:            input offset      0  len  20
[  269.444256] piControl:            output offset    20  len   4
[  269.444259] piControl:
[  269.561986] piControl: start data exchange
[  269.801991] piControl: initialization of module not finished (0,0,4) -> retry
[  269.802524] piControl: Enter Initialization Retry
[  272.443277] piControl: RevPiDevice_init()
[  272.443798] piControl: Enter Init State
[  272.444321] piControl: Enter PresentSignalling1 State
[  272.483886] piControl: Enter InitialSlaveDetectionLeft State
[  272.484407] piControl: Enter EndOfConfig State

[  272.484415] piControl: Device  0: Addr  0 Type 105  Act 1  In   6 Out   5
[  272.484419] piControl:            input offset      0  len   6
[  272.484423] piControl:            output offset     6  len   5
[  272.484427] piControl:            serial number 1  version 1.0
[  272.484430] piControl:
[  272.484437] piControl: Adjust: base 89 in 89 out 95 conf 0
[  272.484442] piControl: After Adjustment
[  272.484447] piControl: Device  0: Addr  0 Type 105  Act 1  In   6 Out   5
[  272.484450] piControl:            input offset     89  len   6
[  272.484454] piControl:            output offset    95  len   5
[  272.484459] piControl: Device  1: Addr 31 Type 32871  Act 0  In  20 Out   4
[  272.484462] piControl:            input offset      0  len  20
[  272.484465] piControl:            output offset    20  len   4
[  272.484468] piControl:
[  272.602018] piControl: start data exchange
[  272.842006] piControl: set BridgeState to running
[  394.226779] piControl: Reset: BridgeState=2
[  394.282215] piControl: stop data exchange
[  394.282244] piControl: piIoComm_gotoGateProtocol returned 0
[  394.283205] piControl: kernel_read returned 0: b7ba7800, 5378
[  394.283227] piControl: 2 devices found
[  394.283231] piControl: 65 entries in total
[  394.283342] piControl: cl-comp:  0 addr 20  bit 00  len  32
[  394.283347] piControl: cl-comp:  1 addr 95  bit ff  len   8
[  394.283961] piControl: RevPiDevice_init()
[  394.283980] piControl: PADS 0 = 0x1b   slew=1  hyst=1  drive=3
[  394.283985] piControl: PADS 1 = 0x1b   slew=1  hyst=1  drive=3
[  394.283990] piControl: PADS 2 = 0x1b   slew=1  hyst=1  drive=3
[  394.284327] piControl: Enter Init State
[  394.284850] piControl: Enter PresentSignalling1 State
[  394.323852] piControl: Enter InitialSlaveDetectionLeft State
[  394.324372] piControl: Enter EndOfConfig State

[  394.324379] piControl: Device  0: Addr  0 Type 105  Act 1  In   6 Out   5
[  394.324383] piControl:            input offset      0  len   6
[  394.324387] piControl:            output offset     6  len   5
[  394.324391] piControl:            serial number 1  version 1.0
[  394.324393] piControl:
[  394.324401] piControl: Adjust: base 89 in 89 out 95 conf 0
[  394.324406] piControl: After Adjustment
[  394.324411] piControl: Device  0: Addr  0 Type 105  Act 1  In   6 Out   5
[  394.324415] piControl:            input offset     89  len   6
[  394.324418] piControl:            output offset    95  len   5
[  394.324423] piControl: Device  1: Addr 31 Type 32871  Act 0  In  20 Out   4
[  394.324427] piControl:            input offset      0  len  20
[  394.324430] piControl:            output offset    20  len   4
[  394.324432] piControl:
[  394.442183] piControl: start data exchange
[  394.682191] piControl: initialization of module not finished (0,0,4) -> retry
[  394.682719] piControl: Enter Initialization Retry
[  397.323399] piControl: RevPiDevice_init()
[  397.323920] piControl: Enter Init State
[  397.324443] piControl: Enter PresentSignalling1 State
[  397.363957] piControl: Enter InitialSlaveDetectionLeft State
[  397.364480] piControl: Enter EndOfConfig State

[  397.364488] piControl: Device  0: Addr  0 Type 105  Act 1  In   6 Out   5
[  397.364492] piControl:            input offset      0  len   6
[  397.364496] piControl:            output offset     6  len   5
[  397.364500] piControl:            serial number 1  version 1.0
[  397.364502] piControl:
[  397.364510] piControl: Adjust: base 89 in 89 out 95 conf 0
[  397.364515] piControl: After Adjustment
[  397.364520] piControl: Device  0: Addr  0 Type 105  Act 1  In   6 Out   5
[  397.364523] piControl:            input offset     89  len   6
[  397.364526] piControl:            output offset    95  len   5
[  397.364531] piControl: Device  1: Addr 31 Type 32871  Act 0  In  20 Out   4
[  397.364535] piControl:            input offset      0  len  20
[  397.364538] piControl:            output offset    20  len   4
[  397.364541] piControl:
[  397.482198] piControl: start data exchange
[  397.722189] piControl: set BridgeState to running
Ich muss mal meinen Kollegen fragen, von dem ich das Modul habe aber ich behaupte mal an seinem RevPiCore tut es....

Power Cycle hilft bei mir leider nicht.

Markus
User avatar
dirk
KUNBUS
Posts: 1926
Joined: 15 Dec 2016, 13:19
Answers: 4

Re: Mittleres Modul nach Neustart nicht gefunden

Post by dirk »

Lieber Nikolai, ich habe Dir per E-Mail ein RMA Formular geschickt. Wir werden die Firmware der Geräte aktualisieren auf den Stand, der allerdings noch nicht Release Version ist.
Post Reply