Alphacam add-in problems: tab missing, macro failing, license errors

Most add-in problems are solved in five minutes; the hard part is knowing which step you are stuck on. This list gives the cases we see most in support requests, by frequency. GMacros add-ins are the example; the first two sections apply to any .arb add-in.

1. Add-in installed but the tab/button is missing

1. Was Alphacam restarted? The Startup folder is read only at start-up. After installation Alphacam must be fully closed and reopened (including any window left on the taskbar).
2. Is the file in the right folder? It must be under LICOMDIR\Startup. With several Alphacam releases installed, each has its own LICOMDIR; the add-in may be in the wrong one.
3. Right module? .arb is for Router; it does not open in Mill. Check the program title for the open module.
4. Version compatibility: the oldest supported release is on the product page (GMacros: 2019 R1+). It does not load on older releases.
5. Ribbon customisation: if the ribbon was customised earlier, the new tab may stay hidden; resetting the ribbon brings it back.

2. The button exists, but the macro errors or draws wrongly

• No open drawing: macros need an active drawing. Open a new or existing drawing first.
• No selection: tools such as "Reverse Direction", "Centre Objects", "Measure Arc Length" need selected geometry; select first.
• Decimal separator: if entering 12,5 or 12.5 gives a result off by 10×, the separator you typed does not match Windows regional settings. GMacros macros accept both; in other macros follow your setting.
• Units: if the drawing is in inches, millimetre input comes out unscaled. Set the drawing unit to mm.
• Layer hidden: macros draw on KESIM, DELIK etc.; if those layers are hidden, geometry looks "not drawn". Turn visibility on in the layer list.
• Geometry far too big/small: cm typed into a mm field makes the part 10× smaller; use Zoom All.

3. "Server unreachable"

The GMacros license connects to lisans.gmacros.com over HTTPS (443); activation and the short check on each start go there. If you get this error, in order:

1. Does the computer have internet? Can the browser open https://lisans.gmacros.com (you should see a response page)?
2. Is the shop firewall/proxy blocking outbound HTTPS? Have IT allow-list the address.
3. Is the Windows clock right? If it is off by more than a few minutes, the TLS connection is refused.
4. If the machine PC is fully offline: activation is online only; give it internet briefly. There is no offline activation (why: What is an Alphacam add-in, how is it installed and how does it work?).

4. "This key is in use on another computer"

The key is already bound to a computer and was entered on a second one. Two cases: (a) the old computer failed or was reinstalled → open My licenses › Reinstall request in the panel; on approval the old key is closed and a new one e-mailed, free of charge. (b) a second machine PC → buy an additional seat; each seat is a separate key. A reinstalled computer does not count as the same machine; the hardware record changes, so a request is still needed.

5. "License expired" or "no uses left"

For time-based licenses the end date is shown in the panel; when it passes, the add-in stops and is renewed from the panel — the key stays the same, no re-activation. In usage-count packages every macro run consumes one use and the counter lives on the server; when it reaches zero, a new package is bought. If you believe a use was deducted wrongly, open a request in the panel; counter records are kept server-side and can be checked.

6. Alphacam was updated and the add-in disappeared

A new Alphacam release may install with a new LICOMDIR; add-ins in the old Startup folder are not carried over. Run the installer again; because the license is on the same computer, no key is asked. However new the release, an add-in stating "2019 R1 and later" runs on it.

Still stuck

Open a support request under Requests in the panel; three details speed up the answer: the Alphacam release (Help › About), the add-in version (GMacros › About) and the full text of the error or a screenshot. Frequent questions are on the FAQ.