We are soon to release a minor update to FireControl to address some issues and bugs noted in the last few weeks. This is a minor release with no major updates to the core of the application but with fixes for specific issues.
Updated in 21.1.4
USB connection stability improvements
Metric Program Speed Fix
Machine Setting: Max Rapid Speed - depending on your machine (XR vs PRO/CrossFire) you can limit the max XY speed of your machine via the Machine Settings menu.
Other minor bug fixes.
We ask that if you have been having issues with any of these items (or not) to check out this new 21.1.4 version. While we test FireControl on many different types of machines, USB issues in particular depend greatly on individual machines so the more users we can have using it the better.
Neither the current release or the compatibility release will work with my laptop. Iām very frustrated as I made the mistake of updating and now I no longer have a working plasma cutter. Will this fix it?
Thank you for pointing me in the right direction. I was able to download that version and get it working on WINDOWS 7 laptopā¦
It really pisses me off that they pushed an āupdate availableā through fire control that downloads an incomparable version!!! They they take you through the rabbit hole of suggesting an incompatible ācompatibilityā version.
Do they not know how to do a simple OS version check?!
Stupidā¦
Even their post above says nothing about not being compatible with windows 7.
Once again I am now angry they did a bait and switch on me. I bought my pro table when it was supposed to come with Mach3, but they switched it Firecontrol and Iāve been their damn ālearning experienceā ever since.
There is nothing about Windows 7 that makes the latest versions incompatible. Most Windows 7 computers are around 10 years old (or older if they were updated to 7) at this point and have older components which can lead to incompatibilities usually surrounding graphics.
We try to develop FireControl in a āgreatest good for the greatest numberā manner but sometimes that leaves older computers behind.
Dude, I have to respectfully disagree with you about accountability.
In my experience with Langmuir they have been really good about about dealing with some of the issues as well as giving options for me with the new version of Firecontrol. Having been in software testing I know that most software vendors try to keep backwards compatibility for exactly your situation which is what Langmuir has done but you canāt be compatible with every piece of older technology.
I figure what youāre asking for in computer terms is the equivalent of asking them to supply OEM parts for a 39 Ford because you have one.
Anyway. My dealings with @langmuirsystems regarding Firecontrol have been great. Sorry yours havenāt been as good.
Hope the rest of your year and 2022 are good to you.
I would bet that the compatibility problem is hardware related, not OS related. Thereās lots of options, but running an older version of the software, so you can keep your 15 year old laptop instead of spending $50 to upgrade to a newer better one, is not a great option. Just my $.02
I upgraded to FireControl 21.1.4 on my MacBook Pro, Big Sur. I find that on loading the software, or a new cut file, FireControl goes into HOLD status. To clear it, I find I have to act like Iām going to run the code, get an error, and choose āresetā in order to get the status to be ready. Itās fine until I load the next code to be cut, then have to do the above again. Is this a feature or an error? Whatās the correct procedure to move from hold? I use SheetCAM to create the g-code. Itās beta, so maybe Iām reporting an issue!
I was able to use older versions without a problem. As it turns out, it seems that this issue only happens when I use SheetCAM instead of Fusion360 for CAM. First video shows a file opened in FC from SheetCAM, and HOLD as a status, I then run the code in FC, get the error and use āresetā. This sets the FC back to āidleā. Second video, shows different files, same result with the SheetCAM coded file. So far, the added step is a minor nuisance. (Sorry, canāt upload videos here and donāt have my own website to host them.)
The problem is those additional THC off/on commands in the Sheetcam file.
I donāt know how Firecontrol treats a semicolon (end of block) command, but it may treat it as a stop and wait for a command to run the next block.
Itās not necessary to add those additional THC on/off commands, since the software turns it off automatically when the torch speed is below 85% of the program speed. Remove the path rule or code snippet that is adding those commands in Sheetcam.
Thank you. Iām learning sheetcam and some tutorials just go a bit over the top with rules. Thanks for looking into this and sorry for the troubles. Happy New Year!
new version does not update. Still shows 20.6 after running and āupdate availableā in Fire Control. uninstalled Fire Control and reloaded - same result