Hello Guest it is December 04, 2021, 09:11:31 PM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - HeadyCS

Pages: 1
I am looking for a way (in LUA script) to switch an output when G31 (probing) is active.

I looked into the API documentation but found no function where can query the status.

I have read the gcode variables / parameters but also found nothing.
local value = mc.mcCntlGetPoundVar (num inst, num PoundVar)
local Gvalue = mc.mcCntlGetPoundVar (inst, 10) -- G
Gvalue: 1.456e-14
local Gvalue = mc.mcCntlGetPoundVar (inst, 10) -- MOD GROUP 1 4001 // Group 1 // active G-code for motion
Gvalue: 1.0 on G1, G31 movements,

I do not know what the output digitize trigger does. So I searched at google and found this page: https://warp9td.com/index.php/faq/faq-mach4
"Digitize Trigger:  This output activates when the Probe is active with a G31/G31.x command."
I tried but there dont switches state on G31. it seems to be for SmoothStepper.

Mach4 General Discussion / script changes not aplied after saving
« on: April 06, 2019, 08:24:11 AM »
Mach4 v3804

When I make changes to Scripts with Notepad ++ and save the file via CTRL + S, they are not taken over in the current instance. m6 or other .mcs in Profile/Macro folder or .lua in Profile/Module folder.
I have to restart Mach4 so that the changes are taken over, very annoying.

In Mach4 v3481, the changes were accepted immediately after saving.

I also tried it with the Zerobrain editor via menu operator -> Edit / Debug scripts. or Open Script Editor.
Open Lua in Profile / Modules folder, make changes, save by Ctrl + S and Menu Project -> Compile show no changes in the current instance.

Following composition:

Milling machine 3 axes, Z+ upwards
Controller: CSMIO IP-M v3.016
Control: Mach4 v3804
CAM: Fusion 360
Postprocessor: newest Mach4 Config from Autodesk Portal: https://cam.autodesk.com/hsmposts?p=mach4mill

Code: [Select]
N1 G90 G94 G91.1 G40 G49 G17
N2 G21

N3 M5
N4 M9
N5 T3 M6
(MRKLEN_1115600600 - D6MM - SPOT DRILL)
N6 S1857 M3
N7 G54.1 P2
N8 M8
N10 G0 X8.08 Y4.075
N11 G43 Z39. H3
N12 M98 P0001
N13 G54.1 P3
N14 M8
N15 G0 X8.08 Y4.075
N16 Z39.
N17 M98 P0001

N142 M9
N143 M64 P41
N144 G04 P1.0
N145 M65 P41
N146 M30

G0 Z-10.
G98 G82 X0. Y0. Z-2.65 R-15.25 P0.06 F56.

G0 Z-10.
G98 G82 X0. Y0. Z-2.65 R-15.25 P0.06 F56.

G91: incremental mode,
G0 Z-10 .: Z moves down 10mm = absolute Z=29
G98 G82 X0. Y0. Z-2.65 R-15.25 P0.06 F56 .: Z moves with rapid traverse to absolute Z=-15.25 through the workpiece and drills up with F=56 to absoulte Z=-2.65.  ???
Correct would be: Z drive down 15.25mm and drill 2.65mm deep.
G82 values are not interpreted incrementally.

Information about G82 in the Mill GCode Programming.pdf page 57, 60 in the Docs folder.

Is it due to mach4 or the csmio controller?

Mach4 General Discussion / Define own global Variables to use in macros
« on: December 25, 2018, 04:09:47 AM »
In the "screen load script" I would like to define my own global variables and functions that are also available in macro scripts (m6).

I tried it with the following variables
myOwnVariable = 1;
mc.myOwnVariable = 1;

but in m6 script these are not available. when calling the scripts is executed up to this point and then the script aborted. I do not see any error message like "m6, line55: attempt to compare nil with string". Is there a log file in which such errors are written?

Mach4 General Discussion / Homing Speed v3481
« on: January 21, 2018, 10:42:38 AM »
The Homing in Mach4 v3481 is unbecoming because the high Homing speed causes inaccurate Home positions. At low homing speed it takes forever until the axes are referenced.

The axes should drive with rapid traverse to the home switches. Then drive away from the switch a bit and drive at low measure speed to the switch and set the home positions.

Pages: 1