[3.3RC3] Missed stepps or overdue moves
-
@typqxq thanks, I will try to replicate your setup today.
-
@typqxq said in [3.3RC3] Missed stepps or overdue moves:
Here is a link to the configuration and a test gcode file https://we.tl/t-DQueVGrH61
Unfortunately that .link has expired. Please provide a new link to your files.
-
@dc42 Here is a new link: https://www.dropbox.com/sh/yfjwidhzvlxk8k2/AAAQd95XneD8zUVNV8VnNO3ya?dl=0
-
@typqxq thanks.
I have spotted an error in your configuration, in file custom/tool_1.g:
; Create Heater M308 S2 P"2.temp1" Y"thermistor" T100000 B4725 C0.0000000706 A"T1 Heater" ; configure sensor 2 as thermistor on pin temp1 M950 H2 C"2.out1" T2 ; create nozzle heater output on out1 and map it to sensor 2 M143 H2 S300 ; set temperature limit for heater 1 to 300C (e3d v6 all metal) M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; Create Part Fan M950 F3 C"2.out4" ; Define Part Cooling fan on out4 (4pin) M106 P3 C"Part Cooling T1" ; Setup Part Cooling Fan as Part Cooling T1 ; Create Hotend Fan M950 F4 C"1.out7" ; Define Hotend Fan on out7 (2pin) M106 P4 S255 T45 H2 ; Setup Hotend Fan for thermal control, full on when H2 reaches 45C
You create the sensor and heater on board 2, but the fan on board 1. RRF has the following documented limitation:
A thermostatically-controlled fan on an expansion board can only be controlled by a temperature sensor on the same expansion board.
Did you perhaps mean to use port 2.out7 for the fan?
I don't know whether this is relevant to the problem of maxOverdue being much too large and the associated print issues. I will change the config to use port 2.out7 and try running your print.
-
@typqxq I have reproduced the problem on my bench system so I am now able to investigate it.
For future reference, it would be easier for me to use your configuration files if instead of using M98 P"/sys/custom/xxx" in many places, you used M98 P"custom/xxx". This is because I have your configuration in a subfolder of /sys.
-
@dc42 Thank you, I found and fixed it last week. It had no effect from what I can see.
This are the configuration files as of when I reported the problem. -
@typqxq please try the new firmware binaries at https://www.dropbox.com/sh/xfsvscbaab0dtzl/AACCcSeiTNINZL-xbs6IhC4Ja?dl=0. Ignore the .map files.
-
@TypQxQ have you had a chance to try the new firmware? We're waiting to release 3.3 stable but I would like to know whether this issue is resolved first.
-
@dc42 Sorry but I have left on vaccation and won’t be able to test it until I get back.
Have a great summer! -
-
@maxgyver said in [3.3RC3] Missed stepps or overdue moves:
@dc42 I had the same problems described by @TypQxQ after upgrading from RC3.2 to RC3.3.
The new binaries fixed the issue.Cheers
MaxThanks for confirming that!
-
-
-
-