Advanced Search

GeckoWorks wrote:

slowpoke wrote:

I had the link for that one. Perhaps I wandered off this thread when I found it. It was a compilation of I think all of the macros showing the actual operation on a lathe much like the video you referenced, just for all the different operations quite a good video, no idea where I found it and can't seem to find it.

Thanks
I think this video does a good job of going through the macros but I don't know if it's the one you had in mind:

 

That is a different video, however somewhat similar. For a small lathe he sure is getting good results.

I'm a bit clueless regarding the available lathe type GUI's (I'm starting with axis), what version is this fellow using?

Are those the "lathe macros" he is using?



 

Hello everyone, ive been trying to set up linuxcnc to work with my Raspberrypi 5 for a week or two now, ive gotten to a point where i can load the hal_pi_gpio driver with no errors showing up, i have a config running in linuxcnc and i can see in halshow that the pins are activating and deactivating, the issue i have is that the pins only activate and deactivate in the software and not physically, i cannot measure any difference on the physical pin itself, i can use gpioset command to set the pins to high or low manually and that works well, but as soon as i try setting it to high/low using halcmd it just doesnt change state, i would greatly appreciate some assistance in setting this up correctly.

The hal file below was given as an example somewhere online, dont remember exactly where i got it but it is as mentioned supposed to work considering that halshow shows the pins and the fact that they should be changing state.

I made the 5.0.0 develop to the main branch and made a release for it.
The way the routine works is the same as you can see in the video of version 4. Also the way to install it is the same.

I was not able to make a version that is usable with all versions of Probe Basic. So I need to make a cut.
Version 4.0.1 is for Probe Basic up to 0.5.4-stable.
Version 5.0.0 is for Probe Basic 0.6.0 and it is also usable with every other GUI.

Quick question: how can I increase jogging linear and angular increment drop-down menu? Is it also in stylesheets like you did for G5x button?

I do not know how you guys even got so far: i have a Raspberry Pi 5 Modell B, 4x 2,4 GHz, 4 GB DDR4 and created images of v. 2.9.4 to SD card & USB drive with 3 different burning software including balenaEtcher. When i boot the RPi5 the drives are not recognized (as bootable) at all. With an image of vanilla Ubuntu it works just fine.

This is from some recent work on table rotation kinematics
Includes:
- Adjustable nutation angle
- Adjustable table offsets x and y
- Adjustable orientation of primary axis (from XYZBC to XYZAC)
- TCP kinematics
- python remap implementing TWP (Tilted work plane) ie G53.n , G68.n , G69 codes


Sim config including the required xyzbc_tnr_kins.comp   (use halcompile --install ... ) and full documentation can be found at:
github.com/Sigma1912/LinuxCNC_Demo_Confi...able-nutating-rotary

 

Sounds like Mesaflash needs to be updated

github.com/LinuxCNC/mesaflash

(build instructions at bottom of page)

Hi Automata,

andrew2085 was very helpfull. It was hard to get his code to work properly.

We have a robust clothoid 2-dimensional library.  
For now it lack's the 3-dimensional clothoid implementation.
github.com/ebertolazzi/Clothoids/issues/45
I am unable to create the 3d clothoid from his comments.

A clothoid needs a iteration ~20  to find optimal fit. This is also the case at a runtime interpolation when u
use the clothoid library in a standard way.

The new approach is time optimal. By this i mean the "arc-strip" method for curves of any type.
The new planner's infrastructure makes it easy to add new trajectory smooth algo's. So almost anyone can
add a algo to it. Sinds it also has a algo template.

Using a clothoid is a very good approach, i agree 100% with that.

Downside is that the real deviation is hard to find. Then 2 attached clothoids could do exact deviation.

When optimizing the path at load time, the clothoid is constructed (~20 clothoid iterations are done) and clothoid is
saved as arc_strip to be interpolated as fast as can be later on.
Soon i wil test a clothoid this way.

Julian made a test environment to test multiple cnc files in a loop. The velocity's are extreme.
We had scurve hang's in certain cases early'er this week. After figuring out, we had some isnan values coming up so now and then.
Isnan = is not a number. This can happen when dividing to zero for example.

We decided that the planner has to first pass test bench, before going any further writing smooth algo's on top.

Let's run the test environement for a few more hours.


 

Another (somewhat random) thing that came to my mind is that we can also change the 'ferror' values from gcode.
That might come in handy.

Good luck.

Hi Grotius,
maybe the biclothoid library stuff you and andrew2085 developed in a previos thread is awesome.
forum.linuxcnc.org/38-general-linuxcnc-q...ruckig-lib?start=350

Maybe that can be used for filleting. And since we can calculate the length of a clothoid given its start and end curvature, maybe it can be used for the S curve trajectory generator more easily and without approximating the arc length.

Thanks for working on this hard problem.
-automata

slowpoke wrote:

I had the link for that one. Perhaps I wandered off this thread when I found it. It was a compilation of I think all of the macros showing the actual operation on a lathe much like the video you referenced, just for all the different operations quite a good video, no idea where I found it and can't seem to find it.

Thanks

I think this video does a good job of going through the macros but I don't know if it's the one you had in mind:

Great news. Just some clarification: is this planner based on your work or it is based on Ruckig Lib with user @Beef : "That's why Grotius and I have decided to start this new project ...." ?

2.4 with round rods on Y and Z, and 10mm belts, not the usual 6mm.

Appreciate the effort.

I've had a think, and I've got one more config attempt left in me before I quit trying to have a working C-axis.

Plan is essentially what PCW suggested in my other 'freewheeling' thread.  I'm going to abandon caxis.comp, and instead use orient as a 'bridge' between velocity spindle and position-axis modes so the c-axis doesn't error out upon reconnection.

Flipping between spindle & axis will use M-codes, and I think it can be done without any halui stuff so I can do everything within the same g-code program.

I'll start a new thread when I run in to problems with this attempt.

I  guess riju didn't need one that badly.