Navigation

    Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Duet2 Wifi+Duex5 and SBC

    Firmware installation
    6
    50
    612
    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.
    • taconite
      taconite last edited by

      Hey guys,

      as this topic is a little flooded (https://forum.duet3d.com/topic/17203/duet-2-ethernet-and-sbc) I would just like to get things straight.

      To get the setup Duet2 Wifi + duex5 + SBC to work I need to do the following

      1. Attach 1 of deadwood83's boards to the duet wifi
        73653393-8143-410a-8760-6e1e42f565ee-grafik.png

      2. Connect the Pi and the Duet with a weird old ethernet cable (for the twisted pairs)

      3. Put DSF on the Pi (Version 3.2.0) and put the SD card into the PI

      4. configure the Pi as in SBC Setup for Duet3 (https://duet3d.dozuki.com/Wiki/SBC_Setup_for_Duet_3)

      5. Bossa RRF 3.2 (Duet2Firmware_SBC.bin) onto the due2 wifi.

      6. Don't have a config on the SD-card of the duet or no SD-card at all

      7. Run it and have fun

      Anything I missed?

      Custom ANET A8
      Custom Delta: D-PATCH (Delta Printer with Automatic Tool CHanging) https://forum.duet3d.com/topic/16082/d-patch?_=1596131234754

      All I do here is under this license: CC BY-NC-SA

      wilriker 1 Reply Last reply Reply Quote 0
      • taconite
        taconite last edited by

        @deadwood83 @bearer @wilriker could you please assist šŸ™‚

        Custom ANET A8
        Custom Delta: D-PATCH (Delta Printer with Automatic Tool CHanging) https://forum.duet3d.com/topic/16082/d-patch?_=1596131234754

        All I do here is under this license: CC BY-NC-SA

        1 Reply Last reply Reply Quote 0
        • wilriker
          wilriker Moderator @taconite last edited by

          @taconite Your list looks complete to me.

          Re #2: Depending on the length of your connection between D2 and Pi you don't need twisted pair (I use ordinary straight jumper wires and even running four 4-wire stepper cablings across it didn't have an influence). But of course better wiring never hurts.

          Re #6: do not insert the SD card.

          Manuel
          Duet 3 6HC (v0.6) with RPi 4B on a custom Cartesian
          with probably always latest firmware/DWC (incl. betas or self-compiled)
          My Tool Collection

          1 Reply Last reply Reply Quote 0
          • taconite
            taconite last edited by

            @wilriker thank you for your reply! Do I need to do something special for the SPI Pins on the WiFi ESP?

            #2 alright than I will try both and see what the difference will be
            #6 alright!

            Custom ANET A8
            Custom Delta: D-PATCH (Delta Printer with Automatic Tool CHanging) https://forum.duet3d.com/topic/16082/d-patch?_=1596131234754

            All I do here is under this license: CC BY-NC-SA

            1 Reply Last reply Reply Quote 0
            • taconite
              taconite last edited by

              So I made the initial setup according to the list. Pi (Pi 3B+) is working but I don't get a connection to the duet: "failed to connect to duet3" Please check your connection (DCS is not started).

              the cable is setup like: duet --> SBC
              CS --> pin 24
              RDC --> pin 22
              3,3V --> pin 17
              MISO --> pin 21
              MOSI --> pin 19
              SCK --> pin 23
              GND --> pin 20

              There is no SD-card in the duet.
              Duet2 Wifi is connected via USB to Laptop
              Pi has its own power supply
              Any ideas how to troubleshoot?

              Custom ANET A8
              Custom Delta: D-PATCH (Delta Printer with Automatic Tool CHanging) https://forum.duet3d.com/topic/16082/d-patch?_=1596131234754

              All I do here is under this license: CC BY-NC-SA

              wilriker 1 Reply Last reply Reply Quote 0
              • wilriker
                wilriker Moderator @taconite last edited by wilriker

                @taconite I don't know what RDC pin is (EDIT: I guess that's a typo and actually refers to the TfrRdy Pin) but I miss Transfer Ready pin that is (in default configuration) connected to pin 25 of RPi.

                EDIT: I found that in my setup it was absolutely necessary to have an addition ground connection between the RPi and the PSU that delivers VIN to Duet. As you are still working with power from USB that's not critical yet, but keep that in mind.

                Manuel
                Duet 3 6HC (v0.6) with RPi 4B on a custom Cartesian
                with probably always latest firmware/DWC (incl. betas or self-compiled)
                My Tool Collection

                1 Reply Last reply Reply Quote 0
                • taconite
                  taconite last edited by taconite

                  @wilriker you are absolutely right - it was a typo. it should be RDY.

                  mhh okay that is weird - I didn't find a 100% info about the wiring so I searched it together from here (https://forum.duet3d.com/topic/17241/quest-duet2wifi-sbc-without-espectomy-possible-yes/2)

                  EDIT: mhh pictures are not uploading
                  and here (https://forum.duet3d.com/topic/17203/duet-2-ethernet-and-sbc)
                  ![0_1612471698173_wire2.PNG](Uploading 100%)

                  EDIT: thank you for the grounding info. that's gonna be a little problematic because for the test setup I am powering the pi with a Pi power supply (micro USB) but I will find a solution for that.

                  Custom ANET A8
                  Custom Delta: D-PATCH (Delta Printer with Automatic Tool CHanging) https://forum.duet3d.com/topic/16082/d-patch?_=1596131234754

                  All I do here is under this license: CC BY-NC-SA

                  wilriker 1 Reply Last reply Reply Quote 0
                  • wilriker
                    wilriker Moderator @taconite last edited by wilriker

                    @taconite My fault. I was mixing up RPi pin numbering schemes. I meant GPIO 25 which is physical pin 22. So that's actually correct on your end already.

                    Too tired right now for good ideas, sorry.

                    Re ground connection: it's totally sufficient to connect any one of the ground pins of RPi's GPIO header to ground of your PSU. While testing I even powered the Duet from one of the USB ports of the RPi. Worked fine. Only when I eventually applied 24V VIN to the Duet it was that I required this extra connection for stable communication.

                    Manuel
                    Duet 3 6HC (v0.6) with RPi 4B on a custom Cartesian
                    with probably always latest firmware/DWC (incl. betas or self-compiled)
                    My Tool Collection

                    1 Reply Last reply Reply Quote 1
                    • taconite
                      taconite last edited by

                      @wilriker alright! Than get a good night of sleep šŸ˜‰
                      I would really appreciate if you could come back tomorrow with some fresh ideas šŸŽÆ haha

                      Maybe with an idea how i could diagnose a possible error. To narrow it down why it is not connecting.

                      Custom ANET A8
                      Custom Delta: D-PATCH (Delta Printer with Automatic Tool CHanging) https://forum.duet3d.com/topic/16082/d-patch?_=1596131234754

                      All I do here is under this license: CC BY-NC-SA

                      1 Reply Last reply Reply Quote 0
                      • A Former User
                        A Former User last edited by

                        logging in via ssh to see why dcs isn't starting would be a a good start, see systemctl status duetcontrolserver.service and/or journalctl -xeu duetcontrolserver.service for details.

                        To troubeshoot the spi stuff maybe search for "loopback" to see an old thread troubleshooting a faulty raspberry pi

                        1 Reply Last reply Reply Quote 0
                        • taconite
                          taconite last edited by taconite

                          @bearer

                          
                          - journalctl -xeu duetcontrolserver.service
                          -- Automatic restarting of the unit duetcontrolserver.service has been scheduled
                          -- the configured Restart= setting for the unit.
                          Feb 05 17:24:24 duet3 systemd[1]: Stopped Duet Control Server.
                          -- Subject: A stop job for unit duetcontrolserver.service has finished
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          --
                          -- A stop job for unit duetcontrolserver.service has finished.
                          --
                          -- The job identifier is 12641 and the job result is done.
                          Feb 05 17:24:24 duet3 systemd[1]: Starting Duet Control Server...
                          -- Subject: A start job for unit duetcontrolserver.service has begun execution
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          --
                          -- A start job for unit duetcontrolserver.service has begun execution.
                          --
                          -- The job identifier is 12641.
                          Feb 05 17:24:25 duet3 DuetControlServer[4176]: Duet Control Server v3.2.0
                          Feb 05 17:24:25 duet3 DuetControlServer[4176]: Written by Christian Hammacher fo
                          Feb 05 17:24:25 duet3 DuetControlServer[4176]: Licensed under the terms of the G
                          Feb 05 17:24:26 duet3 DuetControlServer[4176]: [info] Settings loaded
                          Feb 05 17:24:27 duet3 DuetControlServer[4176]: [info] Environment initialized
                           ESCOC
                          controlserver.service has been scheduled, as the result for
                          he unit.
                          d Duet Control Server.
                          rolserver.service has finished
                          
                          rt
                          
                          .service has finished.
                          
                          ob result is done.
                          ng Duet Control Server...
                          trolserver.service has begun execution
                          
                          rt
                          
                          r.service has begun execution.
                          
                          
                          4176]: Duet Control Server v3.2.0
                          4176]: Written by Christian Hammacher for Duet3D
                          4176]: Licensed under the terms of the GNU Public License Version 3
                          4176]: [info] Settings loaded
                          4176]: [info] Environment initialized
                           ESCOD
                          -- Automatic restarting of the unit duetcontrolserver.service has been scheduled
                          -- the configured Restart= setting for the unit.
                          Feb 05 17:24:24 duet3 systemd[1]: Stopped Duet Control Server.
                          -- Subject: A stop job for unit duetcontrolserver.service has finished
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          --
                          -- A stop job for unit duetcontrolserver.service has finished.
                          --
                          -- The job identifier is 12641 and the job result is done.
                          Feb 05 17:24:24 duet3 systemd[1]: Starting Duet Control Server...
                          -- Subject: A start job for unit duetcontrolserver.service has begun execution
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          --
                          -- A start job for unit duetcontrolserver.service has begun execution.
                          --
                          -- The job identifier is 12641.
                          Feb 05 17:24:25 duet3 DuetControlServer[4176]: Duet Control Server v3.2.0
                          Feb 05 17:24:25 duet3 DuetControlServer[4176]: Written by Christian Hammacher fo
                          Feb 05 17:24:25 duet3 DuetControlServer[4176]: Licensed under the terms of the G
                          Feb 05 17:24:26 duet3 DuetControlServer[4176]: [info] Settings loaded
                          Feb 05 17:24:27 duet3 DuetControlServer[4176]: [info] Environment initialized
                           ESCOD
                          -- Automatic restarting of the unit duetcontrolserver.service has been scheduled
                          -- the configured Restart= setting for the unit.
                          Feb 05 17:24:24 duet3 systemd[1]: Stopped Duet Control Server.
                          -- Subject: A stop job for unit duetcontrolserver.service has finished
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          --
                          -- A stop job for unit duetcontrolserver.service has finished.
                          --
                          -- The job identifier is 12641 and the job result is done.
                          Feb 05 17:24:24 duet3 systemd[1]: Starting Duet Control Server...
                          -- Subject: A start job for unit duetcontrolserver.service has begun execution
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          --
                          -- A start job for unit duetcontrolserver.service has begun execution.
                          --
                          -- The job identifier is 12641.
                          Feb 05 17:24:25 duet3 DuetControlServer[4176]: Duet Control Server v3.2.0
                          Feb 05 17:24:25 duet3 DuetControlServer[4176]: Written by Christian Hammacher fo
                          Feb 05 17:24:25 duet3 DuetControlServer[4176]: Licensed under the terms of the G
                          Feb 05 17:24:26 duet3 DuetControlServer[4176]: [info] Settings loaded
                          Feb 05 17:24:27 duet3 DuetControlServer[4176]: [info] Environment initialized
                           ESCOD
                          -- Automatic restarting of the unit duetcontrolserver.service has been scheduled
                          -- the configured Restart= setting for the unit.
                          Feb 05 17:24:24 duet3 systemd[1]: Stopped Duet Control Server.
                          -- Subject: A stop job for unit duetcontrolserver.service has finished
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          --
                          -- A stop job for unit duetcontrolserver.service has finished.
                          --
                          -- The job identifier is 12641 and the job result is done.
                          Feb 05 17:24:24 duet3 systemd[1]: Starting Duet Control Server...
                          -- Subject: A start job for unit duetcontrolserver.service has begun execution
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          --
                          -- A start job for unit duetcontrolserver.service has begun execution.
                          --
                          -- The job identifier is 12641.
                          Feb 05 17:24:25 duet3 DuetControlServer[4176]: Duet Control Server v3.2.0
                          Feb 05 17:24:25 duet3 DuetControlServer[4176]: Written by Christian Hammacher fo
                          Feb 05 17:24:25 duet3 DuetControlServer[4176]: Licensed under the terms of the G
                          Feb 05 17:24:26 duet3 DuetControlServer[4176]: [info] Settings loaded
                          Feb 05 17:24:27 duet3 DuetControlServer[4176]: [info] Environment initialized
                           ESCOD
                          -- Automatic restarting of the unit duetcontrolserver.service has been scheduled
                          -- the configured Restart= setting for the unit.
                          Feb 05 17:24:24 duet3 systemd[1]: Stopped Duet Control Server.
                          -- Subject: A stop job for unit duetcontrolserver.service has finished
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          --
                          -- A stop job for unit duetcontrolserver.service has finished.
                          --
                          -- The job identifier is 12641 and the job result is done.
                          Feb 05 17:24:24 duet3 systemd[1]: Starting Duet Control Server...
                          -- Subject: A start job for unit duetcontrolserver.service has begun execution
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          --
                          -- A start job for unit duetcontrolserver.service has begun execution.
                          --
                          -- The job identifier is 12641.
                          Feb 05 17:24:25 duet3 DuetControlServer[4176]: Duet Control Server v3.2.0
                          Feb 05 17:24:25 duet3 DuetControlServer[4176]: Written by Christian Hammacher fo
                          Feb 05 17:24:25 duet3 DuetControlServer[4176]: Licensed under the terms of the G
                          Feb 05 17:24:26 duet3 DuetControlServer[4176]: [info] Settings loaded
                          Feb 05 17:24:27 duet3 DuetControlServer[4176]: [info] Environment initialized
                           ESCOD
                          -- A stop job for unit duetcontrolserver.service has finished.
                          --
                          -- The job identifier is 12580 and the job result is done.
                          Feb 05 17:24:21 duet3 systemd[1]: Starting Duet Control Server...
                          -- Subject: A start job for unit duetcontrolserver.service has begun execution
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          -- Support: https://www.debian.org/support
                          --
                          -- The unit duetcontrolserver.service has entered the 'failed' state with result
                          Feb 05 17:24:01 duet3 systemd[1]: Failed to start Duet Control Server.
                          -- Subject: A start job for unit duetcontrolserver.service has failed
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          --
                          -- A start job for unit duetcontrolserver.service has finished with a failure.
                          --
                          -- The job identifier is 12153 and the job result is failed.
                          Feb 05 17:24:01 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=
                          Feb 05 17:24:01 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart j
                          -- Subject: Automatic restarting of a unit has been scheduled
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          --
                          -- Automatic restarting of the unit duetcontrolserver.service has been scheduled
                          -- the configured Restart= setting for the unit.
                          Feb 05 17:24:01 duet3 systemd[1]: Stopped Duet Control Server.
                          -- Subject: A stop job for unit duetcontrolserver.service has finished
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          lines 3310-3332/3657 91%
                          -- Support: https://www.debian.org/support
                          --
                          -- The unit duetcontrolserver.service has entered the 'failed' state with result 'protocol'.
                          Feb 05 17:24:01 duet3 systemd[1]: Failed to start Duet Control Server.
                          -- Subject: A start job for unit duetcontrolserver.service has failed
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          --
                          -- A start job for unit duetcontrolserver.service has finished with a failure.
                          --
                          -- The job identifier is 12153 and the job result is failed.
                          Feb 05 17:24:01 duet3 systemd[1]: duetcontrolserver.service: Service RestartSec=100ms expired, scheduling restart.
                          Feb 05 17:24:01 duet3 systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 181.
                          -- Subject: Automatic restarting of a unit has been scheduled
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          --
                          -- Automatic restarting of the unit duetcontrolserver.service has been scheduled, as the result for
                          -- the configured Restart= setting for the unit.
                          Feb 05 17:24:01 duet3 systemd[1]: Stopped Duet Control Server.
                          -- Subject: A stop job for unit duetcontrolserver.service has finished
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          --
                          -- A stop job for unit duetcontrolserver.service has finished.
                          --
                          -- The job identifier is 12214 and the job result is done.
                          Feb 05 17:24:01 duet3 systemd[1]: Starting Duet Control Server...
                          -- Subject: A start job for unit duetcontrolserver.service has begun execution
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          --
                          -- A start job for unit duetcontrolserver.service has begun execution.
                          --
                          -- The job identifier is 12214.
                          Feb 05 17:24:02 duet3 DuetControlServer[4086]: Duet Control Server v3.2.0
                          Feb 05 17:24:02 duet3 DuetControlServer[4086]: Written by Christian Hammacher for Duet3D
                          Feb 05 17:24:02 duet3 DuetControlServer[4086]: Licensed under the terms of the GNU Public License Version 3
                          Feb 05 17:24:03 duet3 DuetControlServer[4086]: [info] Settings loaded
                          Feb 05 17:24:03 duet3 DuetControlServer[4086]: [info] Environment initialized
                          Feb 05 17:24:04 duet3 DuetControlServer[4086]: [fatal] Could not connect to Duet (Timeout while waiting for transfer ready pin)
                          Feb 05 17:24:04 duet3 systemd[1]: duetcontrolserver.service: Failed with result 'protocol'.
                          -- Subject: Unit failed
                          -- Defined-By: systemd
                          -- Support: https://www.debian.org/support
                          --
                          -- The unit duetcontrolserver.service has entered the 'failed' state with result 'protocol'.
                          Feb 05 17:24:04 duet3 systemd[1]: Failed to start Duet Control Server.
                          -- Subject: A start job for unit duetcontrolserver.service has failed
                          lines 3310-3358/3657 92%
                          

                          Custom ANET A8
                          Custom Delta: D-PATCH (Delta Printer with Automatic Tool CHanging) https://forum.duet3d.com/topic/16082/d-patch?_=1596131234754

                          All I do here is under this license: CC BY-NC-SA

                          A Former User 1 Reply Last reply Reply Quote 0
                          • taconite
                            taconite last edited by taconite

                            systemctl status duetcontrolserver.service
                            ā— duetcontrolserver.service - Duet Control Server
                               Loaded: loaded (/lib/systemd/system/duetcontrolserver.service; enabled; vendo
                               Active: activating (start) since Fri 2021-02-05 17:23:47 CET; 1s ago
                             Main PID: 4023 (DuetControlServ)
                                Tasks: 9 (limit: 2063)
                               CGroup: /system.slice/duetcontrolserver.service
                                       └─4023 /opt/dsf/bin/DuetControlServer
                            
                            Feb 05 17:23:47 duet3 systemd[1]: Starting Duet Control Server...
                            Feb 05 17:23:48 duet3 DuetControlServer[4023]: Duet Control Server v3.2.0
                            Feb 05 17:23:48 duet3 DuetControlServer[4023]: Written by Christian Hammacher fo
                            Feb 05 17:23:48 duet3 DuetControlServer[4023]: Licensed under the terms of the G
                            

                            so there is not a lot of info ...

                            Custom ANET A8
                            Custom Delta: D-PATCH (Delta Printer with Automatic Tool CHanging) https://forum.duet3d.com/topic/16082/d-patch?_=1596131234754

                            All I do here is under this license: CC BY-NC-SA

                            1 Reply Last reply Reply Quote 0
                            • A Former User
                              A Former User @taconite last edited by

                              @taconite said in Duet2 Wifi+Duex5 and SBC:

                              Feb 05 17:24:04 duet3 DuetControlServer[4086]: [fatal] Could not connect to Duet (Timeout while waiting for transfer ready pin)

                              this suggest the trf_rdy pin isn't wired/working correctly.

                              (also please put three backticks (```) over and under long text like that to preserve formatting next time, or use the code formatting button on the toolbar (between strikeout and link))

                              1 Reply Last reply Reply Quote 0
                              • taconite
                                taconite last edited by taconite

                                So I rechecked the wiring and the board itself - didn't find any issues. Reflashed the SBC firmware to the Duet and it seems that now I get a connection even though it is not really stable. BTW the Duex5 is not connected right now

                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] RepRapFirmware got a bad header checksum
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] RepRapFirmware got a bad header checksum
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] Restarting transfer because the number of maximum retries has been exceeded
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] RepRapFirmware got a bad header checksum
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] RepRapFirmware got a bad header checksum
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] RepRapFirmware got a bad header checksum
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] Restarting transfer because the number of maximum retries has been exceeded
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] RepRapFirmware got a bad header checksum
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] RepRapFirmware got a bad header checksum
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] RepRapFirmware got a bad header checksum
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] Restarting transfer because the number of maximum retries has been exceeded
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] RepRapFirmware got a bad header checksum
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] RepRapFirmware got a bad header checksum
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] RepRapFirmware got a bad header checksum
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] Restarting transfer because the number of maximum retries has been exceeded
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] RepRapFirmware got a bad header checksum
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] RepRapFirmware got a bad header checksum
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] RepRapFirmware got a bad header checksum
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] Restarting transfer because the number of maximum retries has been exceeded
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] Bad header CRC32 (expected 0x00000000, got 0x59923eca)
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000000)
                                Feb 06 13:54:07 duet3 DuetControlServer[5480]: [info] Connection to Duet established
                                Feb 06 13:54:08 duet3 DuetControlServer[5480]: [warn] Lost connection to Duet (Board is not available (no header))
                                
                                

                                EDIT: So it's more like a "connection" šŸ˜„ I can reach it over the network and I uploaded a valid config but its not responsive at all

                                e8c89dcc-18a5-4361-acc5-a5dd7f1e2225-grafik.png

                                Custom ANET A8
                                Custom Delta: D-PATCH (Delta Printer with Automatic Tool CHanging) https://forum.duet3d.com/topic/16082/d-patch?_=1596131234754

                                All I do here is under this license: CC BY-NC-SA

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

                                  Can you provide a photo of the wiring between the Duet and the Pi?

                                  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
                                  • A Former User
                                    A Former User last edited by

                                    Verify RRF and DSF versions are compatible, if they are, odds are the connection is the issue given the checksum/crc issues.

                                    How is the common ground between the duet and sbc?

                                    Have you tried lowering the SPI frequency? (Edit there is a json config file under /opt/dsf on the sbc

                                    1 Reply Last reply Reply Quote 0
                                    • taconite
                                      taconite last edited by taconite

                                      @bearer
                                      I got DuetPI (With GUI form here):
                                      https://duet3d.dozuki.com/Wiki/SBC_Setup_for_Duet_3
                                      RRF is 3.2.0

                                      I will provide Pictures of the common ground and the wiring in a minute. (maybe I should increase the gauge of the common ground)

                                      No I didn't change the SPI speed but I could try to
                                      @dc42
                                      EDIT: The black single cable is the common ground
                                      20210206_200350.jpg
                                      20210206_200328.jpg
                                      20210206_200404.jpg

                                      Custom ANET A8
                                      Custom Delta: D-PATCH (Delta Printer with Automatic Tool CHanging) https://forum.duet3d.com/topic/16082/d-patch?_=1596131234754

                                      All I do here is under this license: CC BY-NC-SA

                                      1 Reply Last reply Reply Quote 0
                                      • A Former User
                                        A Former User last edited by

                                        The little pcb has a pad labeled gnd1, this also carries a common ground from the duet to the sbc?

                                        and the shield is grounded at both ends? if the shield is the ground connection thats not optimal either, ground the shield at one end and use a conductor for signal ground

                                        the cable also seems a bit long in the tooth, reducing the spi frequency might help if the length is the issue.

                                        /opt/dsf/conf/config.conf and reduce the "SpiFrequency": 8000000, to maybe 2mhz or even less

                                        1 Reply Last reply Reply Quote 0
                                        • taconite
                                          taconite last edited by

                                          Yes the GND1 of the little PCB from @deadwood83 has a connection to the GND of the Duet and the SBC

                                          So what I did:

                                          1. Removed the Shield from one side
                                          2. connected the GND1 pin of the little PCB with an extra cable to the GND of the SBC
                                          3. reduced the spifrequency to 2 MHz.
                                            --> same thing as before

                                          What do you mean with "bit long in the tooth"

                                          Custom ANET A8
                                          Custom Delta: D-PATCH (Delta Printer with Automatic Tool CHanging) https://forum.duet3d.com/topic/16082/d-patch?_=1596131234754

                                          All I do here is under this license: CC BY-NC-SA

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

                                            The Duet to Pi cable is way too long. Also, as it is a round cable, it will have higher capacitance and more crosstalk than a ribbon cable would. You should replace it by a short (150mm or less) ribbon 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

                                            1 Reply Last reply Reply Quote 1
                                            • taconite
                                              taconite last edited by

                                              Changed to a short ribbon cable - nothing changed - still "no header" fault message

                                              20210207_142122.jpg 20210207_140707.jpg

                                              Custom ANET A8
                                              Custom Delta: D-PATCH (Delta Printer with Automatic Tool CHanging) https://forum.duet3d.com/topic/16082/d-patch?_=1596131234754

                                              All I do here is under this license: CC BY-NC-SA

                                              1 Reply Last reply Reply Quote 0
                                              • taconite
                                                taconite last edited by

                                                maybe I should try the duetpi-lite?

                                                Custom ANET A8
                                                Custom Delta: D-PATCH (Delta Printer with Automatic Tool CHanging) https://forum.duet3d.com/topic/16082/d-patch?_=1596131234754

                                                All I do here is under this license: CC BY-NC-SA

                                                1 Reply Last reply Reply Quote 0
                                                • taconite
                                                  taconite last edited by

                                                  @dc42 Sorry for bothering you again. Do you any other ideas?

                                                  Custom ANET A8
                                                  Custom Delta: D-PATCH (Delta Printer with Automatic Tool CHanging) https://forum.duet3d.com/topic/16082/d-patch?_=1596131234754

                                                  All I do here is under this license: CC BY-NC-SA

                                                  1 Reply Last reply Reply Quote 0
                                                  • wilriker
                                                    wilriker Moderator last edited by

                                                    Sorry for not getting back to you earlier. DuetPi-lite won't make a difference.

                                                    Can you please run DuetControlServer from command-line with -l debug to use debug log level and post the output? Former output posted here did not contain enough information.

                                                    Manuel
                                                    Duet 3 6HC (v0.6) with RPi 4B on a custom Cartesian
                                                    with probably always latest firmware/DWC (incl. betas or self-compiled)
                                                    My Tool Collection

                                                    taconite 1 Reply Last reply Reply Quote 1
                                                    • taconite
                                                      taconite @wilriker last edited by

                                                      @wilriker said in Duet2 Wifi+Duex5 and SBC:

                                                      Sorry for not getting back to you earlier. DuetPi-lite won't make a difference.

                                                      Can you please run DuetControlServer from command-line with -l debug to use debug log level and post the output? Former output posted here did not contain enough information.

                                                      No problem at all! Don't feel sorry - every help is appreciated!

                                                      With what command line exacly? Sorry I am a bit of a noob with RPi and Shell

                                                      Custom ANET A8
                                                      Custom Delta: D-PATCH (Delta Printer with Automatic Tool CHanging) https://forum.duet3d.com/topic/16082/d-patch?_=1596131234754

                                                      All I do here is under this license: CC BY-NC-SA

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