cut height test.tap (224 Bytes) put this file into FireControl. Set fusion for .062 it will stop and you can measure what FireControl thinks is .062.
Example. 062 actually is .10 , then you can subtract the difference and adjust fusion to reflect.
Please send us you consumables pictures. Hopefully they are not Plasmadyne..
I ran the file it came down touched the steel went back up came back down to .060 in fire control but measured.065 . consumable pictures are posted further up
I want to see the ones that are in the torch now.
BigDaddy has a decimal place off (he is obviously replying by phone)
So at 0.062 setting you are getting an actual cut height of 0.1 then you determine how far you are off by: 0.1 - 0.062 = 0.038 (difference off).
To get that to come out right you would subtract the difference from your setting:
0.062 - 0.038 = 0.024.
Set your cut height in the gcode to 0.024. I am thinking if you put that setting in your cut height, you will be satisfied.
(Don’t ask me why it has changed with your set up. Happened to a number of us.)
Would my pierce height also need be adjusted
Likely, yes but you would see a noticeable difference with your cut without changing pierce height.
If pierce height and pierce delay are too large, you might starve the plasma stream for metal to melt, thus losing connection and it might turn off the plasma flow.
Same thing could happen if the cut speed is too slow so you might try BigDaddy’s suggestion to set the cut speed to 47.
Cut good at .024 but misfire at the beginning of a couple of cuts so I assumed the pierce height need to be adjusted too. it seems like this must be an issue with my fusion software
Are you still cutting at 25 ipm? It is way too slow.
You are blowing a hole and losing your smart voltage. 47 ipm
Bumped I up to 30 it would cut good at 47
45 amps 47 ipm is the chart speed. It should be near perfect with almost no dross.
It is not Fusion. It is FireControl, the computer and the electronics of the table that turned gcode 0.062 inch cut height to 0.1 inch cut height. It is related to the electronic communication between the computer and the table electronics. If you change to a different computer you might see 0.062 come out setting it right at 0.062 on the table. Hopefully, you are now on track to having some consistency again.
You might need to re-evaluate all of your settings for different thicknesses of metal with respect to cut height, pierce height, pierce delay and cut speed. If you look at your first cut images in this thread, it is classic “torch too high” behavior (topside dross, incomplete cut and severe positive bevel).
45 amps 47 ipm is the chart speed. It should be near perfect with almost no dross.
25 is the fastest I can go on 1/4” 47 will not cut all the way
As I am guessing you have been cutting items for some time now. This has just started happening, right?
What have you changed before this started?
When you get the time to spend with the table give me a call and I will see if we can get it back up and running.
First you need to clean the Z axes and get some scrap 1/8”/11 gauge to do the testing on.
There is another issue that came up at the same time this started my y axis stepper controller was overheating and shutting down I was able to add a fan to it and stop that issue but with no fan on the stepper controller it will shut down put in a new stepper controller and still needed the fan
This start same time as cutting issue
You need to CLEAN and lube the complete table. Rails, feed screws, tracks, guides, etc. This is what is causing the motors to over heat.
Cleaned and lubed and replacing everything with new and if that doesn’t work I’m out of ideas and will have to throw it all in the trash
If you need help just call me.
Got everything swapped out and it cuts perfect even at 47 ipm but has new problem the longer it cuts its slowly drifting down and hits the metal and dragsl
Ok when swapped everything out with new I hooked to pv instead of div everything working now set to .060 47 ipm cuts perfect
