Messages

301

Mach4 General Discussion / Re: Tool change Problem.

« on: May 13, 2020, 09:00:01 AM »

If you did not set the offset for  T3, T4 etc then they will be wrong.
Mach has no way to know that it is the same tool as T2.
You must set for each tool.

Bill

302

Mach4 General Discussion / Re: pInst and pcall

« on: May 13, 2020, 08:31:16 AM »

Steve,

Thanks for the information.

Bill

303

Mach4 General Discussion / Re: Switching from Mach 3 to 4 - How Do You Change Motor Tuning Time

« on: May 12, 2020, 02:57:50 PM »

It is not wrong.
The time shown to accelerate and decelerate is right there.
The time at constant speed is irrelevant.

304

Mach4 General Discussion / pInst and pcall

« on: May 12, 2020, 01:53:52 PM »

I am looking through some scripts that others have written to see what I can steal or modify.
I came across a script that uses pInst and pcall.
What is the p for?
I understand and have used Inst and call but do not know what they do if p is added.
Hope this is clear enough.

Bill

305

Mach4 General Discussion / Re: Switching from Mach 3 to 4 - How Do You Change Motor Tuning Time

« on: May 12, 2020, 11:10:14 AM »

dmoore,

I really hate to say this but give it a break.
You can clearly see in the graphs the time it takes to accelerate, followed by a max feed followed by a decelerate.
The times are all there.
Who cares if the overall time is 1 sec or 5 sec?

Sorry to be a jerk on this.

Bill

306

Mach4 General Discussion / Re: DRO Units Display scaling Issue

« on: May 08, 2020, 05:42:35 PM »

Good job.
Thanks for the information.

307

Mach4 General Discussion / Re: Transferring to a replacement computer.

« on: April 27, 2020, 05:41:48 PM »

We use laptops with Windows 10.
Inexpensive and have the Ethernet port in them.

308

Mach4 General Discussion / Re: New limit/homing switch settings

« on: April 23, 2020, 11:21:33 AM »

You might have the x and y switched.
When it is looking for the y switch to be triggered the x is being triggered.

309

Mach4 General Discussion / Re: Mach4 in Fusion 360 Post Processor

« on: April 14, 2020, 03:04:23 PM »

Because the same file you would use for Mach3 you can use for Mach4.

310

Mach4 General Discussion / Re: Passing variable for gcode to module

« on: April 13, 2020, 10:56:12 AM »

I found that for me Registers are very useful.


•   How to turn on Registers.
Go to Configure, Control, Plugins tab then place a green check next to Regfile.

•   How to make a new Register.
Go to Configure, Plugins then Regfile.
Click on the green plus sign.
   Give the register a name. (no spaces)
   Give the register a starting value.
   Put in a longer description.
   Persistant
      A green check will keep value on exit from Mach4.
      A red x will start every new start of Mach4 with the starting value.

•   How to read a Register.
local variable = mc.mcRegGetHandle(inst, ‘path’)
local variable2 = mc.mcRegGetValue(variable)
   Examples:
local hreg = mc.mcRegGetHandle(inst, ‘Encoder_0’)
local EncRawVal = mc.mcRegGetValue(hreg)
or
local hreg = mc.mcRegGetHandle(inst, ‘ESS/EncRaw’)
local EncRawVal = mc.mcRegGetValue(hreg)
or
local hreg = mc.mcRegGetHandle(inst, ‘iRegs0/NotchTime’)
local EncRawVal = mc.mcRegGetValue(hreg)

•   How to write to a Register. (this might be wrong)
local variable = mc.mcRegGetHandle(inst, ‘path’)
local mc.mcRegSetValue(variable, value)
or
local variable = mc.mcRegGetHandle(inst, ‘path’)
local mc.mcRegSetValue(variable, tostring(value))
   Example:
local hreg = mc.mcRegGetHandle(inst, ‘ESS/EncRaw’)
local mc.mcRegSetValue(hreg, 23.35)
   or
local Num = 23.35
local hreg = mc.mcRegGetHandle(inst, ‘ESS/EncRaw’)
local mc.mcRegSetValue(hreg, tostring(Num))