Hello Guest it is March 28, 2024, 10:13:42 PM

Author Topic: Scripter Compile Error bites again :(  (Read 15381 times)

0 Members and 1 Guest are viewing this topic.

Offline TPS

*
  •  2,501 2,501
    • View Profile
Re: Scripter Compile Error bites again :(
« Reply #30 on: March 13, 2018, 07:08:48 AM »
just a question, how does your Cam create M3 call's?

M3 S1234 or

S1234
M3
anything is possible, just try to do it.
if you find some mistakes, in my bad bavarian english,they are yours.

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Scripter Compile Error bites again :(
« Reply #31 on: March 13, 2018, 07:22:27 AM »
What about CS Labs new software?

They have one in Beta, I have it downloaded, have not tried it because it has limited functionality, no macro editing and no screen editing - i could not use it on my mill without these functions.

They say it will all be there but after the beta stage is done so no idea when.

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Scripter Compile Error bites again :(
« Reply #32 on: March 13, 2018, 07:23:18 AM »
just a question, how does your Cam create M3 call's?

M3 S1234 or

S1234
M3

(END PROFILES)
N10 M5
N12 M9
N14 T3 M6
N16 S4000 M3
N18 G54
N20 M7
N24 G0 X232.214 Y5.999.........

Offline TPS

*
  •  2,501 2,501
    • View Profile
Re: Scripter Compile Error bites again :(
« Reply #33 on: March 13, 2018, 07:46:44 AM »
i have changed this on my machines to

S1234
M3

years ago, but realy can't remember why.
anything is possible, just try to do it.
if you find some mistakes, in my bad bavarian english,they are yours.

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Scripter Compile Error bites again :(
« Reply #34 on: March 13, 2018, 07:50:53 AM »
Interesting, its the same format in my Vectric code too.

Offline TPS

*
  •  2,501 2,501
    • View Profile
Re: Scripter Compile Error bites again :(
« Reply #35 on: March 13, 2018, 07:58:13 AM »
during trying to remember why i did this, i was googling arround,
and found this:

https://www.machsupport.com/forum/index.php?action=printpage;topic=28339.0
anything is possible, just try to do it.
if you find some mistakes, in my bad bavarian english,they are yours.

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Scripter Compile Error bites again :(
« Reply #36 on: March 13, 2018, 08:47:07 AM »
Interesting, more food for thought.

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Scripter Compile Error bites again :(
« Reply #37 on: March 13, 2018, 02:25:18 PM »
I have saved all my macro's as .mcc files and deleted all the .m1s copies.

Will see if that makes any difference.

BTW do not do this to macropump.m1s - it stops it running ;)

Offline rcaffin

*
  •  1,052 1,052
    • View Profile
Re: Scripter Compile Error bites again :(
« Reply #38 on: March 13, 2018, 04:50:39 PM »
Interesting.
I write my own g-code programs (out of my head) and use the following format:
f100 s2000
m3
As far as I can remember, this has never given the Scripter Compile error.

But playing around with the g84 command seems a bit risky as it is greyed out in the manual, meaning it never got passed Art's checking (or Brian's?). Obviously there was a bug in it they could not find. My spindle can't do tapping anyhow (DC servo, not suited to those speeds) so I thread mill instead. Yeah, slower.

On the other hand, if I launch Mach3 .062 and go straight into a program, the first Spin parameter can be missed, with the spindle going to max speed. If I spin the spindle up just once by hand first, all is well for the rest of the day. There is a funny in there somewhere. (Just one???)

Cheers
Roger

Offline Davek0974

*
  •  2,606 2,606
    • View Profile
Re: Scripter Compile Error bites again :(
« Reply #39 on: March 13, 2018, 05:05:06 PM »
I don't mind messing with post coding but, and thats a big but, i probably will not do it as this is a random issue - if the code was wrong it would fail, every time. This issue seems to have a bit of luck attached to it - most of the time it will work, then fail, i've had it mostly fail in the middle of the day i.e. not right on start-up so it will have done many starts and stops but then just decide to fail, most of the time in the middle of a code file.

All the apps i post code with have the same format so i can't see how it can be that.

My CS-LABS controller has a custom code M84 instead of G84 - pretty certain the rigid tapping is done directly in the controller not Mach.