I’ve ruined my hair cut looking for debug programs that understand the “Fire Control” used with our Pro machine. Some thing comprehensive, a clean nice flowing process, all details covered. Like Post processor programs that blend seamless with Confusion 360 ( hope its not going to be 365 !) and Fire Control . Yeah that’s what I need! Heck maybe a official warning and alarm list with possible remedies could be thrown in as well ?!
Ok …yes I’m delerious, can anyone out there share their Knowledge of all this so as to achieve a smooth operation/process of design and fabrication from the programing side? Bet you’ve heard that before, Thanks in Advance.
Sorry I have no idea what you are asking here. Maybe just stick to what issues you have and you might be able to get some help.
It would help if you could specify what type of issue you are trying to resolve.
Most of the error messages contain suggestions about how to resolve them. The exception being the “Mach 3 post processor” error message. That one doesn’t usually have anything to do with using the Mach 3 post processor. It is a generic message that means Firecontrol doesn’t understand a line in the code.
His Profile shows he has a CF Pro so he shouldn’t have Mach 3 errors, should he?
There is a Firecontrol error code that says “it looks like this file was created using the Mach 3 post processor”. That error message pops up whenever there is code that Firecontrol doesn’t know what to do with.
I think Langmuir created that message to deal with people that might try to run their old Mach 3 files on a Firecontrol machine.
2 Likes
Hi Guys!
G-Code warning is located at the very last line which contains M00 or end program. Above that is the H code for Zaxis raise. I tried entering a Stop spindle M5 code thiking it may have been stopping the program while jogging up. (I know nothing of CNC code, last programing I had was in colledge; Fortran and we used punch cards then to batch programing. Yep…I’m old.) That didn’t work so I’m thinking either wrong code or more likely wrong set up in manufacturing suite of 360. So what’s happening is the program in 360 simulates just fine but Firecontrol won’t load it because of the error/warning. To me this is most likely because of my mis-interpretation of machine setup in 360. Any ideas anyone?
Thanks Again!
what the heck are you doing?
are you trying to modify the gcode or write your own…?
once you draw something you go and post process the DXF and Fusion does all the pro=gramming for gcode for you…
I will invite @TinWhisperer to this as he might be able to understand you
1 Like
the very last line is (ps100) that is program speed 100ipm in this example but it will be( ps(whatever your program speed is))
Could you post your NC file and or F3D file?
1 Like
Hi Mr. Whisperer.
Yes I’ll post it a bit later. But After updating Firecontrol it did accept my modified G-code. The modification was inserting M5 above the M00 in the G-Code profile. Now I’m rechecking machine ie Hypertherm settings for delay etc… If this works I think I might finally have a handle on it. Stand by for update please.
I think he is not producing a post processed .tap or .nc file for firecontrol. I’m not sure he has the work flow down yet.
You don’t seem to be using the correct post processor for Firecontrol. There should be no need for you to enter any G code commands. You should be using the Firecontrol v1.6 post processor.
M00 is not used in Firecontrol. M30 is used to end the program. M5 is used to turn off the torch. The code to raise the Z axis is G0 Z1. H1 and H0 are torch height control on/off commands.
1 Like
ds690
You are correct about the codes. I incorrectly called out M00 when I meant M30.
I had no idea how Langmuir modified M coding to manipulate tool operations, getting a clearer vision about that everyday and I thank you for clarifying torch controls. Now I know.
UPDATE: Updated Firecontrol, reset factory settings in limit switch panel and saved that, restarted Firecontrol. Then loaded problem program from yesterday and it was accepted and ran, but cut quality was poor. So played with over rides feed and pierce delay and got it tuned to everyone here expectations and much much more. I took some notes and edited machine attributes saved those, ran them once more and it perfectly duplicated our best test cuts. So i’m as giddy as a school boy on prom night about what we can do with this asset.
Getting to this point has been an arduous ordeal. The good thing about steep learning curves is that if you don’t quit first, they don’t last to long in the end. We made our first cuts 10 days ago using the straight cut functions on FC panel and went itno the weekend pretty excited about prospects of future projects. I returned to finish setting up thr Pro Wednesday which now required learning F360, its a extremely capable ACAD but I found the syntax to be foreign to my intuition of using our Archectural CAD. The CAM side of things is completely new to me and I knew it would be a challenge and it will be for awhile yet. So there’s my story; Learned F360 CAD and CAM and a debugging program in a weeks time, or at least learned enough to perform relatively simple design and fab projects. In addition researching topics in this forum was/is a tremendously valuable and reliable resource for me. If i ever produce an instructional class about my experience I’m calling it “Don’t do it this way”…just kidding.
Thanks To All!
1 Like