Best posts made by petriheino

Im trying to debug move commands

1. Nothing with M111 S1 P6 ;DDA logging
2. Nothing with M111 S1 P4 ;Move logging
3. Only works with both P6 & P4 on

When both P6 & P4 is enabled, im getting this type of debug info via USB serial, two or more blocks of data repeating as below.

pr 1 ts=512267325 DDA: start=[186.160995 83.862999 7.200000] end=[185.625000 84.664001 7.200000] s=0.963793 vec=[-0.556132 0.831094 0.000000 0.000000 0.000000]
2021-09-12 23:46:28,086 - a=600.000000 d=600.000000 reqv=15.416668 startv=15.416668 topv=15.416668 endv=15.416668
2021-09-12 23:46:28,087 - cks=58609 sstcda=24088 tstcddpdsc=82697 exac=0
2021-09-12 23:46:28,088 - DM0: dir=F steps=79 next=1 rev=80 interval=740 2dtstc2diva=0
2021-09-12 23:46:28,090 - accelStopStep=1 decelStartStep=80 2c2mmsda=35681189 2c2mmsdd=35681189
2021-09-12 23:46:28,092 - mmPerStepTimesCdivtopSpeed=758400 fmsdmtstdca2=0 cc=56250 acc=0
2021-09-12 23:46:28,094 - DMY: dir=F steps=64 next=1 rev=65 interval=915 2dtstc2diva=0
2021-09-12 23:46:28,096 - accelStopStep=1 decelStartStep=65 2c2mmsda=44118924 2c2mmsdd=44118924
2021-09-12 23:46:28,097 - mmPerStepTimesCdivtopSpeed=937744 fmsdmtstdca2=0 cc=0 acc=0
2021-09-12 23:46:28,101 - DMX: dir=B steps=43 next=1 rev=44 interval=1363 2dtstc2diva=0
2021-09-12 23:46:28,103 - accelStopStep=1 decelStartStep=44 2c2mmsda=65665377 2c2mmsdd=65665377
2021-09-12 23:46:28,106 - mmPerStepTimesCdivtopSpeed=1395712 fmsdmtstdca2=0 cc=0 acc=0
2021-09-12 23:46:28,111 - Transformed 163.43 77.45 7.20 to 13074 6196 2880

Can this info be read to check what was the requested motor move for extruder? Because after each gcode theres more than one output logging info block similar to above, which one should be read?

Is it intentional that if not both S6 and S4 are enabled, there is no debug info? Now both M111 S1 P6 ;DDA debug and M111 S1 P4 ;Move debug has to be enabled to get any data.

@marcossf
Could you try to add G29 S2 before each? Could that work (reset the mesh)?

I noticed that if not using G29 S2 in start.g file, then z motor stepcount gets lost when repeating measurement with G30 -> G29. This can be seen by using M114 and comparing the Z stepcount. Maybe observing Z stepcount would be also good to do.

Im also trying to solve issues related to G29 and hopefully soon will measure Z axis with encoder.
My earlier theread here Mesh Bed Leveling G29 issues.

By doing more testing with Retraction distance 0.6mm and retraction speed 1800mm/min, the gaps increase if adjusting pressure advance from 0.04 to 0.07.

Could this issue be related to extrusionPending inside dda.cpp?

Because otherwise print quality is very good but starting point always fails by either missing material or having too much.

Would it make sense to add anything like this to end or beginning of DDA::Prepare etc?

if ( moveBuffer.hasPositiveExtrusion && axesMentionedExceptZ.IsNonEmpty() )
{
extrusionPending = 0
}

@bot
By disabling Pressure Advance, retract and un-retract steps are matching, 662 and 662.

Hey developers, is there any documentation that could help to troubleshoot mesh? Ive been trying to read the code and understand how to debug mesh, and looked at the Gcode states. Should we concentrate on some of them, where the readings go wrong?

Case 29 (G29)

Case 30 (G30)

probingAtPoint0
probingAtPoint1
probingAtPoint2a
probingAtPoint2b
probingAtPoint3
probingAtPoint4
probingAtPoint4a
probingAtPoint5
probingAtPoint6
probingAtPoint7

Re: PA tuning
Re: Enhancing pressure advance

Hi,

After countless trials with configurations, I can also confirm having similar difficulties in PA tuning and retraction tuning as other users on this forum.

By tuning extuder jerk, retraction distance and micro stepping resolution (16x to 256x) Ive been able to make the start point from missing material to having too much material (dot) with direct drive extruder.

The next segments are also effected - if a dot is formed, it measures 0.5mm, and the next lines measure 0.3mm, after it settles to 0.4mm after few millimeters of printing.

Another forum user suggested dynamic unretraction constant. But using firmware from mdealer fork didn’t seem to help.

Similar thing happens when attempting PA calibration method of Marlin PA1.5 so I tried injecting M572 D0 P0 commands to the gcode at G10 and M572 D0 P0.04 at G11. This helped in line test but not in round shape.

Also, when using low retraction amounts, they work nicely in calibration, but in real print start randomly stringing, leaking alot when retracting and moving (when printing larger areas). Large retraction amounts make gaps. Tested with both Simplify3D code and Cura code with absolute, relative and firmware retraction modes.

Could we make some changes to firmware where extruder or filament amount is reset at the event of retraction / unretraction?

Other possible solution would be if the DDA would detect that this is a retraction move, and all corrections should reset when the retraction event is noticed. What would firmware developers suggest?

@bot
Previous post done with M566:
Maximum jerk rates (mm/min): X: 300.0, Y: 300.0, Z: 600.0, E: 3000.0, jerk policy: 1. It resulted in 699 retraction steps and 656 un-retraction steps

I went ahead and re-captured with M566 E120 but it seems to make the problem worse, by resulting in 713 retraction steps, making problem worse (not affecting un-retraction.) Signal seems same, and motor sound is same (one 2A motor stand-alone on table)

Hi,

several times using PanelDue 5i to setup new printer is cumbersome and time-consuming to setup networking.

Could these features be added?

• Longer max characters lenght in console to type in long WIFI config messages (with long SSID & password)
• Network discovery (like selecting Wifi SSID from list and more)

@oliof Thanks for noticing, seems like comment was left out by accident. Will measure tomorrow again.