Advanced Search

i had debounce the proxmitiy sensors in the HAL with debounce.. value is 5.

then i think we need to talk about my toolchange.ngc.
do you want it in english or german... because i wrote all comments in german).

thanks andy

It might be worth debouncing the proximity sensor signals in HAL. (there is a "debounce" component.

The "strobe" pin is an indication that the position inputs are valid. During positioning of a binary or gray-coded carousel there may be transient values on the inputs (caused by the sensors not all seeing new edges at the same time) that would indicate incorrect positions. The "strobe" pin is a shorter pulse that indicates that the position encoder sensors are centred on their targets and will be reporting the true position. It will also indicate that the carousel is correctly aligned on an actual pocket.

In that case the fix should be in the just-released 2.9.5 release. (so you probably won't have to build from source again)

There may be some info here: www.forum.linuxcnc.org/48-gladevcp/28429...-hot-keys-on-widgets

But skimming it doesn't look particularly promising.

I haven't made helical gears, but I am sure I could if I wanted to. It's just a matter of increasing the hob angle and adding in a proportion of the feed distance into the gear blank angular position.

Some links: My first YouTube video (filmed with a potato) where I explain the concept.



The current, much improved setup:



A screenshot of my (written just for me, so not very pretty) GUI. Of note is the top left section that calculates gear parameters based on entries in any gear system (mod, dp, cp). You will see that helix angle is included in the settings, but is currently not implemented.

wiki.linuxcnc.org/uploads/Screenshot.png

And all the files that are used are here:
wiki.linuxcnc.org/uploads/hobbing.zip

Are you sure that EVAL[.....] is valid? Is that documented somewhere?

I don't recognise it as one of the documented unary functions, but can see examples of its use on the forums. I know that py and pyrun exist (I can see them in the source code, they may not be documented) but eval has me stumped.

I'm going to open it up under the Elastic License 2.0. The repo isn't public yet because the internal API is a mess and running it locally is not trivial. So for those that are wary of web services I'll also include a script to make running it locally easy.

tommylight wrote:

LinuxCNC 2.10 can do tandem axis, i do not know if 2.9.4 can.
You need this for the axis with 2 motors, and this way you can change direction of those motors separately, and this does require home switches for each joint that you already have, so all good.

I've never seen LinuxCNC with MATE, only XFCE.
It looks so much better than XFCE!

(Though it brings back bad memories of GhostBSD)

Is it open source?

I recommend MIT (released to all to do with as they wish) or GPL v2 (If people make edits, improvements, forks, they have to release their edits so you, and others, can benefit from them).


If I ommited any letters, I'm sorr; my keyboard has many almost-broken keys.

Your employer is weird.

What's wrong with swapping 2 wires?

Simple, reversible, easy.

Whatever, the tandem axis seems like a good solution.

You have 4 home switches, meaning you only have one input pin for E-Stop, limit switch, etc.

A parallel port only has 5 input pins from machine to PC.

You can have an E-Stop input, you can have a hardware limit switch input, but not both.

Hi andy

Yes i change the stuff from rev-dc 100 to -100... it works.
Still struggle with issues. Possible i can get help from u?
Today i look to the 3 signals from the proximity sensors.. found out that there are some spikes.. but the spikes are only a noise on the signal.. not in the area that they toggle the gpio.

I think my ngc is the issue.
Later i add some debug lines to see where it stops working.

I am xonfused about the strobe pin.. and dont understand the usage.

I use sense0 as index for homing and sense1 for the slot sensor on the slottee disc.
Some time ago you wrote i must use the strobe for the slot disc. But dont understand it correct. Can you please explain a little more please?

Thanks

Hi all,

I decided to build my ideal plasma cutter CAM program over the summer after being dissatisfied with our options for generating QtPlasmaC gcode. 
I've got it to the point where it is useful, so I'm opening it up for previews. 

Please have a look at metalheadcam.alan-gibson.workers.dev. Give it a try and post bug reports and feature requests in this thread.

The basic workflow is:
- Click the hamburger menu and then Tools so you can add your tool parameters
- Import a DXF file on the Import stage
- Skip the Edit stage for now as it doesn't do much yet
- Click the Apply All button on the Prepare stage
- Add operations to parts and shape chains on the Program stage
- Simulate the program on the Simulate stage or just skip it
- Download gcode on the Export stage

Thanks and I look forward to your feedback.
 

LinuxCNC 2.10 can do tandem axis, i do not know if 2.9.4 can.
You need this for the axis with 2 motors, and this way you can change direction of those motors separately, and this does require home switches for each joint that you already have, so all good.

Thanks MaHa,

The bracket syntax worked great, however, I'm still not able to access the INI vars after adding the INI_VARS = 1 to the ini file. Is there another setting that I'm missing?

Here i am again.. this shows us the original circuit of the original controller . the proximity sensor switching gnd. Its a npn normaly open proximity sensor without shielded cables.
Sensor is powered with 24v.

my now setup is:

the output cable from the sensor goes direct to my mesa 7i92t. i see the gpio toggles if i bring the sensor to some metal. it works. the mesa 7i92t is jumpered to pullup.


if i use this circuit i must set the jumper to pulldown. correct?
 

thanks for your help