I have been trying to locate this file for far too long.
I saw it yesterday while surfing on my phone and thought, psh, I can find it on the laptop later and download that file… eh, senior moment…
someone posted a quick file to run. It would essentially zero, and set cut height at .06, I believe. Then, pause. no fire… so a newbie old guy could then go measure where the torch is actually sitting in relation to the steel.
Can someone point me to where that was, is, will forever be?
cut height test.tap (224 Bytes)
Two different ones. Both are provided by @Phillipw
I think you can tell the difference by the name.
cut height testNOSPRINGBACK.tap (223 Bytes)
cut height test.tap (224 Bytes)
BigDaddy…you are just too fast for me!!!
Mrs Bigdaddy got a new Nintendo Switch 2 yesterday, so I am watching Zelda.
Oh boy. Remember, “A happy wife = a happy life,” Jimmy. When she thinks I’m not watching, she shouts Langmuir.
@Bigdaddy2166 mine must be broken. Still trying to figure out how to make her happy… O well guess I need to return her to the manufacturer …
Phillip…you are going to be in so much trouble if she ever gets on this forum.
I just wonder what her username would be if she was trying to make a point…
…not going to even get in the middle of that!!!
And shame on all of us. One post from @HeloMech and the thread is so far off track it will never find the station.
I just showed it to her…
. I may be crazy you know.
Told her mom last week I was going to do a lemon lawsuit… She slammed the door in my face!
Sorry didn’t mean to derail the thread.
@HeloMech sorry for blowing up your thread.
My best friend just bought a Robinson R66 Turbine helo.
He crop dusts as a side gig.
That is some fancy footwork to bring this topic back to Robert!
Yeah, that was WAY quick!! Thanks! That helped a lot! Was set far too high even after using the cheesy measure sticks. Just ran a pretty large file and it looks like everything cut nicely. I’ll have to raise my travel rate back up now and see how it does.
PS, I don’t mind the hostile takeover of my thread… I still got what I needed FAR quicker than me finding it on my own. 
@HeloMech glad you have what you need .
You have to look over us we are just a unsupervised bunch of kids at heart …
Watch out for @ChelanJim and @Bigdaddy2166 they will definitely lead you in the right direction.
Ok, quick question.
I run this file, set my nozzle height. I see in fire control when it sets that physical height, Firecontrol shows cut height at zero.
So, that being said, I physically set my torch height at .06 when the file ran. Loaded a new file, and for giggles, set firecontrol cut height to zero.
Is that right? or completely out of lines.
I have z axis and thc and what’s the other one ihs… ?
setting it physically and then setting firecontrol to height 0 seemed to give me a decent cut.
I also adjusted my air. I had the regulator set to 75, but while it was sitting. I just ran “gas test” so it was on and flowing, and set the regulator at 75 during the flow test.
I’m so close to ending the waste of material! lol… next step… big boy plasma cutter.
After you run the program. You physically check what Fusion is setting the torch height. If it is set for .06 and you measure .10, reduce the Fusion set point to .04. You may also want to set the backash setting to zero from .02.
I am not a SheetCam guy, but the same process applies.
I am not sure if I understand you. You will not be “setting firecontrol cut height to anything.” The gcode will tell FireControl what you have baked into the gcode. Don’t mess with those settings in FireControl.
The file we shared tells FireControl to set the torch height to 0.06 inches. We are only having you measure the outcome of that test to see how everything is communicating that endpoint. If it is not what you expected (namely a torch height of 0.06 inches) you would go back to SheetCAM and adjust your cut height accordingly for your cut files. This then becomes your new target for the cut height and you will need to remember that number (or perhaps SheetCAM will remember the value you last used).
Let’s say you measured an actual torch position of 0.09 inches when you had it set at 0.06. You need to get rid of the addition 0.03 inches so you would tell SheetCAM that your cut height you desire is 0.03 inches.
You can verify if it is actually doing things correctly by interrupting a cut with the space bar and measuring. The reason that is not always accurate is that you are now mixing other factors that might move the torch, in this case THC. If THC is adjusting for the voltage, it might be moving away from this programmed cut height.
Got it. I think…
run the file, it tells it to sit at that height. Measure that height. At this point, can’t I physically adjust my height to match that height?
So then… that means .06 means .06… and if my gcode tells projects to cut at .06… they should be accurate. right?
Sorry… not a spring chicken and had brain surgery… so, the old brainenator sometimes gets out of sync.
Correct. If SheetCam or Fusion’s cut height is set at .06, then the torch should be .06 from the tip to the metal sheet. If it’s higher, like .10, then adjust Fusion or SheetCam to .04. Get it?
After you change the post-processor settings to make the difference, test the code file again. It should be 06.
But why do I adjust to .04 if I can physically match torch height to .06 of the test file?
If it matches, then you don’t. You are in business.
Go wreck some metal😁
Just swapped in new consumables and reset height again. Then wreck-it-ralph’d some metal. Way mo betta.
Ramped up the cut speed. I was cutting far too slowly due to bad settings, which was adding to my blown out smaller lines in lettering, etc.
