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

    New firmware 1.19 beta 2

    Scheduled Pinned Locked Moved
    Firmware installation
    18
    70
    10.0k
    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.
    • Bobblejotundefined
      Bobblejot
      last edited by

      HI dc42 sorry about this but i have never been able to get a stable wifi connection with the DuetWifi, i have always put it down to firmware and the hope the next version will fix the issues but now even with your latest beta releases of 1.19 its even worse. After now 7 months of ownership the board when working is fantastic the only problem is it never lasts more than a few days before i cant reconnect over wifi or the web interface drops out constantly through ajax errors. I honestly couldn't tell you how many times i have come to the machine after a couple of weeks turned it on opened the web interface and nothing to find again for the god knows how many time the port says bossac and not lpt1 and i have to re-flash the firmware. Today was the last straw after running perfectly for 9 hours over the past 2 days i switched the machine off after the print finished and everything cooled down, went to turn it on this morning and again as so many times before no connection to the web interface, hooked up my laptop and again in device manager bossac. Decided to try 1.19beta2 followed your guide and all is well for 2 mins and never managed to got connected again. I know this isn't exactly a commercial board and is always under development but it should at least work more than 15% of the time. I have now come to the conclusion that i cant trust this board for any work i need to do but hope that you can get a handle on all these issues in the future. Because honestly when it works its great just not reliable.

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

        I'm sorry you have had so much trouble. It should not be reverting to Bossa Port like that. Are you quite certain that nothing is pressing against the Erase button?

        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
        • Sniffleundefined
          Sniffle
          last edited by

          DC42, with the current 1.19Beta3, are the flashing instructions still the same as with the previous 1.19 versions that require the firmware and wifi to be updated simultaneously?

          1 Reply Last reply Reply Quote 0
          • Bobblejotundefined
            Bobblejot
            last edited by

            Hi dc42, nothing is pressing against the erase or reset ports like i said i always put down the ajax errors and odd firmware resets down to the firmware but over the months and update after update nothing has ever improved, it just seems to get worse. And as an early purchaser number 62 i think i never expected things to be perfect, but some stability would have been nice, the 2 Duet 0.8.5 i have i haven't updated in a long long time but work fine ( well except one with a fan issue but its fine ).

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

              So is the main problems that the port reverts to the Bossac port, which will have the side effect of making it impossible to connect with the board over WiFi? If so then I'm happy to authorise a replacement board, because that should not be happening. However, if this mostly occurs when the printer has not been used for a while and you live in a country with high humidity, then this problem might be caused by condensation, and I may be able to suggest a modification you could try.

              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
              • dc42undefined
                dc42 administrators
                last edited by

                @Sniffle:

                DC42, with the current 1.19Beta3, are the flashing instructions still the same as with the previous 1.19 versions that require the firmware and wifi to be updated simultaneously?

                Yes if you are upgrading from firmware 1.19alpha or earlier. If you are already running 1.19beta 1 or 2 then you just need to update the main 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
                • StevenLundefined
                  StevenL
                  last edited by

                  I upgraded to 1.19beta3. Now it does not connect over a web connection. In fact it does not advertise its web service at all.
                  (I'm an IT guy…)
                  Do I need to revert to the 1.18 i was running or is there a way to correct this? How would I roll it back to the previous firmwares?

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

                    You need to set up access to your router different!y. There is a link to the instructions in the upgrade notes, but here it is for your convenience: https://duet3d.com/wiki/DuetWiFiFirmware_1.19_alpha.

                    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
                    • robmundefined
                      robm
                      last edited by

                      @dc42:

                      you live in a country with high humidity, then this problem might be caused by condensation, and I may be able to suggest a modification you could try.

                      I'm not having any problems ('over the moon' is best description of my new DuetWifi experience!) - but I do live in such a country. Interested in any suggestions for ensuring the long term health of the system in such an environment?

                      1 Reply Last reply Reply Quote 0
                      • Bobblejotundefined
                        Bobblejot
                        last edited by

                        Hi dc42, i actually live in Scotland so humidity isn't really an issue. The ajax errors have always been there but its the number of times that i need to re-flash the firmware that is starting to really frustrate. I can do a print and everything is perfect then go to do another and have no access to the web interface.

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

                          Please ask your supplier to replace the board. I think the microcontroller chip is faulty, it doesn't seem to be holding the state of the "Boot from flash" flag.

                          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
                          • Bobblejotundefined
                            Bobblejot
                            last edited by

                            Hi dc42 thanks for that, the board actually came direct from yourselves.

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

                              Please send us an email and we will sort it!

                              www.duet3d.com

                              1 Reply Last reply Reply Quote 0
                              • Bobblejotundefined
                                Bobblejot
                                last edited by

                                Hi Tony just emailed you.

                                1 Reply Last reply Reply Quote 0
                                • vhowardundefined
                                  vhoward
                                  last edited by

                                  Well. Just tried the new beta4. Still no joy. Won't connect. Really looking forward to an ethernet module.

                                  1 Reply Last reply Reply Quote 0
                                  • minimundefined
                                    minim
                                    last edited by

                                    Have anyone that had crashes with alpa and beta1/2 tested the most recent ones? Any crashes?

                                    1 Reply Last reply Reply Quote 0
                                    • BlackTomundefined
                                      BlackTom
                                      last edited by

                                      David,
                                      I've flashed beta 4 yesterday on my corexy and the board is resetting by itself without any known reason.
                                      Yesterday the printer reseted during a print that was running for less than 5 minutes and this morning I was running my bed compensation macro and it crashed again.

                                      this is the m122 output.

                                      M122
                                      === Diagnostics ===
                                      Used output buffers: 3 of 32 (5 max)
                                      === Platform ===
                                      RepRapFirmware for Duet WiFi version 1.19beta4 running on Duet WiFi 1.0
                                      Board ID: 08DAM-999TL-NL5T8-6J1DA-3SJ6P-T55BJ
                                      Static ram used: 20356
                                      Dynamic ram used: 95876
                                      Recycled dynamic ram: 2552
                                      Stack ram used: 1304 current, 3804 maximum
                                      Never used ram: 8484
                                      Last reset 00:00:13 ago, cause: software
                                      Last software reset reason: User, spinning module Network, available RAM 8484 bytes (slot 4)
                                      Software reset code 0x5001, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0040080f, BFAR 0xe000ed38, SP 0xffffffff
                                      Error status: 0
                                      Free file entries: 10
                                      SD card 0 detected, interface speed: 20.0MBytes/sec
                                      SD card longest block write time: 0.0ms
                                      MCU temperature: min -270.2, current 16.4, max 16.7
                                      Supply voltage: min 11.2, current 11.4, max 11.7, under voltage events: 0, over voltage events: 0
                                      Driver 0: stalled standstill
                                      Driver 1: stalled standstill
                                      Driver 2: stalled standstill
                                      Driver 3: stalled standstill
                                      Driver 4: standstill
                                      Date/time: 2017-06-03 09:17:31
                                      Slowest main loop (seconds): 0.004786; fastest: 0.000030
                                      === Move ===
                                      MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
                                      Scheduled moves: 0, completed moves: 0
                                      Bed compensation in use: mesh
                                      Bed probe heights: 0.000 0.000 0.000 0.000 0.000
                                      Probe change coordinates:
                                      === Heat ===
                                      Bed heater = 0, chamber heater = -1
                                      Heater 1 is on, I-accum = 0.0
                                      === GCodes ===
                                      Segments left: 0
                                      Stack records: 1 allocated, 0 in use
                                      Movement lock held by null
                                      http is idle in state(s) 0
                                      telnet is idle in state(s) 0
                                      file is idle in state(s) 0
                                      serial is idle in state(s) 0
                                      aux is idle in state(s) 0
                                      daemon is idle in state(s) 0
                                      queue is idle in state(s) 0
                                      Code queue is empty.
                                      Network state is running
                                      WiFi module is connected to access point
                                      WiFi firmware version 1.19-beta1
                                      WiFi MAC address 5c:cf:7f:1b:3c:b8
                                      WiFi Vcc 3.11, reset reason Turned on by main processor
                                      WiFi flash size 4194304, free heap 39864
                                      WiFi IP address 192.168.1.101
                                      WiFi signal strength -63db
                                      HTTP sessions: 1 of 8
                                      Socket states: 2 0 0 0 0 0 0 0
                                      Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)

                                      1 Reply Last reply Reply Quote 0
                                      • BlackTomundefined
                                        BlackTom
                                        last edited by

                                        I ran the macro again and this time it failed just after its completion.

                                        M122
                                        === Diagnostics ===
                                        Used output buffers: 3 of 32 (6 max)
                                        === Platform ===
                                        RepRapFirmware for Duet WiFi version 1.19beta4 running on Duet WiFi 1.0
                                        Board ID: 08DAM-999TL-NL5T8-6J1DA-3SJ6P-T55BJ
                                        Static ram used: 20356
                                        Dynamic ram used: 95876
                                        Recycled dynamic ram: 2552
                                        Stack ram used: 1304 current, 3804 maximum
                                        Never used ram: 8484
                                        Last reset 00:00:13 ago, cause: software
                                        Last software reset reason: User, spinning module Network, available RAM 7824 bytes (slot 0)
                                        Software reset code 0x5001, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0440f80f, BFAR 0xe000ed38, SP 0xffffffff
                                        Error status: 0
                                        Free file entries: 10
                                        SD card 0 detected, interface speed: 20.0MBytes/sec
                                        SD card longest block write time: 0.0ms
                                        MCU temperature: min -270.2, current 16.6, max 17.1
                                        Supply voltage: min 11.2, current 11.6, max 11.7, under voltage events: 0, over voltage events: 0
                                        Driver 0: stalled standstill
                                        Driver 1: stalled standstill
                                        Driver 2: stalled standstill
                                        Driver 3: stalled standstill
                                        Driver 4: standstill
                                        Date/time: 2017-06-03 09:31:52
                                        Slowest main loop (seconds): 0.004088; fastest: 0.000030
                                        === Move ===
                                        MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
                                        Scheduled moves: 0, completed moves: 0
                                        Bed compensation in use: mesh
                                        Bed probe heights: 0.000 0.000 0.000 0.000 0.000
                                        Probe change coordinates:
                                        === Heat ===
                                        Bed heater = 0, chamber heater = -1
                                        Heater 1 is on, I-accum = 0.0
                                        === GCodes ===
                                        Segments left: 0
                                        Stack records: 1 allocated, 0 in use
                                        Movement lock held by null
                                        http is idle in state(s) 0
                                        telnet is idle in state(s) 0
                                        file is idle in state(s) 0
                                        serial is idle in state(s) 0
                                        aux is idle in state(s) 0
                                        daemon is idle in state(s) 0
                                        queue is idle in state(s) 0
                                        Code queue is empty.
                                        Network state is running
                                        WiFi module is connected to access point
                                        WiFi firmware version 1.19-beta1
                                        WiFi MAC address 5c:cf:7f:1b:3c:b8
                                        WiFi Vcc 3.10, reset reason Turned on by main processor
                                        WiFi flash size 4194304, free heap 39736
                                        WiFi IP address 192.168.1.101
                                        WiFi signal strength -63db
                                        HTTP sessions: 1 of 8
                                        Socket states: 2 0 0 0 0 0 0 0
                                        Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)

                                        1 Reply Last reply Reply Quote 0
                                        • BlackTomundefined
                                          BlackTom
                                          last edited by

                                          David,, I just downgraded back to 1.18.1 and everything is fine, no more unexpected reset

                                          1 Reply Last reply Reply Quote 0
                                          • minimundefined
                                            minim
                                            last edited by

                                            Sounds like the kind of crashes I had before but I upgraded to beta4 this morning and it's been printing now for 7-8hours without a crash yet. Seems like the bug I was experiencing is fixed now. I got a old-school cartesian setup tho so no corexy here.

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