I do not know what happened, but it all works now.
I have tried several times with restart of both printer and PC in between. Maybe it comes back.
When upload from slicer failed I still could upload from DWC.
No errors, except within Slic3r when trying to upload.
I have installed latest DWC but I am not using it. I had failures without connecting with the DWC to the Duet since bootup of the Duet. So I do not thing the new DWC is the cause of this.
I will post again if this problem occurs again.
@zerspaner_gerd said in Firmware 2.02 released!:
M291 no longer allows S0 and T0 together because that would create a message that can never time out of be dismissed
I used it as follows
M291 P"Nozzle is heated" R"Loading Support" S0 T0
G10 S230; TEMP
G1 X125. Y10. F6000
M116 H1:2 S3
M292 ; Hide the message
I see now no way to implement the equivalent after the change.
Maybe we could create a new mode that includes:
Only with the "Cancel" button, to cancel the current process.
That would have been missing before me, because if there is a mistake (for example, unintentional confirm) was the one zigste way to end this with an emergency stop.
What do the other people mean?
Why don't you just set a long timeout instead of no timeout? Or allow it to be dismissed?
@hbrownell said in RRF Configurator questions...:
@dc42 does the configuration look ok? Should I start it up like this?
You should not have a M587 command in config,g. it won;t work there anyway. Other than that, I didn't spot anything wrong with it.
@caveman said in RepRapFirmware 2.03RC3 available:
Still the same issue with mesh leveling. 2.02 works perfect.
After installing the first 2.03 RC this issue happened.
Every time you do a mesh level the results are different. So first layers are a pain in the but because you have to ajust z offset every time.
This does not happen in 2.02.
Your config.g file
Your homeall.g and homez.g files
A simple sequence of operations, starting from power up, that reproduces this
Your bed.g file, it there is a G32 command anywhere in that sequence.
@singhm29 said in Thermal runaway not active by default?:
No problem! The issue however is that I get a reading of 2000 instead of fault and no error in DWC making me wonder what I've done wrong in the setup to have the safeguards disabled
If you are getting readings of 2000, the heater will go into the fault state as soon as you try to heat it up. It will not go into the fault state or report any other error as long as you leave it turned off.
I finally found some time and energy to get back to the Ender. I had a few fans swapped, but otherwise things seem to work. I ran the PID tunings, leveled the bed and printed some small bits. First parts out of the Ender and Duet! It really is amazingly quiet for its movements but the full set of fans is still a lot of noise.
Next is figuring out parameters, pressure advance(?), speeds etc.
My PIDs ended up at: (edit: new therm values)
M307 H0 B0 S1.00 ; Disable bang-bang for bed heater, set PWM limit
M305 P0 T98801 B4185 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S90 ; Set temperature limit for heater 0 to 90C
M305 P1 T98801 B4185 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S230 ; Set temperature limit for heater 1 to 230C
; Heater cal
; Heater 1 model: gain 355.8, time constant 112.4, dead time 5.0, max PWM 1.00,
; calibration voltage 24.1, mode PID, inverted no, frequency default
; Computed PID parameters for setpoint change: P11.2, I0.470, D39.5
; Computed PID parameters for load change: P11.
M307 H1 A355.8 C112.4 D5 V24.1 B0
; Bed cal
; Heater 0 model: gain 141.3, time constant 461.3, dead time 1.2, max PWM 1.00,
; calibration voltage 24.0, mode PID, inverted no, frequency default
; Computed PID parameters for setpoint change: P488.5, I20.825, D407.9
; Computed PID parameters for load change: P
M307 H0 A141.3 C461.3 D1.2 V24.0 B0
I presume that looks sane?
@sinned6915 said in Help- Marlin convert: Dual endstops & LCD Menus:
.........................I am leaning towards wiring the other 3 switches in series, NC, so that if one of them trips, the condition is set. I really want this for stopping the printer from crashing the carriage out of bounds resulting from missed steps/layer shifts-hangs-hiccups-whatever................
That's how I have my machine configured. As @Phaedrux says, once homed any moves will respect the axes maxima but I tend to do stupid things from time to time, so having additional switches can be useful. In my case I use a spare end stop on the Duex5 (E4) and connect the 3 switches wired in series to that. So any one opening will cause the trigger to happen using this command in config.g M581 E4 S1 T0 C0. The E4 is the end stop number, S1 means detect rising edge, T0 means do an emergency stop like M122 (but you can take other action or call your own macro), and C0 means any time (using C1 means only when printing from SD card).
That did not seem to affect it when I did it. I intentionally changed the homing speed in that section and while it did affect the homdelta.g file it did not change the T parameter in M558
Though it seems to be doing it now, odd.
It is with great pleasure that I can inform fellow forum members that the printer is now functioning as expected. Setting the endstops to active high at the low end did indeed do the trick.
For reference the endstop LED’s are on and go off when the switches are activated.
Many thanks one and all for your input.
I think your wifi server is a little out of date. Should be running 1.23. Not sure if that will help or not, but worth a shot.
I've never seen that error message before. It could also be related to DWC2.0 RC4. I think it's up to RC6 now, so you may want to also update that.
The problem is that the name of your GCode file contains space characters, and the current stable firmware omits the quote characters around the filename in the M23 command. This is fixed in the most recent beta. Meanwhile, if you edit the resurrect.g file inserting double quote marks around the filename, you will be able to resume it.
Looks like your connection to Duet3D was lost, please wait while we try to reconnect.