Hello Guest it is October 03, 2023, 04:49:53 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.

Messages - rhtuttle

General Mach Discussion / Re: Access to maintenance parameter values
« on: March 17, 2017, 10:48:35 AM »
start a support ticket and see what happens, worth a try.

General Mach Discussion / Re: Access to maintenance parameter values
« on: March 16, 2017, 02:53:54 PM »
AFIK all work on M3 has stopped.  I would bet there is a list somewhere at NewFangled that includes all GetParam strings.  You might try posting a PM to Art Fennerty.  http://www.machsupport.com/forum/index.php/topic,27194.0.html


Mach4 Plugins / Re: Mach4 Plugin-Development
« on: March 15, 2017, 03:42:32 PM »
Their standard policy is that they only provide that for hardware plugins.  Everything else you modify or create lua scripts.

General Mach Discussion / Re: Simple Draw test??
« on: March 15, 2017, 03:38:57 PM »

General Mach Discussion / Re: Access to maintenance parameter values
« on: March 15, 2017, 10:15:28 AM »
In the turn xml there are entries for dist0 to dist5, I assume those are axis xyzabc.  Mine have values for 0,2,3 which would correspond to x,z,a which I have.

There is also a SecondsOn value which I presume is what is retrieved with the TotalHours param.  I couldn't find anything else on the subject.

Mach4 General Discussion / Re: G31
« on: March 15, 2017, 09:40:01 AM »

Ran straight from the MDI:

g1 x.4 f.5
g1 x.3

ran 10 times and the positioning was unchanged

ran straight from the mdi:

g31 x0 f.5
g1 x.3

Ran once and hung until I pressed the stop button

Ran straight from the mdi:

g1 x.3
g31 x0 f.5

ran 5 times and each time the x.3 was closer to the centerline by approx .008



Mach4 General Discussion / G31
« on: March 14, 2017, 04:27:43 PM »
Thought I would measure to see what kind of consistency I was getting from my probe strikes.

I put the following code in a button:

 mc.mcCntlGcodeExecuteWait(inst,'G31 X0 F0.5')  -- First slow strike
 mc.mcCntlGcodeExecuteWait(inst,'G01 X.3 f0.5')
 mc.mcCntlSetLastError(inst,string.format('%1.4f : %1.4f : %1.4f',r1,r2,r1-r2))

The difference between the position in the dro and the probe strike position is consistently .0080 or .0079

While probing the dro's don't change at all, is that how it should be?

Each time I execute it the positions change:

.1958 : 0.2037 : -.0080
.2036 : 0.2037 : -.0080    - creep of 0.0078
.2115 : 0.2195 : -.0080    - creep of 0.0079

Each time the probe beginning position is closer to the contact position even though I start at .3 and return to .3

Its as if the machine position is adjusting automatically for the difference in strike versus end.  Is it supposed do that?

I have checked my couplings and they are secure and I don't believe I am losing steps.

I am using pmdx411 and their plugin is fairly new and I am using it with m4turn.

Before I go to the pmdx forum I want to confirm that this is not normal behavior.



Mach4 General Discussion / Re: Mach4/Lua script do's and Dont's
« on: March 13, 2017, 05:42:40 PM »
I don't believe that is going to work either.  mdiExecute will only execute lines of gCode/mCode and returns immediately before the code is fully executed.  If I want to get the result of a probe I can't do that until the strike has occurred.  It seems we are back to the old while isMoving() sleep for a while except we don't have that function anymore.

Does the mcCntlIsInCycle work for files only or mdi and macro calls to execute gcode?

Mach4 General Discussion / Re: Mach4/Lua script do's and Dont's
« on: March 13, 2017, 05:10:04 PM »
Hi Daz,

Yes, the module does actually load, I am able to call the rtAudio and the rtCountDown through m calls so I know the module is loaded, and the call to rtProbeX actually issues the first g31 'Quick Strike' and backs off and then hangs.  No movement after that.  If I wait and press stop I would actually get a lasterror displayed, before I commented them out.  

Just saw Chaoticone's response.  Not able to use GcodeExecuteWait.  I'll try gCodeExecute unless he tells me that's a no-no too.