@pro3d Totally beside the point and off subject, but what heater is it you're using?

@bernardomattiucci

Glad to hear you got it work.

One thing to remember about M98 parameters: Certain letters cannot be used. It has to do with the fact that there is nothing special to indicate that what follows is actually a parameter as opposed to be a new command.

For example: M98 P"some_code_to_run.g" G1

You might have intended G1 to be a parameter but G1 is a valid command and gets treated as such.

The letters P and M also won't work, if memory serves, and I think there may be a few others.

I have suggested that an alternate syntax be allowed - something like: M98 P"some_code_to_run.g" (A1 B2 C3 D4 E5)

The ( and ) would make it clear that the letters are parameters and not commands.

Frederick

@droftarts I took the values from the Tornado`s original Firmware (Marlin). The Bed on the Tornado is quite huge (300x300, 4 mm Aluminum). I am guessing this is why there is a difference

@gloomyandy

Yes but that reference appears in the section dealing with using a P parameter with G30.

And all of the examples showing Z-9999 include a P parameter.

Since he is using -99999, if it applies in the absence of a P parameter it is just going to be the same as G30 by itself.

Frederick

@T3P3Tony Good point; I didn't think of using the command line console

@droftarts
Sorry I forgot to tell you it's a Prusa MK2S
I ave tried the tramming process using my feeler gauage as reference. However I still get a bogus height map. Now it's has a little mountain in the top right corner.

So I have home all axis then used dwc to move to each of the four corner. the back two corners are now lower than the front two.

I have order some springs from Amazon. I will try with the springs tomorrow.
heightmap

That sure could do it. It wouldn't be using any of your other settings, only the bottom layer settings all the way up.

@dc42
Thank you for this. Now you're getting me excited for 3.6 before 3.5 has even launched 😄

@oliof thank you, that's very useful to know!

@akifakin

And how does one tune a stepper motor?

That is something I have not heard of.

Thanks.

Frederick

@edsped said in M116 and temperature overshoots...:

@deckingman That works well enough for the initial tool but not sure if it would be good for tool changes during the print.

You can read the active temperature for a tool using the object model e.g in your tool change macro use tools[n].active[0] and use that instead of a fixed value.

@oliof said in IDEX XY calibration by electrical nozzle contact:

@NeoDue great stuff! You should consider some way to filter out outliers in your 8 runs (use median or just track lowest/highest and reject runs where the difference is greater than some value you deem an acceptable range).

@oliof Now I finally had the time to dust off and actually use a bit of my old statistics knowledge... Got it 🙂 - here is a test macro that removes outliers from a given array based on their z-score:

; constraints out of experience: ; - electrical nozzle contact never gets activated too soon (=> too low values will never happen and are not taken into account here) ; if that does not apply, a lower acceptance limit for the z-score needs to be defined as well ; - values that are too high are usually at least 0.15...0.2mm off var Referenzwert = {1,1.02,1.05,1.2,1.22,1.3,1.01,} ; test values - the three values that are too high need to be detected and removed from the mean value var Referenzmittelwert = 0.0 var Referenzstandardabw = 0.0 var ReferenzZScore = vector(#var.Referenzwert,null) var ZScoregrenze = 0.5 var Anzahlgueltig = 0 ; calculate mean value while iterations < #var.Referenzwert set var.Referenzmittelwert = var.Referenzmittelwert + var.Referenzwert[iterations] set var.Referenzmittelwert = var.Referenzmittelwert / #var.Referenzwert ; calculate standard deviation while iterations < #var.Referenzwert set var.Referenzstandardabw = var.Referenzstandardabw + (var.Referenzwert[iterations] - var.Referenzmittelwert) * (var.Referenzwert[iterations] - var.Referenzmittelwert) set var.Referenzstandardabw = sqrt(var.Referenzstandardabw / (#var.Referenzwert - 1)) ; calculate z-score of each measurement value while iterations < #var.Referenzwert set var.ReferenzZScore[iterations] = (var.Referenzwert[iterations] - var.Referenzmittelwert) / var.Referenzstandardabw ; re-calculate mean value without detected outliers set var.Referenzmittelwert = 0 while iterations < #var.Referenzwert if var.ReferenzZScore[iterations] < var.ZScoregrenze set var.Referenzmittelwert = var.Referenzmittelwert + var.Referenzwert[iterations] set var.Anzahlgueltig = var.Anzahlgueltig + 1 set var.Referenzmittelwert = var.Referenzmittelwert / var.Anzahlgueltig echo var.Referenzmittelwert

While I do not use that for XY calibration (at least yet - that one works perfectly well as it is so far...), I did add it to the two macros I wrote for z calibration and z-leveling of the U axis relative to the X axis. It definitely makes sense there since slight drops of filament coming out of the nozzle can cause errors.

@tfranssen you can specify proportional control of a thermostatic fan by providing two temperatures in the M106 command.

E jerk can be set very high for most extruders. Try 3000 to 6000 mm/min.

Acceleration Z20 will also make it seem very slow. Try 120 there.

@Dutchprinting said in Nema34 closed loop tuning on megaprinter??:

If you have experience, maybe you could come play around with the setup with me, i'm in the great city of Elburg.

Maybe I do that, I wanted to visit Flevobike in Dronten anyways. Alas, my experience with big printers is marginal and closed loop stepper on RRF even less.
But I often use an anti-racking technology, which is wide spread amongst huge machines.

@dc42 Thank for replying.
But I was wondering what parameters I have to put in the motor settings to have a perfect rotation of 360°. Because the 33 is a value that I approximated using my eyes but it's not a perfect rotation. Or is there a command to control a stepper motor only in degrees of rotation and not in a linear axis ?
Otherwise, thank you very much for your response!

@Arminas In other word, is there a jerk setting that is good for both slower and faster printing speed, and for both high and low resolution stl's?

@tom33 said in mesh bed compensation:

@fcwilt Yes, I have just a system to up and down the second tool head

As you understand the firmware needs to know the locations (X, Y, Z) of the Z probe and the tools, relative to one another.

With a single tool system the tool XYZ offsets are the reference (all zero) and the Z probe offsets/trigger height are set as appropriate.

Typically with a multi-tool system the Z probe is the reference (offsets/trigger height all zero) and the tool XYZ offsets are set as appropriate.

Your are combining both approaches - which will work - it is just unusual.

Where did you get the code in BED.G - there is much there that I don't understand.

When configuring your tools you have G10 L2 P1 X37.60 Y20.00 Z0. Why the L2?

Thanks.

But back to your original problem. Have you updated start.g to include a G30 before the G29 S1? Recall that the G30 used to set the Z=0 Datum should always be at the same XY machine position.

Frederick