Lathe setup question: I have created a lathe profile path that simulated fine in

CAD & CAM Tool Chain ChiliPeppr
1

Lathe setup question:

I have created a lathe profile path that simulated fine in fusion (tool moves perpendicular to the Z axis and excises the path profile)…when the code is pasted into ChiliPeppr the tool has rotated 90 degree axis and operates in the simulation in parallel to the Z axis (is the code not set to recognize a lathe operation and is trying to “mill” the path?)…any clues pls?

first few lines of code:

%
O1007 ( MULTI SPEED PASS)
N10 G98 G18
N11 G20
N12 G50 S6000
N13 G28 U0.

(GROOVE1)
N14 T0404
N15 G54
N16 M8
N17 G98
N18 G97 S500 M3
N19 G0 X3.4053 Z0.9969
N20 G0 Z0.3
N21 X2.7653
N22 G1 X2.6053 F39.3701
N23 X2.2053
N24 Z-3.35
N25 X2.6037
N26 X2.7169 Z-3.2934
N27 G0 Z0.3

2

The simulator doesn’t understand lathe paths. Best to run an air job on your lathe to visualize.

3

@jlauer

well the same problem exits in the live machine…the z axis must need to be transposed to the x axis…is it as simple as find and replace x for z points? or better to create the job in mill space and run it run it in “x” axis space…

4

@brian_lee sorry I guess it would be find and replace all “Z” moves with “X” moves

5

sorry ----- for “y” space…(dyslexia is my strong suit!)

6

GCode plane definitions

G17 XY plane selection
G18 ZX plane selection

On most CNC lathes (built 1960s to 2000s), ZX is the only available plane, so no G17 to G19 codes are used.

This is now changing as the era begins in which live tooling, multitask/multifunction, and mill-turn/turn-mill gradually become the “new normal”.

G19 YZ plane selection

Since “G18” defines “ZX” space why will ChilliPeppr choke on this definition?

John…it is soooooo… close (?)

7

If you look at the code that interprets the gcode I don’t think we ever put in a method for g17 thru 19. Your gcode should run fine though as long as you have your controller configured correctly.

8

I’m dying here…I gave up on Fusion and I created a model in GG and the model runs ok in simulation in CP in both GG and CP…when i run it live in CP it blows by “y” commands and seems to add them to x driver…steeping through the commands in simulation seems to increment/decrement the y axis appropriately (v07 44 20)

here are a few lines of code…

as to configuration: when I go and look at the config file it has separated motors and axis appropriately but when running live it seems to be overwritten to all motors driving X…stop and look at config and it shows proper pairing of motors and axis…axis mode is “standard”…

the ghost in the machine has set the axis to all “X” on occasion but I can’t seem to get that problem to replicate…all the axis are paired correctly (Again) when i go and look at “config” again

( Created by GrblGru:GCodeCreator )
( 10.02.2018 16:44:21 )

( Finfeed= 30 )
( F= 0 )
( Fmax= 0 )
( OffsetX = 0 )
( DeltaY = 2.8 )
( Smart clearance = False )
( Free entry = False )
( Both directions = False )
( Finfeed Finish = 40 )
( F Finish = 40 )
( Fmax Finish= 0 )
( DeltaY Finish = 0.709999999999999 )
( RefPointY = 26 )

G90 G1 F1000

( Rough 154 )

( Move to startpoint )
G90 G1 F0.00 y0.000
F0.00 x0.000

( Line 1: )
F0.00 x6.958 y0.000
F30.00 x6.958 y-2.800
F0.00 x-79.050

( section: 153 <- 0 )
F0.00 y0.000
F0.00 x6.958

( Line 2: )
F0.00 x6.958 y-2.800
F30.00 x6.958 y-5.600
F0.00 x-4.897

( section: 33 <- 0 )
F0.00 y0.000
F0.00 x-10.309
F0.00 x-10.309 y-2.800
F30.00 x-10.309 y-5.600
F0.00 x-79.050

9

ChiliPeppr doesn’t support simulating lathe paths. If you’re seeing correct simulation for lathe paths, that actually makes me think your Gcode is wrong then because I can’t see a way to simulate correct lathe movements in ChiliPeppr. Keep in mind ChiliPeppr simply blindly sends your Gcode to your CNC controller. It does not modify anything. This feels like it’s still your CNC controller config or your Gcode generation. If your y moves get ignored, it’s gotta be a configuration issue or your Gcode generation is off.