Newbie setup Gmocappy setup

Hi

After thumbling around with LInuxcnc/Gmocappy I finally got the program to work with my CNC. I'm still having som smaller, but importent, issues that are killing me.....

I'm trying to set Gmocappy up , to use the tool sensor-probe. I've been following the tutorial: Gmocappy documentation point by point and the Youtube-videos, without any luck

I can't find a small program to test the setup. The once in the sample dir does not use the probe......

I'm Newbe in Linux, LinuxCNC ...and G-codes - so it is a high mountain to climb

Is there a kind soul, that will take a look into my attached files and try to guide me the laste steps....

Sincerly
Steen

i'm looking into this at the moment for my own use

i presume the file change.ngc is the sequence you want
are you changing tools manually or using a ATC ?

what type of probe are you using ?
and i presume you have the probe signal switching ok , as your input

if you care to let me know what other problems your having , we will see how we can help guide you through

Hi cncbasher

Thanks for your help. Some of the files is a "left-over" from other attempt to get it working.
The .ini and .hal changes are all based on the description at Gmocappy

I change the tools manually. The probe is a button-type from: GoCNC.de

The probe is tested and Gmocappy gets the signal on pin 13 - checked ok...

My problem is to figure out some kind off test to check the tool-changing process is functioning - some kind of a simple G-kode with 1 or toolchanges....
I've tried some of the samples, but they don't work.... I don't know if it is because the toolchange is not implemented or the tool-change is not working.

I've cleaned up the files, deleted the files from older attempts...

I hope this is more detailed around the problems I have - sorry for my english. It is not my prior language...

sincerly
Steen

thanks for the update , and for cleaning the files it all helps ...
most of what you need to debug is already their in the form of halshow .

let me get it all working here first
i hope to look at some of this today , although it may take a few days

Hi Cncbasher

I appreciate your help and are looking forward to hear from you.
If you need more information don't hesitate to mail me.

sincerly
Steen

Hi CNCbasher

Have you got time to look into my problem ?

It's some days since I've heard from you...
Sincerly
Stonefire

you have not connected the gmoccapy toolchange pins.
I have not seen the connection of the probe

Please test with the file gmoccapy_2_tools_with_cutter_radius_compensation.ngc located in the examples folder.

Norbert

Hi
Newbynobi

It's connected to pin 13, but I'm not sure how to set it up in the .hal-file.

The documentation looks like:

net probe motion.probe-input <= parport.0.pin-15-in

Do I just have to change it to :

net probe motion.probe-input <= parport.0.pin-13-in ??

Sincerly
Stonefire

Hi

My .hal-file looks like:



# Generated by stepconf 1.1 at Mon Aug 10 21:11:06 2015
# If you make changes to this file, they will be
# overwritten when you run stepconf again
loadrt trivkins
loadrt [EMCMOT]EMCMOT base_period_nsec=[EMCMOT]BASE_PERIOD servo_period_nsec=[EMCMOT]SERVO_PERIOD num_joints=[TRAJ]AXES
loadrt probe_parport
loadrt hal_parport cfg="0x378 out"
setp parport.0.reset-time 5000
loadrt stepgen step_type=0,0,0

addf parport.0.read base-thread
addf stepgen.make-pulses base-thread
addf parport.0.write base-thread
addf parport.0.reset base-thread

addf stepgen.capture-position servo-thread
addf motion-command-handler servo-thread
addf motion-controller servo-thread
addf stepgen.update-freq servo-thread
net spindle-cmd <= motion.spindle-speed-out
net spindle-at-speed => motion.spindle-at-speed

net probe-in => motion.probe-input

net ydir => parport.0.pin-02-out
net ystep => parport.0.pin-03-out
setp parport.0.pin-03-out-reset 1
setp parport.0.pin-04-out-invert 1
net xdir => parport.0.pin-04-out
net xstep => parport.0.pin-05-out
setp parport.0.pin-05-out-reset 1
setp parport.0.pin-06-out-invert 1
net zdir => parport.0.pin-06-out
net zstep => parport.0.pin-07-out
setp parport.0.pin-07-out-reset 1
net adir => parport.0.pin-08-out
net astep => parport.0.pin-09-out
setp parport.0.pin-09-out-reset 1
net xenable => parport.0.pin-16-out
net all-home <= parport.0.pin-10-in-not
net probe-in <= parport.0.pin-13-in-not

setp stepgen.0.position-scale [AXIS_0]SCALE
setp stepgen.0.steplen 1
setp stepgen.0.stepspace 0
setp stepgen.0.dirhold 35000
setp stepgen.0.dirsetup 35000
setp stepgen.0.maxaccel [AXIS_0]STEPGEN_MAXACCEL
net xpos-cmd axis.0.motor-pos-cmd => stepgen.0.position-cmd
net xpos-fb stepgen.0.position-fb => axis.0.motor-pos-fb
net xstep <= stepgen.0.step
net xdir <= stepgen.0.dir
net xenable axis.0.amp-enable-out => stepgen.0.enable
net all-home => axis.0.home-sw-in

setp stepgen.1.position-scale [AXIS_1]SCALE
setp stepgen.1.steplen 1
setp stepgen.1.stepspace 0
setp stepgen.1.dirhold 35000
setp stepgen.1.dirsetup 35000
setp stepgen.1.maxaccel [AXIS_1]STEPGEN_MAXACCEL
net ypos-cmd axis.1.motor-pos-cmd => stepgen.1.position-cmd
net ypos-fb stepgen.1.position-fb => axis.1.motor-pos-fb
net ystep <= stepgen.1.step
net ydir <= stepgen.1.dir
net yenable axis.1.amp-enable-out => stepgen.1.enable
net all-home => axis.1.home-sw-in

setp stepgen.2.position-scale [AXIS_2]SCALE
setp stepgen.2.steplen 1
setp stepgen.2.stepspace 0
setp stepgen.2.dirhold 35000
setp stepgen.2.dirsetup 35000
setp stepgen.2.maxaccel [AXIS_2]STEPGEN_MAXACCEL
net zpos-cmd axis.2.motor-pos-cmd => stepgen.2.position-cmd
net zpos-fb stepgen.2.position-fb => axis.2.motor-pos-fb
net zstep <= stepgen.2.step
net zdir <= stepgen.2.dir
net zenable axis.2.amp-enable-out => stepgen.2.enable
net all-home => axis.2.home-sw-in

net estop-out <= iocontrol.0.user-enable-out
net estop-out => iocontrol.0.emc-enable-in

loadusr -W hal_manualtoolchange
net tool-change iocontrol.0.tool-change => hal_manualtoolchange.change
net tool-changed iocontrol.0.tool-changed <= hal_manualtoolchange.changed
net tool-number iocontrol.0.tool-prep-number => hal_manualtoolchange.number
net tool-prepare-loopback iocontrol.0.tool-prepare => iocontrol.0.tool-prepared



Sincerly
Stonefire

Yes, you have to connect the pin like you mentioned, and get the manuell tool stuff out of the hal and connect the gmoccapy hal pin like mentioned in the doku!