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

    After update to 3.5.0-beta.4 - wifi module reported failed

    Scheduled Pinned Locked Moved Solved
    Beta Firmware
    4
    22
    753
    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.
    • Plohishundefined
      Plohish
      last edited by Plohish

      Good afternoon, ladies and gentlemen! I have a duet 2 wifi board
      I installed firmware version 3.5.0-beta.4 , files:
      Duet2CombinedFirmware.bin
      DuetWiFiServer.bin
      After that I got no connection with my WiFi.
      I connected the terminal, specified the access point again and the system began to connect to my home WiFi, but at startup I still have an error:
      "wifi module reported failed"
      alt text
      I also installed the files
      DuetWebControl-SD.zip
      PanelDueFirmware-3.5.0-rc6-v3-5.0.bin

      Please help me understand what is the problem.

      Please forgive my bad English, it's Google's fault :)

      OwenDundefined 1 Reply Last reply Reply Quote 0
      • OwenDundefined
        OwenD @Plohish
        last edited by

        @Plohish
        Are you sure that all updates were completed?
        Have you checked the firmware versions in DWC and on the PanelDue?

        Plohishundefined 1 Reply Last reply Reply Quote 0
        • Plohishundefined
          Plohish @OwenD
          last edited by Plohish

          @OwenD
          Yes, I'm sure everything ended well
          alt text

          My printer is working, it's printing now...
          however I don't like this error at the beginning...

          Please forgive my bad English, it's Google's fault :)

          Plohishundefined 1 Reply Last reply Reply Quote 0
          • Plohishundefined
            Plohish @Plohish
            last edited by

            M122

            = WiFi =
            Interface state: active
            Module is connected to access point
            Failed messages: pending 0, notready 0, noresp 0
            Firmware version 2.1beta3
            MAC address bc:dd:c2:57:ae:51
            Module reset reason: Turned on by main processor, Vcc 3.36, flash size 2097152, free heap 42924
            WiFi IP address 172.16.1.50
            Signal strength -47dBm, channel 13, mode 802.11n, reconnections 0
            Clock register 00002002
            Socket states: 0 0 0 0 0 0 0 0

            Please forgive my bad English, it's Google's fault :)

            OwenDundefined 1 Reply Last reply Reply Quote 0
            • OwenDundefined
              OwenD @Plohish
              last edited by

              @Plohish

              If the error happens at every restart then please post

              • your config.g
              • the results of running M98 P"config.g"
              • the RRF version you upgraded from
              • if you run a daemon.g the contents of that
              Plohishundefined 1 Reply Last reply Reply Quote 0
              • Plohishundefined
                Plohish @OwenD
                last edited by

                @OwenD
                config.g

                ; Configuration file for Duet WiFi (firmware version 3)
                ; executed by the firmware on start-up
                ;
                ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sun May 03 2020 22:57:59 GMT+0300 (Москва, стандартное время)
                
                ; General preferences
                M80 C"pson"
                G90                                            ; send absolute coordinates...
                M83                                            ; ...but relative extruder moves
                M550 P"Uni_Plo"                                    ; set printer name
                
                M669 K1                                        ; select CoreXY mode
                M575 P1 S1 B57600
                
                
                ;*** End of factory test lines to be removed
                
                ; Network
                M552 S1                                        ; enable network
                M586 P0 S1                                     ; enable HTTP
                M586 P1 S1                                     ; enable FTP
                M586 P2 S0                                     ; disable Telnet
                
                ; Drives
                M569 P0 S0                                     ; physical drive 0 goes backwards
                M569 P1 S0                                     ; physical drive 1 goes backwards
                M569 P2 S0                                     ; physical drive 2 goes backwards
                M569 P3 S1                                     ; physical drive 3 goes forwards
                M584 X0 Y1 Z2 E3                               ; set drive mapping
                M350 Z32 E16 I0                                ; configure microstepping without interpolation
                M350 X16 Y16 I1                                ; configure microstepping with interpolation
                M92 X160.00 Y160.00 Z800.00 E414.00            ; set steps per mm
                ;M566 X600.00 Y600.00 Z40.00 E800.00 P1         ; Максимальный рывок (мм/сек)
                M205 X15 Y15 Z1 E12                      	   ; Максимальный рывок (мм/сек)
                M203 X12000.00 Y12000.00 Z800.00 E6000.00      ; Максимальная скорость (мм/мин)
                ;M201 X1500.00 Y1500.00 Z60.00 E1500.00         ; Максимальное ускорение (мм/сек^2)
                M201 X2000 Y2000 Z60 E2000                     ; Максимальное ускорение (мм/сек^2)
                M906 X1400 Y1400 Z1350 E700 I30                ; set motor currents (mA) and motor idle factor in per cent
                M84 S30                                        ; Set idle timeout
                
                ; Axis Limits
                M208 X0 Y0 Z0 S1                               ; set axis minima
                M208 X280 Y186 Z288 S0                         ; set axis maxima
                
                ; Endstops
                M574 X1 S1 P"xstop"                            ; configure active-high endstop for low end on X via pin xstop
                M574 Y1 S1 P"ystop"                            ; configure active-high endstop for low end on Y via pin ystop
                M574 Z2 S1 P"zstop"                            ; configure active-high endstop for high end on Z via pin zstop
                
                ; Z-Probe
                ;M558 P5 C"zprobe.in+zprobe.mod" H0 F120 T6000  ; set Z probe type to switch and the dive height + speeds
                ;G31 P500 X20 Y20 Z0.25                         ; set Z probe trigger value, offset and trigger height
                ;M557 X10:215 Y5:185 S20                        ; define mesh grid
                
                ; Heaters
                M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
                M950 H0 C"bedheat" T0 Q10                      ; create bed heater output on bedheat and map it to sensor 0
                M143 H0 S150                                   ; set temperature limit for heater 0 to 120C
                M307 H0 B0 S1.00                               ; disable bang-bang mode for the bed heater and set PWM limit
                M140 H0                                        ; map heated bed to heater 0
                ; M308 S1 P"e0temp" Y"thermistor" T100000 B4138  ; configure sensor 1 as thermistor on pin e0temp
                M308 S1 P"spi.cs1" Y"rtd-max31865"			   ; create sensor number 1 as a PT100 sensor
                M950 H1 C"e0heat" T1                           ; create nozzle heater output on e0heat and map it to sensor 1
                M143 H1 S280                                   ; set temperature limit for heater 1 to 280C
                M307 H1 B0 S1.00                               ; disable bang-bang mode for heater  and set PWM limit
                
                ; Fans
                M950 F0 C"fan0" Q500                           ; create fan 0 on pin fan0 and set its frequency
                M106 P0 S0 H-1                                 ; set fan 0 value. Thermostatic control is turned off
                M950 F1 C"fan1" Q500                           ; create fan 1 on pin fan1 and set its frequency
                M106 P1 S1 H1 T45                              ; set fan 1 value. Thermostatic control is turned on
                
                ; Tools
                M563 P0 D0 H1 F0                               ; define tool 0
                G10 P0 X0 Y0 Z0                                ; set tool 0 axis offsets
                G10 P0 R0 S0                                   ; set initial tool 0 active and standby temperatures to 0C
                M911 S22.0 R23.0 P"M913 X0 Y0 G91 M83 G1 Z7 E-3 F500"	; Automatic power saving
                M501
                
                ; Custom settings are not defined
                

                M98 P"config.g"

                HTTP is enabled on port 80
                FTP is enabled on port 21
                TELNET is disabled
                Warning: Heater 0 predicted maximum temperature at full power is 321°C
                Warning: Heater 1 predicted maximum temperature at full power is 670°C
                

                I did an update from version 3_4_5
                i don't have a file daemon.g

                Please forgive my bad English, it's Google's fault :)

                OwenDundefined 2 Replies Last reply Reply Quote 0
                • OwenDundefined
                  OwenD @Plohish
                  last edited by

                  @Plohish
                  I don't see any obvious problems there.
                  As you have updated from 3.4.5 you would have had to reset your access point using M587
                  I run almost the exact same setup without issues.
                  About the only difference I see is that I am specifying the SSID and gateway in M552 and M554
                  Is there any chance there's another WiFi network with a stronger signal?

                  1 Reply Last reply Reply Quote 0
                  • OwenDundefined
                    OwenD @Plohish
                    last edited by

                    @Plohish
                    Also ensure that it's only trying to connect to a 2.4Ghz network.
                    If you have a dual band router and both networks have the same SSID it might be trying to connect to the 5.0Ghz network

                    Plohishundefined 1 Reply Last reply Reply Quote 0
                    • Plohishundefined
                      Plohish @OwenD
                      last edited by

                      @OwenD
                      Until the update, I did not experience any problems with WiFi.
                      I have two bands on my router, but they have different SSIDs.
                      I didn't reset with M587, is that important?

                      Please forgive my bad English, it's Google's fault :)

                      OwenDundefined 1 Reply Last reply Reply Quote 0
                      • OwenDundefined
                        OwenD @Plohish
                        last edited by OwenD

                        @Plohish
                        This is from the change log when wifi 2.1b2 was released.
                        Same would apply to 2.1b3

                        For WiFi enabled boards, DuetWiFiServer version 2.1beta 2 is included with these files; however you can continue using version 1.27 if you wish. In some systems, version 2.1beta2 may give a lower upload speed than 1.27, however it supports additional features such as WiFi scanning and WPA Enterprise (details to follow) and it may work better with some WiFi access points than 1.27 does. Note, if you do upgrade to 2.1beta2 then you will have to re-enter your access point details using M587.

                        Maybe try deleting the access points and redoing again?
                        You'll need to do it via YAT or similar

                        M552 S0
                        M588 S"*"
                        M587 S"yourSSID"

                        Plohishundefined 1 Reply Last reply Reply Quote 0
                        • Plohishundefined
                          Plohish @OwenD
                          last edited by

                          @OwenD

                          i did only M587 S"your-network-ssid" P"your-network-password"
                          I will do it
                          M552 S0
                          M588 S"*"
                          M587 S"yourSSID"
                          if it doesn't work, I'll go back to the old version of WifiServer

                          Please forgive my bad English, it's Google's fault :)

                          OwenDundefined 1 Reply Last reply Reply Quote 0
                          • OwenDundefined
                            OwenD @Plohish
                            last edited by

                            @Plohish
                            You will need the password in M587 of course
                            I omitted that 🙄

                            Plohishundefined 2 Replies Last reply Reply Quote 0
                            • Plohishundefined
                              Plohish @OwenD
                              last edited by

                              @OwenD
                              Unfortunately it didn't help...
                              I returned to 1.27, no more problems!

                              Please forgive my bad English, it's Google's fault :)

                              droftartsundefined 1 Reply Last reply Reply Quote 0
                              • Plohishundefined
                                Plohish @OwenD
                                last edited by Plohish

                                @OwenD
                                there is another small problem, the printer does not turn off the power at the end of printing
                                i read this:
                                The use of M1 to end a job is deprecated. The M1 command no longer runs file sleep.g, instead it runs stop.g like M0. In future we expect to change the behaviour of M1 to be in line with the NIST standard.
                                what should i use instead of M1 ?

                                Please forgive my bad English, it's Google's fault :)

                                OwenDundefined 1 Reply Last reply Reply Quote 0
                                • Phaedruxundefined Phaedrux moved this topic from Firmware installation
                                • OwenDundefined
                                  OwenD @Plohish
                                  last edited by

                                  @Plohish
                                  You should create a stop.g in the /sys directory if you don't already have one.
                                  This will be run at the end of every print job or when M0 is called.
                                  You used to have to call M0 implicitly, but I'm pretty sure in one of the 3.5 betas it started being run automatically.
                                  It should contain your shutdown procedure such as turning off heaters and calling M81
                                  Change your M1 calls to M0

                                  Plohishundefined 1 Reply Last reply Reply Quote 0
                                  • Plohishundefined
                                    Plohish @OwenD
                                    last edited by

                                    @OwenD
                                    The stop.g file is present in my system, I entered the code into it:
                                    M81 S1
                                    It works, I didn't have to change M1 to M0 in the final code

                                    Please forgive my bad English, it's Google's fault :)

                                    1 Reply Last reply Reply Quote 0
                                    • droftartsundefined
                                      droftarts administrators @Plohish
                                      last edited by

                                      @Plohish said in After update to 3.5.0-beta.4 - wifi module reported failed:

                                      @OwenD
                                      Unfortunately it didn't help...
                                      I returned to 1.27, no more problems!

                                      The initial release of 3.5beta4 was posted with the wrong version of DuetWiFiServer firmware; it was 2.1beta3, it has now been updated to 2.1beta4. Can you try that? You will have to connect via USB and re-enter your access point SSID and password using M587.

                                      Ian

                                      Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                                      Plohishundefined 2 Replies Last reply Reply Quote 0
                                      • Plohishundefined
                                        Plohish @droftarts
                                        last edited by

                                        @droftarts
                                        unfortunately my printer is busy for a few days now, maybe I can do it later...

                                        Please forgive my bad English, it's Google's fault :)

                                        1 Reply Last reply Reply Quote 0
                                        • boldnutsundefined
                                          boldnuts
                                          last edited by

                                          I have also seen the same issue using the DuetWiFiServer firmware 2.1beta4 with my Duet2 Wi-Fi, with YAT connected I get SPI errors" unable to get WIFI module status" but on returning to version 1.27 it works ok.

                                          1 Reply Last reply Reply Quote 0
                                          • Plohishundefined
                                            Plohish @droftarts
                                            last edited by

                                            @droftarts
                                            Now I think there is no need to repeat the experiment? boldnuts had the same problem with the 2.1beta4 update...

                                            Please forgive my bad English, it's Google's fault :)

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