8
G-code vs conversational programming - which is actually faster for one-offs?
I read a post on Practical Machinist last night that said conversational programming is 40% faster for single parts but 60% slower for runs over 50 pieces. That surprised me because I always thought learning G-code was the only real way to program. But then I thought about how long it takes me to hand code a simple bracket versus using the control's built in cycles. What do you guys run for quick jobs - do you stick with G-code or switch over to conversational when the boss is breathing down your neck?
2 comments