Hello Guest it is March 28, 2024, 03:10:07 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 - swolf-sm

Pages: 1 2 »
1
Mach4 General Discussion / Re: Probing, mcCntlGet/SetPoundVar
« on: November 06, 2016, 06:05:25 AM »
Ah..., this explains a lot. Surprisingly once I've done it right it works. Great work.
I quickly added the rapid find (double touch) by inserting two lines in the function TouchOff:
  Code(string.format('G91 G' .. ToffProbeCode .. ' ' .. Axis .. ' ' .. PrepDistance .. 'F' .. ToffPrepRate), true)
  TouchRetract(Axis, Direction * -1)
  Code(string.format('G91 G' .. ToffProbeCode .. ' ' .. Axis .. ' ' .. PrepDistance .. 'F' .. ToffProbeRate), true)

A calibration in my opinion is not necessary. The only thing that you have to know is the diameter of the probe, that can easily be measured with a slide gauge.

In the future I would prefer having the TouchOff UI dialog integrated in the main screen.

Thanks, Steve

2
Mach4 General Discussion / Re: Probing, mcCntlGet/SetPoundVar
« on: November 05, 2016, 02:36:04 PM »
Hello Chaoticone,
I've tried to get the TouchOff module working but I'm not sure if have used it correctly.
What I did:
- edited the screen set wx4.set, at the "Offsets" page I changed the
  clicked script for the "Set Z" button ("--Set Z button") in the way you can see in the attached file SetZButton.txt
- Added the  following settings to machine.ini:
[ToffParams]
ToffProbeRate=100
ToffRetractDistance=2
ToffPrepDistance=15
ToffToolDiam=10
because I need it in the units of millimeters.

To get the function TouchOffZNeg0() in mcTouchOff.lua called from the screen set it needs to be prefixed with "mcTouchOff."
So I got the first move of my probe, but the fixture offsets weren't set.
To find the reason for that I reached the function Code(Gcode, ProbeActive) which I do not understand completely.
I'm sure it should execute "Gcode" and wait until movement is finished.
But what is the purpose  of    
   if (ProbeActive ~= true) then
      ProbeActive = false;
   end
and how is the probe state after the movement (did the probe touch the workpiece?) returned?

At this point I stopped my activities full of self-doubts. When I did all right, when a lot of fixes are necessary to get the TouchOff module running.
Sure, this module is much better structed than the probing mod, and is definitely easier to maintain, but at the moment the probing module does the most things I need.
Steve

3
Mach4 General Discussion / Re: Probing, mcCntlGet/SetPoundVar
« on: November 01, 2016, 12:18:17 PM »
Hallo Chaoticone,
you are right, I have not used the TouchOff module yet, for any reason I was focused on the probe module.
But I will have a closer look at touching, I only not know when; maybe at the weekend.
Steve

4
Sure, I can. http://www.warp9td.com/ is the home page and on http://www.warp9td.com/index.php/distributors you can find a list of distributors.

5
Mach4 General Discussion / Re: Probing, mcCntlGet/SetPoundVar
« on: October 30, 2016, 09:27:41 AM »
Ups,...
of course I want attach the changed file, here it is ...

6
Mach4 General Discussion / Re: Probing, mcCntlGet/SetPoundVar
« on: October 30, 2016, 09:24:17 AM »
Hallo Chaoticone,
it goes very well. The save/restore issue is solved and the function Probing.SetFixOffset in mcProbing.lua now works as expected, thank you.
I did some minor fixes in mcProbing.lua so now probing in all available variations operate excellently as long as G69 (no rotation) is active.

With G68 (workpiece coordinate system will be rotated) a new issue surfaces. The calculation of retract and back move destinations fail.
This is being caused by the fact, that in equations like "RetractPoint = ProbePoint - BackOff" (line 608 in mcProbing.lua), for example, RetractPoint and
ProbePoint belong to different coordinate systems. ProbePoint references the rotated coordinates i.e. the real position of the probe relative to the workpiece origin, and
RetractPoint which is used as the destination in G1/G31 will be rotated again.
I started to resolve this problem in conjunction with the retract moves by replacing the absolute moves by relative (G91G1..) ones,
so probing works now even with very small rotation angles.
For the back moves to the starting positions the solution is not as easy.
That moves still may fail when the rotation angle of G68 is bigger and the probing is not done near the rotation center.
For this I need some more time (or should be done by the developers) and a documention of the #vars would be very helpful.

Steve

7
Hi Beat,
here is the behavior of the watch dog led at my mill:
The led is switched on (lit) as soon as mach4 has been loaded and the screen elements are being loaded. It stays on as long as mach4 is running and no e-stop condition occurs.
The led is off (unlit) when mach4 is not running or the e-stop button connected to the bob is pressed.
In the zip file some screenshots of my config are attached.
Hope this helps, Steve

8
Hi Beat,
I have to press the Enable button once.
2nd --> Disable --> Interface Watchdog is on and Ready
This looks strange: If the machine is disabled the watch dog led should be off, I think.
But I will check this on my mill at the weekend.

Regarding to the output settings: I will make some screenshots, also at the weekend.

Steve

9
Mach4 General Discussion / Re: Probing, mcCntlGet/SetPoundVar
« on: October 26, 2016, 02:40:47 AM »
Thank you very much! I will test it next weekend.
Steve

10
Mach4 General Discussion / Re: Probing, mcCntlGet/SetPoundVar
« on: October 25, 2016, 07:52:46 AM »
Sorry, there is a typo, the following is correct: With an active G54 #4014 in build 2914 is "0.1"  ...

Pages: 1 2 »