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

    Error Short to Ground reported by driver(s)

    Scheduled Pinned Locked Moved Unsolved
    Duet Hardware and wiring
    8
    57
    3.8k
    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.
    • davidewenundefined
      davidewen @T3P3Tony
      last edited by

      @t3p3tony

      R40 = off
      R49 = flashing red (slow flash)
      R28 = off
      R27 = off
      R29 = Red
      P30 = Green
      ESP = off

      E8763F98-CDE2-48B3-B28A-7862363876EE_1_105_c.jpeg

      elmoretundefined T3P3Tonyundefined 2 Replies Last reply Reply Quote 0
      • elmoretundefined
        elmoret @davidewen
        last edited by

        @T3P3Tony Could you assist David, please?

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

          @davidewen with it setup as you have it in the image above, please double click the reset button and see if a Duetboot drive becomes available on the PC over USB. If it does then you can drop the 3.3 firmware for mini 5+ into that drive, it will.opy across then install. After that it should be available over YAT.

          Firmware is here:

          Duet3Firmware_Mini5plus.uf2
          https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet3Firmware_Mini5plus.uf2

          www.duet3d.com

          davidewenundefined 1 Reply Last reply Reply Quote 0
          • davidewenundefined
            davidewen @T3P3Tony
            last edited by davidewen

            @t3p3tony
            Tony, as mentioned in a previous post.
            I have followed all instructions for Fallback 1 & 2 per the guide.
            Neither work. Board is not found on computer under System Information, via Terminal or Disk Utility.

            @davidewen said in Error Short to Ground reported by driver(s):

            Followed "Fallback 1 & Fallback 2" instructions @ https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware
            Neither worked.
            Still can not connect to board via USB
            Board does not show up in System Information, or in Terminal via ls /dev/tty.*.

            Results from Terminal
            @Macmini-M1 ~ % ls /dev/tty..
            zsh: no matches found: /dev/tty.
            .

            Results from System Information.
            This is what shows up when board is plugged in.
            ab54173c-01fc-450e-b153-19a24592953a-image.png

            Results from Disk Utility
            I do get a "DuetBOOT" after double clicking the reset button, and copying the firmware to the drive does cause a restart, but then I'm back to square 1.

            No Duet in System Info or Terminal.
            Even with a good copy of sys folder files, no Duet on my WiFi.

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

              @davidewen if DuetBoot shows up and the file is transferred successfully then at least part of the USB system is working as expected. I don't have a Mac to test this on - there might be some interaction between the USB driver in that particular version of MacOS/Mac hardware and the Duet. Or it might be a (partially) faulty USB hardware on the Duet.

              Would it be possible to try connecting on a PC/laptop running windows?

              www.duet3d.com

              1 Reply Last reply Reply Quote 0
              • davidewenundefined
                davidewen
                last edited by

                @t3p3tony
                I don't have a Windows computer. I do run Windows in Parallels and/or Bootcamp, but still on a Mac computer.

                I've tested the connection on the new M1 macMini and an older Intel based MacBookPro_2017. Same issue on both.

                I attempted to connect via Parallels.
                Did not work.
                Could not update the device drivers.

                269ed657-8324-403e-b295-a562b56b5281-image.png

                77ec7ca1-6dff-425e-9645-12b85fe0a210-image.png

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

                  @davidewen in that screenshot it showed a serial port on com4 - is that the Duet?

                  www.duet3d.com

                  davidewenundefined 1 Reply Last reply Reply Quote 0
                  • davidewenundefined
                    davidewen @T3P3Tony
                    last edited by

                    @t3p3tony
                    yes, that's correc

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

                      @davidewen ok so what happens when you connect to com4 with YAT?

                      www.duet3d.com

                      davidewenundefined 2 Replies Last reply Reply Quote 0
                      • davidewenundefined
                        davidewen @T3P3Tony
                        last edited by davidewen

                        @t3p3tony
                        I have Macs only, so I'm using SerialTools.

                        Your (dozuki) instructions are not very clear.
                        First you state to connect using SerialTools.
                        Then you never show any examples of SerialTools again.
                        You only show using Terminal.
                        Some consistency within your instructions would be helpful.

                        https://duet3d.dozuki.com/Guide/1.)+Getting+Connected+to+your+Duet/7

                        It looks like I can connect, but there is no information displayed.

                        f64d0840-3c19-42a6-a758-5ebcbe341c22-image.png

                        And Terminal will not connect
                        28bc1941-8465-4120-9171-8a5a5843e44a-image.png

                        T3P3Tonyundefined 1 Reply Last reply Reply Quote 0
                        • davidewenundefined
                          davidewen @T3P3Tony
                          last edited by

                          @t3p3tony

                          Using Terminal, there is still no connection to the board.

                          This is the output of ls /dev/tty..*
                          @Macmini-M1 ~ % ls /dev/tty..
                          zsh: no matches found: /dev/tty.
                          .

                          System Information does show a "communication device"

                          9704f2c3-62f4-42c9-b138-e6ae7c8dd921-image.png

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

                            @davidewen i saw you were using windows in a VM and it was detecting a Serial device on com4. Thats why I suggested trying YAT within that VM to connect to it.

                            The fact that you can see the DuetBoot device via the double click and successfully upload the firmware means that some level of USB is working so i am trying to find a way to check this without access to an similar Mac with the same OS.

                            www.duet3d.com

                            davidewenundefined 2 Replies Last reply Reply Quote 0
                            • davidewenundefined
                              davidewen @T3P3Tony
                              last edited by

                              @t3p3tony
                              I'm attempting to use Windows to connect.
                              Device drivers won't install.

                              I've downloaded the drivers from this link per the instructions
                              Windows users, download the USB drivers for Duet here and extract the files to a suitable location.
                              https://github.com/dc42/RepRapFirmware/blob/dev/Driver/WindowsDriverFiles.zip

                              cdb91d58-8a8b-4e90-9a93-97b87c9b8ada-image.png

                              1 Reply Last reply Reply Quote 0
                              • davidewenundefined
                                davidewen @T3P3Tony
                                last edited by

                                @t3p3tony
                                Something I'm thinking to mention.
                                Since my Mac has the M1 chip, Windows is the ARM version.

                                This could be the reason the drivers will not install.

                                1 Reply Last reply Reply Quote 0
                                • Phaedruxundefined
                                  Phaedrux Moderator
                                  last edited by

                                  Do you have a raspberry pi?

                                  Z-Bot CoreXY Build | Thingiverse Profile

                                  davidewenundefined 1 Reply Last reply Reply Quote 0
                                  • davidewenundefined
                                    davidewen @Phaedrux
                                    last edited by

                                    @phaedrux
                                    I do. It is not setup yet, so it would be a from scratch project.
                                    I would want / need specific steps to do so in order to accomplish what you're thinking.

                                    Thanks,
                                    David

                                    1 Reply Last reply Reply Quote 0
                                    • Phaedruxundefined
                                      Phaedrux Moderator
                                      last edited by

                                      Well if you setup the Pi as a desktop environment you could use the linux instructions from the getting connected guide to bypass the Mac/M1/WindowsARM/VM thing.

                                      Download the latest Raspberry PI OS with desktop
                                      https://downloads.raspberrypi.org/raspios_armhf/images/raspios_armhf-2021-11-08/2021-10-30-raspios-bullseye-armhf.zip

                                      Download Etcher
                                      https://www.balena.io/etcher/

                                      Burn the downloaded SD card image to an SD card with Etcher

                                      Setup the Pi with a mouse/keyboard/monitor and boot the burned SD card.

                                      Once you're up and running you can connect the Duet via USB and follow along with the getting connected guide to see if it is detected as a USB device and then hopefully connect to it via terminal.

                                      Z-Bot CoreXY Build | Thingiverse Profile

                                      davidewenundefined 1 Reply Last reply Reply Quote 2
                                      • davidewenundefined
                                        davidewen @Phaedrux
                                        last edited by

                                        @phaedrux

                                        I finally got Windows using BootCamp to recognize the Duet on COM4.
                                        The name is: Duet 3 motion control electronics (COM4)

                                        Sorry, not ready to spend the time setting up a rPi

                                        I can seemingly connect to it via YAT and/or Pronterface, but neither app will actually communicate with it.

                                        YAT, sending M115 returns;
                                        "[Warning: 4 bytes not sent anymore.]

                                        Pronterface, attempting to connect returns;
                                        "Could not connect to COM4 at baud rate (tried 9600 & 11500): PermisionError(13, 'Access is denied.' None,5)

                                        janjohundefined 1 Reply Last reply Reply Quote 0
                                        • janjohundefined
                                          janjoh @davidewen
                                          last edited by

                                          @davidewen said in Error Short to Ground reported by driver(s):

                                          @phaedrux

                                          "Could not connect to COM4 at baud rate (tried 9600 & 11500): PermisionError(13, 'Access is denied.' None,5)

                                          "Could not connect to COM4 at baud rate (tried 9600 & 11500): PermisionError(13, 'Access is denied.' None,5)

                                          Error 13 is exactly what the message says. Your process does not have permission to access the port. Usually fixed by running whatever tool in administrative mode.

                                          1 Reply Last reply Reply Quote 1
                                          • Phaedruxundefined
                                            Phaedrux Moderator
                                            last edited by

                                            Well if running as admin doesn't work setting up the pi isn't really too time consuming. Download and file copy take the most time. Other than that it's just plugging the hardware in.

                                            Z-Bot CoreXY Build | Thingiverse Profile

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