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

    Accelerometer M956 failing w Sender

    Scheduled Pinned Locked Moved Solved
    General Discussion
    2
    4
    130
    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.
    • wayneosdiasundefined
      wayneosdias
      last edited by

      I have a working LIS3DH that appears to work just fine launching from DWC, but I can't execute from Openpnp as the sender.
      sending M956 P123.0 S1000 A1 from the Openpnp GCode console results in Openpnp Console responce;

      > M956 P123.0 S1000 A1
      Error: M956: Accelerometer not found
      ok
      

      in Openpnp Log/Trace responce

      2025-02-24 17:36:48.746 GcodeDriver DEBUG: [tcp://192.168.2.1:333] >> M956 P123.0 S1000 A1, 5000
      2025-02-24 17:36:48.748 GcodeDriver$ReaderThread TRACE: [tcp://192.168.2.1:333] << Error: M956: Accelerometer not found
      2025-02-24 17:36:48.748 GcodeDriver$ReaderThread TRACE: [tcp://192.168.2.1:333] << ok
      2025-02-24 17:36:48.748 GcodeDriver TRACE: [tcp://192.168.2.1:333] confirmed M956P123S1000A1
      
      

      Im not sure if this related to Openpnp to 6HC being connected via tcp/ethernet of not, but I can run same code from DWC just fine;
      18d5aab4-6503-4c90-9741-f33ec0ad8446-image.png
      e49ff66d-8afd-48fc-8f7c-a59ec85da811-image.png

      Thanks for any help on this!

      T3P3Tonyundefined 1 Reply Last reply Reply Quote 0
      • T3P3Tonyundefined
        T3P3Tony administrators @wayneosdias
        last edited by

        @wayneosdias

        @wayneosdias said in Accelerometer M956 failing w Sender:

        2025-02-24 17:36:48.748 GcodeDriver TRACE: [tcp://192.168.2.1:333] confirmed M956P123S1000A1

        this is not valid:
        M956P123S1000A1

        P123 isn't a valid accelerometer address, P123.0 is

        looks like the sender is changing part of the gcode command string

        www.duet3d.com

        wayneosdiasundefined 1 Reply Last reply Reply Quote 1
        • wayneosdiasundefined
          wayneosdias @T3P3Tony
          last edited by

          @T3P3Tony ...duh, Thanks Tony. I forgot about the GCode compression asd missed the missing '.' in the log. Changing the command to include the escape character has it all working now;

          M956 P123\u002E0 S1000 A1
          
          2025-02-25 07:08:15.399 GcodeDriver DEBUG: [tcp://192.168.2.1:333] >> M956 P123\u002E0 S1000 A1, 5000
          2025-02-25 07:08:15.450 GcodeDriver$ReaderThread TRACE: [tcp://192.168.2.1:333] << ok
          2025-02-25 07:08:15.450 GcodeDriver TRACE: [tcp://192.168.2.1:333] confirmed M956P123.0S1000A1
          

          Thank you

          T3P3Tonyundefined 1 Reply Last reply Reply Quote 2
          • wayneosdiasundefined wayneosdias marked this topic as a question
          • wayneosdiasundefined wayneosdias has marked this topic as solved
          • T3P3Tonyundefined
            T3P3Tony administrators @wayneosdias
            last edited by

            @wayneosdias thanks for confirming that

            www.duet3d.com

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Unless otherwise noted, all forum content is licensed under CC-BY-SA