Machsupport Forum

Mach Discussion => Mach4 General Discussion => Topic started by: daniba73 on December 24, 2019, 03:04:08 PM

Title: Cycle G83 in the Lathe version creates a collision
Post by: daniba73 on December 24, 2019, 03:04:08 PM
I discovered that there is a bug in the lathe version, regarding the G83 cycle.
The instrument collides for a few tenths of a millimeter (about 0.3) with the material at each stroke.
This defect appears only in the version of the lathe, because in the mill I have not encountered such behavior.
Can anyone check?
thanks and sorry for bad english, i use google translate.
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: Graham Waterworth on December 24, 2019, 07:35:26 PM
Is the collision when the tool returns to the last depth ready to do the next peck cut?
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: daniba73 on December 25, 2019, 02:13:06 AM
I give an example:
G0 X0 Z1 (positioning in the instrument in rapid)
G83 Z-20 R0 Q5

Z-20 (total hole depth)
R0 (quick start position, setting value 0 will use Z1 as start)
Q5 (will make cuts 5 mm deep, to then exit the piece)

the first cut will be +1 (Z1) -5 (Q5) = Z-4
Arrived at the instrument Z-4 must go out (and this works correctly)
the problem in which it collides is the return!
in theory the rapid repositioning should stop about 0.25 mm before (therefore Z-3.75 )
Instead it goes beyond the last depth of cut (Z-4) !! it positions itself in rapid at about Z-4.3 !! then collides about 0.3 at each step !!

It practically reverses the calculation! instead of subtracting it!
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: daniba73 on December 27, 2019, 06:54:35 PM
I made a mistake writing in the gcode.
now I correct it.

G98
G0 X0 Z1
G83 Z-20 Q5 R1 F50
G80 G0 Z1
M30
;

the behavior is however as described, first lunge in Z-4
and in the version of the mill it is correct.
in the lathe version with the same code g the first cut is Z-3 !!!
wrong calculations !!!! generate collisions !!!
I also found anomalies with the G84 G84.2 cycles
the G76 cycle is also of mediocre quality.
am I the only one to find anomalies?
I want to understand if I'm making mistakes ??
none of you are detecting abnormal behavior?
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: rhtuttle on December 28, 2019, 11:54:39 AM
Which motion controller are you using?
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: daniba73 on December 28, 2019, 12:31:33 PM
use the CSMIO / IP-S controller of CsLab.
I spent about 1400 euros between ardware and Mach4 license (not to mention the servo ac drive kit) and I have a mediocre system! : - [
what makes me angry is that with Mach3 it works well (although I don't like it because of the slow response times to the potentiometers).
Mach4 immediately fascinated me! so I immediately bought a license.
But to be honest, my problems have really started since I installed the Mach4 lathe.
I love it because I like it! but I often hate him for the problems he has!
4 or 5 years after its release it should be perfect or almost perfect !!

Poor plug-ins are often the cause, although manufacturers are reluctant to admit their limitations or mistakes.
except for the G83 which is an obvious Mach4 error, for the G84 and G76 cycles I think the cause is the plug-ins, I can't be sure because I'm not a technician, but a mechanic (each his job) so I can only hypothesize without certainties.
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: rhtuttle on December 28, 2019, 01:24:37 PM
Hopefully Brett or Steve will chime in and comment on whether g83 is vendor driven or mach4.
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: Graham Waterworth on December 28, 2019, 01:31:10 PM
It has been passed on to technical for there comments.  May be a few days due to holiday.
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: daniba73 on December 28, 2019, 04:08:29 PM
thanks, I had already notified parallel to the mail of the problem.
we hope they solve the problem.
I find that Mach4 is an exceptional program! deserves to work perfectly !!
I obtained splendid finishes thanks to the perfect functionality of the constant cutting speed !! thing unattainable by Mach3 !!
Come on Mach4 !!
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: daniba73 on January 08, 2020, 05:09:40 AM
At the moment still no answer.
in the meantime, none of you have done a test?
only I in the whole forum have this problem?
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: rhtuttle on January 08, 2020, 01:48:58 PM
I can confirm g83 exhibits odd behavior, I'm using with pmdx411 controller.

RT
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: daniba73 on January 08, 2020, 03:54:11 PM
thanks for participating.
it's not just strange.
tool collides rapidly when returning to the hole.
even the G84 has strange and unpleasant behaviors, rather often it makes sudden uncontrolled shots.
If the G76 cycle is repeated several times, even without any modification or tool correction, it will ruin the created thread.
I really like Mach4! therefore I want it to work perfectly!
because remember that Mach4 is not a videogame, it is a controller of machine tools !!
and repeat.
I have no skills and knowledge to judge who the cause is.
Mach4 or the plugin.
I am a mechanic with a passion for cnc machines.
the only thing I know is that after spending about 1400 euros between only controller and license I expected much more.
said I don't rule out my sub-optimal settings.
for this reason I wanted to compare the results of these tests with other forum users, to understand and understand better.
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: joeaverage on January 08, 2020, 04:18:13 PM
Hi,

Quote
the only thing I know is that after spending about 1400 euros between only controller and license I expected much more.

You bought an expensive controller without doing your homework, CSLabs support for Mach4 and their customers has taken a dive.

Craig
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: daniba73 on January 08, 2020, 04:22:30 PM
please explain yourself better.
I have to use Google translate.
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: joeaverage on January 08, 2020, 04:53:31 PM
Hi,
CSLabs have not been very proactive in correcting their Mach4 plugin for their controller.

CSLabs are trying to promote their own software and have largely ignored Mach4. It has taken over a year for a plugin update
and it still doesn't address all the bugs. For 600 Euro I think that's pretty poor, in fact that sounds like a Chinese rip-off to me.

Craig
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: Graham Waterworth on January 08, 2020, 08:20:58 PM
I am told by technical that the issue has been resolved ready for the next update.
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: daniba73 on January 09, 2020, 12:32:47 AM
thanks for the support you are exceptional!
now I want to understand who is responsible for the G76 and G84.
the plugin or Mach4?
on the G84 I convinced a friend to purchase a new license for Mach4. as controller it has analog CSMIO IP A because it has adapted a CNC milling machine.
this G84 works very badly and I feel a little guilty for having convinced the friend, considering that he spent even more.
on the issue that they are focused on developing their software, they are not to blame, it is their commercial choice.
however if you tell me that it is compatible with Mach4, it must be perfectly! because the money we paid was valid.
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: joeaverage on January 09, 2020, 12:55:44 AM
Hi,

Quote
however if you tell me that it is compatible with Mach4, it must be perfectly! because the money we paid was valid.

That is rather the point, they claim to have a working Mach4 solution, and it must be said its not bad but it is far from
perfect. I doubt in fact if there is ANY controller that could be deemed perfect however there are a number that do a
better job the CSMIO. This is a great pity because CSLabs had a very VERY good reputation for quality, functionality
and support. The quality remains but the functionality lags behind others and support sucks. They also demand quite
a premium for their product....could you be satisfied?.

Quote
now I want to understand who is responsible for the G76 and G84.
the plugin or Mach4?

I cannot answer that, as in a lot of realtime ops, drill cycles included, it is a co-operative venture between the motion controller
and Mach4. It may be that there is fault on both sides. The fact that RT concludes as you do but with a different motion controller
suggests that Mach4 is at fault.

Perhaps someone from NFS would like to explain, at least in general terms, whats going on.

Craig
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: daniba73 on January 09, 2020, 02:05:37 AM
my friend has just informed me that he has received a response from cslab.
CSMIO IP A does not currently support G84 with Mach4.
they don't know for sure if it can be done, they have to investigate.
they informed that the rigid tapping feature works perfectly with Mach3 and their M84 macros available on their website.
this answer left us with a bitter taste.
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: smurph on January 13, 2020, 05:20:33 PM
Build 4369 addresses the G83 issue. 

G84 is regular right hand tapping meant to be used with a floating tap holder.  G84.2 (RH) and G84.3 (LH) are the rigid tapping variants. 

G84 and G74 can be turned into rigid tapping cycles by issuing a M29 prior to the call to G84 or G74.  G80 is the antidote to M29, so after a G80, M29 will need to again be called before G84 or G74 to rigid tap.

G84/G74 should be supported by all motion controllers because there are no real time requirements.  You will need a floating tap holder.  Rigid tapping, on the other hand, does have to be supported by the motion controller.  Not all motion controllers support rigid tapping (and possibly lathe threading), so it is prudent to check with the manufacturer of the controller to make sure it is supported if you need that feature. 

Steve
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: daniba73 on January 16, 2020, 04:48:23 AM
I uploaded version 4369.
in device mode it works perfectly.
the problem is when I use it with the CSMIO.
does not perform any processing.
I read a message from Mach4 respective to a parameter 1801 which is equivalent to zero.
I think it's a plugin problem.
I honestly have not yet figured out who should control, the plugin or Mach4 ??
Title: Re: Cycle G83 in the Lathe version creates a collision
Post by: daniba73 on January 16, 2020, 06:15:34 AM
I solved the problem of the G83 empty thanks to this link:

https://www-cncsteuerung.gitbook.io/docs/mach4-software/bekannte-meldungen/parameter-fehler/1801


super Mach4!!!!!! GO!! GO!!! GO!!!!