Messages

381

Mach4 Plugins / Re: Galil plugin compatibility

« on: December 29, 2019, 03:47:03 PM »

The Galil plugin works with the DMC41x3 and DMC40x0 controllers.  Basically, the new Ethernet controllers.  And the RIOs for additional I/O if needed.  The older Ethernet controllers are not supported, including any PCI or ISA bus controllers.  These older controllers will never be supported. 

Steve

382

Mach4 General Discussion / Re: msvcp140.dll missing

« on: December 29, 2019, 03:00:40 PM »

A google search on "msvcp140.dll" yielded this:
https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/msvcp140dll-is-missing-in-my-win-10/1c65d6b0-68b8-4b59-b720-3e6a33038389

Just copying DLLs from one location to another is not a safe thing to do on Windows.  In your case, the msvcp140.dll file that goes in SysWOW64 is actually a 32 bit version of that DLL and you copied a 64 bit version in there.

Install the 2015 redistributable package as Administrator. 

Steve

383

Mach4 General Discussion / Re: Need the mcTHC.lua file

« on: December 29, 2019, 02:49:59 PM »

I would instead describe the problem and see if the forum members could come up with a solution.  That file is compiled and not editable for a reason. 

Steve

384

Mach4 General Discussion / Re: cant write to registry by Api C#

« on: December 28, 2019, 06:48:54 PM »

Still your function signature is wrong for returning a value in the third parameter.  It is a passed pointer.

Code: [Select]

[DllImport("Mach4Core.dll", CallingConvention = CallingConvention.StdCall)]
[return: MarshalAs(UnmanagedType.I4)]
public static extern int mcRegGetHandle(
[param: MarshalAs(UnmanagedType.I4)]  int mInst,
[param: MarshalAs(UnmanagedType.LPStr)]  string path,
[param: MarshalAs(UnmanagedType.U4), In(), Out()] ref uint hReg);

Steve

385

Mach4 General Discussion / Re: port error

« on: December 27, 2019, 03:51:07 PM »

As administrator, run:

netstat -a -b -n

That will tell you which program has port 50003 open.  Then you can kill the offending program in the task manager and re-start Mach. 

Some programs use random ports when they startup and that will then cause a port conflict if they start up on a port that Mach uses.  The chances are that when restarting the PC, that program (whatever it may be) will not again use the same port range.

The real fix is to remove other programs that are not needed for a machine controller. 

However, If you have to have a program that uses these port ranges, you can change the starting port that Mach uses by adding

BaseIpcPort=<some other starting port number>

to the Preferences section of the Machine.ini file in the profile's directory. 

e.g.

[Preferences]
BaseIpcPort=45000

Steve

386

Mach4 General Discussion / Re: Moving off home switch during RefAllHome ? (Mach4)

« on: December 27, 2019, 03:21:15 PM »

G0 G53 X10 Y10 needs to be in quotes. 

Code: [Select]

mc.mcCntlGcodeExecute(inst, "G0 G53 X10 Y10")

Sometimes things don't get pasted properly from the code editor to the forum post. 

Steve

387

Mach4 General Discussion / Re: cant write to registry by Api C#

« on: December 27, 2019, 03:16:17 PM »

The function signature is incorrect.  Where it your variable to receive the register handle? 

Here is the C definition.

MACHAPI int MACH_APIENTRY mcRegGetHandle(MINSTANCE mInst, const char *path, HMCREG *hReg);

Steve

388

Mach4 General Discussion / Re: Mach 4 Feature Request

« on: December 11, 2019, 04:40:15 PM »

I am sorry, that is not how the interface works.    We use wxWidgets underneath and that dictates how things like this are done. 

Steve

389

Mach4 General Discussion / Re: Capping Z minimum message

« on: December 11, 2019, 04:28:47 PM »

Most of the time, unless the motion controller plugin is specifically using a new API function call, a newer version of the plugin will work with an older version of Mach.  Just testing it out will proved whether is works or not.  But as far as dead nuts comparability is concerned, you are correct to use the the Mach version (or newer) that the plugin was compiled against.

Steve

390

Mach4 General Discussion / Re: Capping Z minimum message

« on: December 11, 2019, 02:25:12 PM »

It means that you are running a development version of Mach.    With Mach shut down, find the parameters.ini file and edit it.  Set the value of 1801 to something way below your Z axis' minimum.  Say something like -100 inches or -2500 mm.  Or set it to NIL or delete the entry from the file all together. 

Steve