Advanced Search

cakeslob wrote:

edit, tommy, there is actually a separate abort function specifically for probe abort for this easyprobe addon called probe_escape.ngc that does other stuff 

I am glad!

If it's related to that issue then we should expect this to also show up using the Axis GUI. Are you seeing it in Axis as well?

Hi,

First off all thanks for the many likes, is appreciated.

Today we made a linuxcnc installer.
Can someone help me to verify if it works ok?
I could be we miss some things.

Work of today:
1. Created a new  cmakelists.txt for the clothoid project.
2. Created a library  motionizer to calculate the best vo's, ve's, vm's  for the trajectory. Also based on curvature input.
3. Created a project installer
4. Renaming of directory's, etc.


 

bkt wrote:

....now the motorbike has dust and it's been almost 10 years.

Same here, been over 3 years since i went for a ride on any of the bikes!

Reliable computer will not help you, any computer will do.
The thing with plasma is they create huge amounts of interference when striking and arc, so grounding and proper shielding are mandatory.
Normally you can get away with Mesa 7i96S and THCAD, and they are extremely reliable.
Here are some ideas:
forum.linuxcnc.org/show-your-stuff/38547...plasma-build?start=0

Mind you there is a fair number of companies and individuals (even some that frequently ask for help on this forum) that make a living using LinuxCNC without giving anything back to the community. Just recently I came across a company in the US that sells Linuxcnc 2.6 (!) installed on a mediocre PC for 1200$.

What PC?
Did you disable power saving options and hyperthreading in BIOS?
What hardware?
What Linux version?
What LinuxCNC versions?
RTAI or RT_Preemt kernel?

2500rpm/60sec=41.66RPS
600PPR*4=2400counts per revolution
41.66*2400=100000 counts per second.
It should work as long as you use the interupts in arduino, so no "digital_read" in the code.

Hi Bkt,

Could be missing a header include path.
But can also have other reason's. Some times hard to say what the cause is.

As has been pointed out, this issue regarding strange moves after stopping a program seems to have been reported on several occasions on older versions of linuxcnc:

I found the trigger. If I use ON_ABORT_COMMAND to call a subroutine:
ON_ABORT_COMMAND=O <on_abort> call
even an empty sub will make it fail. I got the file down to this and it still failed:

o<on_abort> sub
o<on_abort> endsub
m2

If I comment out ON_ABORT_COMMAND I can't get the fault to happen.

github.com/LinuxCNC/linuxcnc/issues/579

So removing the ON_ABORT_COMMAND from the ini file should fix this for you if you are on some earlier version.

[edit]

I will try to get the config zipped and posted here.

No need for that anymore as the bug has been identified to be in the source code of your version of linuxcnc

I got the test report from JT, but nothing else.

I noticed that most of the blocked IP's are 30 minutes but some are 1 day and some are unlimited.

I just did a test report but don't see it anywhere...

JT

Interesting, I wonder if they contribute anything back to the community.

I'm not sure what I changed I just stared from scratch brand new everything fresh install of linux and it works fine. thanks for the help mate and sorry for the hassle.

beavertech.ru/stanki/beavermill-mini



You get a good look at 1:25