It's out! RepRapFirmware 2.0 and 1.21.1 released
-
I confirm the issue @zerspaner_gerd is seeing, have sometimes the same problem.
Reloading the page resolves the problem.
I suspect this is a DWC bug... -
@zerspaner_gerd : what is the value of the Ajax retries in your DWC settings?
-
@whosrdaddy
I tested at times until 4.
For a long time I stayed at 2, without change.Am current back to 3 high, and this seems to show an improvement currently.
Did you observe the same?
-
confused which files i need to use to upgrade to V2.0 for my duetwifi
lots of files listedDuet2CombinedFirmware.bin
5.6 KB DuetDriverFiles.zip
356 KB DuetMaestroFirmware.bin
552 KB DuetWebControl-1.21.1.zip
290 KB DuetWiFiServer.bin
57.9 KB iap.bin
57.8 KB iap4e.bin
58 KB iap4s.bin
370 KB RepRapFirmware-Alligator.bin
292 KB RepRapFirmware-RADDS.bin
373 KB RepRapFirmware.bin
335 KB Symbols-CoreNG-SAM3X8E.zip
322 KB Symbols-CoreNG-SAM4E8E_RTOS.zip
305 KB Symbols-CoreNG-SAM4S_RTOS.zip
110 KB Symbols-FreeRTOS-SAM4E.zip
81.7 KB Symbols-FreeRTOS-SAM4S.zip
1.67 MB Symbols-RepRapFirmware-Duet085.zip
1.5 MB Symbols-RepRapFirmware-Duet2_RTOS.zip
1.48 MB Symbols-RepRapFirmware-DuetM_RTOS.zip
Source code (zip)
Source code (tar.gz) -
@adamfilip What firmware version are you upgrading from?
Duet2CombinedFirmware.bin should work. If you haven't upgraded in a while you may need to rename it. Check the firmware release notes for the interceding firmware.
-
@adamfilip said in It's out! RepRapFirmware 2.0 and 1.21.1 released:
confused which files i need to use to upgrade to V2.0 for my duetwifi
Which firmware version are you using at present?
-
I tried the current Duet2CombinedFirmware.bin file and installed it. but this is what it says currently
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.0 or 1.01
Firmware Version: 1.21RC3 (2018-02-28 build 4)
WiFi Server Version: 1.21
Web Interface Version: 1.21.1 -
@adamfilip Perhaps this will help? https://forum.duet3d.com/topic/5646/duet-wifi-not-updating-firmware-when-installing-2-0/2
-
Hi Dave been a while.. I see things have really progressed since i pestered you last. LOL I am getting ready to upgrade so i can get wifi working again. Great to see the evolution and addition of ssid and pw btw! I see i have some firmware updates to do as well but it is all a little confusing. i was wondering if someone can give me a cliff notes version of what to do 1st.
Duet wifi running ver 1.18.1 with panel due v 1.15c PC and printer are in opposite ends of house so ideally do this via sd card? What do i do 1st? Also confused about which are the latest versions and where to get them. I am hoping to get my ducks in a row for this weekend . BTW, loved the tidbit from E3D on how great the duet is. I have another printer now, running mks 1.4 board and wow, it is a real dinosaur by comparison. I had no idea how lucky i was with my 1st system. I am currently building a system with 1540 mm X, and 1500 mm Y \ Z so looking forward to the Duet2 as well
-
@franknprinter Take a good look through this document.
https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware
You'll need to follow the special steps for updating to 1.19 as things changed slightly at that point.
-
Thank you, yes this was my issue.
-
I have downloaded the Duet2CombinedFirmware.bin, iap4e.bin, and DuetWebControl.zip files. I uploaded all of these to my DuetEthernet and it looked like it installed correctly, but it reports back saying that the firmware version is still 1.21. I'm running DWC 1.21.1, but I tried it with DWC 1.21 as well. Any idea what I'm doing wrong? The firmware updated date is listed as (2018-03-21), which is probably when I updated things last. Unfortunately the link above didn't solve my problem like I had hoped.
Edit: It works now. Tried it again after the 4th or 5th time and it just worked. I honestly cannot think of anything that changed.
-
thanks much @Phaedrux , i will give that a try this weekend!
-
So far so good, havent run into any issues with 2.0 so far
-
THanks @Phaedrux ! I couldn't wait so finished upgrade about 130 this AM LOL that worked like a charm even if it read like mudd. someone might want to update the install for 1.21 vs 1.19 as that was the instruction i used. Still have panel due to go but everything else is 1.21 now. dont suppose there is a way to flash duo from duet wifi? Else wise i will have to pull apart my case un mount and disconnect it so i can carry it to the computer room and plug in usb. Shocked and amazed i have not heard from @dc42 yet. I seem to recall Dave sending me answers before i could finish the question back in the day. LOL Bet you are even more insanely busy but keep up the outstanding work! I can see so many improvements and advances since i went down this road before, it really is awesome the way you take everyone's crazy ideas and turn it into a new release.. epic stuff there that every company on the planet should be doing as a business model!
Now to tackle the bltouch issue again... later... much appreciated! -
I've been busy with EMC compatibility testing for CE certification for the last 2 days, so I've had very little time to respond to forum questions. In answer to your question, we hope to support updating PanelDue version 3.0 controllers through the Duet in the future, however we need to write some firmware to make that possible. So at present you have to update them through USB.
-
Hi, I just have a serious layer shift on some pieces. The printer was running for many days non stop without a single issue.
Mechanically everything moves smoothly.
Here's my M122. After that, I restart the print, and so far everithing is going well.M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS) running on Duet Ethernet 1.02 or later
Board ID: 08DGM-95BNL-MGPSJ-6J1FJ-3S86T-12ZMW
Used output buffers: 4 of 20 (12 max)
=== RTOS ===
Static ram: 28380
Dynamic ram: 95468 of which 16 recycled
Exception stack ram used: 572
Never used ram: 6636
Task NETWORK ready, free stack 324
Task HEAT blocked, free stack 800
Task MAIN running, free stack 3588
=== Platform ===
Last reset 100:27:48 ago, cause: power up
Last software reset at 2018-06-13 12:33, reason: User, spinning module GCodes, available RAM 6924 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0041f000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 16
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 328.9ms
MCU temperature: min 14.0, current 35.3, max 37.4
Supply voltage: min 12.1, current 12.3, max 12.6, under voltage events: 0, over voltage events: 0
Driver 0: ok, SG min/max 0/1023
Driver 1: ok, SG min/max 0/1023
Driver 2: standstill, SG min/max 0/1023
Driver 3: ok, SG min/max 0/1023
Driver 4: standstill, SG min/max not available
Date/time: 2018-06-19 13:36:20
Slowest loop: 634.02ms; fastest: 0.07ms
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 150, MinFreeDm 144, MaxWait: 2564388349ms, Underruns: 2227, 11
Scheduled moves: 12471, completed moves: 12441
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.4
=== GCodes ===
Segments left: 1
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 doing "G1 X75.697 Y152.036 E0.0121" 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
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 634.09ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state: 5
=== Expansion ===The error status 16 is what caught my attention but I couldn't find any info of it.
-
Is this a problem that has only occurred since you upgraded to firmware 2.0?
Layer shifts are typically caused by the nozzle catching on a blob or curl-up. Increasing motor current or reducing travel speed may help. What is the rated current of the motors, and what currents have you set in M906?
The error code bits are defined as follows:
// Enumeration of error condition bits
enum class ErrorCode : uint32_t
{
BadTemp = 1u << 0,
BadMove = 1u << 1,
OutputStarvation = 1u << 2,
OutputStackOverflow = 1u << 3,
HsmciTimeout = 1u << 4
};So 16 means that there was a timeout on the SD card interface, which is unusual.
-
I finally found the problem. It was a belt about to get cut. I didn't notice on first sight, but after a careful look I saw a dent on one of the belts (it's a coreXY), so although it did move smoothly, occasionally it got caught on one of the pulleys...
It last a year, I need to try with an original Gates.Please, delete the posts since it wasn't firmware related.
All this time (many days) I've been working with firmware 2.0. Not a single problem. The only thing that noted is that file upload to SD now reach a maximun of 750kb/s and with 1.21 it reaches 1000kb/s-
-
OK so now a new wrinkle in the Acronym soup ... Sam3 / Sam4 ????
I really dont understand many of the notes put on these github docs and find them to be a bit challenging to follow.
Id like to use FW ver 2.0 here ... for my Duet Wifi [ Duet 2 ver Board ???? ]
My DWC Page tells me - I have this stuff:
=====================
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later [ so is that a Duet 2 or a Duet 1.02 ? ]
Firmware Version: 1.21 (2018-03-21)
WiFi Server Version: 1.21
Web Interface Version: 1.21So am I needing files for a Duet 2 Board even though the DWC interface indicates a cryptic indicator of my Electronics version of 1.02 or later vs. Duet 2 ???
Apparently i need Duet2Combined [ why its combined and with what who knows ] yes / no ?
What wifi server version files do I need to upgrade to ? [ if any ]
Do I also need a New browser interface update aka DWC / a.k.a. Web Interface Version / a.k.a. DuetWebControl.1.???
Also if any of those other files in any combination are needed - how does one know ? As well if so, what order should they be installed.
