Firmware 2.0RC2b/1.21.1 RC2b released
-
Dave,
I don't know if this is a bug, but during the delta calibration routine, if the Emergency Stop button is pressed on the PanelDue, the process does not stop. It continues to run until all the probe points are finished. The only way to stop is to hit the power button. I don't know if this is something that can be fixed in the next revision. It seems like a necessary function if something goes wrong during the calibration routine such as the probe not detecting the bed properly.
Thanks.
-
@dougal1957 said in Firmware 2.0RC3/1.21.1 RC3 released:
Have upgraded both my Ethernet and Wifi cards with this but it reports as being RC2B 2018-05-13b
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.0(RTOS)RC2b ELECTRONICS: Duet Ethernet 1.02 or later + DueX5 FIRMWARE_DATE: 2018-05-13b3
is this right or have I messed it up again
That's my fault, I updated the build date but not the RC version. RC2b it is.
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 -
@shadowx said in Firmware 2.0RC3/1.21.1 RC3 released:
Dave,
I don't know if this is a bug, but during the delta calibration routine, if the Emergency Stop button is pressed on the PanelDue, the process does not stop. It continues to run until all the probe points are finished. The only way to stop is to hit the power button. I don't know if this is something that can be fixed in the next revision. It seems like a necessary function if something goes wrong during the calibration routine such as the probe not detecting the bed properly.
Thanks.
That's a known issue. Panel Due only sends Gcode commands, so the stop command gets queued with everything else.
-
@dc42 thank god for that thought I was being stupid but these things happen lol
-
RC3 is hanging when running a simulation on the attached file.
-
@gen2eng said in Firmware 2.0RC2b/1.21.1 RC2b released:
RC3 is hanging when running a simulation on the attached file.
It simulates OK on my Ormerod:
File 1526229129318-cfdmp_skew-tower.gcode will print in 2h 22m plus heating time
The simulation took 1min 40sec. At what point does it hang on your printer? Which electronics are you running?
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 -
Installed RC3 (or RC2b) and whatever it was with RC2 that led to delayed reaction of the printer when clicking the move buttons while doing a manual
G29has been fixed. I saw no more delays while leveling my printer a couple of minutes ago.
-
It was hanging at about 41sec. I did a hard reset and simulation ran fine on a different file. After the current print job finishes, I will try again.
I tried the simulation immediately after the upgrade. Any chance it needed a hard reset?
I'm running on a 1.03 Duet Wifi.
-
@gen2eng said in Firmware 2.0RC2b/1.21.1 RC2b released:
It was hanging at about 41sec. I did a hard reset and simulation ran fine on a different file. After the current print job finishes, I will try again.
I tried the simulation immediately after the upgrade. Any chance it needed a hard reset?
I'm running on a 1.03 Duet Wifi.
Ran it again, and it did not hang. The original hang was around 41% complete, not 41 sec.
-
Loaded:
Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet Firmware Electronics: Duet WiFi 1.02 or later Firmware Version: 2.0(RTOS)RC2b (2018-05-13b3) WiFi Server Version: 1.21 Web Interface Version: 1.21.1-RC4No prints (yet)
Delta / Kossel printer fanatic
-
You guys are probably past this... but... just in case, I ran a simulation of the skew tower file. Ran to completion, no issues.
7:29:27 PMFile 1526229129318-cfdmp_skew-tower.gcode will print in 3h 7m plus heating time
7:27:27 PMM37 P"1526229129318-cfdmp_skew-tower.gcode"
Simulating print of file 1526229129318-cfdmp_skew-tower.gcode -
Updated successfully with no problems, but I'm having issues while printing (multiple times via USB or local gcode), in that 1\2 to 3\4 of the way through a print, I get "Error: Heating fault on heater 1, temperature excursion exceeded 15.0°C".
This results in two conditions, a local print, parks the toolhead to XY cordinates shuts off Bed & halts the printer and errors with Resume-after-power-fail state saved.
If I'm printing from USB (Simplify3D), when the failure occurs, S3D knows somthing has gone wrong, but the printer keeps on moving, and keeps the bed heater running, but is unable to extrude.
I accept that printer won't know what is being printed, but should the printer do a hard re-set on hard error to at least kill all running prints ??
I was\am attempting to print ABS parts for Panobot on DBot 300x300x300 coreXY printer, driven by a DuetEthernet, so using Bed 110 Hotend 255.
I've chased all the wiring\checked all connectors, at various points around the bed area, bending strains are reduced as I'm using cable chains.
I'm almost at the point where either the problem is on the Board or the heater cartridge (E3D).
Next chance I get I'll re-map the heater to E1, if that fails to fix it, I'll replace the cartridge. But its strange that everything works fine for long periods of time, fails, & the one time it has happened while I was near, a board re-set let it resume.
-
I've just completed a 10.5 hour print on this release without issue. It appears to be stable with the exception of the weird simulation hang. After a hard reset, the simulation ran fine.
-
Does Duet actually choose the correct firmware version automatically? I actually went out of 1.21.1. Now I have 2.0, or have I selected the wrong file?
@dc42 said in Firmware 2.0RC2b/1.21.1 RC2b released:
M502 now resets all firmware parameters back to the values in config.g except network parameters
Are there any other exclusions or only one?
I get this message, is this correct?
M502 Error: Could not set WiFi hostname HTTP is enabled on port 80 FTP is disabled TELNET is disabledFirmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet Firmware Electronics: Duet WiFi 1.02 or later Firmware Version: 2.0(RTOS)RC2b (2018-05-13b3) WiFi Server Version: 1.21 Web Interface Version: 1.21.1-RC4''' -
FWIW after upgrading I also experienced the heater fault issue; 4 times on an 8 hr print. Probably just bad luck with a loose connector, as after a reset and restore the print started right back up, and I didn't have the heater calibrated either, and I had seen this happen long ago too. Simulation worked fine with the updated PanelDue and it would be amazing to see the simulation done as a parallel thread to calculate upon print start. Originally had an issue with losing the web interface, but copying over a new web directory solved that.
Saw a small improvement in WiFi transfer; now close to 500 KB/s, up from about 400 KB/s.
Good work!
-
So far the new firmware and DWC work great. Love the ability to upload files while homing the printer.
A good test will come tonight, Ditto printing (IDEX) on a 8 hour print run.
-
I've been using this since it was released and have not noticed any issues yet.
-
Last night While printing a long running part, I uploaded a 17mb file at speeds of 700KB/s with no issues.
Well done David!
-
I installed RC3 (or RC2b) and printed a couple of small things (~2 hours prints each) without any problems.
The baby stepping command seems to be responding a bit faster than before -
Hi,
I am using RTOS version and generally no problem. Today i add relay unit for controlling 24V line (M80 and M81).
It is work but when i first start the printer 7" Panel due still connection state, if i send M80 from DWC then paneldue's state change to idle. After that paneldue can send M80 and M81 without any problem.Is this firmware problem or i made any mistake?
Thanks,
