Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Accelerometer causes Duet 2 Wifi to crash?

    Scheduled Pinned Locked Moved Solved
    Duet Hardware and wiring
    2
    12
    335
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • kuhnikuehnastundefined
      kuhnikuehnast
      last edited by

      Just tried the other duet board I own (a cartesian printer) - there a file is created with the message

      Sample,X,Y,Z
      Failed to collect data from accelerometer

      very strange...?

      1 Reply Last reply Reply Quote 0
      • kuhnikuehnastundefined
        kuhnikuehnast
        last edited by

        another strange behavior:
        I can adress the Accelerometer with the command:

        M955 P0 I46 C"spi.cs4+spi.cs3"

        but if I then want to change something and post the code again (e.g. to change the Frequency)

        M955 P0 I46 C"spi.cs4+spi.cs3" Q500000

        I get the error

        M955: Accelerometer not found on specified port

        is this normal? Do you have to reset the Board to "re-activate" the possibility to declare an M955 command?

        dc42undefined 1 Reply Last reply Reply Quote 0
        • dc42undefined
          dc42 administrators @kuhnikuehnast
          last edited by

          @kuhnikuehnast I'm not sure why that is happening, however you don't need to repeat the M955 C parameter or I parameter when you just want to change the data collection parameters.

          If the board reboots unexpectedly, please run M122 as soon as DWC has reconnected, and post the output here.

          Duet WiFi hardware designer and firmware engineer
          Please do not ask me for Duet support via PM or email, use the forum
          http://www.escher3d.com, https://miscsolutions.wordpress.com

          1 Reply Last reply Reply Quote 0
          • kuhnikuehnastundefined
            kuhnikuehnast
            last edited by

            tried it:

            M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.4 (2022-10-20 16:17:41) running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SN-6J9F2-3S46K-1UYRD
Used output buffers: 1 of 26 (15 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 76056 of which 168 recycled
Never used RAM 9140, free system stack 186 words
Tasks: NETWORK(notifyWait,9.1%,242) HEAT(notifyWait,0.0%,339) Move(notifyWait,0.0%,363) MAIN(running,81.8%,320) IDLE(ready,9.0%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:10 ago, cause: software
Last software reset at 2023-02-16 18:00, reason: HeatTaskStuck, GCodes spinning, available RAM 7200, slot 1
Software reset code 0x4143 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x20018d84 Task ACCE Freestk 336 ok
Stack: 0045d69d 0045d0f6 6100f000 00000000 0045d69d 2001871b 00000000 00000000 2001871b 2001871b 2000d334 200187e8 00000006 00000028 a5a5a5a5 00000001 0045d797 400a0000 00000001 200186f8 0045b02b 400a0000 00456cb3 0c000000 200186f8 00000007 00000007
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 32.7, current 33.3, max 33.5
Supply voltage: min 23.8, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/24/24, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
Date/time: 2023-02-16 18:00:29
Cache data hit count 386562846
Slowest loop: 11.66ms; fastest: 0.19ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 0.9ms, write time 5.7ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Network ===
Slowest loop: 37.22ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= WiFi =
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.27
WiFi MAC address 84:f3:eb:42:7a:a5
WiFi Vcc 3.40, reset reason Power up
WiFi flash size 4194304, free heap 25784
WiFi IP address 192.168.178.80
WiFi signal strength -52dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
            dc42undefined 1 Reply Last reply Reply Quote 0
            • dc42undefined
              dc42 administrators @kuhnikuehnast
              last edited by

              @kuhnikuehnast I suspect that there may be a problem with the INT connection from the accelerometer to the Duet spi.cs3 pin.

              Duet WiFi hardware designer and firmware engineer
              Please do not ask me for Duet support via PM or email, use the forum
              http://www.escher3d.com, https://miscsolutions.wordpress.com

              kuhnikuehnastundefined 2 Replies Last reply Reply Quote 0
              • kuhnikuehnastundefined
                kuhnikuehnast @dc42
                last edited by

                @dc42 so what should I do? When i connect the same board (and cable) to the other board it "works" - as mentioned above... "failed to collect data"

                1 Reply Last reply Reply Quote 0
                • kuhnikuehnastundefined
                  kuhnikuehnast @dc42
                  last edited by

                  @dc42
                  I now tried something else:

                  • I switched the CS and INT1- Pin (so I declared the M955 to:
                    M955 P0 I46 C"spi.cs3+spi.cs4"
                    instead of
                    M955 P0 I46 C"spi.cs4+spi.cs3"

                  but as soon as I ran the code:
                  M956 P0 S1000 A0

                  I got another crash. In this time this was the M122:

                  === Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.4 (2022-10-20 16:17:41) running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SN-6J9F2-3S46K-1UYRD
Used output buffers: 1 of 26 (18 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 76056 of which 168 recycled
Never used RAM 9140, free system stack 184 words
Tasks: NETWORK(notifyWait,9.4%,242) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) MAIN(running,82.0%,320) IDLE(ready,8.6%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:10 ago, cause: software
Last software reset at 2023-02-17 08:38, reason: HeatTaskStuck, GCodes spinning, available RAM 7200, slot 0
Software reset code 0x4143 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x20018da4 Task ACCE Freestk 344 ok
Stack: 00435245 00435248 61000000 00000001 200186f8 00000001 0000002f a5a5a5a5 00000001 20004c60 00456cab 0c000000 20018dff 200186f8 00000007 00000010 00456cd5 0c000000 200186f8 00000007 00456f17 200186f8 c3000007 00000007 000003e8 2000119c 00456723
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 23.5, current 24.2, max 24.5
Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/24/24, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
Date/time: 2023-02-17 08:38:07
Cache data hit count 405364224
Slowest loop: 10.11ms; fastest: 0.19ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 0.9ms, write time 5.9ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Network ===
Slowest loop: 37.57ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= WiFi =
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.27
WiFi MAC address 84:f3:eb:42:7a:a5
WiFi Vcc 3.40, reset reason Power up
WiFi flash size 4194304, free heap 22360
WiFi IP address 192.168.178.80
WiFi signal strength -54dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

                  Do you see something different? So is my Duet broken? Or how could I solve this problem?

                  Hope you can help me!

                  greetings kuhni

                  dc42undefined kuhnikuehnastundefined 2 Replies Last reply Reply Quote 0
                  • dc42undefined
                    dc42 administrators @kuhnikuehnast
                    last edited by

                    @kuhnikuehnast it could be that writing to the SD card is taking too long. You could try a new SD card. Alternatively, reduce the number of samples you are collecting, for example to 500.

                    Duet WiFi hardware designer and firmware engineer
                    Please do not ask me for Duet support via PM or email, use the forum
                    http://www.escher3d.com, https://miscsolutions.wordpress.com

                    kuhnikuehnastundefined 1 Reply Last reply Reply Quote 0
                    • kuhnikuehnastundefined
                      kuhnikuehnast @dc42
                      last edited by kuhnikuehnast

                      @dc42 tried now only 10 samples by
                      M956 P0 S1000 A0
                      same crash... 😞

                      === Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.4 (2022-10-20 16:17:41) running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3SN-6J9F2-3S46K-1UYRD
Used output buffers: 1 of 26 (16 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 76056 of which 168 recycled
Never used RAM 9140, free system stack 188 words
Tasks: NETWORK(ready,9.6%,242) HEAT(notifyWait,0.0%,329) Move(notifyWait,0.0%,363) MAIN(running,81.5%,320) IDLE(ready,8.8%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:10 ago, cause: software
Last software reset at 2023-02-17 17:11, reason: HeatTaskStuck, GCodes spinning, available RAM 7200, slot 2
Software reset code 0x4143 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x20018d84 Task ACCE Freestk 336 ok
Stack: 0045d69d 0045d0f6 6100f000 00000000 0045d69d 2001871b 00000000 400a0000 2001871b 2001871b 2000d334 200187e8 00000006 00000028 a5a5a5a5 00000001 0045d797 400a0000 00000001 200186f8 0045b02b 400a0000 00456cb3 0c000000 200186f8 00000007 00000007
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 33.3, current 33.9, max 34.1
Supply voltage: min 23.8, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/24/24, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
Date/time: 2023-02-17 17:12:23
Cache data hit count 396566500
Slowest loop: 12.22ms; fastest: 0.19ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 0.9ms, write time 3.9ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Network ===
Slowest loop: 32.53ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= WiFi =
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.27
WiFi MAC address 84:f3:eb:42:7a:a5
WiFi Vcc 3.40, reset reason Power up
WiFi flash size 4194304, free heap 25384
WiFi IP address 192.168.178.80
WiFi signal strength -52dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
                      1 Reply Last reply Reply Quote 0
                      • kuhnikuehnastundefined
                        kuhnikuehnast @kuhnikuehnast
                        last edited by kuhnikuehnast

                        @dc42 btw what is the biggest size possible for the SD-Card? So I'll get to grab a new one...

                        sorry, got it already- so I'm out now heading to a store to get a SanDisk Extreme Pro 32 GB mircoSD 😄 cross fingers for me that this will solve the problem!

                        kuhnikuehnastundefined 1 Reply Last reply Reply Quote 0
                        • kuhnikuehnastundefined
                          kuhnikuehnast @kuhnikuehnast
                          last edited by

                          I think I solved the problem:

                          • it wasn't the SD-card- but as I changed the cable and re-crimped an USB-3-cable everything now seems to work! 🙂

                          yihaaa 🙂

                          1 Reply Last reply Reply Quote 1
                          • Phaedruxundefined Phaedrux marked this topic as a question
                          • Phaedruxundefined Phaedrux has marked this topic as solved
                          • First post
                            Last post
                          Unless otherwise noted, all forum content is licensed under CC-BY-SA