If you guys can add all the versions to this thread, I’ll merge everything together over the weekend, so that we’re working from unified code. Thanks.
2 Likes
That would be fantastic!!! 
What I mean to say is that the value 1.6-af has to be in the generated gcode or the FireControl won’t open it, so Autodesk (nor anyone of us) can really change it, so it must stay the same.
In fact this can be likely changed by messing with the json files found in one of the jar files in FireControl, but who really wants to go there.
1 Like
It does sound like Langmuir is amenable to adding a unique name to whatever post processor you come up with to the list of acceptable post processors. I know Craig already submitted his to them. They have some notation that after a review it will be included in a FireControl update.
But your concern is well taken.
1 Like
Thank you. @ChelanJim placed a link to the post processor I shared a few posts earlier in this thread.
2 Likes
Yes, I noticed this. My post appends a revision comment on line 2 of the tap file).
1 Like
1.6-sc also works, which is the comment required for the post processor from SheetCam (totally irrelevant for a Fusion discussion, but thought I’d throw it out there 
)
1 Like
For consolidation, here’s the post I modified for changing backlash. I also added an M5 to the OnSectionEnd to turn off the torch when cutting multiple tool paths. (Found n the Autodesk Fusion Forum.)
FireControl-v1.7.cps.txt (18.5 KB)
(Remove the .txt extension.)
1 Like
FireControl-v1.6.2-forum.cps.txt (22.0 KB)
I’ve merged my 1.6.2 github code with @Simsworx v1.7 and @manoweb alesan variant and added the ‘-forum’ filename postfix. Please verify that my merging was successful with your additions to the original LS 1.6.2 post code.
I’m not an my shop today to verify firecontrol opens nc file.
2 Likes
The fact that FireControl won’t work when it’s not connected to a machine is also super-annoying.
3 Likes
Agreed, I’ve programmed an arduino with grbl (like the XPro controller) with latest code and its not seen by FireControl. LS isn’t running latest version. Plus, they’ve flashed the USB chip CH341 with a custom ID and label.
16d0:0efb MCS CrossFire CNC
grbl
Grbl 1.3ls [‘$’ for help]
$I
[VER:1.3ls.20220922:]
[OPT:ZSL,15,128]
Oh well. Its probably for the best. LS is minimizing support issues by locking this down, can’t blame them (its what I would do being on their side of the table for my career).
1 Like
Thank you Craig for working on this.
Dan @danbrown , I ran those files. Seemed to have worked as intended! I would show but the signs are soaking in vinegar.
2 Likes
I’m making some plates today, will try the post as well.
1 Like
@ChelanJim happy to hear that. And thank you for confirming the changes.
1 Like
Life got in the way, checking tomorrow.
3 Likes
I cut these plates with 1.6.2-forum.cps this afternoon. It seems to work fine. I did have problems with tweaking tool settings, it seems that Fusion CAM doesn’t reload tool library after setting change. Does anyone have tips on how to force CAM to reload?
When you’re in manufacturing the actions tab there is one action called generate in the drop down menu, it will reload the tool paths it may reload other items as well.The hotkey is Ctrl G in the manufacturing workspace.
Tried that. Home now, let me fool around with Fusion and try a few more things. Its a pain to do this in the shop.
I have my plasma tools in cloud storage. “Generate” doesn’t reload the tool library. I had to reselect the tool in the profile operation to get tool changes incorporated. I tested by changing the feed rate.
1 Like
As soon as you use a tool to develop a toolpath it does make a copy the tool and sticks in the “documents” (in the tool menu) to be store with that project or F3D file if exported. Maybe you can access that information there because it will refresh with any change to the tools used in the 2D profile menu. Maybe that helps ?
When changing the library copy or document copy? The document copy is the one tied to the setup.
Where is the option for cloud storage ?