Machsupport Forum
Mach Discussion => Mach4 General Discussion => Topic started by: KatzYaakov on January 30, 2020, 03:09:48 AM
-
hi
i have very strange behavior on new machine that i never mat on mach system
when we turn on mach we make homing ,then when we try move by jog or run any program all movement very very slow
we need turn off mach restart then its back as normal
but before we try turn on again mach there already one instance of mach that already run ,and we must go in task manager and close it
sure when we close mach we close it as must with confirm not only turn off pc
is anyone have like this?
-
Hi,
yes I have had instances where I have accidentally caused a fault with Mach that requires I shut it down. While some
parts of Mach do shut down, other parts do not, and thereafter it necessary to use Task Manager to shut it down.
The issue is what is causing Mach to fail/run slow in the first place? If you prevent that from happening then the restart
problem ever arises.
My understanding is that if a fault occurs in Machs core, something like an infinite loop, then the GUI will shut down but not
the core.
Craig
-
thanks craig
but do you have ide why its happened?or how solve
its only in 1 or 2 machines happened not all
and the pc is dell new i3 ssd windows 10 64 bit , not some cheap pc
-
Hi,
the only common theme that ties those occasions together was that I was scripting Lua code, I guessed that I had caused a compilation
fault from which the compiler could not extract itself.
I have been using Mach a lot lately but have not be writing any code and no faults.
Craig
-
about speed that it run very very slow do you have any ide?
-
i dont think its lua problem ,because after that problem happened ,restart the computer solve it ,so if lua ....
-
Hi,
about speed that it run very very slow do you have any ide?
No, sorry I don't.
i dont think its lua problem ,because after that problem happened ,restart the computer solve it ,so if lua ....
I think you are correct, a Lua coding fault would be persistent. None the less you have a fault that is hanging up
Machs core (my guess). There is to my knowledge no way to monitor Machs core ad/or selectively kill processes.
Craig
-
and because the second instance its run very slow?
-
Hi,
and because the second instance its run very slow?
To my knowledge Mach WILL NOT OPEN if there is ALREADY a current instance running.
Craig
-
thanks craig
is there some one from mach here can explain why this happened and how should solve?
-
This single instance checking is done in the GUI. To Craig's point, this is what tries to prevent multiple Mach programs running.
When the Mach4GUI.exe program is executed, it loads the Mach4Core.dll file. Mach4Core.dll then loads the plugins. If something is hanging the core (most likely a motion plugin) after Mach4GUI is closed, then it is possible that the GUI shuts down and the cores remains running in the background. In this scenario, it is possible to re-launch Mach4GUI.exe and startup another GUI, core, and a set of plugins. Because the original instance of Mach4GUI is not running, but the core still is!
Now, this is not a good thing at all, obviously. It is why we don't allow two Mach programs running at the same time. My GUESS at this point, because I have no information about what Mach build you are running or what motion controller you are using (things you should really mention when you are having problems), is that is what happened. Two motion plugins fighting over the same motion hardware is probably going to affect performance at the very least!
Steve
-
thanks steve
we use pokeys
tomorrow ill go there and try reinstall all pokeys st up and plug in with the last version hope its will fix that
thanks