Machsupport Forum
Mach Discussion => General Mach Discussion => Topic started by: egerber on November 29, 2011, 06:55:03 PM
-
Has anyone seen this error??
I get periodic scriptor compile errors in spindle .mis and when tapping in:M4.mis
Any ideas
-
Yup, I get those periodically, and got one today on M3.m1s. The fix is usually to open the offending file with Notepad, and you should see a few garbage characters at the end of the file. Delete those, and save it, and the problem should go away.
spindlespeed.m1s does actually have a syntax error in it, in some versions of Mach3, yet it does not always generate an error message.
Regards,
Ray L.
-
Thanks that fixed the problem
-
Still getting Scripter Compile Error in M3.mis
Machine ran fine all day no problems, started this morning agin, checked files and everything looks normal but spindle does not turn,Requries mach reboot to fix
Any Ideas??
-
Has anyone seen this error??
I get periodic scriptor compile errors in spindle .mis and when tapping in:M4.mis
Any ideas
Problem continues
-
Still getting Scripter Compile Error in M3.mis
Machine ran fine all day no problems, started this morning agin, checked files and everything looks normal but spindle does not turn,Requries mach reboot to fix
Any Ideas??
That, too, is, sadly, consistent with my experience. I believe something is happening inside Mach3 that causes this, as the same script will throw an error one time, and not the next. Sometimes editing the script will help, sometimes not. I've got quite a number of conditions that pop up more or less randomly, that require re-starting Mach3 to restore proper operation. It is my great frustration with Mach3 - I can go days at a time and everything will function perfectly, then I'll have a day where I have one bizarre problem after another, and I can't get any work done.
Regards,
Ray L.
-
What version of mach3? I use an old version, and have never seen this error.
-
What version of mach3? I use an old version, and have never seen this error.
Gerry,
I couldn't tell you when this issue first cropped up, but it's been around a couple of years, since at least 3.042.022. I'm now using 3.043.053, and have used dozens of intermediate versions.
Regards,
Ray L.
-
Hiya Ray there is a reason that a lot of us stay at the 3.042.020 version or very close to it.
(;-) TP
-
Hiya Ray there is a reason that a lot of us stay at the 3.042.020 version or very close to it.
Ain't that the truth. I just can't understand why subsequent releases have been made without thorough beta testing. Personally I wouldn't go near them with a barge pole.
Ian
-
Gerry,
I am running version 3.042.040
-
3.42.020 here, and never see any errors.
-
Hiya Ray there is a reason that a lot of us stay at the 3.042.020 version or very close to it.
(;-) TP
Terry,
I would do the same were there not many crippling bugs in those old versions. Despite its *many* problems, v53 is FAR better far me than 022.
Regards,
Ray L.
-
HIYA RAY, To each his own, But from the sounds of the earlier comments you are not doing well at all. Still suffering fromteh Lost Mach Syndrome
I feel your pain but there is little i can say to make it better other than YEP it should get fixed. But I am just speaking to the Choir (;-)
(;-) TP
-
HIYA RAY, To each his own, But from the sounds of the earlier comments you are not doing well at all. Still suffering fromteh Lost Mach Syndrome
I feel your pain but there is little i can say to make it better other than YEP it should get fixed. But I am just speaking to the Choir (;-)
(;-) TP
Terry,
Yup, but, like I said, as bad as it is now, it's still MUCH better than it was. I am still inching towards switching to KFlop, but it's a big project, due to all the wiring changes, and all the KFlop code that needs to be written to duplicate the essential functionality I have in Mach3. The last bit is getting my pendant moved over, and I just bought the bits I need to make the cable today, so I should have the pendant going soon.
Regards,
Ray L.
-
Notepad edited the .NC file, rebooting, etc. did not fix.
BUT, I simply took a copy of the Mach3/macro/myproflie/M3.m1s from ANOTHER
profile and overwrote the corrupt one, and it FIXED.
M3.m1s appears to be a one line file but is NON-ASCI. Looks same in all profiles.
Phil
-
Actually, forget coping the M3.m1s, found other problems: code got stuck in
subroutine, endlessly looping. Not sure if coping the M3.m1s from another profile caused this,
or if I had multiple corrupted files.
Better fix for the M3.m1s error message is to DELETE the directory under MACRO
for your profile. Since the .xml for your profile is still in the Mach3 directory, when you run MACH3 again,
it will RECREATE the MACRO directory and all the files including the M3.m1s, so you have all new uncorrupted
files.
-
Actually, forget coping the M3.m1s, found other problems: code got stuck in
subroutine, endlessly looping. Not sure if coping the M3.m1s from another profile caused this,
or if I had multiple corrupted files.
Better fix for the M3.m1s error message is to DELETE the directory under MACRO
for your profile. Since the .xml for your profile is still in the Mach3 directory, when you run MACH3 again,
it will RECREATE the MACRO directory and all the files including the M3.m1s, so you have all new uncorrupted
files.
Just make sure that if you do this you save any Non-standard macros if you have any ;)
Hood