Unfortunatelydue to the rare nature of the issue combined with the fact that it stems Windows - not FireControl itself - at this time all we can do is provide suggestions that might work and collect data that may help us formulate a consistent fix.
The windows 7 machine is running an Intel Core 2 Duo CPU L7500 @ 1.60 GHz with 4 GB of Ram. The computer is a Panasonic CF30. I have removed an re-installed the Fire Control a couple of time and I keep getting the same error messages with all.
It will not even start the program before it crashes with the v21.1.5 and 21.1.4 but it runs the 20.6.2 fine. The errors seem to indicate (from what I have been able to locate) that there is a system file missing or corrupt that will not allow the program to load properly in the latest versions. Also the fact that these program are only allowed to install into the Users directory (I tried to install it into the Programs directory but it would not let me. It gave me an error that the installer did not have the proper permissions to install in that directory) might have an effect on this. I have been reading through the forum the past day or so and it seems that the newer versions of the FireControl are have issues with top end machines running Windows 10 and 11 too. Very few seem to have solved their issues or if they did there was no indication the problem was solved other than reverting back to the v20.6.2.
To install to Program Files, the file path should look similar to the path highlighted in green below (keep in mind that the FireControl folder in Program Files needs to be manually created prior to this process):
Over the years havr had issues with DLL files while running CF29 toughbooks. Based on already uninstalling and reinstalling Fire Control I would say reinstall windows and then install fire control and see if it works. If works good then run all the uodates and recheck. Sometimes DLL files can be a pain. Good luck!!
I have a Yorahome laser that I replaced the controller with with MKSDLC32. I can not get the laser to come on with a program (fire button works and the wireless interface works.
Here are my starter questions:
When creating laser manually, what selection should I use? GRBL, GRBL-LPC, GRBL M3?
I added limit switches and set the home to lower left. The home button works and when I try to create a simple program (circle) I get an out of bounds error and the gcode is showing negatie values. What did I mess up?
MKS DLC32 motherboard kit, which is an offline engraving master control kit developed for desktop engraving machines. The hardware is equipped with a 32-bit high-speed ESP32 module, integrated WIFI...
If you've been keeping up with the nightly builds, the only major change since the last one is a reworking of the peer connection mechanism that better packs together the whole simultaneous direct/indirect connection business in a way that's a lot less likely to default on you as you exchange peer messages and/or transfer files with other clients. A full changelog of everything new since Public Build 3 is available further below. And, oh yes, Linux! Many caveats with that one. First of all, it's 32-bit. I haven't had much luck getting it to work in a 64-bit Linux virtual machine. And unfortunately getting a 64-bit version to compile appears to be a little less simple than running the codebase through a 64-bit toolchain, so for now it'll have to wait. You'll need the latest Qt libraries installed. I tried with just the Debian Qt4 packages and it wasn't enough. The easiest, most sure-fire way of getting the right ones is via the Qt SDK online installer (link below). You can choose a custom installation and de-select everything except Qt Creator (which can't be de-selected). The executable, also linked to below, can be run from anywhere once you've set the right permissions (chmod u+x). You'll notice some of the labels and buttons have their text cut short, and some of the columns not quite accommodating their content without resizing.. The default Qt font is bigger in Linux than it is in Windows, which will be addressed in future releases. I've also noticed upload speed limiting doesn't work anywhere as accurately in Linux. Not sure if it's something to do with the fact I was testing it in a virtual machine. Further investigation is requisite.
3a8082e126