Hello Guest it is June 18, 2019, 02:00:49 AM

Author Topic: Mach Not Responding & how to recover  (Read 1427 times)

0 Members and 1 Guest are viewing this topic.

Mach Not Responding & how to recover
« on: May 08, 2014, 04:19:39 PM »
Brand newbie here making my first parts.
Running on XP SP3 on a stripped down machine(not a laptop) no internet, no updates, etc...
 Controller is The Soigeneris STDR-4C with Smooth stepper

Using OneCNC XR3 for CAM.

Aircuts run fine and so far out of 6 parts I have had Mach just stop in the middle of the program 3 times. No crash, just stop. Clicking on anything, Stop, Feed Hold, etc, brings up "Program Not responding" The next restart brings up "No USB Device found...try unplugging the USB cable and restarting" The next restart its fine.

I realize this could be a large number of things...but is there something I can try?

Also, so it just happened again and I made note of all the X,Y,Z locations, and shut down Mach restarted and then moved from that location back to 0,0,0 and reset my zeros. I then picked a spot about 10 lines earlier in the code and choose Run From Here.

The tool plunged straight down into my hold down bolt, a spot it never went to before.

So what happened and what is the best way to recover when the software stops responding?

Thanks for any help,

Paul

Offline Hood

*
  •  25,844 25,844
  • Carnoustie, Scotland
    • View Profile
Re: Mach Not Responding & how to recover
« Reply #1 on: May 08, 2014, 04:43:00 PM »
What have you got the controller frequency set to in the SS config?
Kind of sounds like the SS is running out of data.
Hood
Re: Mach Not Responding & how to recover
« Reply #2 on: May 08, 2014, 04:55:18 PM »
Set to 1KHZ, is that correct? I have no idea....

Offline Hood

*
  •  25,844 25,844
  • Carnoustie, Scotland
    • View Profile
Re: Mach Not Responding & how to recover
« Reply #3 on: May 09, 2014, 02:46:45 AM »
1KHz should be ok unless your PC is very slow.

One thing to look at, when it happens again, is the LEDs on the SS to see if it has crashed.
Also may be a good idea to have the SS diagnostics page open whilst running code to see if it holds any clues when the problem happens.

Hood