Resolution of Trigger-height in G30 and G31
-
@wildblue said in Resolution of Trigger-height in G30 and G31:
extreme invariances
Would a rounding of the 3rd decimal place really cause extreme variance?
I'm not sure that it rounded internally or not though. The display may be.
For what it's worth I do a round of 10 G30 S-1 and take an average rounded to two decimal places and don't have any issues.
What kind of probe are you using? You may want to look into using some of the additional parameters available for the M558 command to help increase consistency.
M558 P9 H3 F100 T6000 A10 S0.003 R0.75 B1 ; P9 for BLTouch, dive height 3mm, probe at 100mm/min, travel 6000mm/s, up to 10 probes until two match within 0.003, pause 0.75s, heaters off -
I tried all available Options before. Now i am calibrating the System to Maximum precision and therefore a rounded decimal place is a huge issue. Even when i am turning all Options to Minimum precision, this phenomenon won't Go away by itself and Others people WHO Care for precision will still be wondering why the Numbers don't Match...
-
You cannot determine the actual values used behind the scenes based on what is displayed.
Ask dc42.
Frederick
-
I Just want you to make Sure the values shown are consistent and valid.
I do Not assume anything beyond what i am seeing, and for this reason i wrote a Short notice to the manufacturer of my printer-hardware asking for help. Thats you, Guys!
-
@wildblue said in Resolution of Trigger-height in G30 and G31:
I Just want you to make Sure the values shown are consistent and valid.
Certainly. The values should be consistent.
But my earlier point still remains; consistent results are possible, so what is it about your setup that differs?
We don't have any details about your printer or probe, so it's hard to know what to troubleshoot.
-
Forget about my system.
I want consistent Numbers in my system.When i Take a measurement with G30 s-2 and got the result 0.885 i will Not have to worry about what this translates to, when i use this Stored value somewhere Else. I only See the saved result with G31 and there is one decimal place Missing.
Just fix the mismatch considering the shown and saved values regarding G30 and G31.
-
@wildblue said in Resolution of Trigger-height in G30 and G31:
Forget about my system.
Consider it forgotten.
-
What i meant was, this issue is Not bound to a specific system, but occours on all Installations.
-
Just fix the mismatch considering the shown and saved values regarding G30 and G31.
I’m just a bystander without a horse in this race, and even I find this an incredibly rude approach to getting resolution or information to your question/issue.
Maybe it’s a language barrier, but you may want to consider how the tone comes across.
-
@wildblue, you didn't say which firmware version you are using, but I can confirm that in 3.0RC1 only 2 decimal digits are shown which displaying the trigger height in response to G31. I will change it to 3 in the next 3.0RC release. It's purely a display issue, there is no rounding of the value that is actually used.
-
Thanks you very much for taking a Look into this.
I was using rrf2 until Yesterday, but upgraded my complete Installation to rrf3 and completed this Task just a few Moments ago. Because the new Handling of the pin-names and all the other changed gcode, this was Not an easy Task.
As i Love my Job as a Software-Developer and even are spending some of my spare time with this stuff, i Started participating in the duetProject (for now Bug Reports here in the Forum), because i want to get the Project to move Forward.
I don't want to explain, why a Missing decimal place (even If only Not shown in the GUI) is a critical Thing for me and how These things make my experience AS a User Not consistent at all.As Language-barriers are Not very helpful when communicating, i have to thank you for your Patience with me. I am getting a littlebit more handsome every single day.
I will try the next RC, when IT IS available.
-
@wildblue Please don't take this the wrong way but I do find your posts difficult to read due the the scattering of upper case letters. Do you think you could fix that? It would help others to better understand the meaning of what it is you are trying to say.
In English, we do not use capital letters very much. We use them mainly for the first letter of sentences, names, days and months as well as for some abbreviations. We always write the first person pronoun as a capital I. But other than that, most words are written in lower case.
If you write "IT" or "AS" in capital letters it comes across as being highly stressed as if you were shouting and can seem rude, when I'm sure that is not your intention.
-
Thats the autocompletition of my Android Phone. Everything i Type in is lowercase AS i Type, but gets converted automatically, AS you can See very clearly.
Maybe i will buy an external Keyboard for my Phone in the Future, which has These old school Hardware Buttons. But until then, i will try to correct every single Word after i have written ... No. Not really.
Happy Christmas, everybody.
-
@wildblue said in Resolution of Trigger-height in G30 and G31:
Thats the autocompletition of my Android Phone. Everything i Type in is lowercase AS i Type, but gets converted automatically, AS you can See very clearly.
Maybe i will buy an external Keyboard for my Phone in the Future, which has These old school Hardware Buttons. But until then, i will try to correct every single Word after i have written ... No. Not really.
It may be that your smartphone is converting words to uppercase because it thinks you are entering words in your native language. Does it have options for input in multiple languages?
-
Hey dc42,
i will change these settings of my phone and until then very carefully correcting my words.As it is christmas today, i jumped over my shaddow with this. Maybe the karma will come back to me anytime soon.
My wishlist this year has only one point. I want to be able to calibrate my z-probe automatically with "G30 S-3" and multiple probing, but that's another topic.
Merry christmas
