Hello Guest it is March 28, 2024, 07:05:15 AM

Author Topic: Serious problems with G76 cycle in Mach4 Lathe and CSMIO IP S  (Read 5249 times)

0 Members and 1 Guest are viewing this topic.

Re: Serious problems with G76 cycle in Mach4 Lathe and CSMIO IP S
« Reply #10 on: January 22, 2020, 02:23:35 AM »
hi, try to understand, i use a translator to read and write, sometimes some sentences are diverted.
Yes, I contacted the helpdesk.
if I have to be honest, I have more faith in you.
I will explain why.
up to now I have used the helpdesk service twice.
the first time about 1 year ago.
I had already warned of the collision problem of the G83.
answered a boy or a girl, now I don't remember well. saying it was not entirely clear what the G83 was doing.
I didn't answer anymore.
The second time I asked how to create macros for the mechanical range.
their response was to use M40 etc. etc. that I had to create it myself or ask on the forum.
Re: Serious problems with G76 cycle in Mach4 Lathe and CSMIO IP S
« Reply #11 on: January 22, 2020, 02:37:01 AM »
in a virtual way I tried to make a thread using the G32 to understand who makes mistakes in the trajectories, Mach4 or plugins.
from video graphic everything seems ok.
as soon as possible I will make a test piece using this method.
the result should bring to light those who make mistakes.

Offline Tweakie.CNC

*
  • *
  •  9,196 9,196
  • Super Kitty
    • View Profile
Re: Serious problems with G76 cycle in Mach4 Lathe and CSMIO IP S
« Reply #12 on: January 22, 2020, 02:43:41 AM »
Please contact the help desk by email. http://support.machsupport.com/en
Please describe the problem in as much detail as you can.

Mach4 is a fully supported product, the help desk is there to specifically help resolve any problems users may have with Mach4.

Please accept my apologies for being blunt in my earlier posting, I had not realised you were using a translator.

Tweakie.
PEACE
Re: Serious problems with G76 cycle in Mach4 Lathe and CSMIO IP S
« Reply #13 on: January 22, 2020, 03:11:51 AM »
do not worry.
I usually always notice when I start a post that I use a translator.
I am on your side.
I love Mach4!
I convinced 3 friends to buy a license.
it's beautiful software! and I want it to work as it deserves, which is why I am working hard to find the problems.
P.S. when I get the test result with G32 I will contact the helpdesk if necessary.
I must first understand who is wrong.
Mach4 or plugin.
Re: Serious problems with G76 cycle in Mach4 Lathe and CSMIO IP S
« Reply #14 on: January 26, 2020, 06:47:30 PM »
Update the post with the results of various tests.
these were performed on 2 different lathe, mine and that of a friend (one of those that I convinced to purchase the Mach4 license).
the 2 machines have the same hardware and software. (his has more power).
mine has a unique range.
his has mechanical reach.
we are waiting for a response from cslab regarding the topic described at the beginning of the topic related to errors in the feed during the thread.
we tried the thread with G76 and G32.
The result is the same.
if you run the thread in a loop, it is not the best, but it is acceptable.
if the cycle is repeated, both empty and with correction on the measurements, the wire is slowly damaged.
as already said, we are waiting for an answer.
I will keep you informed.

Offline Tweakie.CNC

*
  • *
  •  9,196 9,196
  • Super Kitty
    • View Profile
Re: Serious problems with G76 cycle in Mach4 Lathe and CSMIO IP S
« Reply #15 on: January 27, 2020, 05:42:37 AM »
Hi Daniba73,

Judging by the serious lack of response to these postings I have a feeling that, sadly, you are the only person here that is threading with Mach4.  :'(

I look forward to hearing about your latest testing.

Tweakie.
PEACE
Re: Serious problems with G76 cycle in Mach4 Lathe and CSMIO IP S
« Reply #16 on: January 27, 2020, 06:32:22 AM »
Start off topic.

The real rival of Mach4 that blocks sales and development is Mach3 itself.
we face reality.
Mach3, although long-standing, still works quite well, although it is now never weak.
Mach3 has become a free program, given the countless bogus licenses that run on the web.
Users are unlikely to switch to Mach4 for this cause.
in my opinion if they want to stop it, they should remove Mach3 from their site.
Mach4 has if it works perfectly, it would have no equal, I am convinced!

end of topic.
Re: Serious problems with G76 cycle in Mach4 Lathe and CSMIO IP S
« Reply #17 on: January 28, 2020, 02:01:50 AM »
for the tests we also tried with a parametric program (made by my friend).
The purpose of this program was to exclude Mach4 for thread calculations.
he only had to carry out the instructions provided by mathematical calculations.
some past emails, cslab told us that the trajectories are calculated by Mach4, CSMIO just needs to synchronize (and here it does it well, because we tried to disturb the rotation of the spindle with a wooden rod while running the wire, and not lost the pace despite revolutions that varied by about 10 or 15 shifts).
nevertheless, if the thread was passed over again, the thread was slowly damaged.
we evaluated the conditions:
the defaut lathe has trapezoidal belts between the engine and gearbox.
the trapeze belts, as is known, have oscillating rotation.
since turns oscillate for that cause, we have deduced that for the calculations a certain number of turns is taken into consideration, and the thread is valid.
the cycle is repeated, and due to oscillation (given by the trapezoid) another rpm value is taken.
by varying the turns the calculations also vary.
and this could be the cause.
ArtSoft and CsLab should communicate well how to solve the problem.

unfortunately now my friend has influence.
as soon as it heals, we run the tests again and insert the images of the results.
I attach the parametric program.

%
O1
(............................................)
(.........INIZIO DATI DA INSERIRE............)
(............................................)
T202 (FILETTATORE, INTERNO o ESTERNO)
G97 S500 M3
G99
G61
(............................................)
#101=10 (POSIZIONAMANTO..Z..)
#102=105 (POSIZIONAMENTO..X..)           
#103=100 (DIAMETRO INIZIO FILETTO)
#104=97.4 (DIAMETRO FINE FILETTO)
#105=1 (  1 FILETTO ESTERNO     -1 FILETTO INTERNO )     
#106=12 (NUMERO PASSATE)
#107=0.02 (SOVRAMETALLO PER FINITURA SUL DIAMETRO)
#108=1 (PASSATE DI FINITURA. MINIMO 1)
#109=1 ( 0 INCREMENTO RADIALE   1 INCREMENTO X/Z+  -1 INCREMENTO X/Z- )
#110=30 (ANGOLO DI ENTRATA FILETTO)
#111=30 (..Z.. FINALE. METTERE VALORE SENZA SEGNO)
#112=2 (PASSO FILETTO)
(............................................)
(.........FINE DATI DA INSERIRE............)
(............................................)
%
#120=[#103-#104-#107] (METALLO DA ASPORTARE)
#121=[#120/#106] (INCREMENTO IN X)
#121=[#121*#105]
#122=TAN[#110]
#123=[#121/2] (INCREMENTO Z)
#123=[#123*#122] (INCREMENTO Z)
#123=[#123*#109] (INCREMENTO Z)
G0 Z#101 (POSIZIONE INIZIO PROGRAMMA)
G0 X#102 (POSIZIONE INIZIO PROGRAMMA)
#130=#103 (NUOVO VALORE PER SOTTOPROGRAMMA IN X)
#131=#101 (NUOVO VALORE PER SOTTOPROGRAMMA IN Z)
M98 P2 L#106
G0 Z#101 (POSIZIONE INIZIO PROGRAMMA)
G0 X#102 (POSIZIONE INIZIO PROGRAMMA)
#140=[#103-#104] (INCREMENTO Z FINALE)
#140=[#140/2] (INCREMENTO Z FINALE)
#140=[#140*#122] (INCREMENTO Z FINALE)
#140=#101-#140 (INCREMENTO Z FINALE)
M98 P3 L#108
G0 Z#101 (POSIZIONE INIZIO PROGRAMMA)
G0 X#102 (POSIZIONE INIZIO PROGRAMMA)
M30
;

%
O2
#130=[#130-#121]
#131=[#131-#123]
G0 X#130 Z#131     
G32 Z-#111 F#112
G0 X#102
G0 Z#101
M99


%
O3
G0 X#104 Z#140
G32 Z-#111 F#112
G0 X#102
G0 Z#101
M99
;
« Last Edit: January 28, 2020, 02:07:06 AM by daniba73 »

Offline RICH

*
  • *
  •  7,427 7,427
    • View Profile
Re: Serious problems with G76 cycle in Mach4 Lathe and CSMIO IP S
« Reply #18 on: January 28, 2020, 07:34:17 AM »
daniba,

I will post a few "simple" tests that you need to do. Leaving for a trip very shortly.
I'll post them when I get back in a few days.

Till then,
RICH
Re: Serious problems with G76 cycle in Mach4 Lathe and CSMIO IP S
« Reply #19 on: January 28, 2020, 09:45:05 AM »
Thanks for your interest.
I will also run your tests.
although I believe the problem has been identified on the issue of recovering the damaged thread.
example.
suppose we have a G97 S500 M3
due to the oscillation this value oscillates between 500 and 505 rpm.

when the thread cycle starts, Mach4 will draw on one of those values to perform trajectory calculations.
the thread is working properly.
now you have to repeat the cycle to reach the correct size.
start the spindle and repeat threads.
but due to the swing this time it generates a trajectory based on 505 rpm.
inevitably the newly created thread will be damaged.
now it's up to ArtSoft and CsLab to find a solution.