@Bill_A @bobdobqb The compatibility version installer had a configuration issue. It has now been updated. Please give it another try and thank you for your patience!
1 Like
Loaded up fine and visualizer seems to be working great. Iāll let you know if I run into any further issues. Thanks a bunch folks!
just downloaded 21.1 and so far everything seems good. only thing I have a question on, which has been on all the firecontrol versions, is there anyway to change our āzero axis locationā if we rotate a program in FC 90 degrees? Maybe its not possible to do, but it would be nice if we were able to rotate a part, zero the axis and it zero in the bottom left corner like it typically does if you load the program without rotating it.
Use the āset program originā function. Click on the green box in the corner that you want the origin.
3 Likes
Ahhh perfect! I will give that a try. Thank you!
Installed and it works perfect until you close the program and re-open, it starts responding very slow. Uninstalling and reinstalling returns it to normal until you try to close it and open it again. Restarting does not help, neither does deleting the user/.FireControl folder. Love it when it works though!
@langmuirsystems I ran some jobs today with 21.1 and everything seems to be working fine. Iād say thatās pretty darn good considering some of the beta tests Iāve been involved with in the past. 
3 Likes
I downloaded the software today and ran a few cuts. Did some straight cuts with no issues and cut out a 10x10 with no issues. So far, it works.
This is very unfortunate, as for more than 1 year comments on this board from Langmuir accounts have at various times indicated that integrating the Hypertherm arc established signal was something you were working on for PRO. At least one comment even that it would be āvery easyā.
It has been a request from several users since you launch the pro, why the change of heart?
1 Like
I have been having intermittent issues with fire control freezing up in the middle of a cut. I am not 100% sure it if this issue is from 21.1 or something else but I never had this issue with the old fire control. This seems to happen at least every 800-1000 pierces but occasionally will freeze after 30-40 pierces. When this happens everything stops moving, and fire control becomes unresponsive, but the torch remains lit. I have to either unplug the usb to the computer, or kill power to the control box to kill the arc. then i have to use task manager to close fire control and reopen it. when it reopens, the x-y is now lost and the torch fire/timer is reset to whatever it read before the session that froze up. I have sent the email reports to LS numerous times, but i donāt know if the error reports are for the freezeup, or for unplugging the usb.
Iāve had one issue with it and it was in the patterns function. I imported my program and then hit the pattern function. I gave it my material parameters then hit go ans violaā the gcode for 48 parts came up. Up to this point it was fabulous. It started cutting and it cut all 48 parts but on the last three parts before the final part it left out features on the part. I j6st didnt program the cuts. I guess itās just a bug but I thought you should know.
Iām having intermittent issues with tab key not toggling the jog mode. This is in 21.1.1-compatibility version.
@Wingnut180 - What you are describing seems like a noise issue. Did anything else change in your setup around this time? This is unlikely related to the new FireControl. Freezing of the application will not save XY position or torch pierce/time counting. Is the popup allowing you to send the crash to crashes@langmuirsystems.com? When does this popup occur? Are you still getting these crash reports in 21.1?
@rpswim - Could you send us the file you were patterning? Were you able to dig into the visualizer and see that these features had no cut lines?
@MrHaNkBoT - The Tab hotkey to toggle jog mode will only work if your context is the application window. If you clicked the visualizer or another application window last, it will not work. If you are finding it not working, click somewhere in the application window (not the visualizer) like the Jog Mode buttons and you should get it back!
It didnt freeze, It kept cutting but it simple didnt have the Gcode there to cut the feature in the part. It didnāt program the feature. I donāt know why it just didnāt.
Yes, Iām familiar with how keyboard shortcuts work. The tab key doesnāt always work to toggle the jog mode. Even when no other applications are open, even when the other shortcuts do work (like the arrow keys for movement). I would not have said anything unless I was certain. Iāll be happy to take a video of it if needed.
Having an issue with the latest version of FireControl 21.1.2 Beta Release. After loading program the Visualizer is blank.
If I load the Compatibility version for old graphics cards the Visualizer works.
Here are the specs for my display card:
| Name | Microsoft Basic Display Adapter |
|---|---|
| PNP Device ID | PCI\VEN_8086&DEV_5916&SUBSYS_14C01043&REV_02\3&11583659&0&10 |
| Adapter Type | , (Standard display types) compatible |
| Adapter Description | Microsoft Basic Display Adapter |
| Adapter RAM | 0 bytes |
| Installed Drivers | Not Available |
| Driver Version | 10.0.19041.868 |
| INF File | display.inf (MSBDA section) |
| Color Planes | Not Available |
| Color Table Entries | 4294967296 |
| Resolution | 1920 x 1080 x 1 hertz |
| Bits/Pixel | 32 |
| Memory Address | 0xEB000000-0xEBFFFFFF |
| Memory Address | 0x80000000-0x8FFFFFFF |
| I/O Port | 0x0000F000-0x0000F03F |
| Driver | C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\BASICDISPLAY.INF_AMD64_65AB9A260DBF7467\BASICDISPLAY.SYS (10.0.19041.868, 67.00 KB (68,608 bytes), 4/9/2021 8:47 AM) |
| Name | NVIDIA GeForce 940MX |
| PNP Device ID | PCI\VEN_10DE&DEV_179C&SUBSYS_128E1043&REV_A2\4&319F5B&0&00E0 |
| Adapter Type | GeForce 940MX, NVIDIA compatible |
| Adapter Description | NVIDIA GeForce 940MX |
| Adapter RAM | (2,147,483,648) bytes |
| Installed Drivers | C:\Windows\System32\DriverStore\FileRepository\nvam.inf_amd64_1aae4f19e68d0780\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvam.inf_amd64_1aae4f19e68d0780\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvam.inf_amd64_1aae4f19e68d0780\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvam.inf_amd64_1aae4f19e68d0780\nvldumdx.dll |
| Driver Version | 23.21.13.8857 |
| INF File | oem3.inf (Section148 section) |
| Color Planes | Not Available |
| Color Table Entries | Not Available |
| Resolution | Not Available |
| Bits/Pixel | Not Available |
| Memory Address | 0xEC000000-0xECFFFFFF |
| Memory Address | 0xC0000000-0xCFFFFFFF |
| Memory Address | 0xD0000000-0xD1FFFFFF |
| IRQ Channel | IRQ 4294967293 |
| Driver | C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVAM.INF_AMD64_1AAE4F19E68D0780\NVLDDMKM.SYS (23.21.13.8857, 16.22 MB (17,003,280 bytes), 6/11/2021 11:11 AM) |
@MrHaNkBoT - Sorry! Not trying to make any assumptions. I will have our team go through that feature and try to reproduce it.
Strange that your relatively new card isnāt working but not a bug per se. It seems like the compatibility version is working properly. There is one particular function that a critical library uses in the non-compatibility version that it is likely not working with. You may want to try this with your 940MX:
1 Like
I read the link for My Nvidia GeForce 940MX and I have absolutely no idea what I read. Itās all Greek to me. āgo to PC graphics configuration and force renderingā ?
if thereās an Invidia Icon in the taskbar right corner, right click on it and go to options or configuration and you should get a list of other options.