![]() | |
| Home Page | Mark Forums Read | Today's Posts | My Replies | Classifieds | Reviews | Photo Gallery | Web Links | Share Files | Advertise With Us | Ad List |
| |||||||
| Fanuc Discuss Fanuc controllers here! |
| This forum is sponsored by: |
![]() |
| | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#1
| |||
| |||
Hello all, I have gotten a lot of help on this forum before on lathe offsets, see if anybody can help me on this one. I am using the Fanuc 21i-t and 21-TB controls. When I set my workshift value, I use something like this "G10 P0 Z-3.25". Now I am wondering if it is possible to read this value into a variable so I can use it in further calculations? Is there a certain parameter that the workshift is stored in? |
|
#2
| |||
| |||
| Yes this is setting the “common” workshift correct? I did not see the L2 in the line but I ass u me it is still setting it properly. Anyway there are variables that are set to the common. IIRC it should be #5201=X, #5202=Y and #5203=Z. So you can set this up however you want. The best way to do it would be to just use the #5203 in your calculations or change it to a common variable right after your G10 line. G10P0Z-3.25 #500=#5203 You can then use the #500 later in your calculations. The downside to this is if someone makes a manual change to your Z in the common offset then the #500 will not be updated to the current value. Stevo |
|
#3
| |||
| |||
| Ok, thanks for the info. But when I type in #1 = #5203, I get an error message, "Illegal variable number". When I try the same thing with variable #3000, the value of 3000 gets copied into 1. Is there another way to check the value of the system variables? Maybe my machine doesn't support these 52xx variables? |
|
#4
| |||
| |||
| That’s odd. Your machine should support it. Try #5201 as this should relate to your X position in common, just to see if it works. You are on a lathe so it could be #5201 for X and #5202 for Z and you have no #5203. I don’t have any manuals in front of me at the moment to confirm this. There are other options to what you are trying to achieve. This is just an example and still holds true to what I said earlier if someone changes the common in the offset page then the variable you use in the calculation will not match what it actually is. #1=-3.25 G10P0Z#1 You can then use the #1 later in the program. Stevo |
|
#7
| ||||
| ||||
|
|
#8
| |||
| |||
| Well there you go crazy….my bad, give those a shot. Stevo |
![]() |
| 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 |
| Are lathe offset values on radius or diameter? | sinha_nsit | Fanuc | 5 | 11-06-2009 08:46 AM |
| Reading workingoffset values | rui.costa | G-Code Programing | 4 | 12-20-2007 02:27 AM |
| Offset values get changed | sab | General Metal Working Machines | 0 | 06-27-2007 11:42 PM |
| wire offset values | Stevatome | Fanuc | 4 | 03-09-2007 07:42 AM |
| NC reading tool length from offset page, not data page..? | RMagnusson | Mazak, Mitsubishi, Mazatrol | 1 | 03-21-2006 04:07 PM |