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

    [Solved][Duet2Wifi] WiFi SPI Timeout after removing SBC Mod

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    5
    13
    781
    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.
    • keyz182undefined
      keyz182 @T3P3Tony
      last edited by

      @t3p3tony

      Connecting...
      Printer is now online.
      >>>M997 S1
      SENDING:M997 S1
      Trying to connect at 230400 baud:
       success
      Erasing 4096 bytes...
      Erasing 196608 bytes...
      Uploading file...
      5% complete
      10% complete
      15% complete
      20% complete
      25% complete
      30% complete
      35% complete
      40% complete
      45% complete
      50% complete
      55% complete
      60% complete
      65% complete
      70% complete
      75% complete
      80% complete
      85% complete
      90% complete
      95% complete
      Upload successful
      

      And for good measure I did an M997 S0 too which correctly reports 3.3 after a restart and M122.

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

        @keyz182 ok to the UART comms to the module is working. Have a look at the schematic here

        https://github.com/Duet3D/Duet-2-Hardware/blob/master/Duet2/Old versions/DuetWifiv1.02/DuetWifi_Schematic_v1.02.pdf

        you can test the continuity for the SPI pins

        www.duet3d.com

        keyz182undefined 2 Replies Last reply Reply Quote 0
        • keyz182undefined
          keyz182 @T3P3Tony
          last edited by

          @t3p3tony Continuity to the MCU for MOSI, MISO and SPCK, any other pins I should check?

          dc42undefined 1 Reply Last reply Reply Quote 0
          • keyz182undefined
            keyz182 @T3P3Tony
            last edited by

            @t3p3tony There's continuity on all three.

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

              @keyz182 also the ESP_DATA_RDY and NPCS0

              www.duet3d.com

              keyz182undefined albertshaoundefined 2 Replies Last reply Reply Quote 0
              • dc42undefined
                dc42 administrators @keyz182
                last edited by

                @keyz182 is the SPI timeout message consistent? That message is sometimes produced spuriously, especially when sending a M587 command for the first time after re-flashing the WiFi firmware.

                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
                • keyz182undefined
                  keyz182 @T3P3Tony
                  last edited by

                  @t3p3tony Continuity (through 2.2KOhm) on both which seems to tally up with the schematic.

                  @dc42 It's consistent. Right after a flash, leaving it a while, rebooting, etc, all the same as soon as I try M587 or M122.

                  Connecting...
                  Printer is now online.
                  >>>M552 S1
                  SENDING:M552 S1
                  WiFi module started
                  WiFi reported error: no known networks found
                  WiFi module is idle
                  WiFi reported error: no known networks found
                  WiFi module is idle
                  WiFi reported error: no known networks found
                  WiFi module is idle
                  WiFi reported error: no known networks found
                  WiFi module is idle
                  WiFi reported error: no known networks found
                  WiFi module is idle
                  WiFi reported error: no known networks found
                  WiFi module is idle
                  WiFi reported error: no known networks found
                  WiFi module is idle
                  WiFi reported error: no known networks found
                  WiFi module is idle
                  >>>M587 S"IoT_2G" P"********"
                  SENDING:M587 S"IoT_2G" P"********"
                  Error: M587: Failed to add SSID to remembered list: SPI timeout
                  [ERROR] Error: M587: Failed to add SSID to remembered list: SPI timeout
                  
                  Error retrieving WiFi status message: SPI timeout
                  [ERROR] Error retrieving WiFi status message: SPI timeout
                  
                  WiFi module is idle
                  Failed to change WiFi mode: SPI timeout
                  >>>M552 S-1
                  SENDING:M552 S-1
                  >>>M552 S0
                  SENDING:M552 S0
                  WiFi module started
                  >>>M552 S1
                  SENDING:M552 S1
                  WiFi reported error: no known networks found
                  WiFi module is idle
                  WiFi reported error: no known networks found
                  WiFi module is idle
                  >>>M587 S"IoT_2G" P"********"
                  SENDING:M587 S"IoT_2G" P"********"
                  Error: M587: Failed to add SSID to remembered list: SPI timeout
                  [ERROR] Error: M587: Failed to add SSID to remembered list: SPI timeout
                  
                  Error retrieving WiFi status message: SPI timeout
                  [ERROR] Error retrieving WiFi status message: SPI timeout
                  
                  WiFi module is idle
                  Failed to change WiFi mode: SPI timeout
                  
                  
                  jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                  • jay_s_ukundefined
                    jay_s_uk @keyz182
                    last edited by

                    @keyz182 can you try sending M552 S0 before trying M587?
                    I find its sometimes not happy sending the wifi details when in S1

                    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

                    keyz182undefined 1 Reply Last reply Reply Quote 1
                    • keyz182undefined
                      keyz182 @jay_s_uk
                      last edited by

                      @jay_s_uk OK, that worked. Is that documented behavior that I've just misread? I swear I've always done M552 S1 before any M587 commands.

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

                        @keyz182 the step by step guide does say to put it in S0 mode first.
                        Its also they way I've documented it on all the STM32/LPC port support pages.

                        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

                        1 Reply Last reply Reply Quote 1
                        • albertshaoundefined
                          albertshao @T3P3Tony
                          last edited by

                          @t3p3tony what do ESP_DATA_RDY and NPCS0 for? can this to pin connect to GND or 3.3V pull up, thanks for reply

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