Posts made by zylantha

Thanks @dc42, I have reprinted the exact same GCODE on 3.4.0beta6 and the tab didn't appear - so looks like this bug is fixed in this latest beta firmware.

@droftarts I agree - Arc welder isn't smoothing the outside of the model, which is a separate problem (probably need to tweak a setting somewhere, but even so that tab really shouldn't be there according to the GCODE as interpreted by various apps.

I have a video of it printing, including where it did the tab - I might have to upload to Youtube to share though as it doesn't look like I can upload here to the forums?

@phaedrux No difference with coasting disabled - tab is still there.

@phaedrux No wipe, but I do use coasting. It's enabled with defaults - Coasting Volume 0.064 mm3, Minimum volume before coasting 0.8 mm3 and Coasting Speed 90%.

Should I try disabling it and see if the tab still appears?

@phaedrux How's this?

@pcr Not using firmware retraction (I don't think Cura supports this?)

Here is my config.g:

; Configuration file for Duet Maestro (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.5 on Fri Oct 29 2021 22:45:49 GMT+1100 (Australian Eastern Daylight Time)

; General preferences
M575 P1 S1 B57600                             ; enable support for PanelDue
G90                                           ; send absolute coordinates...
M83                                           ; ...but relative extruder moves
M550 P"Ender 5 Plus"                          ; set printer name

; Network
M552 P0.0.0.0 S1                              ; enable network and acquire dynamic address via DHCP
M586 P0 S1                                    ; enable HTTP
M586 P1 S0                                    ; disable 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 S0                                    ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3                              ; set drive mapping
M350 X32 Y32 Z16 E16 I1                       ; configure microstepping with interpolation
M92 X160.00 Y160.00 Z800.00 E403.35           ; set steps per mm
M566 X1200.00 Y1200.00 Z24.00 E300.00         ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z180.00 E6000.00       ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z100.00 E5000.00         ; set accelerations (mm/s^2)
M906 X700 Y920 Z920 E900 I50                  ; 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 X355 Y360 Z400 S0                        ; set axis maxima

; Endstops
M574 X2 S1 P"xstop"                           ; configure switch-type (e.g. microswitch) endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop"                           ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin ystop
M574 Z1 S2                                    ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"zprobe.mod"                         ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000           ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-42.5 Y0 Z2.35                      ; set Z probe trigger value, offset and trigger height
M557 X15:305 Y15:335 S50                      ; define mesh grid

; Heaters
M308 S0 P"ctemp" Y"thermistor" T100000 B4092  ; configure sensor 0 as thermistor on pin ctemp
M950 H0 C"bedheat" T0                         ; create bed heater output on bedheat and map it to sensor 0
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
M143 H0 S150                                  ; set temperature limit for heater 0 to 150C
M308 S1 P"e0temp" Y"thermistor" T100000 B4092 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1                          ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00                              ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S275                                  ; set temperature limit for heater 1 to 275C

; 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
M950 F2 C"fan2" Q500                          ; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H1 T45                             ; set fan 2 value. Thermostatic control is turned on

; Tools
M563 P0 D0 H1 F0:2                            ; 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

; Custom settings
M106 P0 L0.6                                  ; Minimum 60% fan speed
M501

; Miscellaneous
M501                                          ; load saved parameters from non-volatile memory
T0                                            ; select first tool

@pcr

I can't see how to upload gcode to the forums but maybe these sharing links will work?

No ARC:
https://drive.google.com/file/d/1BpifPhJUYhkYpxqv4E8VMEdjSa1XMdIg/view?usp=sharing

With ARC:
https://drive.google.com/file/d/1BmFRK3AwKcSvsFkpU_evZFoFvfbI_kv1/view?usp=sharing

I've started using the Arc Welder plugin for Cura and most results have been awesome, however I have had some strange behaviour printing this relatively simple model from Thingiverse:
https://www.thingiverse.com/thing:4649358

The one on the bottom was printed with Arc Welder enabled, and the one on the top with it disabled - otherwise all other settings are identical.

There is clearly a very distinct "tab" sticking out from the Arc Welder (i.e. G02/G03 enabled) print at a very particular point, which is definitely not there in the model. The tab that's printed isn't in Cura's "Preview", and I have imported the "Arc Welder" enabled GCODE into Simplify3D and I can't see the tab there either - everything looks fine, so while it certainly could be an issue in what Arc Welder outputs, the GCODE doesn't seeem to evidence it.

So far I can only conclude that there is some fault in Reprapfirmware's handling of the G02/G03 commands that's somehow creating this weird extra tab here, which as far as GCODE simulators can tell me shouldn't be there.

Happy to provide the respective GCODE files for closer examination.

Relevant config details:
Generated by: Cura_SteamEngine 4.11.0
Board: Duet 2 Maestro (2Maestro)
Firmware: RepRapFirmware for Duet 2 Maestro 3.3 (2021-06-15)
Printer: Ender 5 Plus

Thanks, you're right ... this file is included in the RC1 release but it wasn't showing up in any searches (and I didn't just look for it in the RC1 tag).

I've uploaded it and successfully downgraded.

I'm trying to downgrade my Duet 2 Ethernet from 3.2-RC1 back to 3.1.1 (I'm having Delta calibration issues with the Smart Effector), however when I try to upload any prior version of firmware, it fails with an error
M997 S0
Error: M997: In-application programming binary "Duet2_SDiap32_WiFiEth.bin" not found

I can't find this file anywhere, nor do I follow why it needs this.

TIA

@Phaedrux said in M564 S0 (Disable limit axes/think outside the box) has no effect:

It would appear you've identified a bug with M564. This should be fixed in 3.01.

Thanks for confirming! This was my suspicion but I couldn't follow how it all fit together in the source code.

@bearer said in M564 S0 (Disable limit axes/think outside the box) has no effect:

@zylantha said in M564 S0 (Disable limit axes/think outside the box) has no effect:

but maybe S0 is also being blocked in error?

S0 is depricated anyway so shouldn't be used. (It has conflict with laser mode where S sets power level)

I was referring to M564 S0, not G1 S0. There were no publisihed notices with respect to M564 that I had seen?

Did this work in 2.xx or is a new function you're adding after the 3.0 upgrade? Also you may want to post your config file for the wizards to review

It wasn't working in 2.xx that I was on, so I upgraded to 3.0 and still didn't work - behaviour was identical between the versions.

Here is my config

; Configuration file for Duet Ethernet (firmware version 1.20 or newer)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Wed Mar 14 2018 21:48:01 GMT+1100 (AEDT)

; General preferences
G90                                       ; Send absolute coordinates...
M83                                       ; ...but relative extruder moves
M555 P2                                 ; Set firmware compatibility to look like RepRapFirmare

M665 L360.250:360.250:360.250 R175.628 H292.4 B149.1 X0.000 Y0.000 Z0.000
M666 X0.131 Y0.241 Z-0.372 A0.00 B0.00

; Heater model parameters
M307 H0 A261.7 C621.1 D4.9 S1.00 V0.0 B0
M307 H1 A636.3 C196.6 D6.3 S1.00 V25.4 B0

; Network
M550 PKossel                              ; Set machine name
M540 PBE:EF:DE:AD:FE:ED                   ; Set MAC address
M552 P192.168.245.165 S1                  ; Enable network and set IP address
M553 P255.255.255.128                     ; Set netmask
M554 P192.168.245.129                     ; Set gateway
M586 P0 S1                                ; Enable HTTP
M586 P1 S0                                ; Disable FTP
M586 P2 S0                                ; Disable Telnet

; Drives
M569 P0 S1                                ; Drive 0 goes forwards
M569 P1 S1                                ; Drive 1 goes forwards
M569 P2 S1                                ; Drive 2 goes forwards
M569 P3 S0                                ; Drive 3 goes backwards
M350 X128 Y128 Z128 E16 I1                ; Configure microstepping with interpolation
M92 X1600 Y1600 Z1600 E2656               ; Set steps per mm
M566 X1000 Y1000 Z1000 E40                ; Set maximum instantaneous speed changes (mm/min)
M203 X16000 Y16000 Z16000 E1800           ; Set maximum speeds (mm/min)
M201 X800 Y800 Z800 E120                  ; Set accelerations (mm/s^2)
M906 X800 Y800 Z800 E500 I30              ; Set motor currents (mA) and motor idle factor in per cent
M84 S30                                   ; Set idle timeout

; Axis Limits
M208 X350 Y350 Z350                       ; Set minimum Z

; Endstops
M574 X2 Y2 Z2 S1                          ; Set active high endstops

; Z-Probe
M558 P5 R0.4 H3 F1000 T6000               ; Set Z probe type to effector and the dive height + speeds
G31 P100 X0 Y0 Z-0.07                     ; Set Z probe trigger value, offset and trigger height; increase to move closer to bed, decrease to move further away (faketak = -0.05; geckotek = -0.08; pei = 0.03)
M557 R118 S20                             ; Define mesh grid

; Bed
M308 S0 P"bed_temp" Y"thermistor" T100000 B3950 R4700               ; Set thermistor + ADC parameters for heater 0
M950 H0 C"bed_heat" T0 A"Bed"
M143 H0 S120                              ; Set temperature limit for heater 0 to 120C

; Extruder
M308 S1 P"spi.cs1" Y"rtd-max31865"        ; Configure PT100 for heater 1
M950 H1 C"e0_heat" T1 A"Extruder"
M143 H1 S285                              ; Set temperature limit for heater 1 to 280C
M950 F1 C"fan_1" A"Extruder" 
M106 P1 S1 H1 T30                         ; Set fan 1 - hotend, on from 30C

; Firmware retraction
M207 S1.0 F1800 Z0.0                     ; S - length, F - Speed in mm/min, Z = additional z-hop

; Fans
M106 P0 S0 F500 H-1                   ; Set fan 0 - print 
M106 P2 S1 F500 H1 T180 S100          ; Set fan 2 - stepper drivers, only while printing

; Tools
M563 P0 D0 H1                             ; 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

G29 S1                                    ; Mesh grid load

; Automatic saving after power loss is not enabled
; load overrides
M501

I have a Duet 2 Ethernet which was running 2.xx but I have now just upgraded to 3.0, on a custom delta with smart effector and a Mosaic Palette 2.

I want to be able to move the effector outside the limits of the print bed in order to set up an in-place side transition for the Palette 2 - effectively allowing me to purge the transition material generated by the Palette 2 off the side of the printer into a container, rather than needing to print a transition tower between the colour changes.

To do this I expect that I will need a before- and after- purge script configured in Canvas3D to permit the effector to be moved outside of the print bed dimensions, and that I should simply be able to use M564 S0 and M564 S1 in these scripts respectively.

However in testing I cannot jog the print head past the edge of the bed even after I have issued the M564 S0 command, even though according to the documentation I should be able to - I can get to the edge of the bed but further jogs are ignored (or just edge towards Xmin / Y0). This happened on both 2.xx and 3.0 firmwares.

Is there something I've missed to allow movement outside the delta print bed limits? I know that H0 is not permitted on my Delta but maybe S0 is also being blocked in error?

@dc42 said in Unstable temperature readings during heating:

It sounds that you have insufficient thermal insulation underneath the bed heater.

This is true. Unfortunately I haven't found the right case for the Duet to isolate the flow from the cooling fan, and have deferred the cork base until I receive the 240V heater - so resolution of this is in the works, however this isn't the cause of the erratic temp readings.

@t3p3tony said in Unstable temperature readings during heating:

what would be odd about it being a physical connector issue is that it was not noisily when at temperature, and was noisy when cooling down.

That's what had me stumped ... it's been an issue for some time, and I thought I had eliminated the connector issue with all of the iterations of different thermistor cable connector that had exhibited the issue ... and I can't think of why it would only be unstable during heat-up/cool-down (but hey I'm a lawyer not an electrical engineer).

I will continue to try to unroll these latest changes and reproduce the issue again and isolate the fix, if nothing else the thread may be useful for somebody else who may end up having the same issue, even though I seem to be the only one ever.

OK so in frustration at only being able to reach 50C before a heater fault, I re-installed the ferrite core, wrapping the thermistor lead around it three times (previously only did it two with the original bed heater - lead was too short to do it any more). I also rotated this new bed by 120o - since with the shortened thermistor lead it needed to be closer to where the Duet connectors are. This does result in a very different path for the 24V leads - away from the input leads, and the bed leads are in a completely different orientation as well (fwiw).

Result ... a completely smooth and perfect heating profile

I can't really accept that this was because I wrapped the thermistor leads through the ferrite core 3 times instead of 2, so looks like I have to do some isolation tests ... removing the ferrite core while leaving everything in its current orientation, looking at the power lead paths, etc.... it all seems very strange!

Most obvious stupid cause is a loose thermistor connection that was solved by removing and re-connecting the bed temp sensor, but I will continue to refuse to accept that this is the cause as well (until all other less likely causes have been eliminated).

Try #1 to reach 100C .. fault after reaching only 50C

@t3p3tony said in Unstable temperature readings during heating:

setting it to a temperature that your bed cannot reach

The limiting factor is the Duet's propensity to return "heater fault" due to (what I presume is) the unstable readings messing with the dead time safety. I frequently get a heater fault when trying to reach 100C, when it is definitely capable of getting to this temp in 15 mins (which really isn't that awful). Sometimes I have to restart several times before it will get to 100C - but I have never had an issue with a heater fault error after actually reaching 100C.

Some of the issues in getting to / maintaining 100C are caused by my stepper driver fan under the bed, which kicks in at 180C hot end temp to avoid the warnings about stepper drivers overheating - the extra air movement under the bed results in a significant heat loss and means the underpowered heater struggles to maintain the 100C (I have seen it drop to 92C) - in these circumstances, the temp readings are still stable, just lower than the target - during times when the heater would logically have full PWM.

The noisy profile seems to only be during heat up / cool down (note that this includes cool down), but not while cold or while at temp.

I will try to get it stable at 100C and then push it up to 110C and see what happens (this is something I haven't tried yet as I never thought it could get to 110C).

@deckingman I agree - it's not a correct reading; this bed is very thick, 7mm cast aluminium plate (Geckotek 310mm round magnetic), however my other aluminium plate with the same issue is only 3mm.

If it's a noisy signal (and I had drawn that conclusion too - hence my experimenting with a ferrite core), the first weird thing is that it's not noisy once it has reached temperature - why would that suddenly stop it from being noisy?

Where is the noise coming from? And even then, what can be done about it ... I tried the ferrite core - wrapping the thermistor's leads around it twice, but it didn't seem to do anything; should I try putting a ferrite core around the bed leads? One bed lead? Both together? Or just one of the thermistor leads? I'm not an electrical engineer so am really just poking in the dark here ...

I am eventually going to be replacing the heater with 240v (since it's so underpowered with 225w) - I don't know if that's going to help but it will eliminate some variables. It's dependent on Aliexpress lead times at the moment, so could be a long way away still.

@T3P3Tony here is it getting up to 30C from cold (dead stable), lots of spurious readings during heating up, and then stabilising at ~31.5C steady, similar to once it gets up to 60C or 75C or 80C and remains stable - but only once it's there.

My power supply is 17A (400W) and I have a power meter on it showing draw during heating as ~10.5A. Vin looks stable at 24-24.1V during the unstable temperature readings (confirmed on both the power meter and the DWC/Paneldue). Incidentally I think the DWC "hover over" text is incorrect for the voltage - it is displaying oC instead of V for min/max.

If it was a power supply adequacy issue, then I would also expect unstable temperatures once at 100C - since the heater is underpowered, it is on almost constantly to try to keep it at 100C.