1. Forum
  3. Search

Advanced Search

Search Results (Searched for: )

  • axel88
  • axel88
28 Nov 2010 10:15 - 28 Nov 2010 10:18
Replied by axel88 on topic Manual tool change + tool lengh touch off

Manual tool change + tool lengh touch off

Category: Advanced Configuration

2.) I've got problems with the subprograms:

I wrote to files: first-tool.ngc and auto-tool-change.ngc and located them in ../emc/nc-files which is defined as the PROGRAM_PREFIX folder in the Portalfrase.ini .

when I run:
o<first-tool.ngc> call
or
o<first-tool> call
the error "File not open" appears.

here is my subprogramm:
o<first-tool> sub
G90 G53 G0 Z0
G53 G0 X0 Y0
G91 G38.3 Z-180 F500
G38.5 Z10 F15
#1000=#5063
G90 G53 G0 Z100
G90 G53 G0 X50 Y50
o<first-tool> endsub
M02

But even if I copy the fred.ngc example it doesn't work.
  • axel88
  • axel88
28 Nov 2010 09:41 - 28 Nov 2010 09:43
Replied by axel88 on topic Manual tool change + tool lengh touch off

Manual tool change + tool lengh touch off

Category: Advanced Configuration

1.) By moving the debounce procedure to the custom.hal I've got some errors:

CUSTOM.HAL (line 4 to 10)
unlinkp parport.0.pin-10-in-not
unlinkp motion.probe-input
loadrt debounce cfg=1
addf debounce.0 base-thread
setp debounce.0.delay  10
net probe-raw parport.0.pin-10-in-not => debounce.0.0.in
net debounce.0.0.out => motion.probe-input
ERROR:
(...)
custom.hal:10: Signal name 'debounce:0.0.out must not be the same as pin.
8635
(...)
  • andypugh
  • andypugh's Avatar
27 Nov 2010 21:47
Replied by andypugh on topic Manual tool change + tool lengh touch off

Manual tool change + tool lengh touch off

Category: Advanced Configuration

axel88 wrote:

which hal file?
/usr/share/emc/tcl/bin/halconfig.tcl?

EDIT: /home/axel/emc2/configs/Portalfrase/Portalfrase.hal looks good, right?


Yes, I came into the forum at a run to make sure you weren't about to do something silly.

(I had to delete your umlauts as the forum refuses to show any message with odd characters at all, including three full stops in a row, and the UK currency symbol)

You can either edit that file, or if it was created by stepconf you can put your new stuff in the custom.hal file where stepconf won't over-write it.

The drawback with putting it in the custom.hal file is that you might need to unlink some connections to insert your new stuff.
unlinkp parport.0.pin-10-on-not
unlinkp motion.probe-input
Would do that.

HAL is one of the most powerful features of EMC2, it allows you to connect any inputs and any outputs together in a completely free way, optionally processing the signals on the way.
  • axel88
  • axel88
27 Nov 2010 21:03 - 27 Nov 2010 21:43
Replied by axel88 on topic Manual tool change + tool lengh touch off

Manual tool change + tool lengh touch off

Category: Advanced Configuration

I had to change the last comands to:

setp debounce.0.delay 10
net probe-raw parport.0.pin-10-in-not => debounce.0.0.in
net probe-in <= debounce.0.0.out

otherwise I got errors. I hope the function is the same?
  • andypugh
  • andypugh's Avatar
27 Nov 2010 20:56
Replied by andypugh on topic Manual tool change + tool lengh touch off

Manual tool change + tool lengh touch off

Category: Advanced Configuration

debounce needs to be added to the hal file. The process is much the same for any HAL component.

1) load the component:
loadrt debounce cfg=1
This loads a 1 channel debounce called debounce.0

2) Make the debounce function run in the base thread:
addf debounce.0 base-thread

3) set the debounce time:
setp debounce.0.delay  10

4) put the debounce between the parport and the probe input
net probe-raw parport.0.pin-10-in-not => debounce.0.0.in
net probe-filtered debounce.0.0.out => motion.probe-input
  • axel88
  • axel88
27 Nov 2010 20:37
Replied by axel88 on topic Manual tool change + tool lengh touch off

Manual tool change + tool lengh touch off

Category: Advanced Configuration

Where do I have to add the debounce command and which are the right parameters for
"parport.0.pin-10-in-not" ?
  • andypugh
  • andypugh's Avatar
27 Nov 2010 16:07
Replied by andypugh on topic Manual tool change + tool lengh touch off

Manual tool change + tool lengh touch off

Category: Advanced Configuration

You could probably remove the lowpass and use the "debounce" function in HAL.
www.linuxcnc.org/docview/html//man/man9/debounce.9.html

I think that probe moves towards the indicated position. You might need a G53 on the same line as the probe command.
  • axel88
  • axel88
27 Nov 2010 15:57 - 27 Nov 2010 16:17
Replied by axel88 on topic Manual tool change + tool lengh touch off

Manual tool change + tool lengh touch off

Category: Advanced Configuration

How can I set the direction of G38.5 Z0 f15?

EDIT: Ok found it
  • axel88
  • axel88
27 Nov 2010 15:38 - 27 Nov 2010 15:39
Replied by axel88 on topic Manual tool change + tool lengh touch off

Manual tool change + tool lengh touch off

Category: Advanced Configuration

Ok i found the reason, my paralell-port has internel pullups, so if my switch was closed there was a current backwards through my lowpass causing 1,8V drop, an thats no clear signal.

EDIT: G38.5 works fine
  • axel88
  • axel88
27 Nov 2010 15:10
Replied by axel88 on topic Manual tool change + tool lengh touch off

Manual tool change + tool lengh touch off

Category: Advanced Configuration

File Attachment:


I can't imagine that it's electrical noise, because in this picture my power stage is not enabled and i build an RC lowpass with 1kHz corner frequency. This signal is about 3kHz. And why is there no electrical noise if the switch is open?
  • andypugh
  • andypugh's Avatar
27 Nov 2010 14:55
Replied by andypugh on topic Manual tool change + tool lengh touch off

Manual tool change + tool lengh touch off

Category: Advanced Configuration

It could be electrical noise. Exactly how is the switch wired, and to what?

What does the probe signal look like in Halscope?
If you are in the axis UI then it is Machine -> Halscope.
  • axel88
  • axel88
27 Nov 2010 14:28 - 27 Nov 2010 14:40
Replied by axel88 on topic Manual tool change + tool lengh touch off

Manual tool change + tool lengh touch off

Category: Advanced Configuration

I found the reason for this error with the hal-meter:

If the "probe-switch" is open I've a clear FALSE if the switch is closed it toggles between FALSE and TRUE even if I press the switch so that I'm sure he's not at the break over point. And also with a second switch. I've already send the signal through an low-pass filter so I'm 99% sure that hardware couldn't be the reason.

Any Ideas?
  • andypugh
  • andypugh's Avatar
27 Nov 2010 13:27
Replied by andypugh on topic Manual tool change + tool lengh touch off

Manual tool change + tool lengh touch off

Category: Advanced Configuration

I am afraid I am completely out my depth here, as I have never done any probing.

I might get the chance to experiment later, but I have a lot of other things to do.

It is probably worth taking this query to the emc2 mailing list, as developer coverage is better there.

From the docs it really does look like you should be able to do a fast G38.2 onto the switch and then a slow g38.5 off of it. If that is not working then I suspect there might be a bug that needs squashing.
  • axel88
  • axel88
27 Nov 2010 11:51
Replied by axel88 on topic Manual tool change + tool lengh touch off

Manual tool change + tool lengh touch off

Category: Advanced Configuration

Ok, I found out that G38 need to be run in G90 mode. But even if I try to release the switch with G38.5

Code Target state Direction Signal Error
G38.2 Contact Toward workpiece Yes
G38.3 Contact Toward workpiece No
G38.4 No Contact Away from workpiece Yes
G38.5 No Contact Away from workpiece No


which shouldn't cause an error, I get one :(
  • axel88
  • axel88
27 Nov 2010 11:19 - 27 Nov 2010 11:38
Replied by axel88 on topic Manual tool change + tool lengh touch off

Manual tool change + tool lengh touch off

Category: Advanced Configuration

So far I installed a touch probe and started experimenting with the gcode. But there are some errors I can't cope with:

If i follow the tool-length-probe.ngc example i touch of with

G38.2 Z0 f50 (f50 is modified)
when I try to run
G91 g0Z.2 (off the switch) I get the error:" Probe tripped during non-probe MDI command"

This could be solved by running the probe slower (f30) but if I want to have a big safety distance this could take a long time :(
Is there a better command to release the switch that ignores that the probe is pressed?

Second Error:

I touched of my tool the first time, joged a bit with the manual control, changed the tool length and run a G30. If I try to touch of again(G38.2 Z0 f30) I get "Startpoint to close to probe point"
Displaying 285181 - 285195 out of 285941 results.
  1. Forum
  3. Search
Time to create page: 13.359 seconds
Powered by Kunena Forum