Jump to content

Welcome to eMastercam

Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.

Use your display name or email address to sign in:

Bryan Johnson

Resellers
  • Posts

    993
  • Joined

  • Last visited

Everything posted by Bryan Johnson

  1. You may need to re-install or repair to correct this. An easy work around may be to set your default editor to CIMCO. This setting is in your configuration->start/exit
  2. Also consider Circle Mill. With it, I do not think that start point is an issue.
  3. The post edit is very simple, and if you are not comfortable with the post edit, your dealer could do it for you. As a bonus, you would not have to worry about "D/H" values again, and you could post the same file to dissimilar machines without having to go through all the ops and change the “D” value.
  4. "I always have to edit this to put the comment in the right location" For something as common as a program stop/M00, you may find it more better to use the miscellaneous page to trigger this. That way you can control the locations, and have the format the same every time. You would need to add some logic to the toolchange post block. Example: If mi1$ = 2, “M00 (CHECK PART)”, e$ Else, n$, “M01”, e$ Mpmaster already has this feature.
  5. another way would be to modify your post. Look for the "pccdia" post block, and change to: pccdia #Cutter Compensation if prv_cc_pos$ <> cc_pos$ & cc_pos$, prv_tloffno$ = c9k sccomp tloffno$ = t$ + 50 # adds 50 if cc_pos$, tloffno$
  6. what was in the TXT file is now included at the bottom section of the PST file.
  7. Yes. You can update a post that is already in the correct folder. TXT file ??? Not used since V9
  8. the number in () is very important. this is what line in the PST file that the error is at.
  9. Brent76, I just setup a FANUC post for this exact thing. You can copy from it and modify your Fadal post. You have mail.
  10. Pete and I are on the same page That can't be good.
  11. "Seems to me that "top" should be "top", no matter the CAD system". In SolidWorks, the coordinate system XYZ is clearly shown ay bottom left of screen. Terms like Top/Right/Front can be confused, but XYZ is XYZ.
  12. Another take on this would be to modify the post so that the H/D values are always correct. p_tloffno # output tool dia offset tloffno$ = t$ # or t$ + 20 etc... tloffno$ p_tlngno # output tool length offset tlngno$ = t$ *tlngno$
  13. good question. I had never noticed that feature in V9, but looking at X3/4, I do not see a way to do this.
  14. my understanding is that to format a variable, is not considered a duplication. I see many examples of this in X4 posts, and am not getting any error in the log. I would search the post file for any other occurrences of the of those variables being “initialized”.
  15. In X3, edit the default file as follows. Settings->Control Definition Manager, and access the default file from there. Maybe this will do the trick.
  16. There is nothing wrong with what you are showing. What does the error log have in it?
  17. if you switch parameter 278:9 to 0, you would be able to single blok through, BUT, you will also be able to start a program with the chuck not closed (not good).
  18. below is what I use for bar pull on haas. using Stock Advance, edit free. Because it outputs "W", it is very easy for operator to adjust part count for any length bar. M97 P999 L1 (SET REPEAT FOR BAR PULL) M30 N999 N8(T8) (BAR PULLER) G00 G129 X0 Z0 T0 T0808 M9 M05 G00 G54 X0 Z1.382 M5 Z-1.868 M11 (CHUCK OPEN) G04 P0.5 (PAUSE) G0 W1.628 (PART LENGTH + PART-OFF + FACE OFF) M10 (CHUCK CLOSE) G04 P1. (PAUSE) G0 W.5 (CLEAR) G0 X6. (CLEAR) G00 G129 X0 Z0 T0 M01
  19. On Haas, you can NOT single block through a bar pull. If in single block, you get the chuck alarm. Take it out of single block, and it will run without error.
  20. the programs will be separated when you load to the machine controller.
  21. look like mine pre-dates mplmaster. Its an oldie, but has had all its shots.
  22. Modifying the machine definition should work. The problem there is when you write a lot of programs for the same machine, some with and some without using the rotary. Another way to handle this is to setup the post file so that it scans the program, and if no rotary moves are found, it does not output and rotary moves. That way you can use the same files for both. On the FTP site, look for "Mill_Haas-VF" post files.
  23. Ron, I have a lot of experiance with the C axis haas, and have a good post. Have your reseller send me an email, and I will send him a copy of my post.
  24. to force output if not 0, add this post line: p_user_postline if peck1$ <> 0, *peck1$ if the drill post line, substitute "p_user_postline" for "peck1$"

Join us!

eMastercam - your online source for all things Mastercam.

Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.

Follow us

×
×
  • Create New...