4th axis

[balsaman]

I will have to hurry and get this built so I can try it.

Thanks to all who helped.

Here is a screen shot of the name "LIZ" wrapped around a 3" cylinder. I cant wait to try it.

Eric

[balsaman]

Ok oh Mastercam guru's. I have my 4th axis working but there is a problem. Have a look at the following gcode:

N454 X.752 A-106.732 F515.16
N456 X.7581 A-106.554 F529.03
N458 X.7642 A-106.375
N460 X.7703 A-106.196
N462 X.7764 A-106.015
N464 X.7825 A-105.833
N466 X.7886 A-105.651 F541.5
N468 X.7946 A-105.468
N470 X.8007 A-105.283
N472 X.8067 A-105.097 F555.91
N474 X.8127 A-104.911
N476 X.8187 A-104.723
N478 X.8247 A-104.536
N480 X.8307 A-104.346
N482 X.8367 A-104.157 F567.83
N484 X.8375 A-104.131 F596.27
N486 X-.5255 F20.

The problem is that my controller (turbocnc) thinks that all the negative angles are moves over 360 degrees. So, instead of going from -106.554 to -106.375 the short way, it goes the long way around. Positive numbers are ok. Is it my post, or Turbocnc? Maybe I should put all the geometry in the positive quadrant in Mastercam? Lemme go try that.

Eric

[balsaman]

If I move the geometry so all of it is in the positive quadrant, all is well. Turbocnc doesn't like the negative angles I guess.

Eric

[balsaman]

Could I ask someone to look at my post? I set it for incremental but it's still spitting out absolute coordinates, with no G91 in sight.

Eric

[HomeCNC]

If you find that you want to try another controller, give Mach 2 a try.

[balsaman]

I would like to. I got a 400 mhz computer so I could try mach 1, but I can't for the life of me get XP installed on it. Errors on install.

Eric

[HomeCNC]

What about W2K?

[balsaman]

I will have to try it.

never mind about the post guys. The solution was a simple one found at the turbocnc yahoo group. I set the axis up in the software as a linear axis with one revolution = 360 inches. It works perfectly this way.

Turbocnc converts all angles to something between 0 and 360 degrees. so an angle of 370 gets converted to 10 degrees after it's made the move. This is fine but if a gcode wants to make a move to 370, then the next move to 380, it goes to 370, gets converted to 10, then moves alllllll the way to 380, which then gets converted to 20. (I am not sure why it does this)

Anyways, we are up and running!

Eric