PathPilot Lathe with 6 place turret

Thanks' Chris

I have it moving , Z is moving backwards and seems to need input from spindle to run at constant speed. Here is first test video.



Thanks'
Brian

brianTruck wrote: Thanks' Chris

I have it moving , Z is moving backwards and seems to need input from spindle to run at constant speed. Here is first test video.

Thanks'
Brian

That's awesome! Guessing that's the Constant Surface Speed requiring the spindle input for movement?

brianTruck wrote: Thanks' Chris

I have it moving , Z is moving backwards

The simple answer to that is to invert the "dir" pin, but making the stepgen scale negative is probably better.

Chris,
Yes that is the constant surface speed in action. My lathe has only a index pulse on the spindle and I'm trying to figure out how to make that work with the CSS. PathPilot see's my index pulse on the z input of the spindle encoder.

Andy,
Made stepgen scale negative and now it's going the right way.

Thanks'
Brian

So i disabled the CSS by calling a M51 P1 in the g-code. So I now have the same lathe I had in Mach3 ,except it's faster, smother and has a nicer interface. This is when the gray hairs start growing.

My first order of business is to get the tool changer working. I see that PathPilot calls a function (is function the right name) called tormachltc in hal. This function appears to be already compiled so there is know messing with it (I think).

What is the proper way to write and call a function from hal ?

edit:
I read the full documentation on this turret code and it fully describes how to implement it.

wiki.linuxcnc.org/uploads/oracchanger.comp

But where is timedelay2.comp


Thanks'
Brian

Where does PathPilot hide the pin assignments for step & direction. I know what pins they are using ,but for life of me I cannot figure out how they set them.

The input pins stand out like this - hm2_5i25.0.gpio.003.in_not

Brian

Stepgen (and PWM,Encoder etc) pins are determined by the specific
FPGA configuration you are using, so stepgens are addressed by number
( 0..N ) in hal

Out of curiosity, I would assume that if pathpilot is preconfigured for most functionality already, would it make the most sense to replicate their connections to avoid alot of "coding" programming for those of us very nervous about doing such things? And is there a list of connections for the tormach machines to make that easier?

As much as I hate wiring, I would be much more comfortable going through my control cabinet to mimic pathpilot than trying to program everything around from the looks of it.

Thanks,

Chris

Lcvette wrote: Out of curiosity, I would assume that if pathpilot is preconfigured for most functionality already, would it make the most sense to replicate their connections to avoid alot of "coding" programming

I think this makes sense, especially as moving step/dir pins around with a 5i25 means recompiling FPGA firmware...

Have you worked out which pin is which with the installed firmware yet?

So the 2 lines I've highlighted should be the only 2 that control the steppper on stepgen 0 , right ?


# loading the toolchange and timedelay2 components in .hal file
###############################################################

loadrt oracchanger
addf oracchanger servo-thread

loadrt timedelay count=1
addf timedelay.0 servo-thread
# will wait 5 secs approx and turn motor off after reversing against stop
setp timedelay.0.on-delay 5

net tool-change iocontrol.0.tool-change => oracchanger.toolchange
net tool-changed iocontrol.0.tool-changed <= oracchanger.toolchanged
net tool-number iocontrol.0.tool-prep-number => oracchanger.toolnumber
net tool-oldnumber iocontrol.0.tool-number => oracchanger.currenttoolnumber
net tool-prepare-loopback iocontrol.0.tool-prepare => iocontrol.0.tool-prepared

net sig1 oracchanger.opto1 <= parport.x.pin-xx-in <<<<< these 3 need to be 5i25 inputs
net sig2 oracchanger.opto2 <= parport.x.pin-xx-in
net sig3 oracchanger.opto3 <= parport.x.pin-xx-in

net sig-forward oracchanger.forward => parport.x.pin-xx-out <<<<<these 2 need to be 5i25 stepgen.1 ,right ?
net sig-run oracchanger.run => parport.x.pin-xx-out <<<<<<

net xhomed axis.0.homed => oracchanger.ishomedX
net zhomed axis.2.homed => oracchanger.ishomedZ

net delaystart timedelay.0.in <= oracchanger.delaystart
net delaydone timedelay.0.out => oracchanger.delaydone

# if the delay is too long in switching relays for forward and reverse
# setp oracchanger.times 300
# for instance will make it shorter, default is 500 - about 1-2 secs on my system

################################################################################


Thanks'
Brian