Advanced Search

you mean this one?
forum.linuxcnc.org/configuration-tools/5...ale-vs-encoder-scale

this link has only pi 4 images, not any oi 3. what need doing can use pi 3 and linuxcnc, what is patch and how need doing, or what need doing, not understand , ready to install pi 3 image only need how need patch or what this mean and how change kernel if need no understand anything linux and code, secret engineer language all.

not understand what is compile and how need do ? or have ready to use image to rpi3.
i looking make rpi3 linuxcnc small cnc my son.
or how kernel need use or how can change kernel or what need doing. too hard all linux system but have only what can use good whit linuxcnc and rpi3 board. not want buy old computer and paraller port use this.

If gentelmen have any other tips for reducing latency .. share it please

I did changes for my machine and it runs for few days at 3khz without problem...

Reading the datas take less then 250us with timeout 100000ns and 250us is now limit... + Other stuff in the thread and we are under the 300us

Motion is smoother by the sound and scope profile and compensation of position in the velocity mode is faster==smoother ... It is real difference now

 

I'm thinking that would be a great idea.

Regards
Bob

I've just been down that road (at least one of them):

forum.linuxcnc.org/9-installing-linuxcnc...aughter-board#339636

I'm trying to figure out my options for homing everything. Originally my plan was to launch it with:
cd /home/titus/linuxcnc/configs/pullmax
halrun -I -f config.hal

within that hal I load everything else including:
loadusr gladevcp -Wn pullmax -H ui.hal pullmax.ui
also hostmot2, mesa, ethercat, etc.

This leaves me without motmod (motion), homing, etc. It is just a simple Glade + hal app.

I would like to use the full linuxcnc system instead of writing my homing and slave axis (ram control) from scratch. Maybe avoid reinventing the wheel.

I am currently studying how to load everything with like:
cd /home/titus/linuxcnc/configs/pullmax
linuxcnc pullmax.ini

Progress is coming in small increments. Currently struggling to get past this:
USRMOT: ERROR: command timeout
emcMotionInit: emcTrajInit failed
Waiting for component 'inihal' to become ready............USRMOT: ERROR: command timeout
emcMotionInit: emcTrajInit failed

full error attached
the ui comes up and works (I only got the position readouts hooked up at this point and encoder scales all at 1.0, servos all disabled yet, bumped each axis with my hands and got counts.

I'll keep poking at it. I'm learning as I go.

johnB wrote:

I wonder, is there a Raspberry HAT that can direct interface with a stepper driver ?

Thanks
Jonh.

www.instructables.com/LinuxCNC-on-Raspbe...i-With-GPIO-Control/

You are absolutely right about most of that, and it’s certainly many months in the future.
But one nitpick: what I want is not a perfectly synced machine/CAM system. It’s more a system where we don’t have to care about the sync. But let’s leave that aside for now. I can revisit it in due time and see whether it works the way I think it will or not.

Martin

The sort of thing you are imagining is a bit of a fantasy for our kind of lathe and use case. A perfectly synced tool table in CAM and LinuxCNC is unlikely to work, as you will never have enough tool holders to never have to edit them. Think drills. I can say from experience that the next size drill you need is never the one loaded.

Maybe on those big machining centers with chain type 60 tool magazines, but it is not going to happen on our set ups. 

In practice, there are two scenarios.
- You are making one off home shop/ tool shop parts. You have enough tool holders for  the most common tools, and you have assigned them pockets where they are most often used. For these jobs, you will often not program full multi tool programs, but use a mix of simple programs for more complex bits using a single tool and Lathe macros for simpler paths where you also manually swap in tools. 
- You tool up the machine for a production run. In this case you will go through and set up each tool, assign a pocket and if needed set manual break points for manual tool changes with our lathe. Tool set up is a fact of life in CNC machining. LinuxCNC can't know which tool holder you are planning to swap in manually.

There are many many more things to work through getting your lathe running under LinuxCNC before you even need to consider this issue.

 

It should work now.

I don't seem to have that handy. I will be back to the machine in a week or 2. I will make a backup and upload my configuration. What issues are you having?

Hi,
could you finally solve the following error problem with your delta Servos?

I am really interested to learn more about the problem and the final solution.

best wishes,
Gogonfa

That's a great condensed source of network latency reducing tips

Only quibble I would have is that:

setp hm2_7i76e.0.read.timeout 100000  

Is not correct as the hm2 read timeout is scaled in percent of the servo period

EDIT: actually that is correct as values larger than 100 are interpreted as ns

But a 100 usec margin is very small on most systems and will likely result in many
unnecessarily dropped packets .

Default is 80% of servo period and this is fine normally




 

How did you realise the integration loop? Is it possible to share your cia402.conf?