Messages

61

General Mach Discussion / Re: Spindle button and M3 and M4

« on: September 15, 2016, 10:14:40 AM »

We'll make a programatist of you yet Dave  

500-600 are persistent (they're saved in the xml) so you're good to go.

62

General Mach Discussion / Re: Spindle button and M3 and M4

« on: September 15, 2016, 09:32:43 AM »

Looks good - just a typo - you've set 1601 to 0 in both

Here's one for you though - what happens when you start Mach and hit the spindle button for the first time i.e. when it's off?

63

General Mach Discussion / Re: Spindle button and M3 and M4

« on: September 15, 2016, 08:49:29 AM »

You need both LEDs to detect for ON just as you've used both outputs

Spindle rotating CW LED,   164
Spindle rotating CCW LED,   165

64

General Mach Discussion / Re: Spindle button and M3 and M4

« on: September 15, 2016, 08:39:16 AM »

You could remove the dependency on hard coded pins by using the CW and CCW Leds.

65

General Mach Discussion / Re: Spindle button and M3 and M4

« on: September 15, 2016, 07:16:44 AM »

Close Dave but that means your spindle button has no way of turning OFF your spindle - but you're getting there  

66

General Mach Discussion / Re: Spindle button and M3 and M4

« on: September 15, 2016, 06:16:17 AM »

From my experience when some data need to be saved and read it only worked saving them in file otherwise every time I enter in macro variable is not remebered. Probbly I could use saving in file information but was hoping that there exist something simpler of what I am not aware of. Thank for your help. I assume somebody had this kind of problems already.

BASIC variables are destroyed between macro runs (except in the macropump) but GCODE vars are not. That's why Dave is suggesting you use a gcode var to maintain state between calls. Look up setVar and getVar().

67

General Mach Discussion / Re: Bridgeport Knee Mill Conversion?

« on: September 07, 2016, 05:46:13 AM »

OK - the screen button - (back to a familiar issue) what is the actual code in the button?

Why am I asking?

Well if (for example) the button code is doSpinCW then it's NOT calling the M3 macro and that tells us something. However if it's got (for example) call "M3" in it then it IS calling the M3 macro and that tells us something else.

68

General Mach Discussion / Re: Bridgeport Knee Mill Conversion?

« on: September 07, 2016, 05:08:03 AM »

even though all went well the first check-run failed because mach started running the code without starting the spindle!
It would work from the panel button as well as the screen button but NOT from MDI or G-Code.

I have seen this before on the engraver and a Mach restart fixes it as it did this time, but of course you have to re-home. The only message you sometimes get is "Scripter compile error in M3.m1s" but as usual that file only contains DoSpin...

Any ideas??

How does your panel button activate your spindle?
How does your screen button activate your spindle?
Do you REALLY mean your M3 macro contains "DoSpin..."?

69

General Mach Discussion / Re: Bridgeport Knee Mill Conversion?

« on: September 05, 2016, 07:37:03 AM »

LOL - no worries - hopefully you'll make some progress.

You'll probably know enough about my attitude to software by now to know why I can't let this one go without comment:

this should put my system perfectly in line with Hood's proven working version

Working - yes - proven - no. It works for Hood on Hood's system - but I've been around Mach3 long enough to know it WILL fail on SOME other systems.

One suspect area is this:

Code "G90" & "G10" & "L1" & "P" & Tool &"Z" & Offset
DoOemButton(121)

You hopefully know enough by now about what the "code" call actually does to know why this can fail.
Does it matter? Not to Hood and not to me - might do to someone who comes across this thread sometime and copies it though. 

70

General Mach Discussion / Re: Bridgeport Knee Mill Conversion?

« on: September 05, 2016, 06:47:32 AM »

EDIT: I posted this to reply to your previous post just as you posted your last reply. I can't be arsed to edit it so I'm pleased you've addressed BOTH issues. 

I have now got a custom screen set from Ger21 with the A axis DRO removed and replaced with UserDRO(1444) so that should solve all issues instantly as it will not be connected to anything internally.

I'm hoping I've convinced you to address the M code as well.

I guess pressing the stop button resets the interpreter?

That would be my guess - though that was one thing I didn't see here. pressing cycle start STILL left the interpreter hung - but then I'm using an old version so maybe that was a "fix" for some related bug introduced sometime later.

I will abort further testing and go straight for the new screen-set and test on that, no point in beating the dead horse any more.

I'm REALLY hoping I've convinced you to address the M code as well.

Maybe it is more allied to the Mcode calling issue than the actual DRO used as Hood has his code in the buttons??

I'm REALLY REALLY hoping I've convinced you It's BOTH that need addressing.

As for your last paragraph I am still trying to get my head round that conundrum! Sounds like a real hornets nest of trouble there, is there a safe way to not run into that issue or prevent it happening?

I guess just being aware is half the battle. Don't have the time or the will to go off down another rabbit hole just now.