Hello Guest it is March 28, 2024, 02:20:49 PM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - FocusPaul

Pages: 1 2 3 4 5 »
1
Mach4 General Discussion / Re: Probing, mcCntlGet/SetPoundVar
« on: November 26, 2019, 10:01:16 AM »
Today I encountered the problem "#4003 assigment value gets divided by 10" too (Mach4 v4310), so here's a quick workaround:

#500 = #4003   
G#500

2
The machine we watched the correct (as in "expected") behaviour had simple stepper drives. I don't understand why you insist on battery / mechanics backed-up absolute encoders.
My point is, if you use open-loop encoders, you should still see the last know position in M4 when you start it up, or at least 0, but _never_ at a random position.

3
Seen another Mach4 output device in action, which does not have the problem described above.
When you close M4, it comes up with the exact same motor positions in UI as before ... as expected.

It does not matter whether the user changed the motor positions manually while the machine was offline, but loading M4 with some random motor positions on start-up is absolutely not what I was expecting. Unfortunately that's what ESS does.

4
Mach4 General Discussion / Re: Programmatically zero axis (G code)
« on: November 13, 2017, 05:34:05 AM »
Correctly, there's a 0.3 seconds pause. Without it, the new axis position is sometimes not recognized. That's why I'm looking for smth better.

Your Lua script is probably faster than my one, but maybe there's a version without any delay. *cough-cough-Steve-cough*

5
Mach4 General Discussion / Re: Programmatically zero axis (G code)
« on: November 13, 2017, 01:54:39 AM »
Hello Craig,

thank you for the Lua script!

Is there a G code only way to do it, which is easier than the G code mentioned in my 1st post? (M code breaks the CV chain, that's why I ask.)

Paule

6
Mach4 General Discussion / Programmatically zero axis (G code)
« on: November 10, 2017, 04:20:45 AM »
Hello!

Is there a way to zero specific axis (G54) in G code?
I currently use the following piece of code, but I guess there's a better way to do it, because without the appended wait, it sometimes does not work.

Code: [Select]
G10 L2 P1 X[#5001] Y[#5002]  (#5001 and #5002 are machine coordinates for X/Y; make a local coordinate system shift)
G4 P0.3 (wait for variable to become set)

Best regards,
Paule

7
Mach4 General Discussion / Re: Mach4 build 4.2.0.3481 released
« on: September 06, 2017, 02:42:58 AM »
After some discussion with Mach4 staff: The error shown is expected to happen in some cases and will probably be removed in future versions. It does not affect Mach4 functionality.

8
Mach4 General Discussion / Re: Mach4 build 4.2.0.3481 released
« on: September 06, 2017, 01:46:46 AM »
Mach4Gui.exe is started by double-clicking (using a Norton Commander clone app), so the working directory should be the main Mach4 directory. There are no path environment definitions for M4 set.

I reduced M4 to minimum runnable version (stripped documentation, SDK, debug DLLs and various other things) and will send you a PM with the link to it.

9
Mach4 General Discussion / Re: Mach4 build 4.2.0.3481 released
« on: September 05, 2017, 08:03:19 AM »
Btw: Copying Mach4Core.Dll to the plugins sub-folder removes the log entry. But it leads to a strange empty entry in plugin configuration UI.

10
Mach4 General Discussion / Re: Mach4 build 4.2.0.3481 released
« on: September 05, 2017, 07:58:45 AM »
Hello Steve,

to answer your questions:

- Mach4 SDK v3485 (that's why it isn't located in C:\Mach4 folder)
- Windows 7 x64
- The problem happens on start-up without any other actions performed.
- The message is created as log file in plugins folder in file coreinit.log. It seems the whole logging mechanism is new, at least I haven't seen it since 2013.
- Error message, partly in German language:
(1) Das angegebene Modul wurde nicht gefunden.

: Handle in NULL! Failed to load core at 'G:\VS-Project2008\test-3485\Plugins\Mach4Core.dll'.


- Screenset is blank.set (an empty screen), but also tried it with my custom screen set before. It does not matter.
- Only files located in plugins folder is simulation plugin. It is enabled and the active output device. But it is also does not depend on whether there's a plugin or not, error remains the same.
- No wizards and/or custom macros in profile.
- Profile: fresh created profile.
- Modules folder is empty (just to make sure it's not smth related to it).

The reason for the error is obvious: Mach4Core.dll is located in main folder, not in plugins subfolder. I think smurph has to take over.

Pages: 1 2 3 4 5 »