Topics created by CR3D

@CR3D did you take the M122 reports one right after the other? The M122 report for the master board says it was reset 38 minutes ago, but the board 1 report says it reset 17 minutes ago. So perhaps board 1 had an unexpected reset. Unfortunately the M122 report for board 1 doesn't give the reset reason. However, next time it happens, if the M122 B1 report shows that board 1 has reset, you could connect to board 1 via USB so that you can send M122 directly to it and get the complete report.

OOH if the 3.5beta3 firmware is working well for you, then you can continue using it. We hope to release 3.5beta4 next week.

@dc42 said in software limits prevent negative tool offset on IDEX Printer:

Why don't you change the Z limit in the tool change file to a value based on the Z offset of the incoming tool? That way you can use the same code for all tools.

@CR3D
Based on DC42's advice, I think this would work in your tool change file

M208 S1 Z{min(0,0 - tools[state.nextTool].offsets[2])} ; set Z minima to the lower of zero or zero minus incoming tool offset

But this line in the G10 documentation

Tool offsets are given as the offset of the nozzle relative to the print head reference point, so the signs are opposite to what you might expect because tool offsets are subtracted from the required printing locations during printing.

makes me wonder if the math should be
Z{min(0,0 + tools[state.nextTool].offsets[2])}

I don't have multiple tools, so I,m not 100% sure on the G10 setup.
e.g.
Let's say tool 1 is zero offset (reference) and tool 2 is 1mm higher in Z

If that means your Z offset for tool 2 is +1, then use the first example.
If it means your tool 2 offset is -1, then use the second example.

@dc42 Thank you!

It worked 🙂

@dc42 thank you i will check the resistor 🙂

@sebkritikel I actually figured it out... lol I was doing a negative value on my T1 z-offset. But I changed, I got rid of the negative sign on the Z offset. it is working now. the layers are going down now.

Only wish I could use a fork of slic3r that allowed you to adjust the z-hop, z-retration, etc in the slicer itself instead of the firmware.

@cr3d it's a known issue in beta7 that sometimes a heater will not heat up. Usually it only occurs after doing a print and then letting the heater cool down to below 25C. Fixed in RC1.

One additional test, that can help determine probe offset changes is to run the probe out near a corner of the bed, use the probe to home Z in that location, then print a one layer test square there. If the probe z-offset is different in that location, then the locally zero'd test patch should look just as bad as when the bed was homed in the center. If, however, the test patch looks great, this means that the probe Z-offset has not changed between the center of the bed and the edge.

@oliof Thank you a lot! Now it works great 🙂

IMG_20220215_213052.jpg

P.S.: Also with downgrade to RRF 3.3 😉

In other words, more people need to test these releases (-:

@cr3d if you have already homes Z by other means, one approach would be to configure that switch as an additional Z probe, then probe it with each tool using the G30 S-2 command to set the Z offset of the tool.

@t3p3tony

no ... the first project was now with a german industrial adhesive manufacturer where we then processed their adhesives. The next step are very soft silicones ...

Quick answer -> after a firmware change in that thread:

https://forum.duet3d.com/topic/24816/m500-after-pid-autotune-overwrites-g31-in-config-override-g/19

Now it works!

We can use M500 / M500 P10 / M500 P31 / M500 P10:31 and nothing gets deleted 🙂

Thank you!

Take a look at these threads for ideas on using a door trigger to alter behaviour using conditional gcode.

https://forum.duet3d.com/search?term=door&in=titles&matchWords=all&sortBy=topic.lastposttime&sortDirection=desc&showAs=posts

@dc42 Thank you!

Short report:

I have added the Heater to Board 0 (mainboard) and now the M141 command works well!

; Heaters M308 S0 P"temp0" Y"thermistor" A"Druckbett" T100000 B4092 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 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 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"temp1" Y"thermistor" A"Links" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M308 S2 P"temp2" Y"thermistor" A"Rechts" T100000 B4725 C7.06e-8 ; configure sensor 2 as thermistor on pin temp2 M950 H2 C"out2" T2 ; create nozzle heater output on out2 and map it to sensor 2 M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ;Chamber Temp M308 S3 P"temp3" Y"thermistor" A"Bauraum" T100000 B4725 C7.06e-8 ; Case temp 100k semtek M950 H3 C"out7" T3 ; create chamber heater output on e1heat and map it to sensor 3 M307 H3 B0 S1.00 ; disable bang-bang mode for the chamber heater and set PWM limit M141 P0 H3 ; map chamber to heater 3 M143 H3 S70 ; set temperature limit for heater 3 to 80C

2d63a80c-0b66-43fa-b31d-3f8d28406db8-image.png

Thank you for your help! 🙂

@cr3d No, i have no working example at the moment. And i'm not at the machine, so no access to the object model.
Normally when i try to write some code out of my head, then it will have some errors... 😵

I'm specialist for coding some small mistakes. I allways need some iterations for a working code. 😇

@phaedrux It displays the extruder location correctly during a print.
What is more odd is the output of M114

m114 X:121.263 Y:143.324 Z:0.300 E:0.000 E0:896.7 Count 10462 12499 120 Machine 121.263 143.324 0.300 Bed comp 0.000

I only have 1 extruder configured....

Closing due to inactivity.

So the test print runs without problems! 🙂

IMG_20201128_084305.jpg

@dc42 did you made any changes in this direction?
I did not read something about a topic like this in the changelog...
Please let me know, because there are machines outside from us with the old firmware...

Regards Christian ✌

@Phaedrux ok thank you for this Information! 🙂 i will contact Roland 🙂

@CR3D said in Massive Vibrations with Duet3 & NEMA23 drives:

@sebkritikel

Thank you for your response! The part was printed as your picture shows ....

I use the Duet 3 and I also think the problem is the firmware settings and not the steppers themselves ...

I can feel the ripple along the whole object ... that's that strange for me ...

the axes themselves run very smoothly and do not jam.

A change in the acceleration values ​​can affect the shape of the waves ...

@JoergS5

ok now i understand what you meant!

Yes, I've already checked it, the axes run very smoothly. The printed image occurs in a cold and in a warm state.

I have been building the mechanical structure for about a year. Cartesian with two separate Y-motifs. So far it has always been NEMA 17 motors and the Duet Wifi.

That was the reason why I first blamed the bigger motors or the other drivers.

I once read a post by @dc42, where he said NEMA 23 tend to vibrate.

on the subject of M593:

How do you find the Find the right frequency?

Unfortunately I cannot find where it was written, but if the picture is as you say, the ripples are likely not caused by the Y stepper motors, but the the movement of the print head wobbling parallel to the X axis while the gantry moves down the Y axis.

Please run the test DC42 recommended and report back to us.

For specifically M593:
'To measure the ringing frequency, take a print that exhibits ringing on the perimeters (for example a cube), preferably printed single-wall or external-perimeters-first. Divide the speed at which the outer perimeter was printed (in mm/sec) by the distance between adjacent ringing peaks (in mm). When measuring the distance between peaks, ignore peaks close to the corner where the ringing started (these peaks will be spaced more closely) because the print head will have been accelerating in that area.'

If the perimeter is 60mm/s, and the 'waves' are 2mm pitch, 60mm/s / 2mm = 30 1/s, so "M593 F30; frequency 30hz"