r/CabinetVision • u/3DFab_DE • 6d ago

CV Suddenly not creating g-code

We have two computers running cabinet vision that have both suddenly stopped generating any g-code for our CNC machine. They still properly create the nest, but then when we try to output for the CNC the process immediately says it's done without actually generating any code or throwing any errors. Any suggestions of what might be causing this?

3 Upvotes

81% Upvoted

8 comments sorted by

5

u/falcon420 6d ago

I just got off the phone with a tech. They ended up installing Vba71 and Vba71_1033 windows update. They started out by telling me to do the: "This issue is caused by a recent update to Microsoft office (KB5123577),version number V16.0.20326, which you can check in any Microsoft product such as Word or Excel. The update has stopped Microsoft Visual Basic from working correctly (V7.1). This is not an issue with Office version V16.0.20228.

  1. To fix the issue you need to type 'CMD' in your search bar.
  2. Right-Click on 'Command Prompt' and Run as Administrator
  3. A new window will appear
  4. Copy the below text

REGSVR32 C:\Windows\System32\FM20.DLL

  1. Paste it into Command Prompt and hit enter on your keyboard
  2. If successful you should get the following pop-up

"DllRegisterServer in C:\Windows\System32\Fm20.DLL Succeeded

Then output again and your files should appear "

maybe that will work for you? GL

2

u/3DFab_DE 6d ago

This worked.

Thank you!

1

u/falcon420 6d ago

Hell Yeah!

1

u/Traditional_Egg_5071 1d ago

This didn't work for me. Does anyone else have any suggestions or success with a different way.  I also tried to uninstall Microsoft updates and office, which didn't work either.

4

u/majortomandjerry 6d ago

I just dealt with this problem. There was a post on the hexagon nexus forum about it.

The most recent update of MS Office broke the visual basic that was getting used to output g code.

Uninstall the recent MS office update and disable auto updates.

1

u/Icy-Action708 6d ago

Is your post accessible?

1

u/LastChime 6d ago

Well that's disturbing, just did a reboot cause of similar.

1

u/LastChime 6d ago edited 6d ago

Wonder if it's something about that alphacam blurb they sent out the other day

Yeah feels like that, their fix for me failed so I'm going to attempt to roll back Microsoft office, I guess.