Messages

71

Mach4 General Discussion / Re: Mach 4 to Windows 7 : Debug Report Crash

« on: July 12, 2018, 04:45:15 PM »

Curious, I searched for the Static GUI shortcut, which I'd never seen before..  Sure enough it was present and it points to the wxMach screen set. So it can indeed be safely deleted.

Allan

72

Mach4 General Discussion / Re: Mach4 problems when moving.

« on: July 12, 2018, 06:56:12 AM »

Does the setting "Cycle Stop is Controlled Stop" have any effect on your machine?

Allan

73

Mach4 General Discussion / Re: I NEED ''Enable'' an ''Cycle Start'' scripts for activating with a ESS input

« on: July 01, 2018, 06:27:19 PM »

Open the Screen Load script in the screen editor and find the line:

    SigLib = {

This is the beginning of the signal table. Now try inserting the following between 2 existing entries:

Code: [Select]

--AW: Set cycle start if user presses key assigned to Input0
[mc.ISIG_INPUT0] = function (state)
    if (state == 1) then
        CycleStart()
    end
end,

--AW: Set feed hold or stop if user presses key assigned to Input1
[mc.ISIG_INPUT1] = function (state)
    if (state == 1) then
        local hSig = mc.mcSignalGetHandle(inst, mc.OSIG_RUNNING_GCODE)
        local codeRunning = mc.mcSignalGetState(hSig)
        if (codeRunning  == 1) then
            mc.mcCntlFeedHold(inst)
            --CycleStop()
        end
    end
end,


Use your own inputs instead of inputs 0 and 1. That's all there is to it.

Allan

74

Mach4 General Discussion / Re: I NEED ''Enable'' an ''Cycle Start'' scripts for activating with a ESS input

« on: July 01, 2018, 05:12:18 PM »

jbraddock

Notice that individual table entries are separated by a comma , so be sure to include one after your code unless it is the final entry in SigLib{}.

Allan

75

Mach4 General Discussion / Re: jogging

« on: July 01, 2018, 03:19:25 PM »

See this topic:


http://www.machsupport.com/forum/index.php/topic,37378.msg255652.html#msg255652


Allan

76

Mach4 General Discussion / Re: WHATS THIS ERROR..??? Clearing a spurious limit hit latch event,

« on: June 30, 2018, 05:30:48 PM »

The last fft certainly gives a graphic indication of how those sharp edges translate into the frequency domain. As you say, it is an aside since the op says it isn't RFI from the spindle drive, but it's interesting to see anyway.

Allan

77

Mach4 General Discussion / Re: ISIG_DIGITIZE

« on: June 26, 2018, 04:56:52 PM »

The probe input was named ISIG_DIGITIZE in earlier versions of Mach4, but was later renamed to ISIG_PROBE. This relates to G31.0. G31.1-3 are similarly now given the more intuitive names of ISIG_PROBE1 to ISIG_PROBE3.

These are defined in machine.ini

Allan

78

Mach4 General Discussion / Re: My new screenset (and thanks to all)

« on: June 25, 2018, 06:35:17 AM »

Paul

Nice clean layout. Good to see you achieved your ambition. The learning curve can be steep, but all it needs is a degree of determination.

Allan

79

Mach4 General Discussion / Re: Are #100 thru #199 #vars safe for user functions?

« on: June 22, 2018, 04:54:03 AM »

Also be aware if you use it that some of these vars are cleared and used within the Probing module.

Allan

80

Mach4 General Discussion / Re: Can't seem to get load_modules.mcs working

« on: June 17, 2018, 06:33:09 PM »

You are calling the module from the screen, so the require statement needs to be within the screen script, as you have discovered. Placing it in the Macros directory in LoadModules makes the module available to all macros, as these share a single file when compiled.

Allan