Messages

1

Mach4 General Discussion / Re: Cannot use G53 incremental

« on: January 02, 2018, 03:08:56 PM »

I think the problem arises when the Set to Work Zero script trys to use G53 while in incremental mode. For now I am going to leave the modified line in that script and flip to G90 before executing the G53.
When I have a little time I will modify the script to check for the current mode and if it is G91 switch it to G90 then switch back to G91 at the end.
Chuck

2

Mach4 General Discussion / Re: What is the purpose of Motor35 in the ini fie?

« on: January 02, 2018, 03:04:09 PM »

Craig, All
I am thinking that disabling all of these motors probably won't hurt.
It is very curious that somehow motor35 comes up in some of the messages in the message log.
Thanks
Chuck

3

Mach4 General Discussion / Cannot use G53 incremental

« on: December 31, 2017, 02:54:02 PM »

If I try to use the GO TO WORK ZERO button after performing the Touchoff for the Z axis I got an error "Cannot use G53 incremental".
By reading other posts I learned that I would need to change from G91 to G90 before it would work.

In my logic, if I prefaced the GO TO WORK ZERO button code so that it first issued a G90 it would work. And it does.

So... my code line is like this.....    mc.mcCntlMdiExecute(inst, "G00 G90\nG00 G53 Z0\nG00 X0 Y0\nG00 Z0")--With Z moves

Are there any negatives to doing it this way? Should I setup a routine for the button to see if I am in G91 then do the switch to G90 and switch back after I have moved to the work offset?

Thanks

4

Mach4 General Discussion / What is the purpose of Motor35 in the ini fie?

« on: December 30, 2017, 11:52:48 AM »

There are several motors near the end of the ini profile that are all enabled, including motor35. When I am logging diagnostic data I  see messages about motor35 along with messages for my  X, Y, and Z motors?

Should these motors be enabled?
What is the purpose of these motors?

Thanks

5

Mach4 General Discussion / Re: Jogging and DRO errors

« on: December 29, 2017, 05:40:35 PM »

My X and Y are set to 1/8 and my Z is set to 1/4. MY X and Y are on a belt and my Z is on a screw.

What is the message "Attempt transition from "Jogging" on event "Stop Jog" Controller.cpp:1379" indicate? Where can I find a listing of all the error messages?

The actual error is extremely small considering what I use my machine for so it probably doesn't matter but it is curious.

6

Mach4 General Discussion / Re: Jogging and DRO errors

« on: December 29, 2017, 04:48:51 PM »

Forgot to mention I have Mach 4 build 3481 and latest PMDX software.

7

Mach4 General Discussion / Jogging and DRO errors

« on: December 29, 2017, 04:41:05 PM »

With machine homed and zeroed if I use jog in either X or Y direction the DRO indicates that the move is longer than the Jogging increment.
    If the increment is 1.00 the DRO shows 1.0002
    If the increment is 0.1 the DRO shows  0.1003
    If the increment is 0.0100 the DRO shows 0.0103
    If the increment is 0.0010 (or smaller) the DRO doesn't change and the X or Y axis does not move.
    In all cases if I jog back in the negative direction the DRO goes exactly the correct amount.

    The Z axis does not have this error

The diagnostic screen does not show the error because it only shows 3 places to the right of the decimal point.
In the jogging configuration jogging is shown to support from 1.0 to 0.0001


    If I activate the diagnostic log I can see each of the jog increment change requests.
2017-12-29 13:33:28.832 - API: mcJogSetInc(inst = 0, axis = 0, inc = 0.1000) (Mach4GUI)
2017-12-29 13:33:28.833 - API: mcJogSetInc(inst = 0, axis = 1, inc = 0.1000) (Mach4GUI)
2017-12-29 13:33:28.833 - API: mcJogSetInc(inst = 0, axis = 2, inc = 0.1000) (Mach4GUI)
2017-12-29 13:33:28.833 - API: mcJogSetInc(inst = 0, axis = 3, inc = 0.1000) (Mach4GUI)
2017-12-29 13:33:28.833 - API: mcJogSetInc(inst = 0, axis = 4, inc = 0.1000) (Mach4GUI)
2017-12-29 13:33:28.833 - API: mcJogSetInc(inst = 0, axis = 5, inc = 0.1000) (Mach4GUI)
2017-12-29 13:33:30.409 - API: mcJogSetInc(inst = 0, axis = 0, inc = 0.0100) (Mach4GUI)
2017-12-29 13:33:30.410 - API: mcJogSetInc(inst = 0, axis = 1, inc = 0.0100) (Mach4GUI)
2017-12-29 13:33:30.410 - API: mcJogSetInc(inst = 0, axis = 2, inc = 0.0100) (Mach4GUI)
2017-12-29 13:33:30.410 - API: mcJogSetInc(inst = 0, axis = 3, inc = 0.0100) (Mach4GUI)
2017-12-29 13:33:30.410 - API: mcJogSetInc(inst = 0, axis = 4, inc = 0.0100) (Mach4GUI)
2017-12-29 13:33:30.410 - API: mcJogSetInc(inst = 0, axis = 5, inc = 0.0100) (Mach4GUI)
2017-12-29 13:33:31.465 - API: mcJogSetInc(inst = 0, axis = 0, inc = 0.0010) (Mach4GUI)
2017-12-29 13:33:31.465 - API: mcJogSetInc(inst = 0, axis = 1, inc = 0.0010) (Mach4GUI)
2017-12-29 13:33:31.465 - API: mcJogSetInc(inst = 0, axis = 2, inc = 0.0010) (Mach4GUI)
2017-12-29 13:33:31.465 - API: mcJogSetInc(inst = 0, axis = 3, inc = 0.0010) (Mach4GUI)
2017-12-29 13:33:31.465 - API: mcJogSetInc(inst = 0, axis = 4, inc = 0.0010) (Mach4GUI)
2017-12-29 13:33:31.466 - API: mcJogSetInc(inst = 0, axis = 5, inc = 0.0010) (Mach4GUI)
2017-12-29 13:33:33.059 - API: mcJogSetInc(inst = 0, axis = 0, inc = 0.0001) (Mach4GUI)
2017-12-29 13:33:33.060 - API: mcJogSetInc(inst = 0, axis = 1, inc = 0.0001) (Mach4GUI)
2017-12-29 13:33:33.060 - API: mcJogSetInc(inst = 0, axis = 2, inc = 0.0001) (Mach4GUI)
2017-12-29 13:33:33.060 - API: mcJogSetInc(inst = 0, axis = 3, inc = 0.0001) (Mach4GUI)
2017-12-29 13:33:33.060 - API: mcJogSetInc(inst = 0, axis = 4, inc = 0.0001) (Mach4GUI)
2017-12-29 13:33:33.061 - API: mcJogSetInc(inst = 0, axis = 5, inc = 0.0001) (Mach4GUI)

If I attempt to jog when the increment is lower than 0.001 I get this:

2017-12-29 13:35:10.582 - API: mcJogSetInc(inst = 0, axis = 0, inc = 0.1000) (Mach4GUI)
2017-12-29 13:35:10.582 - API: mcJogSetInc(inst = 0, axis = 1, inc = 0.1000) (Mach4GUI)
2017-12-29 13:35:10.583 - API: mcJogSetInc(inst = 0, axis = 2, inc = 0.1000) (Mach4GUI)
2017-12-29 13:35:10.583 - API: mcJogSetInc(inst = 0, axis = 3, inc = 0.1000) (Mach4GUI)
2017-12-29 13:35:10.583 - API: mcJogSetInc(inst = 0, axis = 4, inc = 0.1000) (Mach4GUI)
2017-12-29 13:35:10.583 - API: mcJogSetInc(inst = 0, axis = 5, inc = 0.1000) (Mach4GUI)
2017-12-29 13:35:12.054 - API: mcJogSetInc(inst = 0, axis = 0, inc = 0.0100) (Mach4GUI)
2017-12-29 13:35:12.054 - API: mcJogSetInc(inst = 0, axis = 1, inc = 0.0100) (Mach4GUI)
2017-12-29 13:35:12.054 - API: mcJogSetInc(inst = 0, axis = 2, inc = 0.0100) (Mach4GUI)
2017-12-29 13:35:12.054 - API: mcJogSetInc(inst = 0, axis = 3, inc = 0.0100) (Mach4GUI)
2017-12-29 13:35:12.054 - API: mcJogSetInc(inst = 0, axis = 4, inc = 0.0100) (Mach4GUI)
2017-12-29 13:35:12.054 - API: mcJogSetInc(inst = 0, axis = 5, inc = 0.0100) (Mach4GUI)
2017-12-29 13:35:15.342 - API: mcJogSetInc(inst = 0, axis = 0, inc = 0.0010) (Mach4GUI)
2017-12-29 13:35:15.343 - API: mcJogSetInc(inst = 0, axis = 1, inc = 0.0010) (Mach4GUI)
2017-12-29 13:35:15.343 - API: mcJogSetInc(inst = 0, axis = 2, inc = 0.0010) (Mach4GUI)
2017-12-29 13:35:15.343 - API: mcJogSetInc(inst = 0, axis = 3, inc = 0.0010) (Mach4GUI)
2017-12-29 13:35:15.343 - API: mcJogSetInc(inst = 0, axis = 4, inc = 0.0010) (Mach4GUI)
2017-12-29 13:35:15.343 - API: mcJogSetInc(inst = 0, axis = 5, inc = 0.0010) (Mach4GUI)
2017-12-29 13:35:19.824 - API: mcJogIncStart(inst = 0, axis = 0, inc = 0.0010) (Mach4GUI Button)
2017-12-29 13:35:19.824 - Attempt transition from "Idle" on event "Jog" Axis.cpp:564
2017-12-29 13:35:19.824 - Signal id 1127, (Jog Enabled), changed from HIGH to LOW.
2017-12-29 13:35:19.824 - S_IDLE_on_exit
2017-12-29 13:35:19.824 - ACTION_start_jogging
2017-12-29 13:35:19.824 - S_JOGGING_on_entry
2017-12-29 13:35:19.831 - Attempt transition from "Jogging" on event "Stop Jog" Controller.cpp:1379
2017-12-29 13:35:19.832 - S_JOGGING_on_exit
2017-12-29 13:35:19.832 - S_FILE_RUNNING_stop_jogging
2017-12-29 13:35:19.832 - S_IDLE_on_entry
2017-12-29 13:35:19.832 - Signal id 1127, (Jog Enabled), changed from LOW to HIGH.

I can't figure out what is going on here.  I have a PMDX 416 controller, Windows 10

Thanks