Hello Guest it is December 06, 2019, 01:33:39 AM

Author Topic: m3 not always recognized  (Read 8124 times)

0 Members and 1 Guest are viewing this topic.

m3 not always recognized
« on: March 18, 2008, 11:52:48 PM »
I am running mach on 3 machines, 2 lathes and a mill and at some point on everyone of them the m3 command fails to start the spindle, wont work at the MDI line or in the gcode file. It usually happens later in the day after the system has been running 6-8 hours sometimes not for a couple of days. I am not sure what the common link is three seperate machines, three seperate computers all have the problem at some point. Closing and restarting mach doesnt seem to fix it . Always requires rebooting the computer.

vmax549

*
Re: m3 not always recognized
« Reply #1 on: March 19, 2008, 12:27:55 AM »
Art has recomended that IF you run into this problem Go to General config page and turn ON debug this run. THen try using the mdi many times to get the m3 to work. THen send them the file that mach generates to help them find the bugger that causes it.

(;-) TP


ART's instructions:

One thing you CAN do is , if the MDI problem occurs and things wont move,
select "Debug This Run" in config/general, then
try quite a few MDI commands. Close the program and show us the entries in the
..hmm, I think its called debug.txt or LastErrors.txt file in the mach3 folder.
Im not sure it will help, but the debugrun logging has allot more in it than
normal mode, so it may show a possible bug location. Also, on the Diags page of
the program is a queue depth DRO. Try several MDI moves, do they get queued and
just not execute, or do they not get queued.. in the end the more info we can
giev brian in that area, the faster he can zero in on a possability..

Thanks,
Art
« Last Edit: March 19, 2008, 12:32:17 AM by vmax549 »
Re: m3 not always recognized
« Reply #2 on: March 19, 2008, 09:48:12 PM »
one of the lathes did this again  but I didnt have any failure to move but when m3 is called out in the gcode  I get a popup that says "uknown error 1 occured, m3 not recognized" when I click the OK on that popup it opens the VB editor with the DoSpin (cw) command, Require machine reboot to recognize m3

Offline Glenn

*
  •  129 129
    • View Profile
Re: m3 not always recognized
« Reply #3 on: May 02, 2008, 05:53:48 PM »
Hi Panaceabeachbum,
  Today I was hooking up my first spindle relay, and after several good
program run-throughs, (motor on-motor off by m3, m5), Mach 3
 would run down to the m3 line, and just stop-- I could rewind
start again, but it just won't cross the m3 line and proceed on with the
rest of the program. I can hit letter "s" on keyboard to start/stop spindle
and it does work. Any ideas on what it is up to?

cnc-erly,

Glenn :)
Don't assume anything.....it'll make a Manager out of U and Me!
Re: m3 not always recognized
« Reply #4 on: May 02, 2008, 07:42:33 PM »
What version are you runing?

Offline Glenn

*
  •  129 129
    • View Profile
Re: m3 not always recognized
« Reply #5 on: May 02, 2008, 10:48:11 PM »
Hey Sid,
  I'm running licensed version R2.63..But of course, I shut it down and ate supper (My wife
brought me a steak sandwich from the local Wild Turkey Festival), and now it works!
  I'll keep my fingers crossed!
   Thanks,
Glenn :)
Don't assume anything.....it'll make a Manager out of U and Me!
Re: m3 not always recognized
« Reply #6 on: May 02, 2008, 11:25:33 PM »
Wow, nice Wife!  Bon Apitit!

I seem to recall having similar internittent M3 issues around the ver 2.X times.  You might want to give ver 3.41 a try I think things have progressed a bit since back then!  But then again.. "If it ain't broke..."

Regards,
Sid

Offline jimpinder

*
  •  1,233 1,233
  • Wakefield, West Yorks, UK
    • View Profile
Re: m3 not always recognized
« Reply #7 on: May 03, 2008, 04:29:14 AM »
I cannot remeber having this problem when I was only using M3.M4 and M5, and using the inverter manually to control the speed.

My problems started when I started using PWM to control the speed - and since I had set a minimum speed, I put in M3 with an S - and, of course, nothing happens. If I don't notice the warning  about it being below minimum, I'm left scratching my head.
Not me driving the engine - I'm better looking.

Offline Bodini

*
  •  216 216
    • View Profile
Re: m3 not always recognized
« Reply #8 on: August 14, 2008, 04:27:10 PM »
So did anything ever get straightened out with this problem?  I've been having it for a month now (at least)... M3 not being recognized in MDI or during gcode.  I'm using v2.63. 

-Nick

addendum- I just noticed that during a gcode routine, Mach had ran through a bunch of macros, then when it got to the M3 (the first one of the routine BTW), Mach quit running the code.  Also, after that point, NO macros would run, OEM or custom.
« Last Edit: August 14, 2008, 04:35:38 PM by Bodini »

Offline Katoh

*
  •  274 274
    • View Profile
Re: m3 not always recognized
« Reply #9 on: November 15, 2008, 08:14:39 AM »
Hi Bodini
I'm experiencing exactly the same problems at start up, you can go to the MDI screen hit M3 or M4 even M5 and it comes back with an unspecified error down the bottom will say syntax error, even just typing s*********x will cause it to go into error mode. Have you found a solution yet? Or has anyone addressed the problem; so it takes out one less thing to look at when it falls in a heap. As yours the only way to get mine to work is to re-boot.
Regards Katoh
Cheers
Katoh