Messages

11

General Mach Discussion / Re: Fast Z on 2.5D machine

« on: November 06, 2006, 09:23:43 AM »

I think this is an input parameter...
I have both "debounce interval" and "index debounce" set to 0 (zero).

12

General Mach Discussion / Fast Z on 2.5D machine

« on: November 06, 2006, 02:08:57 AM »

I am using M functions to activate and deactivate an output (output4) in my 2.5D machine. Everything works fine but there is a delay of some milliseconds (>350ms) from the execution of the M function to the next G command and from a G command to a M function.

Sample code:

N0440 X153.8415 Y44.6080 I5.1038 J-3.4409
N0450 X92.5577 Y69.9926 I-39.1988 J-7.9659
N0460 X90.8241 Y61.4619 I3.3986 J-5.1321
N0470 M17<----------------------------------------------------- (machine stops, M function deactivates output after some ms)
N0480 G00 X131.1282 Y101.9559
N0490 M18<----------------------------------------------------- (M function activates signal but the movement starts after a while)
N0500 G01 X104.6245
N0510 X123.8448 Y121.1526
N0520 X127.6986 Y126.9220
N0530 X129.6661 Y130.8300

M17 code:
DeActivateSignal(Output4)
M18 code:
ActivateSignal(Output4)

There is a liquid running from the .5 axis and as a result of the delay I get a big dot in the beginning and in the end of the contour.
Do I need a faster PC?

Because I had to modify the hardware and the postproseccor I did not try the "Z is 2.5D on Output #6" on config->state... window. Do you thing that it will make any difference?

What else do you recommend?

Thank you

13

General Mach Discussion / Re: stop waiting G4

« on: July 26, 2006, 02:51:27 AM »

Sorry for not making myself clear.

I use a DRO with dwell time. Instead of M3 I use M18. I do exactly what you said and it is ok.
Your M3 is

preheat=getuserdro(1000)
DoSpinCW()
code ("G4 P" & preheat)

My M18 is

b=Timer()
setuserdro(1002,b)
preheat=getuserdro(1000)
ActivateSignal(Output4)
code ("G4 P" & preheat)

The only difference in that you use DoSpinCW() and I use ActivateSignal(Output4). I also use userDRO 1002 as a public var to store the exact time that preheat was started. I want this time because I have a button with the following script.

c=Timer()
totaltime=(c-getuserdro(1002))
setuserdro(1000,totaltime)   
dooembutton(1000)   

When the user presses THE button during waiting time (dwell) I calculate the "totaltime" var which is the time from the beginning of the preheat and the time THE button is pressed. Then I store this time to the userDRO 1000. This time will be used the next time from M18.

ALL these works fine.

The problem I have is with the DoButton(0) and the equivalent DoOEMButton(1000).

During dwell (G4 Psomething) time you can cancel waiting by pressing the Run button. I put dooembutton(1000) in my button so after the calculation of totaltime the movement to be start. This also works well in all occasions except form one. I have to explain it to you with a small example

N01 G00 X100 Y100
N02 M18
N03 G01 X250 Y200 F3000
N04 M17
N05 G00 X200 Y100
N06 M18
N07 G01 X350 Y200
N08 M17
N09 ....

I have the script editor open with the script of THE button. I press the green play button inside the editor during dwell time in line N02 and it work fine.
I also press it during N06 line and it also works fine. Now I close the editor window.
If I press THE button during N02 "totaltime" calculations are done well but the movement is not G01 X250 Y200 F3000 it is G01 X200 Y0 F250.  (Feedrate is the X, X is Y and Y is 0)
If I press the button during N06 then everything is OK. It is OK even if I had already pressed THE button once in N02 or for the first time.

I am again very sorry for not making myself clear. Maybe is my English. It is not my mother language.
Bye from Greece

Thanx

14

General Mach Discussion / Re: stop waiting G4

« on: July 25, 2006, 06:04:01 AM »

It is exactly what is being discussed here

http://groups.yahoo.com/group/mach1mach2cnc/message/25060

Thanx

15

General Mach Discussion / Re: stop waiting G4

« on: July 24, 2006, 04:44:55 AM »

I also found out the "no sense" movement. In G is

G01 X119.7404 Y112.9179 F180.3516

which is not so much "no sense".

Normal line is
G02 X180.3516 Y119.7404 I-67.4337 J0.0000 F3000.0

Y gets X
I gets Y (180.3516-67.4337=119.7404)
and X get F

I though that while N0150 is the first "cutting" line a problem occurs. So I put a G01 F3000 in the beginning but it did not work.

I am very sorry for bothering you so much

Thanx

16

General Mach Discussion / Re: stop waiting G4

« on: July 24, 2006, 04:20:43 AM »

Here is the button script

c=Timer()
totaltime=(c-getuserdro(1002))
setuserdro(1000,totaltime)   
dooembutton(1000)   

1002 userDRO is the time from the beginning of the preheat. I use M18 to fill 1002 up.

b=Timer()
setuserdro(1002,b)
preheat=getuserdro(1000)
ActivateSignal(Output4)
code ("G4 P" & preheat)

totaltime is the the xx (G4 Pxx) time
dooembutton(1000)=dobutton(0) I think. I tried them both.

As I have described when I use the normal Run button it stops waiting and continue with next line. When I use this button the calculations in the first 3 lines are done correctly but then the feedrate gets equal to Xposition and it moves to a no sense place. When it reaches that place it continues as if it has done next line.
Appart from the fact that if I have open the script editor and I "play" the script from within the editor, it works fine, it works fine the for the second or third curve.
For example:

N0000 (Filename: Drawing1.tap)
N0010 (Post processor: Copy of Mach2.post)
N0020 (Date: 24/7/2006)
N0030 G21 (Units: Metric)
N0040 G40 G90
N0050 F1
N0060 (Part: Drawing1)
N0070 (Process: No offset 0, Mill/Router, 0,1 mm diameter, 0 mm Deep)
N0080 M6 T0  (Mill/Router, 0,1 mm diameter)
N0090 G43 H0
N0100 G00
N0110 M04
N0120 X180.3516 Y119.7404
N0130 (Part: Drawing1 Duplicate 1)
N0140 M18
N0150 G02 X180.3516 Y119.7404 I-67.4337 J0.0000 F3000.0
N0160 (Process: No offset 0, Mill/Router, 0,1 mm diameter, 0 mm Deep)
N0170 M17
N0180 G00 X170.1790 Y266.9916
N0190 (Part: Drawing1 Duplicate 2)
N0200 M18
N0210 G02 X170.1790 Y266.9916 I-67.4337 J0.0000
N0220 (Process: No offset 0, Mill/Router, 0,1 mm diameter, 0 mm Deep)
N0230 M17
N0240 G00 X306.6313 Y199.9025
N0250 (Part: Drawing1 Duplicate 3)
N0260 M18
N0270 G02 X306.6313 Y199.9025 I-67.4337 J0.0000
N0280 (Process: No offset 0, Mill/Router, 0,1 mm diameter, 0 mm Deep)
N0290 M17
N0300 G00 X388.5027 Y82.7810
N0310 M18
N0320 G02 X388.5027 Y82.7810 I-67.4337 J0.0000
N0330 M05
N0340 G00
N0350 G00 X0 Y0
N0360 G49
N0370 M05 M30

If I push the button while waiting in N0140 
If I push it during N0200, N0260 or N0310 it works well 

Thanx

17

General Mach Discussion / Re: stop waiting G4

« on: July 22, 2006, 07:24:37 AM »

There is a userDRO with the time xx (G4 Pxx) given by the user. This is the preheat time of an oxy flame.
Usually the user set this userDRO before start cutting without knowing if this time is ok. Usually he sets a high number. During preheat user can see the flame and push a button when he thinks that the time is ok. The time from the start of the preheat is recorded in this userDRO so next time preheat will be ok.
So M0 is not an option.

Thanx

18

General Mach Discussion / Re: stop waiting G4

« on: July 21, 2006, 09:00:58 AM »

It's me again

Accidentally I found that the button I asked above is the "Run" button.
BUT
I created a new vb script button with dobutton (0) and some other lines. When I press the green play button in  the script editor it works fine (NOT step by step). When I close the editor and press the button it is not the same!! (feedrate gets equal to x position, the movement is not the next line.... )

Thanx

19

General Mach Discussion / stop waiting G4

« on: July 21, 2006, 06:11:13 AM »

Hello

I am using a script for a M function with G4 Pxx (wait xx seconds).Thats fine

Then I want by pressing a button to stop waiting and continue executing next line.
Any help?

Thanx

20

General Mach Discussion / Re: Has Mach got user timers

« on: July 13, 2006, 05:07:34 PM »

I did it with time() vb script function

Thanks anyway