Hello Guest it is April 19, 2024, 08:49:15 PM

Author Topic: Capping Z minimum message  (Read 1251 times)

0 Members and 1 Guest are viewing this topic.

Capping Z minimum message
« on: December 10, 2019, 03:55:58 PM »
What does mean log message:

Capping Z minimum to 0.000000.4 based on parameter 1801

I cant get working G91 G01 Z-10.0 command and see this message, Z+10.0 works

Jog and referencing works as required

Version 4300+
Re: Capping Z minimum message
« Reply #1 on: December 11, 2019, 06:33:59 AM »
I tried to disable soft limits it didn't help, so, jogging works, homing works

here is a log of G91 G01 Z-1.0 F50

2019-12-11 14:25:49.255 - Logging Enabled.
2019-12-11 14:25:50.533 - API: mcCntlMdiExecute(inst = 0, commands = 'G91 G01 Z-1.0 F50') (Mach4GUI)
2019-12-11 14:25:50.637 - Attempt transition from "Idle" on event "MDI Start" controller.cpp:2260
2019-12-11 14:25:50.637 - Signal id 1127, (Jog Enabled), changed from HIGH to LOW.
2019-12-11 14:25:50.638 - S_IDLE_on_exit
2019-12-11 14:25:50.638 - Signal id 1172, (Machine Idle), changed from HIGH to LOW.
2019-12-11 14:25:50.639 - ACTION_start_mdi
2019-12-11 14:25:50.639 - SoftSync()! Clearing planner.
2019-12-11 14:25:50.660 - S_MDI_RUNNING_on_entry
2019-12-11 14:25:50.660 - SoftSync()! Clearing planner. stateinterface.cpp:1313
2019-12-11 14:25:50.660 - S_MDI_RUNNING2_on_entry
2019-12-11 14:25:50.661 - Signal id 1114, (Gcode Running), changed from LOW to HIGH.
2019-12-11 14:25:50.679 - Capping Z minimum to 0.000000.4 based on parameter 1801
2019-12-11 14:25:50.781 - Attempt transition from "MDI Running" on event "Stop" gcodeexec.cpp:1309
2019-12-11 14:25:50.781 - S_MDI_RUNNING2_on_exit
2019-12-11 14:25:50.781 - Signal id 1114, (Gcode Running), changed from HIGH to LOW.
2019-12-11 14:25:50.781 - S_MDI_RUNNING_on_exit
2019-12-11 14:25:50.781 - ACTION_stop
2019-12-11 14:25:50.799 - S_IDLE_on_entry
2019-12-11 14:25:50.804 - Signal id 1172, (Machine Idle), changed from LOW to HIGH.

Offline smurph

*
  • *
  •  1,546 1,546
  • "That there... that's an RV."
    • View Profile
Re: Capping Z minimum message
« Reply #2 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
Re: Capping Z minimum message
« Reply #3 on: December 11, 2019, 02:34:00 PM »
okay thank you I use it because Smoothstepper is requires 4322 now and ask to install it

Offline smurph

*
  • *
  •  1,546 1,546
  • "That there... that's an RV."
    • View Profile
Re: Capping Z minimum message
« Reply #4 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