View Single Post
  #2   Ban this user!
Old 02-19-2004, 06:46 PM
camsoft camsoft is offline
 
Join Date: Apr 2003
Location: United States
Posts: 279
camsoft is on a distinguished road

There are a few things you can do.

Use the Search for Solutions button (Starting with Version 15) to review Question #232

It's true the SOFTLIMITS position settings in CNC SETUP are relative to the machine home not tool or job home. However, these positions can be changed on-the-fly with the logic command equivalent called SOFTLIMITS or the G codes G170,G171,G172.

Think of the SOFT LIMITS as a virtual over-travel limit switch in the computer. These may be used as crash barriers to prevent the tool from hitting the chuck, fixture or clamp for example.

What actions will occur when a crash barrier or SOFTLIMITS is crossed can be customized by the end user in detail inside the SOFTLIMITS.FIL file.

Here are the 3 choices.

(1) Enter in the tool size or length into the CUSTOM1 or CUSTOM2 box on the TOOL PARAMETER screen for each tool number. At each new tool change, perhaps in the logic for the M06 code you can setup the new crash barrier positions for each new tool. Use the lower case t value to determine the current tool number.
Example:
TOOLCUS1STt \123
SOFTLIMITS BACKWARD {-10+\123};0;0

This will retrieve the value stored in the CUSTOM1 box on TOOL PARAMETER SCREEN for current tool number and store it in variable \123 then reset the SOFTLIMITS for the BACKWARD limit of the first axis to -10 were it was originally plus the tool size or length stored in variable \123.

If the physical chuck was at -10 away from machine home in Z (in this case axis number 1 on a lathe) and the lathe tool length stored in CUSTOM1 box was added to the original chuck location then the number 1 axis could not pass this coordinate without causing the SOFTLIMITS event to execute. This would also work for 3D mills or other machine types despite additional offsets for the fixture, job home or other user defined added offsets because the internal position register compares the actual axis location minus any offsets in a separate register and it's this value that is compared to the SOFTLIMITS position. All we are doing here is adding the tool size or length to SOFTLIMITS.

When the tool enters the crash barrier limits the logic in the SOFTLIMITS.FIL file will automatically run. Here you display messages to the operator, stop the machine or even automatically back away slowly.

(2) These G codes setup new crash barriers from within the G Code program G171,G172. The G170 resets them back to the defaults. This way the positions that are given for this particular part would be saved for the next time it's run, right inside the G code file.

(3) Enter logic directly in the GCODE.FIL file table that specifies what will happen, what messages get displayed and what action will occur before the GO command to move the machine takes place. In the example below if the X axis position in the G code program is ever less than or equal to the value 1.234 then the machine stops and displays a message and exits out before it moves there.
The -1.234 maybe the distance from the face of the part Z0 to the chuck jaws.
For example:
If x<=-1.234 THEN ESTOP:MESSAGE CRASH BARRIER HIT:EXIT

The big advantage here is that you are working with numbers in the G code program that are already the tip of the tool. No offsets to worry about in your calculation. The lower case x value is the tip of the tool. All tools despite their length get setup and touched off the part face at Z0 on a Lathe or Z0 on the top of the part on a mill/router. This way the tool number doesn't matter and neither do the offsets. If the tip of the tool is commanded in the G code program to cross a certain fixed coordinate that is the chuck or fixture then this will catch it. Besides this way the move is never actually made so the crash is caught before the tool even gets near the chuck.

(4) In the standard version of CNC professional watch the solid modeled simulation on the screen in SUSPEND PREVIEW mode before you press cycle start. In Level-5 or higher you can also preview a full solid modeled verification of the G code program. Although you can't always count on this method unless you humanly notice something, but again it's a high probability that you will notice well before the machine operator has even has a chance to press cycle start.

Tech Support
CamSoft Corp.
(909) 674-8100
support@camsoftcorp.com
www.cnccontrols.com
Reply With Quote

 

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361