Just got the Pro all set up and tried playing around with the jog functions. It would take a couple of seconds to respond to the X/Y forward and back arrows but when it did it made erratic stops and starts. I was running 21.1.5 and I remembered reading in the forum that version could be dodgy. I deleted it and tried loading the older 20.6 version. It seemed to download OK, went thru the setup wizard, but it won’t come up on the screen. The Langmuir logo appears for about 5 seconds or so then disappears.
So I deleted that and tried re-installing the 21.1.5, run thru the wizard etc, and the compatibility layer etc ,but that won’t come on screen either.
Tried loading and deleting 2 or 3 times but nothing seems to work anymore.
Anybody have any ideas, I’m getting callouses on my fingers.
First off, what type of computer are you using (laptop, PC, Mini PC)
What Operating System (Win NT, 7, 8, 10, 11, Evil Apple)
Second, if you are trying different generations of Fire Control, you need to run the uninstall program from settings, then after that is done, find the parent folder for Fire Control (usually in C/Program Files) and manually delete it before you do another install.
Did you happen to reboot windows between installs? Windows can be dodgy when uninstalling external device controlling software and not removing allocated addresses before trying to install another program on top of the uninstalled one.
Thanks for the responses guys, I got 21.1.5 back in last night. For some reason (old?) I was thinking of the compatibility programme as an extension and not a stand alone programme. I was trying to install one into the other! I still can’t get 20.6 to come on screen though. The Fire Control logo shows up, as well as a pop up in the task bar saying “please wait”, then about 5 seconds later they both vanish with nothing else happening.
Going back out to the shop now to see if the erratic behavior still exists.
Oh, I’m running a Thinkpad with Windows 11 Pro.
Follow the Uninstall / Reinstall instructions I stated above.
Hi Sticks,
Yea, that’s how I was installing and uninstalling the programmes. I discovered something new this morning though. When I double clicked the desktop shortcut the same type of thing happened. Not being a very patient person I multi clicked on the logo that came up on screen untill firecontrol launched. Therein lay the problem as nothing ran right. So I cleared everything, double clicked the shortcut, held my temper and waited. After 5 seconds the logo vanished as before, and about 40 seconds more Firecontrol launched and seemed to run just fine!
I never expected it to take that long to launch, I figured something was amiss. Anyway it seems OK now. Thanks for all your help.
Having a second instance of FireControl running in the background, I have done that. This is why I stopped using the touch screen. The mouse works better for me. Plus, I got sick of Sterling Cool dripping down the screen when you have to push the annoying pop-up
“The program is complete.” Damn, I know it’s complete; I have the freaking part in my hand.
How dodgy is the 21 version, should I use the 20? I notice there is a 24 version out now.
I’ve been using 24.1 for several months. No issues at all.
No, its windows 11 on a thinkpad.
Laptops are not ideal, in my opinion. Most new laptops have PowerSaver chips that try to control the power used by the USB port. Langmuir’s control board is partially powered by the 5 volts from the computer’s USB port. It may work great till it doesn’t.
Yea, I went through the device manager and disabled the “allow comp to shut off usb’s” last night thinking that was part of my problem. Hopefully that gremlin is put to bed.
Good start.
I’ve always disliked the “job done” pop up window that makes you click something before being able to take control of the torch and jog it.
Would be super cool to have a post script that will auto jog the torch to z=“work clear” and then home it to move it outta the way.
7 posts were split to a new topic: Dumb Stuff we have to deal with
Don’t know if this should be a new thread or not, but it is startup headaches so here goes.
Trying to insert a simple programme ( a maple leaf ) into FC but I get an error message saying
error @ line 79 M62P4 thc allowed AD2.
It dawned on me that I dont have the thc module yet, so I ran it thru Sheetcam again this time de-selecting the thc allowed option at the bottom and tried again. This time I got the error
error @ line 79 M63P4 thc inhibited AD2.
So I ran it thru Sheetcam once again this time selecting “none” to see what that would do; same error message as at first.
The g code won’t come up on the screen for me to look at either.
Anybody have any ideas as to what’s going on?
Hey Tin, you’re crediting me with more savvy than I possess; can you spell it out for me?
What post processor are you using?
Those are not Firecontrol THC commands. The error is coming from unknown commands in the code.
YouTube videos can be good for learning the basics of Sheetcam, but ignore anything about adding THC commands or code snippets. They will mostly be unknown commands in Firecontrol.
You should be using the Firecontrol v1.6 post processor in Sheetcam. I can post a short video of how to select the post processor, if you need it
According to the machine options box in sheetcam , I am using the v1.6 (Edited) and I set the cut and pierce heights to 0 in the jet tool box but I still get the same error showing up.