Advanced Search

Bad luck for me, changing boot drive did not work.

I tried to install a 'standard' debian-live-12.6.0-amd64 iso and that worked without any problem. Maybe I can use that to 'upgrade' with the LinuxCNC iso or change the installation to be acceptable for LinuxCNC. I don't know yet how to do the first or the second option.

With those settings(attached) i'm nearly there. Sometimes it is spot on, but sometimes like on the screenshot

I can see tool table is good. I changes on g43 g-code. And also adjusts g54 offsets. But there is no change in machine coordinates.
So do I have change xyzac-trt-kins.z-rot-point pin value to according to tool I am using, everytime I change tool. But I think that should not be the case.
"I notice that work coordinate changes according to tool.
But kinamatics is taking machine coordinates so there is problem in RTCP on every tool change.

Aaaaahhh paperless offices ... that never came. That was the promise made by e-mail .
Yes, print screen works on most distros, although XFCE used by LinuxCNC version of Debian did not work but it had screenshot in the main menu somewhere.

Good morning everyone. I am using debian 10 and kernel 4.19.19-rt-amd 64. I noticed that in the repositories there are later versions and I installed the kernel 4.19.27-rt-amd64 which still works well with ethercat. I also noticed that there are kernels 5.10.0-0.deb10.30-rt-amd64. This kernel would work with ethercat. Regarding performance and stability which kernel is better to use?
Thanks

Thank you very much for your help, it worked, I've been trying to get this to work for a while, thank you for your help, I hope I have enough knowledge to be able to reciprocate someday

You are great, thank you very much. I will try to do it tomorrow.

Schematic for the wizzy part. In case someone needs that. Never know...

meister wrote:

it always depends on the application,
 

True. Let's hope that badboy will be fit for a 4ax mill, 2ax lathe and ofc a 3ax co2 retrofit (<- my first project). Nice connector link up btw, I use the same although in a 2.54mm pitch. 

Too kind, as always. Thanks for sharing your expertise. I've removed the uart interface, will add a ws2812b status led, and added an automotive 2A input supply from MPS (supporting 9~60vdc). That should work with my 24v and 48v PSUs. For the remaining bits you've advised, I'm eager to simply add bidirection translation for the 50 gpios and send that out "as-is" rather. Reason for this is; I want to test ALL gpios on that unknown-to-me fpga before sending out a final board version. Would that be a fair approach? 

Tiny motion control board, although likely to pack an incredible power (thanks to the Rio Cult!!). Still plenty real-estate for the translation and other upcoming gizmos. 

Hi

Is there an example on the forum of how to do this? I guess it would just be based on the relevant HAL pin?

If M3 is active, I would like a large red icon, if M5 is active either a grey version of that or nothing

tommylight wrote:

Screenshots should do just fine, upload her on the forum under the editor click on "attachments"
 

how to get screenshots ? push the PrtScr button ? I can also add pictures ?

also might be interesting to mention that you need to have a wired internet connection to do the install... probably because i missed some part in the 1330+ pages to read , i tried to get stuff done over wifi... it's not working over wifi
I hope that i will get linuxcnc-ethercat to work and i will for sure make a contribution to the forum with how i got it to work. super detailed ... taking notes about everything ... imagine when everybody was saying ... " when pc's will be completely integrated in modern society , the usage of paper will be decimated!" hahahahahahahahahhahahahahahha

There is really no control mechanism that can compensate for backlash
in a very satisfactory way, especially if the cutting forces can reverse.

Linear scales can compensate for ballscrew thermal growth, and flex
in the drive system in response to acceleration and cutting loads.
With any system you would need a way to read the scales and combine
the scale information with the main position loop.

Typically 2 PID loops would be involved as the tuning of the scale feedback
would have lower bandwidth than the much more tightly coupled rotary
encoder feedback.

 

I am a little bit confused about what to download, the one Rodw put on google drive or the one that was posted on 03/08
because I got the same errors about the opensuse stuff
it was really hard for me to get my boss to agree with changing from his hacked mach3 shit to linuxcnc with ethercat ...

Thanks.
Do I read between the lines, that you think it hardly makes sense?

If the hardware would be “perfect” with no backlash at all, there would'nt be an necessity for linear scales… And with backlash it is “problematic”.

Originally, the machine had tacho’s on the motors, to detect the motors were spinning and to control theirs rpm... Based on the position measurement of the linear scales (distance to go), the loop was closed until position was reached.

Would that principle be different if I would use step/dir instead of analog +/-10VDC in the old situation? The resolver needs at least 10x higher resolution than the 1um resolution of the linear scales I presume….

And is there then a necessity for a drive with two resolver inputs? Or can a controller-card take over the correction of backlash (which will be in any case)
Do they even exist without paying the highest price?