The console displays shown help us determine multiple (3X) G32 convergence when called from a macro. Console display are from M665 and M666 calls within the macro.
Under DWC 1.21 the posted results are rationally presented chronologically whereas in 2.0.0-RC6 the M665 and M666 results are separately grouped. Chronological display (1.21) is sensible making associating adjustments with convergence error easy,
Or did you make the change for a reason that is not obvious to me?
Best posts made by Ethelred
-
Irrational G-Code Console Ordering
-
RE: Hobby servo behavior
I had purchased from Amazon (addicted, I fear) and was unaware of the Pololu info at that time. Amazon almost never has any reliable tech info and sometimes publishes downright lies.
So thanks - I've ordered 180 degree replacements (metal gear MG90S).
I had tested microsecond values but had just not included them in this post. I'll fill in the blanks when the new ones arrive. -
RE: M558 ignores quantity of probe hits
Replacement probe arrived and installed. Works perfectly and converged at 0.003mm - good enough for government work. I must have somehow bumped or otherwise disturbed the optical alignment.
AND the good news is the latest I-R probes now have surface mount emitter/detector optics which are impossible to move out of alignment. Thanks DC42 or Tony or whoever. -
RE: Max file count error
@Ethelred
Flashed an updated PanelDue binary and all is well - gadzooks, the previous version was pre-historic.
Thanks to all for the help. -
RE: Delta: Increase/Override bed radius?
@bearer Sorry, I think you are wrong. At least in latest firmware 2.05.1 the "P" parameter is functional ( Invoking via the S parameter does nothing ). My previous post's screenshot is directly from the console and I tested the command functionally and M564 P1 does indeed allow out of limit effector travel. Perhaps you are running an older firmware version.
Latest posts made by Ethelred
-
RE: Echo M291 on PanelDue
@OwenD All firmware the latest and greatest. I'm wondering about M292 in conjunction with M291. The dictionary seems to indicate that that PanelDue "may" be able to acknowledge blocking M291 messages. It is somewhat unclear in my mind and I've been unable to get any combination of M291/M292 to work.
It would be helpful for an example or two to have been included. -
RE: Echo M291 on PanelDue
Macro is invoked from the print file when a filament change is requested. The fil change and purge (Macro-line 21) routine is manual at the printer. Line 23 instructs a trip back to the computer to resume as instructed on line 24.
Two ~20 ft trips printer/computer back and forth required presently. It would really be of help if the resume commands could be done at the printer panel.COLOR.png](/assets/uploads/files/1689879039441-color.png)
-
RE: Echo M291 on PanelDue
@Phaedrux I'm running RRF 3.5.0 B4 and 3.4.1 on the panel.
-
Echo M291 on PanelDue
I would like to see and acknowledge the M291 (truncated ok) message on Panel Due. Now I need travel back and forth between the printer and the computer in order to complete my semi-automated manual filament swaps. Any sneaky way to do this?
-
RE: Max file count error
@Ethelred
Flashed an updated PanelDue binary and all is well - gadzooks, the previous version was pre-historic.
Thanks to all for the help. -
RE: Max file count error
@Phaedrux said in Max file count error:
M98 P"config.g"
PanelDue 1.22.1 (28b1)
M98 P - error flash on both PanelDue and on DWC console screen -
RE: Max file count error
@jay_s_uk No daemon.g present - config.g below.
Perhaps interesting is that the error message appears on PanelDue only but not on the DWC console window.
config.g -
Max file count error
I'm getting a "max open file count" error message displays on PanelDue upon system bootup. Supposedly V3.5.0-b4 permits 20 open files. I have only 13 macros total with no nesting. I see no ill effects - printing perfectly. Duet-2 board.
-
RE: [3.5b1+ (ArrayElementSet)] Error: Max open file count exceeded
@dc42 I'm getting the "Max Open Files Exceeded" alert upon system startup. Duet-2 board running 3.50-b4. This seems to be new unless I've just never noticed it before. I have a total of 16 macros.
Doesn't seem to have any operational impact.