Messages

11

Mach4 General Discussion / Re: Probing, mcCntlGet/SetPoundVar

« on: October 24, 2016, 03:12:26 PM »

Thank you, Chaoticone, these informations are most welcome.

Of course I can fix the lua script, but relating to #4001 and #4003, in my opinion a save and restore of a variable shall not change the value of that variable. In this case I presume the bug is located in the mach kernel itself. So "mc.mcCntlSetPoundVar(inst, 4003, CurAbsMode *10)" would fix the symptom and solves my problem with the build I use, but doesn't fix the bug itself.

Var #4014 is a different kettle of fish. With an active G54 #4014 in build 2914 is "1" and in build 3208  #4014 is equal to "54". So it looks like a different interpretation of the value. If this change is permanent the lua script has to be adapted. For this it is very usefully to know something about  the meaning of the #vars. Do you, or someone else, know whether and where the #vars are documented?

Steve

12

Mach4 General Discussion / Re: Enable my interface with a Wachdog Signal? Possible?

« on: October 24, 2016, 02:09:26 PM »

Hi beat,
I don't know. Indeed, I use the same breakout board (BOB) but I have sitting the Ethernet Smooth Stepper (ESS) between the PC and the BOB. As far as I know the ESS generates the charge pump signal by itself.
After hardly trying to remember what I did a year ago I come to the result that I never have checked whether the Charge Pump LED at the BOB follows the Enable/Disable button at mach4.
I installed and tested the hardware using mach3. The BOB is located in a control cabinet and this is closed since then, even after the upgrade to mach4.

Hope this helps, Steve

13

Mach4 General Discussion / Re: Enable my interface with a Wachdog Signal? Possible?

« on: October 24, 2016, 07:29:20 AM »

Did you remove the jumper JP2 from your "interface advanced Pro" according to page 7 of the linked manual?

14

Mach4 General Discussion / Probing, mcCntlGet/SetPoundVar

« on: October 23, 2016, 05:38:31 AM »

Hallo everyone,

I try to get probing working in mach4.2.0.2914 (screen wx4.set) with basic success.
But after each "Probing->Single Surface->Measure X" for example the "Go To Work Zero" at "Program Run" does not work any more.
The reason for this is that the values of the registers #4001 and #4002 are divided by 10 witch each call to
CurAbsMode = mc.mcCntlGetPoundVar(inst, 4003) and mc.mcCntlSetPoundVar(inst, 4003, CurAbsMode).
Is this a bug or a feature ?

Build 3208 has the same behavior at this point.
Additionally in build 3208 the probing failed because the new calculated offsets are not correctly stored in the #vars.
Apparently the meaning of var #4014 has changed and function Probing.SetFixOffset in mcProbing.lua should be adapted.
Can somebody confirm this?

Thanks, Steve