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

    [FW 3.5.1] Is parameter "A" implemented in M956?

    Scheduled Pinned Locked Moved
    General Discussion
    3
    4
    188
    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.
    • leoneundefined
      leone
      last edited by

      Hi all!
      I would like to use the command M956 to record accelerometer data while doing a single move. It would be great to start the recording at the end of the move or right before the deceleration phase. My understanding is that this is the function of the "A1" and "A2" parameters, but I am unable to make it work as such. Is this parameter actually implemented, or is there an additional step required? If it is not implemented, are there any plans to do so, or are there any workarounds available in the meantime?
      Thank you!

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

        @leone it is implemented. What version of firmware are you using?

        Note the command all needs to be sent on one line. If you use the Input Shaping plugin it sends a command like this:
        G1 Y222.1 F18000 M400 M956 P20.0 S1000 A0 F"37-T1-Y77.1-222.1-20.0-zvdd-42Hz-0.05.csv"

        www.duet3d.com

        leoneundefined 1 Reply Last reply Reply Quote 0
        • leoneundefined
          leone @T3P3Tony
          last edited by

          @T3P3Tony thanks for your answer.
          Based on your suggestion I managed to have the intended behaviour with the A1 parameter by running on the same line:

          M956 P20.0 S1200 A1 F"move.csv" M400 G1 X300 F18000

          If I run the same command but with A2 instead, the logged data are pretty much the same, with acceleration and deceleration segments. With A2 I would expect to see only the deceleration phase, am I right?

          Btw, I am using 3.5.1.

          Thanks for the support!

          gloomyandyundefined 1 Reply Last reply Reply Quote 0
          • gloomyandyundefined
            gloomyandy @leone
            last edited by

            @leone From the 3.5.1 source....

            	gb.MustSee('A');
            	const uint8_t mode = gb.GetUIValue();
            ...
            ...
            ...
            	(void)mode;									// TODO implement mode
            

            So the various A options are not currently implemented.

            See: https://github.com/Duet3D/RepRapFirmware/blob/3.5-dev/src/Accelerometers/Accelerometers.cpp#L391

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