motor35 and disable with probe action

[Chuckb67@live.com]

I am have been having a heck of a time with my system disabling itself after:
- any probe action via the Probing tab or the TouchOff
- anytime I jog to a location then press Work Zero button
- anytime I jog to a location and enter a MIDI command G00 G90 GX0 (for example)

The Log facility is consistent with output in all of these situations and shows a Requesting a stopped report for motor35.
Following this is what appears to be a report from my 4 motors but not one from motor35.
What is motor35? I don't have one but there is one in the ini file that is enabled. Disabling motor35 has no effect.
At this point my Enable button still shows enabled but my jog keys are all dim and the machine can't be moved until I press the enable key twice.
I have opened a ticket with Artsoft but have not heard anything yet.

I completely rebuilt my setup and reinstalled PMDX and Mach4 then reconfigured the motors and the switches.

Here is a sample of the Log report: (Mach4)(jogged out on X and Y and Z away from my work zero position.  Then pressed the Work Zero button)

2018-01-07 13:49:45.399 - API: mcCntlMdiExecute(inst = 0, commands = 'G00 G90
G00 G53 Z0
G00 X0 Y0
G00 Z0') (Mach4GUI LUA script)
2018-01-07 13:49:45.500 - Attempt transition from "Idle" on event "MDI Start" Controller.cpp:1875
2018-01-07 13:49:45.500 - S_IDLE_on_exit
2018-01-07 13:49:45.500 - ACTION_start_mdi
2018-01-07 13:49:45.501 - S_MDI_RUNNING_on_entry
2018-01-07 13:49:45.501 - S_MDI_RUNNING2_on_entry
2018-01-07 13:49:45.501 - Signal id 1114, (Gcode Running), changed from LOW to HIGH.
2018-01-07 13:49:45.503 - Waiting on SetStill...
2018-01-07 13:49:47.085 - Controller::RunCanonBuffer called AddStopReportRequest() RunCanon.cpp:85
2018-01-07 13:49:47.085 - Requesting a stopped report for axis 0 motors.
2018-01-07 13:49:47.085 - Requesting a stopped report for motor 0.
2018-01-07 13:49:47.085 - Requesting a stopped report for axis 1 motors.
2018-01-07 13:49:47.085 - Requesting a stopped report for motor 1.
2018-01-07 13:49:47.085 - Requesting a stopped report for motor 3.
2018-01-07 13:49:47.085 - Requesting a stopped report for axis 2 motors.
2018-01-07 13:49:47.085 - Requesting a stopped report for motor 2.
2018-01-07 13:49:47.085 - Requesting a stopped report for axis 3 motors.
2018-01-07 13:49:47.085 - Requesting a stopped report for motor 35.
2018-01-07 13:49:47.108 - API: mcMotionSetStill(inst = 0, motor = 2) (unknown caller)
2018-01-07 13:49:47.332 - API: mcMotionSetStill(inst = 0, motor = 0) (unknown caller)
2018-01-07 13:49:47.332 - API: mcMotionSetStill(inst = 0, motor = 1) (unknown caller)
2018-01-07 13:49:47.332 - API: mcMotionSetStill(inst = 0, motor = 3) (unknown caller)

I really don't know if this is a Mach4 or PMDX issue.
I have a PMDX 416 and Mach4 build 3481

Appreciate any help with this issue.
Chuck

[12strings]

Need more information.  What version of the PMDX plug-in are you running?  See item (3) here:

http://faq.pmdx.com/content/6/4/en/how-to-report-a-problem-what-to-tell-us.html

Posting a snippet of the Mach4 diagnostic log windows is helpful.  What is happening is that after the move, Mach4 requests that the PMDX plug-in tell it when the motors have actually stopped moving.  The PMDX SmartBOB responds saying motors 2, 0, 1 and 3 have stopped.  The SmarBOB knows nothing about motor35, so it cannot report that it has stopped.  So Mach4 is sitting there waiting for someone to tell it that motor35 has stopped.  That never happens, so Mach4 never finishes the move.  And most of the screen buttons remain grayed out, as you've seen.

But you say disabling motor35 has no effect?  That I cannot explain. 

If you are not running PMDX plug-in version 0.52.254, then you should install this version.  See this forums post:

https://www.pmdx.com/PMDX-Forums/index.php?topic=455.0

The post is long but please PLEASE read the entire post.  There is important information near the end.  You will need to re-create your profile from scratch.  Yeah, that can be a pain, but necessary.  You can write down the motor tuning parameters, axis configuration, homing parameters, etc.  And as long as the values look OK and the current (possibly corrupted) profile moves the motors as expected (correct distance and direction), then enter them in the new profile.

If the problem continues, post again.  You will most likely need to capture a SmartBOB debug log and post it.

http://faq.pmdx.com/content/2/3/en/how-to-capture-a-debug-log-file-and-send-to-pmdx.html

[12strings]

Regarding motor35 and for other people's reference on these forums, see this post on the Mac4 support forums:

https://www.machsupport.com/forum/index.php/topic,36260.msg248317.html#msg248317

It explains what motor35 is used for.  It seems that if you have an axis enabled but no motors assigned to it, Mach4 assigns one of motor32 or higher to that axis.