Messages

51

General Mach Discussion / Re: Slave A & X problems.

« on: December 01, 2006, 06:04:07 PM »

Hi,

Thank you for help. I discovered the problem. First of all, those circles came from the fact that in General config the IJ Mode was on Inc. I checked on Absolute and the circles disappeared. The problem with stops and no running of file came from the fact that backlash was enabled. It seems that backlash is not working on slave setup, or on other words if it is enabled it makes impossible to run a file in slave mode. I fix these two issues and now Mach3 is working OK in the slave mode.

Zoltan

52

General Mach Discussion / Re: Slave A & X problems.

« on: November 29, 2006, 03:31:37 PM »

Hi,

This is the file.

Thank you.

Zoltan

53

General Mach Discussion / Re: Slave A & X problems.

« on: November 29, 2006, 04:58:02 AM »

Hi,

I have also a problem with slaving as it is first time for the new machine I just built with two racks & pinions on axis X. I have cloned a profile of 3 axis machine which is working great. On the clone I added a new axis A with port, step, dir and slaved at X, and rotating unchecked. I restart and tuned the same X and A axis. The machine is working great on jog, but when I open any Gcode file (i.e. any old file which I have used on 3 axis machine, and it worked) the display is showing a lot of circles the machine is trying to cut and also it stops for tool changing. After reset is says it initializes the tool change macro. I did no do other change to the clone. After I "change the tool" it works but is stopping without reason in the middle of cutting. As I said I used the clone of a working profile and just added the slave axis, no other change. If I close the slave axis profile and open the original 3 axis profile, the same file opens correctly without those circles and without tool change request and without any initialization after reset, and it works OK. Please, help me understand what I did not do or what I can do.


Thanks.

Zoltan

54

LazyCam (Beta) / Re: LazyCam ver 2.64 and G(Mode) generation of G41, G42

« on: October 26, 2006, 01:52:58 AM »

Hi Brian,

Please, take a look at LazyCam 2.66 as it does not work on Vdrill. It crashes each time.

Thank you.

Zoltan

55

LazyCam (Beta) / Re: LazyCam ver 2.64 and G(Mode) generation of G41, G42

« on: October 24, 2006, 02:40:19 AM »

Hi Brian,

No news?

Thank you.

Zoltan

56

LazyCam (Beta) / Re: LazyCam ver 2.64 and G(Mode) generation of G41, G42

« on: October 13, 2006, 05:11:27 AM »

Hi,

I got Lazycam 2.66 with the newest version of Mach3, but when I tried Vdrill, after I open the bmp during conversion it gets blocked. I could not make it works during several trials. With the same setting - pixels, size, pixel size, number of dots, etc the previous 2.64 is doing the conversion really fast.

Thank you,

Zoltan

57

LazyCam (Beta) / Re: LazyCam ver 2.64 and G(Mode) generation of G41, G42

« on: October 11, 2006, 03:53:51 AM »

Hi Brian,

Any updates?

THank you.

Zoltan

58

LazyCam (Beta) / Re: LazyCam ver 2.64 and G(Mode) generation of G41, G42

« on: October 03, 2006, 08:12:45 AM »

Brian,

I really think that we must focus little bit on this feature of Lazycam as this is a very potential feature of it. Just imagine that converting a regular CNC machine into an impact engraver would be very easy with the help of Lazycam and Mach3. Just a replacement of Z axis with that electromagnetic hammer - which is a small electromagnet with a plunger with carbide tip. Everything what Metaza is doing can be done very very easy. I have done already this. The issue is only the speed of process.

Zoltan

59

LazyCam (Beta) / Re: LazyCam ver 2.64 and G(Mode) generation of G41, G42

« on: October 03, 2006, 08:07:45 AM »

Hi Brian,

Thank you for reply. I think it is a matter of using/setting up of it. Let me explain to you. I open the bmp in Lazycam and generate the Gcode for the lowest grid value accepted by program (btw if I try to setup a lower value that the lowest accepted then the program is blocking). I define a value for feed let's say F3000 when I generate the Gcode. I open the Gcode in Mach3 or in a simulator program and the value of speed between two dots during the engraving or simulation is not bigger than 30-40 mm/min despite the maximum value setup in the tuning of motors and whatever value of acceleration. The idea is to change this value higher than 30-40 mm/min. BTW I am speaking about V-dril process. If you give a trial of doing from bmp a V-dril engraving you will see exctly what I mean.

Thank you.

Zoltan

60

LazyCam (Beta) / Re: LazyCam ver 2.64 and G(Mode) generation of G41, G42

« on: October 03, 2006, 02:46:57 AM »

Hi Brian,

Regarding LazyCam I have tried something similar to Metaza machine from Roland - impact printer. I modified a cnc machine and instead of Z axis I have replaced with an electromagnetic plunger which is hammering each dot times corresponding to Z depth. Everything is going superb except the speed which is very slow around 30-40 mm/min, between dots. The rapid is around 5000 mm/min. I mention that there are no limitations of the machine in the respects of speed & acceleration. Could you, please, help to modify the speed? How I can change the speed between dots? It is not a matter of machine; it is a setting matter as during the simulation is the same speed. If the speed can be changed (I did not figure out how) then we can do the same things as Metaza is doing, but on regular CNC with electromagnetic plunger instead of Z axis assembly. I have already produced some photoengraving and the quality is very good but the time is too long due to low speed.

Thank you.

Zoltan