[Vern Smith]

I'm a newb to CNC and do not have a very good handle of G code yet. I have a 6 month old Haas TM-1P that's on it's third processor board. Soooo - I don't have a lot of confidence in the Haas or my ability to analyze code problems.

The OneCNC produced code listed below runs through the Haas simulator with no problem. When I run it real time it stops at N652. No alarms or red lights, just sits there. The screen reads "running" try to stop the spindle and it says "spindle in use" hit feed hold and it recognized the condition, hit start and it goes back to "running" but never moves. The only way to stop it is reset.

I ran it several times, reposted it in the software, same result every time. I'm hoping someone will see a problem in the code so I don't have to bug Haas again about a screwy processor. You will probably need more information that I will be glad to supply if you point me in the right direction.

N631Z-0.1542
N632X-1.6381 Z-0.1507 F44.
N633X-0.9578 Z-0.151
N634X-0.8959
N635X-0.03
N636Z-0.15
N637G00 Z0.1
N638Y-0.8103
N639Z0.
N640G01 Z-0.15 F22.
N641Z-0.1503
N642X-1.3907 Z-0.1508 F44.
N643X-1.4526
N644X-1.6381
N645X-1.7 Z-0.1533
N646Z-0.15
N647G00 Z0.1
N648Y-0.781
N649Z0.
N650G01 Z-0.15 F22.
N651Z-0.1507
N652X-1.6874 Z-0.15 F44.
N653G00 Z0.1
N654X-6.89 Y-1.25
N655G01 Z-0.0373 F22.
N656X-6.8615 Z-0.0129 F44.
N657X-6.8331 Z0.0008
N658X-6.8046 Z0.0072
N659X-6.7762 Z0.008
N660X-6.15
N661Z0.05

Vern

[serviceman]

running and no motion is a common software error on haas machines i would look for a spftware upgrade or downgrade what software version do you have on the tm?

[Vern Smith]

When the Haas teck installed the last processor board he installed the latest software. This was about 3 months ago. On the parameters "inputs2" screen, where the hours and such are listed there is a listing "ver M15. 04B" If that's not what your asking I'll look elsewhere if you tell me where to look.

Vern

[HuFlungDung]

Try first writing down the entire line somewhere, then delete that entire line. Then, type it back in. This might discover some sort of non-printable machine character was loaded in with the program.

How are you loading programs in, btw? Not with floppies, I hope. BTW, are you checking your program first by running it in graphics mode?

Another test: leave the bad program in memory and load in a second copy of the program (alter the name and number). Then try running the second copy. This might discover a bad bit in the ram where the first copy of the program is stored.

I dunno, just a couple of things I would try

[Vern Smith]

I'm loading with a memory stick into the Haas USB port. The program ran fine in the Haas graphic simulator. That's what really confuses me, I would think if there ware problems in the code the simulator would stop at the same place.

I'll try your other suggestions.

Vern

[Ken_Shea]

Vern,
Another "Vern Anomaly"

BTW, My TM-1 is now 6000 RPM and runs just fine.

If you want send me the file and I can try it on my machine and see if the problem is duplicated at my end.

Send it to:
[email protected]

[Geof]

I'm loading with a memory stick into the Haas USB port. The program ran fine in the Haas graphic simulator. That's what really confuses me, I would think if there ware problems in the code the simulator would stop at the same place.

I'll try your other suggestions.

Vern

I have found that the Graphics on the machine will sometimes behave different to actually running the machine.

[Vern Smith]

Ken,

Thanks for the offer, I finally recreated the tool paths and made a few other changes to the CAM file and the next post worked just fine. I didn't bother to save the problem post in it's entirety but I'm sure it will happen again and I'll ship it off to you ASAP.

Glad to hear the Haas hop up went well. I'll be sending you and Chris a PM tomorrow.

Geof,

It's always reassuring to know the test function does not play be the same rules as the real thing. I guess that's why we have test pilots. I appreciate the response. I think I'll send Haas a note for my file in case it comes up again after the warranty period.

Has anyone found a spell checker that works in this forum, I don't type for s**t.

Vern

[mactec54]

Hi Vern Smith

Try putting a G01 on that line N652 & see if that helps

[Geof]

Has anyone found a spell checker that works in this forum, I don't type for s**t.

Vern

Vern; do you have the latest Internet Explorer that does multiple tabs, etc.?

It has a spell check that works in these forms.

And when I use it, it insists on making Geof into Geoff.

Geof

[Vern Smith]

Mactec, I'll try the G01

Goef / Geoff, I'm not using the latest version, I guess it's time to update.

Vern

[ltmquik]

I'm a newb to CNC and do not have a very good handle of G code yet. I have a 6 month old Haas TM-1P that's on it's third processor board. Soooo - I don't have a lot of confidence in the Haas or my ability to analyze code problems.

The OneCNC produced code listed below runs through the Haas simulator with no problem. When I run it real time it stops at N652. No alarms or red lights, just sits there. The screen reads "running" try to stop the spindle and it says "spindle in use" hit feed hold and it recognized the condition, hit start and it goes back to "running" but never moves. The only way to stop it is reset.

I ran it several times, reposted it in the software, same result every time. I'm hoping someone will see a problem in the code so I don't have to bug Haas again about a screwy processor. You will probably need more information that I will be glad to supply if you point me in the right direction.

N631Z-0.1542
N632X-1.6381 Z-0.1507 F44.
N633X-0.9578 Z-0.151
N634X-0.8959
N635X-0.03
N636Z-0.15
N637G00 Z0.1
N638Y-0.8103
N639Z0.
N640G01 Z-0.15 F22.
N641Z-0.1503
N642X-1.3907 Z-0.1508 F44.
N643X-1.4526
N644X-1.6381
N645X-1.7 Z-0.1533
N646Z-0.15
N647G00 Z0.1
N648Y-0.781
N649Z0.
N650G01 Z-0.15 F22.
N651Z-0.1507
N652X-1.6874 Z-0.15 F44.
N653G00 Z0.1
N654X-6.89 Y-1.25
N655G01 Z-0.0373 F22.
N656X-6.8615 Z-0.0129 F44.
N657X-6.8331 Z0.0008
N658X-6.8046 Z0.0072
N659X-6.7762 Z0.008
N660X-6.15
N661Z0.05

Vern

I think that you need to work on the post processor. First off it might be a good idea to have spaces after the line numbers. I know HAAS does not care wether it has line numbers or not but this may be confusing the controller and can only make debugging easier. Second, there are alot of redundant axis moves. Like you have one line that says N643X-1.4526 and the next line is N644X-1.6381. I would think the the line N643 could just say X-1.6381. Again, I doubt that these are causing the problem but it can only help the situation to have 'clean' code.

[Vern Smith]

Jeff,

Thanks for the G code advise, I hate to admit it but 99% of my code is created by a CAM program. This is the first time my Haas has choked on it to my knowledge, although my CAM software has choked many a time on my attempts to create tool paths.

Vern