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

3.5.0b1+ Wifi error - SPI timeout

Scheduled Pinned Locked Moved Unsolved
Beta Firmware
8
39
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.
  • undefined
    StreetFurnitureAustralia @OwenD
    last edited by 28 Mar 2023, 21:29

    @OwenD I can't replicate it but when it happens again then I can try and get it.

    1 Reply Last reply Reply Quote 0
    • undefined
      StreetFurnitureAustralia @OwenD
      last edited by StreetFurnitureAustralia 30 Mar 2023, 23:22

      @OwenD I'm not in the office but a colleague sent me thisreceived_6062637163802703.mp4

      As you can see its being spammed

      undefined 1 Reply Last reply 31 Mar 2023, 03:00 Reply Quote 0
      • undefined
        OwenD @StreetFurnitureAustralia
        last edited by 31 Mar 2023, 03:00

        @StreetFurnitureAustralia
        That's the same behaviour
        Can you try to get the reports as shown above and then roll the wifi back to 1.2.7
        I haven't had a repeat since rolling back but it's infrequent for me, so I can't be sure it's the firmware

        undefined 1 Reply Last reply 3 Apr 2023, 22:11 Reply Quote 0
        • undefined
          StreetFurnitureAustralia @OwenD
          last edited by StreetFurnitureAustralia 4 Mar 2023, 22:55 3 Apr 2023, 22:11

          @OwenD I will try just never don't this before, is there a way to log this via the duet webinterface and not need to connect a laptop directly?

          undefined 1 Reply Last reply 4 Apr 2023, 02:22 Reply Quote 0
          • undefined
            OwenD @StreetFurnitureAustralia
            last edited by 4 Apr 2023, 02:22

            @StreetFurnitureAustralia
            No, if the wifi module can't connect then the only way to get the info is via a terminal like YAT using the usb connection
            If you roll back to 1.27 and have no further issues it's at least showing the same results as I'm getting
            Maybe it's an Aussie only issue?
            Wifi channel or something related?

            undefined 2 Replies Last reply 4 Apr 2023, 03:06 Reply Quote 0
            • undefined
              StreetFurnitureAustralia @OwenD
              last edited by 4 Apr 2023, 03:06

              @OwenD could make sense, This is at my work and we use Unifi wifi gear. How about yourself?

              undefined 1 Reply Last reply 6 Apr 2023, 10:25 Reply Quote 0
              • undefined
                Aitor @StreetFurnitureAustralia
                last edited by 6 Apr 2023, 10:25

                Good morning @dc42 ,

                I would like to share my case in this post, I don't know if it will help.

                After a while (X), usually the next day, my printer loses connection and I have to reset it to get a new IP address. In addition, it often changes IP addresses, and I have even been given IP addresses that have already been assigned to other Duets.

                The commands I used to use to establish a connection no longer work:

                M552 S-1
                G4 S1
                M552 S0
                G4 S1
                M552 S1
                

                To solve this problem, I have had to use the following commands:

                M552 S-1
                G4 S1
                M400
                M552 S0
                G4 S1
                M400
                M552 S1
                

                If I don't perform these steps, sometimes I can't connect the printer. I suppose that these commands cannot be launched during a print to switch from M552 S1 to M552 S2 (although I haven't tried it).

                Finally, I would like to share the results of M122 and the object model and M540 command, as I think this may be where one of the problems lies:

                In M122, the MAC address is visible.
                In the object model and the M540 command, the MAC address is "00:00:00:00:00:00".

                6/4/2023, 12:19:43	M540
                MAC: 00:00:00:00:00:00
                6/4/2023, 12:04:07	M122
                === Diagnostics ===
                RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5beta2+ (2023-02-10 11:58:19) running on Duet WiFi 1.02 or later
                
                === Network ===
                Slowest loop: 6.76ms; fastest: 0.00ms
                Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
                HTTP sessions: 1 of 8
                = WiFi =
                Network state is active
                WiFi module is connected to access point 
                Failed messages: pending 0, notready 0, noresp 0
                WiFi firmware version 2.1beta3
                WiFi MAC address e8:68:e7:79:5f:a3
                WiFi Vcc 3.39, reset reason Turned on by main processor
                WiFi flash size 2097152, free heap 43068
                WiFi IP address 192.168.1.18
                WiFi signal strength -54dBm, mode 802.11n, reconnections 0, sleep mode modem
                Clock register 00002002
                Socket states: 0 0 0 0 0 0 0 0
                
                1 Reply Last reply Reply Quote 0
                • undefined
                  StreetFurnitureAustralia @OwenD
                  last edited by 11 Apr 2023, 23:51

                  @OwenD I couldn't get the info due to time restraints at work but I have rolled it back.

                  undefined 1 Reply Last reply 17 Apr 2023, 02:58 Reply Quote 0
                  • undefined
                    StreetFurnitureAustralia @StreetFurnitureAustralia
                    last edited by 17 Apr 2023, 02:58

                    @OwenD @dc42 reverting back to 1.27 has made the SPI issue disappear for me.

                    undefined 1 Reply Last reply 17 Apr 2023, 07:32 Reply Quote 0
                    • undefined
                      OwenD @StreetFurnitureAustralia
                      last edited by 17 Apr 2023, 07:32

                      @StreetFurnitureAustralia
                      I also did not get any re-occurences with WiFi 1.27
                      I have been running RRF3.5b4 and WifFi version 2.1b4 for several days now with no errors.
                      May be too early to tell but it may be fixed.

                      undefined 1 Reply Last reply 18 Apr 2023, 06:40 Reply Quote 0
                      • undefined
                        StreetFurnitureAustralia @OwenD
                        last edited by 18 Apr 2023, 06:40

                        @OwenD I can't see beta 4 only beta 3.

                        undefined 1 Reply Last reply 18 Apr 2023, 06:52 Reply Quote 0
                        • undefined
                          OwenD @StreetFurnitureAustralia
                          last edited by 18 Apr 2023, 06:52

                          @StreetFurnitureAustralia
                          Typo on my part.
                          RRF is b3
                          BAB3A2BA-E7E6-4149-9EBD-4CCA6D67548C.jpeg

                          undefined 2 Replies Last reply 20 Apr 2023, 06:43 Reply Quote 0
                          • undefined
                            StreetFurnitureAustralia @OwenD
                            last edited by 20 Apr 2023, 06:43

                            @OwenD ok cheers will give it a try

                            undefined 1 Reply Last reply 25 Apr 2023, 21:30 Reply Quote 0
                            • undefined
                              StreetFurnitureAustralia @StreetFurnitureAustralia
                              last edited by 25 Apr 2023, 21:30

                              This post is deleted!
                              1 Reply Last reply Reply Quote 0
                              • undefined
                                StreetFurnitureAustralia @OwenD
                                last edited by 26 Apr 2023, 00:51

                                @OwenD @dc42 I am still getting the SPI issue on the new firmware and I seem to be able to recreate the issue by going into the Unifi web UI and going to the duet and clicking reconnect that seems to put it into that error state

                                1 Reply Last reply Reply Quote 0
                                • undefined
                                  RozMark
                                  last edited by 16 May 2023, 08:54

                                  I have the same issue, Duet 2 WiFI v3.5.0-beta.3, Duet WiFi server 2.1beta4 and DWC 3.5.0-beta.3
                                  Currently can't connect to board trough USB, not enough place for straight USB plug, waiting 90 degrees USB plug.
                                  Reseting WiFI (M552 S-1) is hard trough PanelDue because error was spaming PanelDue with popup messages and it's not posible to press Console button when errors poping constantly.
                                  Any news about that error?

                                  undefined 1 Reply Last reply 16 May 2023, 09:02 Reply Quote 0
                                  • undefined
                                    OwenD @RozMark
                                    last edited by 16 May 2023, 09:02

                                    @RozMark
                                    I haven't had a re-occurrence since 3.5b3 (now on 3.5b3+)

                                    1 Reply Last reply Reply Quote 0
                                    • undefined
                                      RozMark
                                      last edited by 16 May 2023, 11:07

                                      I think this error started when I did upgrade firmware from 3.4.3 to 3.5.0beta3.
                                      At first I didn't upgraded DuetWifiServer and then first time this error happened.
                                      So I concluded that most likely problem was with old version od Wifi server so I upgraded to latest version.
                                      And I did it twice because first time I was not sure if it finished correctly because error apared again.
                                      I'm not home at the moment so I can't check if DuetWifiServer is 2.1beta4, It is 2.1 just not sure if it is beta4 or what.

                                      Yestereday, in 3 hours got this error twice.
                                      I'm using WiFi extender because signal was to weak for direct connecting to router if that have any importance.

                                      1 Reply Last reply Reply Quote 0
                                      • droftartsundefined droftarts referenced this topic 17 May 2024, 16:38
                                      • First post
                                        Last post
                                      Unless otherwise noted, all forum content is licensed under CC-BY-SA