Advanced Search

@Hi Arciera,

We can do so. We could write a tooldir blended gcode file out. This then can be runned in the current interpreter of linuxcnc.
But i heard, when a,b,c are involved it falls back to no look ahead mode.

So maybe with a trick it can use look ahead for xyz, and then just output the interpolated a,b,c values?

Aciera wrote:

I think I already tried using "not" component, can you confirm this is right format?
I know nothing about EtherCAT, so I have no idea if you can get an inverted value back from the drive. What I suggested was using the built in HAL component called 'NOT'. For which you would need to use 'loadrt' and 'addf' commands and connect the input and output pins in hal.

You really should give Ethercat a try! Some Ethercat settings can have the direction altered by changing a SDO setting. But I doubt a status pin will. 

Cant do this anymore bye all wrote:

I just compiled an dloaded your comp and was just going to compare kurt's to yours. You beat me to it.
All the best, makes hal alot more manageable.

Yeh, dunno how I missed that,
The MPG is fine as I did it in Hal 7-8 years ago for this same device but I wanted to enable the Plus and Minus jog buttons that also have a third button to select between low speed and high speed jogging. That was very difficult to do in hal.

I just compiled an dloaded your comp and was just going to compare kurt's to yours. You beat me to it.
All the best, makes hal alot more manageable.

Cant do this anymore bye all wrote:

I did that a few years ago, based on the work here github.com/KurtJacobson/RF45-CNC/tree/ma...HAL%20Components/MPG does make the whole mpg setup easier.

Well that was interesting. cornholio, your link showed me I was missing this line
github.com/KurtJacobson/RF45-CNC/blob/ma...nts/MPG/mpg.comp#L14
Fixed now thanks!

Just be careful cross compiling isn't easy (if not quite possible) for Linuxcnc.

Funny how some things are in the documentation, below links to how to build linuxcnc from source. Be aware the build deps will install Apache2. Ahh the beauty of debian\ubuntu

linuxcnc.org/docs/master/html/code/building-linuxcnc.html

Yes I see, the smoothed tooldir line does not necessarily retain the constant distance from the tcp path which is fine since we are really only interested in the direction of the tool vector.
I'd say this looks quite promising!
So, does the smoothing process ingest a gcode file, process it according to 'smoothing' parameters and then output another gcode file? If so could this output file be run with the current Gcode Interpreter/ trajectory planner?

But if I  do the same thing with say o2, I get an address. What causes i tto be missing?

I did that a few years ago, based on the work here github.com/KurtJacobson/RF45-CNC/tree/ma...HAL%20Components/MPG does make the whole mpg setup easier.

Thanks Andy but I am still none the wiser
 

The user really wanted to know how to cross complie linuxcnc on a x86 platform for arm64. There's some secret customisations that he requires. Unfortunately cross compiling doesn't appear to be an option. So it's either natively on an arm machine or in qemu running arm64 binaries.
But due to the low spec of the machine (low ram) and a tested latnecy of 180us (this is using non linuxcnc latency test) I'm not sure about the suitability of the board.

Mayhaps if you had of read the thread from the beginning...........................

Thank you . Yes, Its working good with linuxcnc2.9.2 image file. But Actually i want build linuxcnc and ethercat from source that only i can able to modifies it for different UNIX device for later. could you share with me any reference for build linuxcnc and ethercat from source file.

Well done mate.

There is a lot of consumers here, unless it relates directly to themselves, it's like meh. Don't take it to heart. Unless you come up with a "pretty gui" then it's all different.

Exactly the same question, see the link provided there:
forum.linuxcnc.org/post-processors/53197...x-to-linuxcnc#304893

@Hi Arciera,

I tracked down the issue. One important issue, that was responsible for wrong cone preview angles.
The other issue i will show you in video.

The important issue was a function that calculated the abc angles from a given tcp & ta point in space.
The function was using atan... for 3 planes. However, it did not output what we want to see.

Now i changed the function to use a quaternion with config : gp_Extrinsic_XYZ. new function. This seems to work properly.

Now in next video i recorded tooldir axis lines, to show you what is the difference between

1. recorded tooldir path
2. blended or optimized tooldir path.

In the video the vertical axis lines can contain 2 different colors. One color is for recorded tooldir path. Other color
is for blended tooldir path. The axis lines can be off different lenght between path's. However they are valid as they
are on the same plane.