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

    Ethernet with SBC (RPI) on Octopus Pro F429 board

    Scheduled Pinned Locked Moved
    STM
    3
    21
    1.7k
    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.
    • jay_s_ukundefined
      jay_s_uk @selva_tvi
      last edited by

      @selva_tvi yep, those connections are correct.
      Whats not clear about them?

      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

      selva_tviundefined 1 Reply Last reply Reply Quote 0
      • selva_tviundefined
        selva_tvi @jay_s_uk
        last edited by

        @jay_s_uk @gloomyandy Hi, I have tried connecting Octopus pro with RPI.

        Octopus Pro side:

        1. Already ESP8266 was connected. Removed that.
        2. Updated the firmware to 'firmware-stm32f4-sbc-3.3.0_11.bin'. Renaming to firmware.bin. Updated successfully.
        3. I used the existing folders - code, macros, www as it is.
        4. Uploaded the new sys files (through the configurator with SBC)
        5. Connected with Pronterface. It was connecting. Movements are happening. But while homing, it showed 'homex.g not found.

        RPI Side: (RPI 4 Model B)

        1. Got a new sd card of 32GB

        2. Flashed Duet Pi Lite through Balena Etcher

        3. Created wpa_supplicant.conf in the root folder of boot drive, added the following line: (Used the country as India)
          country=IN
          update_config=1
          ctrl_interface=/var/run/wpa_supplicant

          network={
          ssid="SSID_OF_NETWORK"
          psk="PASSWORD_OF_NETWORK"
          }

        4. Kept the SD card in RPI. (Didn't do any extra steps)

        5. RPI powered through Power bank (5V, 2.1A)

        6. Gave the Jumper connections between RPI and Octopus Pro

        7. Except GND all were connected through 100ohm Resistor.
          Connection.jpeg

        8. Switched on both the printer and RPI

        9. After 1 minute, RPI showed in Network. Checked with Fing app
          Fing.jpeg

        10. When Trying to connect to the network by using duet3d.local/ or the given IP address, it is not connecting.
          Following error is coming.
          Error.jpeg

        Pls let me know if anything is wrong

        jay_s_ukundefined 1 Reply Last reply Reply Quote 0
        • jay_s_ukundefined
          jay_s_uk @selva_tvi
          last edited by

          @selva_tvi that shows you your wiring is wrong so revisit that.
          please keep the cables nice and short (under 100mm)
          and if you downloaded the latest duetpi image, use 3.4 on the octopus not 3.3

          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

          selva_tviundefined 1 Reply Last reply Reply Quote 0
          • selva_tviundefined
            selva_tvi @jay_s_uk
            last edited by selva_tvi

            @jay_s_uk Thanks. I updated 'firmware-stm32f4-wifi-3.4.0_1.bin'.

            There is confusion with the configuration.

            Below are the lines are taken from the below website:
            https://teamgloomy.github.io/btt_octopus_pro_1.0_f429_connected_sbc.html

            //Config for BTT Octopus Pro v1.0 F429 Version
            board = biqoctopuspro_1.0
            sbc.TfrReadyPin = D.10

            heat.tempSensePins = { F.3, F.4, F.5, F.6, F.7 }
            leds.diagnostic = A.13

            In the above, Tfr ready pin is given as D.10

            But, when i used the configurator for SBC, it is giving the below lines
            //SBC Settings
            sbc.TfrReadyPin = G.7;
            heat.tempSensePins = {bedtemp,e0temp,e1temp}; //Max of 3 entries

            1. Which one is correct? D.10 or G.7
            2. Also pls check the heat.tempsensepins.
            3. Also, should I copy all the sys files from Octopus Pro SD to RPI SD?

            My main error is 'Timeout while waiting for Transfer ready pin'.

            Pins.jpg

            jay_s_ukundefined 1 Reply Last reply Reply Quote 0
            • jay_s_ukundefined
              jay_s_uk @selva_tvi
              last edited by

              @selva_tvi

              @selva_tvi said in Ethernet with SBC (RPI) on Octopus Pro F429 board:

              I updated 'firmware-stm32f4-wifi-3.4.0_1.bin'.

              you need the SBC build not the WiFi build

              Use D.10. Looks like I have an issue with the configurator that I need to fix so I will investigate that.

              Don't worry about updating the config files yet, just get the connection going first.
              The only files you should have on the SD card on the octopus is the board.txt file in the sys folder

              Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

              selva_tviundefined 1 Reply Last reply Reply Quote 0
              • selva_tviundefined
                selva_tvi @jay_s_uk
                last edited by selva_tvi

                @jay_s_uk Great. Thanks 👍 . It worked

                DWC.JPG

                http://duet3.local/ is working.

                Also, I used the IP address and connected. It connected. I copied the sys files to the Octopus Pro board and now it is fully working.

                Now, I need only the Ethernet. (As per the client requirement). I hope this maynot be problem. Still the question.

                1. Should I disable the Wifi settings in ' wpa_supplicant.conf file' or delete the file itself? (I didn't find this file in the RPI folder ' wpa_supplicant.conf'
                jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                • jay_s_ukundefined
                  jay_s_uk @selva_tvi
                  last edited by

                  @selva_tvi i believe ethernet has priority over wifi so you shouldn't have to do anything

                  Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                  selva_tviundefined 1 Reply Last reply Reply Quote 0
                  • selva_tviundefined
                    selva_tvi @jay_s_uk
                    last edited by

                    @jay_s_uk Thanks connections is proper. Later we updated the sys files through DWC itself.

                    Now axis movements are giving issues.

                    X and Y is moving. But Z is not at all moving.

                    We are using BTT TMC2209 - 08nos in the STEP mode only.

                    In the board.txt, initially we gave as 'stepper.numSmartDrivers = 0'.

                    Then later changed to 'stepper.numSmartDrivers = 8'.

                    With this X and Y are moving. Z is not moving.

                    Also, the commands are taken very slowly by the board. After giving movement, it takes some time to move.

                    jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                    • jay_s_ukundefined
                      jay_s_uk @selva_tvi
                      last edited by

                      @selva_tvi post an output of M122
                      it might be quicker for you to come join us on discord for realtime support https://discord.gg/uS97Qs7

                      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                      selva_tviundefined 1 Reply Last reply Reply Quote 0
                      • selva_tviundefined
                        selva_tvi @jay_s_uk
                        last edited by

                        @jay_s_uk Sure. I have messaged you in Discord. Pls check

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