Fadal 4020 control locking up

[Ron]

I am posting a students project to the fadal via RS 232 connection. Just this project locks up the control and I have to power off and restart. If anyone could help me trouble shoot, I would greatly appreciate it. I am not that experienced at this. (I am a high school teacher) It locked up on line 108. I am using MCam 8.1.1 We have cut out three others with no problems. (not even any broken .125 endmills! wahoo!)

 

Thanks

Ron

[email protected]

 

N100O0001(BRONCOS2)

(DATE=DD-MM-YY - 18-12-02 TIME=HH:MM - 13:41)

N102G20

N104G0G17G40G49G80G90H0E0Z0

N106(1/8 FLAT ENDMILL TOOL - 6 DIA. OFF. - 6 LEN. - 6 DIA. - .125)

N108T6M6

N110G0G90S10000M3E1X.8775Y-1.7592

N112H6Z1.05M8

N114G1Z.4F4.8

N116X.8781F9.6

N118X.8784Y-1.7576

N120X.8913Y-1.7341

N122G3X.9003Y-1.6991I-.0635J.0349

N124X.8945Y-1.6708I-.0725

N126G1X1.1829

[d0gFartz]

just out of curiousity try putting the m6 on a line by itself......N108 T6 the on the next line N110 M6 and see what it does

[TheePres]

Do a search for Letter "O" in your program, one of the "zeros" might actually be letter O.

[perfecseal mankato]

another thing to try is to post process the

program without line numbers. the date line has no line number in it. the newer fadal controls will automatically give you line numbers, so line numbers not really needed anymore.

[GARRY P]

DOES YOUR OTHER PROGRAMS THAT HAVE WORKED HAD T6M6 IN THE SAME LINE. YOUR PROBLEM MIGHT BE FURTHER DOWN IN THE NEXT LINE. IF IT READ N108 THEN THE NEXT LINE CONTAINS THE GLICH

[Mattingly]

A couple of things to check make sure that you ample space for the program we have 5 Fadal's here and from what I see everything looks corrrect in the program also check your baud rate at the control as well as at the computer your downloading from... Try this it might work

[Ron]

Thanks for all the suggestions. I will try them out and let you know what happens.

 

Ron

[Guest]

I believe line 112 should have a G43 to go with the H6.

[Surface]

Ron, if you Email your code, I could try it on my Fadal and see if it runs ok. I know these things can get frustrating.

[resjun]

N110G0G90S10000M3E1X.8775Y-1.7592

Check the E after M3

[MetalMarvels]

I had exactly this problem with my Fadal 3016L. The problem was the unnumbered date line.......sending all unnumbered or all numbered works. Sending a mix of unnumbered and numbered, particularly in the header section, would lock my 3016L every time. The code you show is otherwise what I run.

 

In the psof section of your post it should read:

 

"%", e

 

n, *progno, "(", sprogname, ")", e

n, "(", "DATE=DD-MM-YY - ", date, " TIME=HH:MM - ", time, ")", e

pbld, n, *smetric, e

 

 

The "n, " in front of the date line is what is necessary to add a line number in the posted code. The "M3E1" should be fine for a Fadal 4020 with the control in Format 2 mode. Format 2 mode should be the default.

[Jack Mitchell]

Resjun & others,

 

E1 is an acceptable substitution for G54.

E2 = G55, etc! – In fact some of the older machine tools will only recognize “E” as a fixture offset (This precluded the Fanuc standardization of coordinate presetting via G92 and G54 thru G59).

 

As suggested, I believe the culprit to be the most common of all programming errors encountered - "O" instead of "0"

 

“O” is a double edge sword – it gives us the ability to number programs AND the ability to open the RS232 port to receive data.

“O” causes the port to open and receive until the encounter of another “O” or the End of Record symbol “%”; I have seen student’s type entire programs with OOHHSS.

 

O0001 (Program numbering should not be prefixed with an "N" number)

(DATE=DD-MM-YY - 18-12-02 TIME=HH:MM - 13:41)

N102 G20 (space your numbers as I am, this makes for easier reading)

N104 G00 G17 G40 G49 G80 G90 H00 E0 Z0 (Most of us know these codes, looking good)

N106 (1/8 FLAT ENDMILL TOOL - 6 DIA. OFF. - 6 LEN. - 6 DIA. - .125 - looking good)

N108 T06 M06 (present tool six adjacent to the spindle, physical tool change to whatever is currently present)

N110 G00 G90 S10000 M03 E1 X.8775 Y-1.7592 (looking good)

N112 Z1.05 H06 M08 (looking good)

N114 G01 Z.4 F4.8 (looking good)

N116 X.8781 F9.6 (looking good)

N118 X.8784 Y-1.7576 (looking good)

N120 X.8913 Y-17341 (looking good)

N122 G03 X.9003 Y-1.6991 I-.0635 J.0349 (looking good)

N124 X.8945 Y-1.6708 I-.0725 (looking good)

N126 G01 X1.1829 (looking good)

 

I believe MetalMarvels has a valid point about the comment line on N106 – Fadal is probably 98% Fanuc compatible, so often it’s the 2% chance upon error.

 

Thank you, Ron for posing the question – please visit the forum more often (we are here to help and be helped)

 

Regards, Jack

[Keith Graydon]

Hi,

 

We have an older FADAL VMC15XT and I've noticed something similar happen.

 

Say my active program is 01234 named (PART).

If I DELETE this from memory and RELOAD via the RS-232 (with a program with IDENTICAL 0-word and NAME) the load will fail at the same n-number virtually every time.

 

I either cold reboot the machine or use the RI command to re-intialized the control memory. Or,

I just load the new program and let the control overwrite the active program. that allways works.

 

does this sound similar to your problem.

 

All this assumes that ALL your COMM parameters are correct.

 

HTH

-KLG

[Ying Jiang]

Are you doing drip feeding or send the file to machine memory? ("DNC" or "TA,1")

 

Many Fadals don't like programs with comments when drip feeding.

[Keith Graydon]

This has happened to me only when TA,1

 

I tweaked my post to output TA,1 in the header, above the TOF. It works well and saves steps to the machine. see below.

 

code:

---

TA,1

%

N1O5566(PLATE)

N2G0G17G40G49G80G90H0E1Z0

---

-KLG

 

[ 12-19-2002, 01:47 PM: Message edited by: Keith L. Graydon ]