I was excited for the 1st cut so I downloaded the “Pup” file in Fireshare. When I loaded the program, it inserted the file outside of the travel limits. How do i get it inside the travel limits?
In firecontrol, click on set program origin, then click in the upper left green box in the cut path window.
OR
Manually move the torch Y- the distance of the cut program and zero the axis
The XR by default sets the home location at the upper left corner.
As Sticks says: Set your “program origin” at the left upper corner; and,
See if you can move the gantry/torch to the upper left corner then “zero all axes” at that location.
Everything should be okay with the limit switches and the cutting area.
Thanks for the help guys. I had already walked away from my shop a bit frustrated. It kinda felt like getting all psyched up for a big event only to find out at the last minute the event was canceled. Hopefully for me, it was just rescheduled for tomorrow. I will give it a whirl tomorrow after work. Thanks again.
I moved your topic to FireControl. Hope you don’t mind.
All FireShare files are user-generated and uploaded. Whoever designed and uploaded this file likely didn’t have the Limit Switch Kit and did not run into this issue, or did what @Sticks / @ChelanJim suggested.
Try zeroing the X-axis and Y-axis somewhere else on the table, then uploading the file. This is because there is a difference between the home position ( where the switches are physically located on the machine) and the origin point of the G-code (where the X-axis an Y-axis are zeroed when the G-code is loaded in). Anywhere within the cut area can be set as the XY zero point, and the G-code will run from there.
Thanks for the assist! It’s all good to go in Firecontrol now, will be making the first cut in a bit.
And then he was gone. Radio silence from poor @Bastrawn.
WELL: How did it go??? I stayed up all night waiting for you to tell us?!
Very funny @ChelanJim, not all of us are retired lol. Cut went great (flawless for me since I know no better). The torch wouldn’t fire at first, discovered I needed to turn off the THC. I’ll try to post a pics of it later. One thing i am questioning is if my torch was turned up too high. Cut on 14g 45A. This was the recommendation off the cut chart.
Good comeback!
Hey…I worked, sort of. Drove a dump truck for 8 1/2 hours yesterday and dumped most everything, mostly where people wanted it!
Not sure how you are making this conclusion. Most cutting can be performed with the 45A setting unless you are using fine-cut consumables. The speed is increased to compensate for the metal being thinner.
Ah. Like said in my introduction - get ready for some crazy questions (and reticle comments). You don’t know until you know, right?
Good job. A slight edge cleaning, and you’re in the club.
Very good start!
It looks like on your single line cuts you still had the Lead-in turned on. For single lines (not closed loops), most people create a separate tool path with that turned off and the Center Compensation selected.
Also, for the eyes, looks like your Lead-in radius and length may have caused you some issues. All of us struggled (and some(me) still do) with getting those parameters set just right.
Thanks for the feedback @Wsidr1. I will research the things that you mentioned and try to figure it out. Appreciate it
It looks like those weren’t supposed to be single lines and the cut is not completing. Longer pierce delay is usually the answer.
If it was cut ready on fireshare up your piece delay and those cuts will probably complete.
That’s probably why you needed to turn off THC. Did you keep getting the torch moved before voltage sensed error?
You will probably need at least .5 sec pierce delay. But we don’t know what cutter you’re using, or speed you were at.
@brownfox The torch wouldn’t fire at all until I turned off THC, I didn’t get any voltage errors. My torch is a XP45. Settings that I inputted when I downloaded the G code was .2 for pierce delay and 225 ipm for speed. Those are the recommended settings out of the cut chart.
That .2 pierce delay is most likely your problem.
Firecontrol measures delay from when the command to fire the torch is given. Hypertherm measures it from when the torch actually fires.
The shortest delay I have been able to use is .4 sec. Most people recommend a minimum of ,5 for reliability.
@ds690 I’ll try that the next time I cut. Is too long of a pierce delay a bad thing? I appreciate all the help.
The worst that will happen is the torch may burn away all the metal and lose electrical connection and the torch will turn off. You will have a larger-than-necessary hole in your metal.
I never saw what plasma cutter you are using. If it is Hypertherm, by all means your pierce delay is way too short. You might get your first cut but the second cut will stop before it even starts. Brownfox and DS690 are the professionals on this forum. They know what they are talking about.
I have Hypertherm and rarely get the torch to fire with less than 0.5 seconds. My go to number now is 0.72. You want it as short as possible and still be 100% successful with firing the torch. Anything less than 100% will potentially wreck your day.