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

    Accelerometer Usage

    Scheduled Pinned Locked Moved
    Beta Firmware
    25
    191
    20.0k
    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.
    • StaticRedundefined
      StaticRed @dc42
      last edited by

      @dc42 Sure nothing else is connected to the board. Just the normal stuff like fans motors heaters

      1 Reply Last reply Reply Quote 0
      • StaticRedundefined
        StaticRed @dc42
        last edited by

        @dc42 okay so i rechecked every wire, seems to be all fine. I think its just something about wrong gcode, nothing more.

        Maybe my config.g can help? https://just-paste.it/SqW7DwJd1j

        GCode im using just to try the accelerometer

        M956 P0 S1000 A0

        DIY-O-Sphereundefined 1 Reply Last reply Reply Quote 0
        • DIY-O-Sphereundefined
          DIY-O-Sphere @StaticRed
          last edited by

          @staticred
          If you paste

          M955 P0  C"io0.out+io0.in"
          

          to the DWC gcode input box, what is the replied message?

          StaticRedundefined 1 Reply Last reply Reply Quote 0
          • StaticRedundefined
            StaticRed @DIY-O-Sphere
            last edited by

            @diy-o-sphere Error: M955: Accelerometer not found on specified port

            StaticRedundefined 1 Reply Last reply Reply Quote 0
            • StaticRedundefined
              StaticRed @StaticRed
              last edited by

              @staticred https://imgur.com/a/p3jq7Oh this is how i hooked it up

              DIY-O-Sphereundefined 3 Replies Last reply Reply Quote 0
              • DIY-O-Sphereundefined
                DIY-O-Sphere @StaticRed
                last edited by DIY-O-Sphere

                @staticred

                I remember that I also had strange readings in the beginning, but the sensor still worked and was found with the M955 command. I have also plugged it to Io0. But I have connected all wires to the paneldue port.

                1 Reply Last reply Reply Quote 0
                • DIY-O-Sphereundefined
                  DIY-O-Sphere @StaticRed
                  last edited by DIY-O-Sphere

                  @staticred
                  That is my wiring

                  f63ed4a3-277c-4793-b62f-293a51c42ad3-grafik.png

                  1 Reply Last reply Reply Quote 0
                  • DIY-O-Sphereundefined
                    DIY-O-Sphere @StaticRed
                    last edited by DIY-O-Sphere

                    This post is deleted!
                    StaticRedundefined 1 Reply Last reply Reply Quote 0
                    • StaticRedundefined
                      StaticRed @DIY-O-Sphere
                      last edited by

                      @diy-o-sphere Thanks a lot man, i will try it out. I have another version of the Lis3DH sensor, stemm qt. It just has 2 ports on the side, not sure if it will effect anything, but i dont think so.

                      DIY-O-Sphereundefined 1 Reply Last reply Reply Quote 0
                      • DIY-O-Sphereundefined
                        DIY-O-Sphere @StaticRed
                        last edited by DIY-O-Sphere

                        @staticred

                        Sorry, had to delete my previous post. Now I noticed that you have connected the wires to the temp dautherboard. That looks right to me.

                        StaticRedundefined 1 Reply Last reply Reply Quote 0
                        • StaticRedundefined
                          StaticRed @DIY-O-Sphere
                          last edited by

                          @diy-o-sphere Ok it now it works,

                          Accelerometer 0:0 with orientation 20 samples at 1344Hz with 10-bit resolution

                          It worked until i tried to run a test. Then DWC timed out, and now im getting no connection anymore. Same wiring. Really weird.

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

                            @staticred said in Accelerometer Usage:

                            @diy-o-sphere Ok it now it works,

                            Accelerometer 0:0 with orientation 20 samples at 1344Hz with 10-bit resolution

                            It worked until i tried to run a test. Then DWC timed out, and now im getting no connection anymore. Same wiring. Really weird.

                            That suggests that something is wrong with the interrupt input. Check the connection between INT0 on the LIS3DH and io0.in, and perhaps try using a different IO port.

                            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

                            StaticRedundefined 1 Reply Last reply Reply Quote 0
                            • StaticRedundefined
                              StaticRed @dc42
                              last edited by

                              @dc42 Nope no chance. I wired it to io1. Same thing. I tested all connections with a multimeter and they work. But sadly my board cant build up a connection to the accelerometer. Is there something like a debug mode, which may teaches me more about what exactly the problem is?

                              StaticRedundefined 1 Reply Last reply Reply Quote -1
                              • StaticRedundefined
                                StaticRed @StaticRed
                                last edited by

                                @staticred seems like it still did record some data at some point.
                                aa562860-14d7-4554-9ac1-8924487b9324-image.png

                                But it does not make sense that that is the z axis. Because the board is mounted flat on the toolhead. Really strange

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

                                  @staticred I will re-test accelerometer with Duet 3 Mini later today or tomorrow.

                                  What did the raw data look like, before you clicked Analyse?

                                  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

                                  StaticRedundefined 1 Reply Last reply Reply Quote 0
                                  • StaticRedundefined
                                    StaticRed @dc42
                                    last edited by

                                    @dc42 Thank you alot!
                                    2718ce0e-d153-4dd6-9cea-48819629d1f4-image.png
                                    This is what the raw data looked like

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

                                      @staticred the raw data looks OK except for the spikes and drops, assuming that you collected that data while the machine was stationary. My guess is that those spikes/drops were where the firmware was unable to extract the data from the accelerometer fast enough. You can check this by looking at the end of the .csv file to see if there is a message about this. I think the DWC accelerometer plugin may report it too. See the notes at https://duet3d.dozuki.com/Wiki/Accelerometers#Section_Retrieving_the_data to see what you can do about it; or just try re-running it a few times to see if you can get a clean run.

                                      The analysis isn't valid if the data contains dropouts. To get a useful analysis you need to do a suitable move while the data is being collected as described at https://duet3d.dozuki.com/Wiki/Accelerometers#Section_Using_accelerometers.

                                      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
                                      • dc42undefined
                                        dc42 administrators @StaticRed
                                        last edited by

                                        @staticred I just connected a LIS3DH board to my Duet 3 Mini5+ WiFi and it is working as expected. I used connector IO2 to connect the CS and INT lines.

                                        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

                                        StaticRedundefined 1 Reply Last reply Reply Quote 0
                                        • StaticRedundefined
                                          StaticRed @dc42
                                          last edited by

                                          @dc42 thank you for all the infos. I will tomorrow (after upgrading to my new orbiter extruder) solder all the wires to the lis3DH and also make proper connections. Maybe just a faulty cable caused it.

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

                                            For anyone having problems getting an SPI-connected accelerometer to work:

                                            I have found that capacitive coupling between the SDO and CS signals in the cable can cause a glitch on CS when the accelerometer replied to a read register request, and this glitch stops the accelerometer sending any more data. This is especially likely if those two signals, which use adjacent pins on the Adafruit LIS3DH board, use adjacent conductors in a flat cable. I was able to work around this by putting a 1K resistor in series with SDO at the accelerometer end of the cable.

                                            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

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