Messages

5391

Mach4 General Discussion / Re: Offsets, probing and operation manual

« on: February 04, 2018, 03:17:54 AM »

Hi,
welcome to Mach4 and CNC.....you poor sick little puppy...LOL

What manual are you reading? Can you post a link?

It is one of the persistent bug-bears of Mach4 that the documentation falls well behind where Mach is and often the documents are incomplete and if not
wrong....out of date. NFS doesn't have the resources to devote to the task. As a consequence the forum has become the goto place to get info.
Perhaps not ideal but it is what it is.

There is a good video about the new probing functions, absolute must see. I'll try to find a link for you.

Craig

5392

Mach4 General Discussion / Re: Mach4 Button OFFLINE

« on: February 04, 2018, 02:58:52 AM »

Hi,
OK I've got a solution that has improved the function a lot.

Code: [Select]

function OfflineButton()
local inst=mc.mcGetInstance()
local hsigenable=mc.mcSignalGetHandle(inst,mc.OSIG_ENABLE0)
local hsigbuttonstate=mc.mcSignalGetHandle(inst,mc.OSIG_OUTPUT2)
if (mc.mcSignalGetState(hsigenable)==1) then
    if (mc.mcSignalGetState(hsigbuttonstate)==1) then
        -- Mach is enabled and the servos are 'online'
        -- Need to save current position and set servos 'offline'
        local state=mc.mcCntlGetState(inst)
        if (state ~=0)then
            mc.mcCntlCycleStop(inst)
        end
        local Xpos=mc.mcAxisGetMachinePos(inst,mc.X_AXIS)
        local Zpos=mc.mcAxisGetMachinePos(inst,mc.Z_AXIS)
        mc.mcCntlSetPoundVar(inst,500,Xpos)
        mc.mcCntlSetPoundVar(inst,501,Zpos)
        mc.mcSignalSetState(hsigbuttonstate,0)
    else
        --Mach enabled but servos 'offline'
        --Need to restore current position and reset servos 'online'
        local state=mc.mcCntlGetState(inst)
        if (state ~=0)then
            mc.mcCntlCycleStop(inst)
        end
        local Xpos=mc.mcCntlGetPoundVar(inst,500)
        local Zpos=mc.mcCntlGetPoundVar(inst,501)     
        local rc=mc.mcCntlGcodeExecuteWait(inst,'g53 g0 x'..Xpos..' z'..Zpos)
        if (rc ~=0) then
                mc.mcCntlEnable(inst,0)
                mc.mcCntlEnable(inst,1)
                rc=mc.mcCntlGcodeExecuteWait(inst,'g53 g0 x'..Xpos..' z'..Zpos)
        end
        if (rc==0) then mc.mcSignalSetState(hsigbuttonstate,1) end
    end
else
    --Mach disabled....do nothing
end
end
if ( mc.mcInEditor()==1) then
    OfflineButton()
end
Note Dany this is the complete fuction code intended to be put in a folder that you may use your new found editor/debug skills!
Once youv've got it running to your satisfaction then strip off the last mc.mcInEditor test lines at the end ans put the remainder in the screen load script.
Note also that I think you have attached the function as 'clicked button' script which is not correct. Attach the function as 'Left up' script.

The changes over my original code all relate to the function performing when using Gcode files. You will note that this group of lines occur in two different
places. It purpose is to test if the controller is at idle before you attempt any thing else. If you do attempt to do something with the control state other than
idle will crash Mach.

        local state=mc.mcCntlGetState(inst)
        if (state ~=0)then                -- state==0 measns control state=idle
            mc.mcCntlCycleStop(inst)  -- A CycleStop will ensure the control state is idle
        end

The second change relates to the difficulty I note and posted in my previous post in this thread. The issue is that if you have a Gcode job loaded and running, even with
the job stopped or EVEN closed, the Gcode interpreter is unavailable to accept a fresh MDI command embedded in the GcodeExecuteWait() API call. The only way I could
find which would ensure that the Gcode interpreter was ready to accept a fresh MDI command was to disable and then enable Mach. This cycle in addition to freeing
the interpreter of code allows the Gcode job as loaded is preserved at its correct line number. I am a little unsure how it handles modals yet but it seems to work on
my laptop.

        local rc=mc.mcCntlGcodeExecuteWait(inst,'g53 g0 x'..Xpos..' z'..Zpos)
        if (rc ~=0) then
                mc.mcCntlEnable(inst,0)
                mc.mcCntlEnable(inst,1)
                rc=mc.mcCntlGcodeExecuteWait(inst,'g53 g0 x'..Xpos..' z'..Zpos)
        end
        if (rc==0) then mc.mcSignalSetState(hsigbuttonstate,1) end

The code works this way: the GcodeExecuteWait() API is attempted. If the return code is zero then the call succeeded. If the call failed the return code will be other than
zero. The two CntlEnable() calls first disable Mach and then enable Mach again. The GcodeExexcuteWait() call should now succeed. If it does as evidenced by a return
code of zero then  OSIG_OUTPUT2 can be set to reinstate the servos.

Still not quite sure why with the control state at idle the GcodeExecuteWait() API wont progress...that's subject to further investigation and another thread. In the mean
time this should go close to what Dany has wanted from the start.

Craig

5393

Mach4 General Discussion / Re: MERROR_NOT_NOW from GcodeExecuteWait() API Call

« on: February 04, 2018, 01:30:02 AM »

Hi,
have done a little more experimenting and found a workaround.

The problem is that if a Gcode file has been loaded and run, then stopped in cycle that an API call which requires MDI support to execute fails.
Closing the Gcode file does not restore MDI functionality. It requires either a RegenToolpath or a MachDisable/MachEnable cycle.

A Disable/Enable cycle preserves the Gcode file at its current line and is therefore suitable for my purpose.

The workaround goes something like this:
1) Try the GcodeExecuteWait() API
2) Test the return code, if rc=0 the call has succeeded. If rc=-18 then mc.mcCntlEnable(inst,0) mc.mcCntlEnable(inst,1)
3) Try the GcodeExecuteWait() API call again
4) By now the return code should be rc=0 so re-enable the servos

This sequence allows the machine coordinates to be restored and yet preserve the part completed Gcode job.

Still interested to hear an explanation for this behavior....hint...hint Daz and Smurph.

Craig

5394

Mach4 General Discussion / Re: Tormach moved from Mach 3 to Mach 4 - Feedrates 2X what is requested

« on: February 04, 2018, 12:09:53 AM »

Hi,
I've encountered a few situations where Mach4 did not do as I expected and thought I'd discovered a bug. In just about every case it is because I did not understand
how Mach4 works so it was not in fact a fault with Mach4 but rather my understanding/expectation that was wrong.

Would appear you've just had a lesson in the same vein.

Craig

5395

Mach4 General Discussion / MERROR_NOT_NOW from GcodeExecuteWait() API Call

« on: February 03, 2018, 06:50:45 PM »

Hi All,
have run into a problem with some code.This is a snippet, I've left the wxMessage boxes etc in there, they are for testing purposes only.

Code: [Select]

        --Mach enabled but servos 'offline'
        --Need to restore current position and reset servos 'online'
        local Xpos=mc.mcCntlGetPoundVar(inst,500)
        local Zpos=mc.mcCntlGetPoundVar(inst,501)
local state=mc.mcCntlGetState(inst)
local statename=mc.mcCntlGetStateName(inst,state)
wx.wxMessageBox(statename)
local rc=       mc.mcCntlGcodeExecuteWait(inst,'g53 g0 x'..Xpos..' z'..Zpos)
wx.wxMessageBox(tostring(rc))
        mc.mcSignalSetState(hsigbuttonstate,1)
    end
What appears to be happening if there is a Gcode file loaded and has partly run then Stopped, the control is Idle,
but when I execute the GcodeExecuteWait() statement it returns -18 or MERROR_NOT_NOW. My guess is that the Gcode interpreter is still loaded with
the Gcode file and is unavailable to execute the Gcode within my API call in MDI context?

Has anyone encountered this? Is my guess as to why the GcodeExecuteWait() API call does not complete correct? That same stament does execute correctly
under other circumstances so I am reasonably confident that its not some syntax error in my code.

If my guess is correct is there some way to shove the Gcode file out of the way, have the MDI Gcode execute, then shuffle the Gcode file back in?

Craig

5396

Mach4 General Discussion / Re: Mach4 Button OFFLINE

« on: February 03, 2018, 06:31:41 PM »

Hi,
have been doing some testing and the function works as anticipated under some circumstances but not others.

If you go 'offline' and jog or MDI when you go 'online' the machine coordinates reset to that they were prior to going offline. As anticipated.

Where it fails is if some Gcode from a Gcode job is executed between going offline and then later going back online the servos reinstate
but the machine coordinates do not (always) update.

rc = mc.mcCntlGcodeExecute(
      number mInst,
      string commands)

But the notes say:

Notes:


If the control is in the idle state, this function will execute the G code in MDI mode.

I can report that if the control is not idle when this statement is executed then you will crash.

There needs to be a test in the code that prevents the statement from running if the control is not in idle state. That's easy enough but there is a further complication
that I can't solve yet.

The return codes for this API are:

Returns: Return Code Description
MERROR_NOERROR No Error.
MERROR_INVALID_INSTANCE The mInst parameter was out of range.
MERROR_NOT_NOW The operation could not be completed at this time.
MERROR_NOT_COMPILED The macro scripts could not be compiled.

If have found that if a Gcode file is loaded but stopped (control idle) the API will not execute and comes back with a return code of -18 which corresponds to
MERROR_NOT_NOW

I don't know why this should be. I suspect that the GcodeExecuteWait() API requires MDI functionality but the loaded Gcode is already hogging the Gcode
interpreter so the MDI can't run. I feel a call being put out to Daz and Smurph about this!

Craig

5397

Mach4 General Discussion / Re: Additional Button Properties

« on: February 03, 2018, 04:23:20 PM »

Hi Russ,
thanks, worked a treat. Didn't realize that there is more than one type of button.

Craig

5398

Mach4 General Discussion / Additional Button Properties

« on: February 03, 2018, 03:38:57 PM »

Hi All,
in the screen editor when I look at the properties availble to be edited for Machs Enable button I see entries like 'Text Up' , 'Text Down'
'Button Colour Up' and 'Button Colour Down'.

I have a button on screen wish I wish to be able to change colour when active.  This button was one that was already there, I've just resused it for my purposes.
I doesn't have all the properties that the Enable button has.

How can I add those properties to my button?

Craig

5399

General Mach Discussion / Re: Steppers have no torque.

« on: February 03, 2018, 02:37:19 PM »

Hi,
it sounds to me like your drivers have lost the plot.

Testing a stepper driver is not straight forward, you really need an oscilloscope ideally with a high bandwidth current clamp. Do you have acess to
that sort of gear?

Can you tell me a little more about the steppers and the drivers, a few pics would help.

In absence of some good test gear you might be advised to beg/steal/borrow  or buy one good driver like a Gecko and hook up your stepper. If the stepper
performs it rather tells you the original drivers are faulty or just plain crap.

Craig

5400

Mach4 General Discussion / Re: Mach4 Button OFFLINE

« on: February 03, 2018, 02:26:57 PM »

Hi,

through the relay I will use a function, of which the units ignore any signal. (they still remain in position, without moving)
when the function changes state, normal use of the drives is restored

Isn't that what they are supposed to do? The trick is that when you restore the servos (so that they again respond to movement signals) is that while
they were disabled you may have jogged or MDI'ed Mach so Mach believes the servos are in one place when in fact they are where they were left
some time ago. Ergo the 'restore machine coordinate' instructions in the code.

Craig