![]() | |
| Home Page | Mark Forums Read | Today's Posts | My Replies | Classifieds | Reviews | Photo Gallery | Web Links | Share Files | Advertise With Us | Ad List |
| |||||||
| Haas Mills Discuss Haas machinery here! |
| This forum is sponsored by: |
![]() |
| | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#1
| |||
| |||
| Hi; I've got a problem with a haas machining center that I have been tasked to edit some code on. At the risk of sounding like a total newbie, I don't know at this minute what model the machine is, as I am sitting at home and the machine is in a shop 2oo miles away. When I get to work today I can find out which model, but I don't have internet access at work and I am hoping someone might make a suggestion before then. OK, here is my problem. They have been running this machine in a production enviroment to machine aluminum castings. They have sent the machine to a vendor to have it retrofitted with laser tool-break sensors. We have another machine on which this has already been done, and I am trying to use basically the same code for this one. The machine runs the first tool and then the check code goes like this: g80 g53 g0 z0 g90 g53 x-2.6 y-10.2 g53 z43.5 [if #1019 eq 0 goto500] (with 500 being a non-existant line so the machine will fault Basically the x-2.6 y-10.2 z43.5 puts the tool in the path of the laser, and if the #1019 doesn't see 0 it faults out the machine. The problem is everytime the machine reads this it throws an overtravel range alarm on the x axis and will not move to the location. I can move the spindle to the location in MDI mode with no problem, but it won't go there in auto. These same commands supposedly work fine on another machine just like this one, but the guy who wrote the code is no longer available. I would add that I know virtually nothing about Haas machines, but I am fairly competent on fanucs |
|
#2
| ||||
| ||||
| I'm fairly green to this stuff but I'm seeing G53 in your code, not G54. Which work offset are you using? < snip > Your Z values also say 43 inches. I assume that you know this and it's just a typo. I don't know of any Haas machines with 43 inches of Z travel (or that really is your problem). That's my guess. Now somebody will come along an make me look stupid ![]() edit: yes, somebody came along and made me look stupid. ![]() I was thinking of G52, not G53. DOH!
__________________ Greg Last edited by Donkey Hotey; 12-06-2007 at 09:57 AM. |
|
#4
| |||
| |||
| G53 is machine coordinate. On the Haas anyway, the absolute home of 0,0,0 is at the upper right of your table and toolchange position on Z. All machine coordinates are negative from there. The 43.5" of Z travel sounds god awful much to begin with, but the definiate problem is that it's positive. |
|
#6
| ||||
| ||||
|
If 'tool change' (all the way up) is zero, then a positive 43mm is still out of range. As SeymoreDumore already posted: did you mean Z-43.5?
__________________ Greg |
|
#8
| |||
| |||
| EDIT: 43mm is less than 2 inches.
__________________ An open mind is a virtue...so long as all the common sense has not leaked out. |
|
#9
| ||||
| ||||
| Is this a VMC? When you say you can move to that position in MDI, are you observing the position displays and the machine coordinate readout when you have jogged to that position? Apart from that, you could try removing the G90 from in front of the G53, as it serves no purpose. Moves in the machine coordinate system are always absolute moves, and perhaps the presence of the G90 might mess with the command logic somehow. I never tried it
__________________ First you get good, then you get fast. Then grouchiness sets in. (Note: The opinions expressed in this post are my own and are not necessarily those of CNCzone and its management) |
|
#10
| |||
| |||
| Just a thought. I guess you typed the lines of code in your post. Are you sure on the machine that the X command is G53 X-2.6? I have made the mistake a few times of doing something like G53 X2.6 and failing to see the missing - for a long time.
__________________ An open mind is a virtue...so long as all the common sense has not leaked out. |
| Sponsored Links |
|
#12
| |||
| |||
| yes it is the location of the laser. I was thrown into this deal after the guy who originally was involved refused to have any more to do with it, and the guy on the other end (who wrote the macro arguments) left the company. The problem I have is that the machine is in a vendors shop 150 miles from me. |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | Search this Thread |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Mid range design #1 | CNCadmin | Open Source CNC Machine Designs | 101 | 01-23-2011 10:03 AM |
| Mid-range first CNC | iXô | Open Source CNC Machine Designs | 14 | 09-18-2007 08:42 PM |
| Refractometers - What Range to Order | bill south | General Metalwork Discussion | 7 | 05-11-2007 07:56 AM |
| CNC 35,000 to 50,000 price range | deathbot3000 | Commercial CNC Wood Routers | 16 | 11-15-2006 01:14 PM |
| Puma 450 gear range? | wjbzone | Daewoo/Doosan | 0 | 02-15-2006 06:15 AM |