Messages

5251

General Mach Discussion / Re: Weird behaviour on limit switches

« on: February 16, 2018, 10:38:14 PM »

Hi,

Removing the signal from the input is not enough to be able to reset the system?

No. Commonly a limit event will Estop Mach. Even if you remove the offending limit signal Mach will still have to be reset manually. If you don't have "Overide Limits'
then you will not be able to jog off the limit switch.

If I power down the limit switch circuit, the X++ and X-- lights still stay lit, even though the ESS input has returned to a high level and there is no longer a limit input. 

I suspect this is a result of Mach being disabled. The sequence of events is that the limit switch triggers and Mach disables. Your description suggests to me that Mach
is not responding to new inputs until it has been re-enabled.

Craig

5252

Mach4 General Discussion / Re: Lua programming of voltage meter

« on: February 16, 2018, 06:23:35 PM »

Hi,
the 57E will need to communicate a digital word to your PC over its Ethernet connection. You will have to read the manual as to how to cause the 57E to that
and to where it would store its value.

Craig

5253

Mach4 General Discussion / Re: Lua script detect when the cycle is running

« on: February 16, 2018, 03:17:04 PM »

Hi,
that can be done.

Note that the one thing which determines if your M6 has been stopped or the machine disabled is the state of the control. If the m6 is progressing normally
the control state is busy and you wish to leave it alone. If however it has been stopped then the control state would be Idle and you wish to RETURN.

How about this:

if (mc.mcCntlGetState(inst)==mc.MC_STATE_IDLE) then return end

So if the control is in Idle state, and we know it shouldn't be if every thing is normal, then cause the macro to return immediately.

Craig

5254

Mach4 General Discussion / Re: Lua script detect when the cycle is running

« on: February 16, 2018, 03:03:21 PM »

Hi,
I owe you an apology I misinterpreted what I saw.
When I <stop> the code while the delay is timing the error log shows that CycleStopped has been issued but then Lua is stuck in limbo and it carries on from
the point that it stopped, and you note that now because of the CycleStop the control state is IDLE, then it reaches the end.

Craig

5255

Mach4 General Discussion / Re: Lua script detect when the cycle is running

« on: February 16, 2018, 02:54:38 PM »

Hi,
whoops posted before I'd actually finished. The code runs fine.
If I leave it to time out its delay it completes with the 'end' message and if I look at the error log it is preceeded with 'else' as it should be. Note that because
m401 is running the control can't be Idle, we happen to know that its busy running our script!
If however I either <Stop> or <Disable> m401 while the rather lengthy pause it running the script end and prints 'end' but doesn't print the 'else' which would
ordinarily preceed it. That is to say it skipped over the mc.mcCntlGetState() and the if-then-else-end code between the point at which I <stop> and the scripts
endpoint. Once the endpoint is reached m401 releases control and control reverts to the state which preceeded the m401 call namely Idle.

Craig

5256

Mach4 General Discussion / Re: Lua script detect when the cycle is running

« on: February 16, 2018, 02:42:21 PM »

Hi,
I had to modify your script slightly to get it to run, my installation wont do anything useful with 'print()'
Also your  G4 P3 statement is interpreted by my machine as 'pause for 3 milliseconds', if you put a decimal point in the P parameter it is interpreted as seconds,
as you see I changed mine to P10.0.

Code: [Select]

function m401()
    local inst = mc.mcGetInstance()
    mc.mcCntlSetLastError(inst,"starting")
    mc.mcCntlGcodeExecuteWait(inst,"G4 P10.0")
    local mcState,rc=mc.mcCntlGetState(inst)
    if (mcState==mc.MC_STATE_IDLE) then
        mc.mcCntlSetLastError(inst,"IDLE")
    else
        mc.mcCntlSetLastError(inst,"ELSE")
    end
    mc.mcCntlSetLastError(inst,"end")   
end
if (mc.mcInEditor()==1) then
    m401()
end

5257

Mach4 General Discussion / Re: Lua script detect when the cycle is running

« on: February 16, 2018, 02:12:17 PM »

Hi,
I'm with Daz and am unsure that I understand the problem you are describing.

but the machine is stopped or disabled halfway through by the operator. The execution starts at the top, YET STILL ENDS AT THE BOTTOM, since Mach actually doesn't stop executing until the whole thing has been gone through.

I'm not sure about this....surely the M6 starts at the top but the code stops at the point that you disable or stop it? The only way I can think that the code would continue
to execute but not actually physically move would be if the motors/servos were disabled while Mach remained enabled and therefore carried on executing?.

You may have noted a current and fairly long running thread where a guy wanted an 'Offline' button on his machine. The solution was to disable the physical motion of
the servos while allowing normal operation of Mach. When the machine is to be re-instated it is necessary to apply a machine coordinate correction so the machines
referencing remains consistant. Eventually I got the code to work pretty well, regrettably the OP is being rather obtuse and refuses to follow the steps required to get it
to work on his machine but it works fine here.

With the solution I proposed for his "Offline' button the servos stopped motion but if a signal changed state as a result of Mach's continued execution while the servos
are offline that could cause problems. Is this the concern you have?

Craig

5258

General Mach Discussion / Re: ARFcnc 6040 Mach 3 USB configuration help

« on: February 16, 2018, 03:12:21 AM »

Hi fredeflint,
you used to have this board....did you ever get it to work properly? 'Use to have' sounds like past tense, do you not have it any more?

Craig

5259

Mach4 General Discussion / Re: Lua script detect when the cycle is running

« on: February 15, 2018, 04:15:33 PM »

Hi,

http://www.machsupport.com/forum/index.php/topic,36548.0.html

No, what I am saying is that IF you try to execute code when the control is NOT idle then you'll
crash Mach.

What you are asking is: 'how did the control become idle...did the previous code execute and exit normally...
did it get aborted or did it fail to execute?'

I can see that you may not wish to execute your code if the previous code ended abonrmally, this test does'nt
help it that decision. It does tell if you 'could' execute your code.

Craig

5260

Mach4 General Discussion / Re: Lua script detect when the cycle is running

« on: February 15, 2018, 12:56:48 PM »

Hi,

The piece of code isn't related to the motion planner, rather changing the state of signals.

No that's correct but if you check that the control state is Idle then that will determine that no code is running, Gcode or MDI or screenscript.

LUA Syntax:
mcState, rc = mc.mcCntlGetState(
      MINSTANCE mInst)

local mcState,rc=mc.mcGetState(inst)
if (mcState==mc.MC_STATE_IDLE) then
--
-- execute your code as the control is idle and ready for use
--
else
--
-- the control is not idle and not available to be tasked
-- if required you can terminate the current task
--
end

Craig