Messages

701

Mach4 General Discussion / Re: Mach 4 licence not instaling

« on: September 06, 2015, 11:54:10 AM »

Same Here?? I only have 1 computer using Mach4 and so far i'm on 3rd licence...

DazTheGas

702

Mach4 General Discussion / Re: Homing

« on: September 05, 2015, 05:18:44 AM »

Check your Mach config, A axis is set to home last, although in the input signals there is nothing set for Motor 3 Home.
This could mean that motor 3 is homing as should but it does not back off to complete the cycle.

DazTheGas

703

Mach4 General Discussion / Re: Homing

« on: September 04, 2015, 11:50:39 AM »

The posted log is showing the estop etc,

With the log being outputed start up the machine, and click home all axis. Then we can see only what has been run in the api and motion controller befor it hangs.

The thing we need to discover is if there is something else that is causing the hang.

DazTheGas

704

Mach4 General Discussion / Re: Homing

« on: September 04, 2015, 10:40:40 AM »

Your missing the point, we are trying to get the log so we can see what is called before it hangs.....

DazTheGas

705

Mach4 General Discussion / Re: Homing

« on: September 03, 2015, 06:43:30 PM »

Perhaps this might help or not, it will start the logging within the plc and dump it out to a file called Output.log in the mach4 directory. The internal logging is a lot faster updating than this but might just take you to just before the crash.

Using the Screen Editor use the codes below.

--screen load script

Code: [Select]

local inst = mc.mcGetInstance()
mc.mcCntlSetLogging(inst, 1)
local done = ''

function WriteLog()
    local var = mc.mcCntlGetLastLogMsg(inst)
    if var == done then
    return
    else
    file =io.open("Output.log", "a")
    file:write(var..'\n')
    file:close()
    done = var
    end
end
and in the PLC Script

Code: [Select]

if testcount > 5 then WriteLog() end
Theres 2 variables being used here 'var' and 'done' just check and make sure these are not in use elswhere...

DazTheGas

706

Mach4 General Discussion / Re: DRO unit display

« on: August 29, 2015, 12:38:28 PM »

Have you thought of using a wxtextctrl and updating its value using a timer event.

DazTheGas

707

Mach4 General Discussion / Re: Screen Set Ideas

« on: August 23, 2015, 11:44:55 AM »

Showing multiple stay on top wizards

Nice..

708

Mach4 Toolbox / Re: Floating MDI Panel V1

« on: August 22, 2015, 10:45:15 AM »

As of Mach4 V2 the modules directory has now been moved out of individual profile directories and moved to the root directory. This allows all profiles to access the modules and makes it easier for installers etc, Thanks for the heads up Brett..

The DTG_MDI.mcc file will now need to be moved to root/Modules and the loader script changed to

Code: [Select]

local inst = mc.mcGetInstance()
package.path = mc.mcCntlGetMachDir(inst) .. "\\Modules\\?.mcc;"
DTG_Widget = require "DTG_MDI"

DTG_Widget.LoadMDI(1000,300)
DazTheGas

709

Mach4 Toolbox / Floating MDI Panel V1

« on: August 20, 2015, 10:15:32 AM »

V1 of a floating mdi panel.


:Instructions

1. Create a button and in the left up script place

Code: [Select]

local inst = mc.mcGetInstance()
package.path = mc.mcCntlGetMachDir(inst) .. "\\Profiles\\" .. mc.mcProfileGetName(inst) .. "\\Modules\\?.mcc;"
DTG_Widget = require "DTG_MDI"

DTG_Widget.LoadMDI(1000,300)
2. Copy into your profiles/modules directory the attached file DTG_MDI.mcc file.

You can change the panel size with the loadMDI function ie: DTG_Widget.LoadMDI(500,300) will give you a panel of 500 x 300 etc

710

Mach4 Toolbox / Re: Saving the selected spindle speed range

« on: August 14, 2015, 05:37:02 PM »

OOps didnt spot that. posted the screen load twice

Screen Unload script should be

Code: [Select]

--local inst = mc.mcGetInstance() -- not needed if already declared
local val = mc.mcSpindleGetCurrentRange(inst)
mc.mcProfileWriteInt(inst, 'SpindleDefaultRange','Range',val)
DazTheGas