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

Accelerometer INT1 error

Scheduled Pinned Locked Moved
Duet Web Control
2
2
122
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.
  • undefined
    Piet
    last edited by droftarts 22 Mar 2025, 21:32

    Hi All,

    I'm upgrading my printer a bit and decided to install an accelerometer, an lLIS3DSH to be exact.
    I followed the instructions in the documentation for the connections and about 50% of the time it recognises the accelerometer and other times I'll get Error in start-up file macro line 50: Accelerometer not found on specified port.

    If it gets recognised I can call it with M955 P0 and it responds with Accelerometer 0 type LIS3DH with orientation 20 samples at 1344Hz with 10-bit resolution, SPI frequency 2000000. I declared it with M955 P0 C"spi.cs2+spi.cs1"M955 P0 C"spi.cs2+spi.cs1"
    I used an old Cat5e cable of ~70cm with the following connections:

    • VCC (3.3V) - Orange
    • GND - Orange/White
    • SCK - Green
    • SDA - Green/White
    • INT1 - Brown
    • SDO - Brown/White
    • CS - Blue

    When I use the plugin and it makes the first move it will return the following error:
    c423f742-db9a-4c81-a669-a467b227d374-image.png
    Error: M956: Failed to start accelerometer data collection: INT1 error

    I checked the wiring and also used a multimeter to beep the wires.

    My diagnostics:

    RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.4 (2024-11-24 10:43:42) running on Duet WiFi 1.02 or later
    Board ID: 08DGM-956GU-DJMSN-6JKD2-3S46Q-TVQBH
    Used output buffers: 6 of 26 (14 max)
    Error in macro line 50 while starting up: Accelerometer not found on specified port
    === RTOS ===
    Static ram: 23488
    Dynamic ram: 72168 of which 32 recycled
    Never used RAM 14936, free system stack 184 words
    Tasks: NETWORK(2,nWait 6,13.9%,222) HEAT(3,nWait 5,0.0%,328) Move(4,nWait 5,0.0%,361) MAIN(1,running,85.3%,758) IDLE(0,ready,0.8%,29), total 100.0%
    Owned mutexes:
    === Platform ===
    Last reset 00:02:01 ago, cause: power up
    Last software reset at 2025-03-22 22:10, reason: User, Gcodes spinning, available RAM 14936, slot 1
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
    Error status: 0x00
    MCU temperature: min 24.2, current 29.7, max 30.0
    Supply voltage: min 24.1, current 24.3, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
    Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/52/0, 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: 2025-03-22 22:40:39
    Cache data hit count 4277550534
    Slowest loop: 7.27ms; fastest: 0.19ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
    === Storage ===
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest read time 1.2ms, write time 0.0ms, max retries 0
    === Move ===
    DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
    no step interrupt scheduled
    Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
    === DDARing 0 ===
    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
    === GCodes ===
    Movement locks 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
    Q0 segments left 0
    Code queue 0 is empty
    === Filament sensors ===
    check 0 clear 493929
    Extruder 0 sensor: no data received
    === Network ===
    Slowest loop: 133.35ms; fastest: 0.00ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
    HTTP sessions: 1 of 8
    === WiFi ===
    Interface state: active
    Module is connected to access point
    Failed messages: pending 0, notrdy 0, noresp 0
    Firmware version 2.2.0
    MAC address 60:01:94:73:5f:25
    Module reset reason: Turned on by main processor, Vcc 3.36, flash size 4194304, free heap 34260
    WiFi IP address 192.168.178.206
    Signal strength -66dBm, channel 11, mode 802.11n, reconnections 0
    Clock register 00002002
    Socket states: 0 5 0 0 0 0 0 0

    Can anyone give me some pointers or tell me what I'm doing wrong? That would be greatly appreciated!
    Thanks in advance.

    Kind regards, Piet.

    undefined 1 Reply Last reply 24 Mar 2025, 14:20 Reply Quote 0
    • undefined
      dc42 administrators @Piet
      last edited by 24 Mar 2025, 14:20

      @Piet please post a photo showing how you have connected that cable to the Duet.

      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
      1 out of 2
      • First post
        1/2
        Last post
      Unless otherwise noted, all forum content is licensed under CC-BY-SA