Hello Guest it is March 28, 2024, 05:12:24 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 - wilfoude

Pages: « 1 2 3
21
Hello Graham,

Obviously you have taken out the relative coding (G91), which is something I absolutely need. (I make big instrument panels on which I have to distribute holes relative to some origin). However, I tried your code, and this did not show that overshoot. The offset stayed at 2mm precisely. So I toke the relative coding (G91 etc.) out of my own part program and see, the overshoot was still present. Now my problem is not so much "how to get a square", but what is wrong in my coding that produces the effect. I like to learn what faults I made in order to avoid them in future parts. Meanwhile I have produced a number of panels, all with relative coding and tool compensation. None had this problem. (Just the problem with tool comp in subroutines). How did you came to those strange numbers in this line: G00 G90 G43 X2.442 Y-9.085
What is their origin ?
Wilfried

22
I took the G91, G90 ouside the toolcomp part of the program. But still the same results.
Despite I programmed tool T4 to be 4 mm diameter, I once saw the ofset to be 2.9925 mm. I think the program means 3 mm. But it should be 2 mm. Looks like something is not stable here.
Wilfried.

23
Hello Tomi,

Yes the curved entry is a 1/4 circle with a radius of 15 mm. The toolbit is only 4 mm diameter (radius 2 mm).
Wilfried

24
It's some time ago, but I have a new question regarding tool compensation.
I noticed some strange behaviour of Mach3 in a very simple product, so I made a test program. It's just a square of 300*300 mm with rounded corners. When I use a curved entry move (line 3735) to the bottomline of the square, the controlled point makes an overshoot of about 0.1 mm. When I replace the curved entry move by a straight one (line 3735), it works OK. In this test example, with a tool of 4 mm, the controlled point should move at -2.0 to draw the bottom line. This line however is drawn at -1.950, with an overshoot to -1.920. Does anyone have any idea what causes this error ?
Other part programs I made using tool compensation don't show errors (as far as not used in subroutines).
Best regards,

Wilfried

25
This is nice to know, but how do we know whether Art soft is going to fix this problem?
I have noticed that Mach3 is widely used and appreciated, even in professional applications, so I'm very surprised that Mach3 can't cope with this toolcompensation in sub's. I also can hardly imagine I'm the only one who stumbles over this item.

26
General Mach Discussion / Re: What does the "To Go" button do?
« on: November 28, 2010, 08:09:24 AM »
Many thanks Hood. This is crisp and clear.
Wilfoude

27
OK, I now understand that toolcompensation does not work in a sub. But is this something that will be corrected, or do we simply have to accept that it simply is not working? I think subs are the best way to deal with repeated structures in a design.
My first product was an aircraft instrument panel with a lot of the same instrument holes. It was very annoying I could not use subs to cut those holes.
Wilfried.

28
General Mach Discussion / Re: What does the "To Go" button do?
« on: November 28, 2010, 05:01:22 AM »
Hello Everybody,

Despite the answers given in this topic, me too, I still don't know what to "Go to" button is meant to do.
Can anyone explain ?

29
That sounds a bit cryptic What exactly do you mean by that ?

30
G-Code, CAD, and CAM discussions / Mach3 and code G41/G42 in subroutines
« on: October 26, 2010, 02:46:45 PM »
I am a newbie to Mach3 and try the master it. I needed to make a number of 80 mm diameter holes in an instrument panel. So I made a subroutine with tool compensation to produce the holes. This worked fine for only the first hole, but the next holes are totally screwed up. It is as if in each consecutive call to the sub, the sub is partly switching back to the first hole. It works OK without the tool compensation. It also works when the code producing the hole is repeated for each and every hole. But that is bad practise, increasing code size.  Who can help me to make that sub working ?

Newbie Wilfried

Pages: « 1 2 3