Hello Guest it is October 15, 2019, 05:54:06 AM

Author Topic: ShuttlePro V2 with ESS e-stop bug  (Read 3687 times)

0 Members and 1 Guest are viewing this topic.

ShuttlePro V2 with ESS e-stop bug
« on: November 27, 2013, 05:34:07 AM »
I've come across a bug that causes unexpected movement on reset if the hardware e-stop is triggered while the shuttle is being used to jog an axis. The steps to reproduce are as follows:

1. use wheel on shuttle to jog an axis on the machine
2. while moving the axis, trigger hardware e-stop on machine (this triggers a mach3 reset as we have the enable signal hooked up)
3. reset hardware e-stop and press the reset button in mach3. This enables the machine and it can be used as normal
4. press the reset button in mach3 again to disable
5. press the reset button in mach3 once more to re-enable. At this point the machine will resume whatever motion was happening when the hardware e-stop was originally triggered, without any input occuring from the user. I believe it also resumes at full speed.

- I have tested this same sequence both during a running program and using the keyboard to jog an axis. The problem only occurs when the estop is triggered when jogging with the shuttle
- I have tested this same sequence on another of our machines which uses the same breakout board, but uses a parallel port instead of the smoothstepper. It does not have this bug
- I'm using version 3.00 of the shuttlepro plugin found at http://www.machsupport.com/wp-content/uploads/2013/04/ShuttlePro_3.m3p
- I'm using ESS_v10h2d1a for the ESS plugin. We had the same problem with older plugins

Given that the uncontrolled motion happens after the second reset in Mach3, I'm fairly sure this is a software bug, probably in the shuttle plugin. My questions are: can anybody else reproduce this bug, can anybody else reproduce this bug using a USB smoothstepper, and who should I advise of the issue as machines moving by themselves is a fairly serious safety issue for us.

I'm happy to answer any questions and trial things if the developer is contactable. Thanks.

Offline poppabear

  • *
  •  2,233 2,233
  • Briceville, TN, USA
    • View Profile
    • S S Systems, LLC
Re: ShuttlePro V2 with ESS e-stop bug
« Reply #1 on: February 12, 2014, 10:48:37 AM »
My suspicion is you may need to contact Greg of SS, on this issue.
External motion pluigns have Movement buffers in them, so that they can continue
moving while M3 is looping (this is so motion does not stop, or get jerky).

The shuttle pro, his just an HID device, it just sends commands to mach3 per event and that is it.
Mach3 then handles the info. So if your jogging the shuttle pro is sending jog command to
m3 engine strucs which in turn the external motion plugin picks up what you want to do,
it then sends that motion amount/buffer to the external devices buffer.
In a motion plugin, the device developer will need to handle all motion and I/O
that his device handles, i.e. Jogging, Estop, etc...

I suspect that given your situation, there is some kind of logic in the motion plugin that is not clearing
the "left over" job motion, or not cancelling the jog command or process in the device or device plugin.

NOTE:  Greg is VERY, VERY good about looking into stuff like this, also, "Jeff Brit" is the Raining king as far as all things Smooth Stepper, as far as a user and OEM reseller & support. I would go to the Warp9 web site, and post your questions on the forum or email Greg (or Jeff) from here, or that website. Both of those guys are TOP SHELF and will get to your issue, especially a safety issue.

Caviot:  Greg uses FTDI chips for his USB, I have done other plugins for other OEMs that also use FTDI chips, and we (Greg and I) had a collision. I spoke to him about it, and he figured out what was the issue and fixed it on his end.  It has been a long, long time since I fooled with the SP3.0 plugin, and I would have to dig it out if the issue is NOT on Gregs end.

Commercial Mach3 & Mach 4, Design/Build/Retrofit CNC and Industrial machines.
Re: ShuttlePro V2 with ESS e-stop bug
« Reply #2 on: February 12, 2014, 08:23:36 PM »
the same behavior with the USB SS.