Advanced Search

Hi guys i have been updating to the latest 2.9.3 pre-empt iso and seem to have an issue with my settings.
The last time i set up the machine i had a nuc which had realtek nics because i was running debian 10 i was able to select a slightly older board to make the compatibility, but with the debian 12 i have moved on to a slightly newer computer with intel 226 nics.

This newer board seems fine but i am having issues that i can't pin down.
So in summary i can't latch out of e-stop.the settings are the same, but it seems to be an issue.
 

Ha, so here we are for pathpilot. Seems to behave exactly like i imagine it would. Woo.



I guess I need to go look at the probe basic features now.

Hi Mark,
While I looking around for stuff on the previous entries I came across these 2 images, I can't recall where I got them from. They relate to stuff we discussed a way back. I mentioned that the resistors on the gear change were never invoked on my machine. I translated the images using Google, which I know you don't need, but I see at the bottom they mention the resistors are not needed for later Mahos. Mine is certainly fine without them. I'm thinking that the earlier Philips controller would have been much slower and maybe could monitor the cams fast enough. The diagrams are also the first I've seen that explain the actual reason for cams 4 and 5. So it may be that with the massive improvements in clock speeds since then the LinuxCNC conversions may not need them either? Mine still uses cam 5 as I recall to decide which way the ladder code hunts a cam lobe first. Presumably for the case where you've had a crash and it's not on a cam lobe.

Another thing I'm surprised at is that in the LinuxCNC conversions you keep a lot of the relay logic. Wouldn't it be better to shift the I/O for that into the computer and make it "fly by wire". As it stands there is a lot of relay logic outside LinuxCNC that it doesn't know about. You would still need relays for shifts in voltage like 5K1, but it wouldn't be for logic. On my machine it would involve a more than it can do I think. But in both our cases it seems we have a dinosaur brain sitting in parallel with a modern one.

Cheers,
David

Cool. That's seems to be the same function I need. I just need it to be in a probe cycle.

That answers the "is it there" question for sure. Thanks.

QtPlasmaC does that with a camera, see here
www.linuxcnc.org/docs/devel/html/plasma/...c.html#plasma:camera

Working on my larger machine and based on the work I'm gonna use it for, being able to probe a part or work piece and then have the machine not just offset but also rotate the coords would be nice. For clarity, I want to stick stock down and if that stock happens to be 12 degrees out of square the probe will measure and then rotate the program to match the stock. (12 degrees is extreme of course, but it gets the point across).I understand linuxcnc *can* rotate coords, but beyond that I know nothing on the topic. Has anyone made use of this? How does it work? 

 
 
 

Gave it a try, still reboots when enabling LinuxCNC.
Have to try another module just in case.

For the impatient, here are all the commands after installing the OS with a GUI

"The forum always changes the hyperlinks, so when you do the "git" clone commands, type out the full hyperlink"

sudo apt update
sudo apt dist-upgrade
sudo apt install linux-image-rt-amd64
sudo apt install linux-headers-rt-amd64
sudo reboot
uname -a
dpkg --list | grep linux-image
sudo apt remove --purge linux-image-(THE REST OF THE KERNEL NAME FROM GREP)
sudo apt install git build-essential
git clone github.com/LinuxCNC/linuxcnc.git   linuxcnc-dev
cd linuxcnc-dev
git checkout master
cd debian
./configure uspace no-docs  
cd ..
dpkg-checkbuilddeps  
sudo apt install  "LIST OF DEPS COPIED FROM DPKG-CHECKBUILDDEPS"
dpkg-checkbuilddeps  
cd src
./autogen.sh
./configure --with-realtime=uspace --disable-build-documentation-translation
make
sudo make setuid
. ../scripts/rip-environment
linuxcnc   (this will fail and you run the script below to get LCNC working)
~/linuxcnc-dev/lib/python/qtvcp/designer/install_script
2  (YOU CAN CHOOSE 1 OR 2 DEPENDING ON IF YOU WANT TO EDIT OR NOT)
cd ~
git clone gitlab.com/etherlab.org/ethercat.git ethercat-master
cd ethercat-master
git checkout stable-1.6
./bootstrap
sudo lspci -v
./configure --sysconfdir=/etc/ --disable-8139too --enable-userlib --enable-generic
make all modules
sudo su
make modules_install install
depmod
exit
ip a
sudo pico /etc/ethercat.conf
   (FIX YOUR MAC ADDRESS AND DEVICE NAME, THEN SAVE AND EXIT)
sudo systemctl enable ethercat.service
sudo systemctl start ethercat.service
sudo systemctl status ethercat.service
sudo chmod 666 /dev/EtherCAT0
ethercat master
sudo pico /etc/udev/rules.d/99-ethercat.rules
   (ADD THIS TO THE ABOVE FILE)
KERNEL=="EtherCAT[0-9]", MODE="0777"
   (THEN SAVE AND EXIT PICO)
sudo udevadm control --reload-rules
cd ..
git clone github.com/linuxcnc-ethercat/linuxcnc-ethercat.git linuxcnc-ethercat
cd linuxcnc-ethercat/src/
sudo pico Makefile
   (Now comment out part of lines.  Just add the “#” where shown below:)
   (At line 83 of the code, comment out “lcec configgen”)
user: lcec_conf lcec_devices #lcec_configgen
   (At line 92 of the code, comment out the whole line)
# cp lcec_configgen $(DESTDIR)/usr/bin/
   (At lines 113 - 121 of the code, comment out the whole line)
#lcec_configgen: configgen/*.go configgen/*/*.go
# (cd configgen ; go build lcec_configgen.go)
# cp configgen/lcec_configgen .
#configgen/devicelist: configgen/devicelist.go
# (cd configgen ; go build devicelist.go)
#configgen/drivers/drivers.go: configgen/devicelist lcec_devices
# (cd configgen ; go generate)
   (THEN SAVE AND EXIT)
cd ..
make clean
make
make install
sudo pico /etc/ld.so.conf
   (ADD THIS TO THE ABOVE “ld.so.conf” FILE)
/usr/local/lib
   (THEN SAVE AND EXIT PICO)
sudo su
ldconfig -v
exit

Then you setup your XML and LCNC config and that's it...

I did this a little different because of the forum changing the format

 

I'm trying to get the gowin toolchain up and running on rpi5. It gives me an error when execute making all.I see you've already mentioned this error. I downloaded and cloned the dev version and it still doesn't work. Any tips...

I see there is another option 'generic_spi'. I will test that on rpi5 too just to get that toolchain working. I don't want to take the TN9 out of the device and program on windows anymore.

 

Uthayne wrote:

Thanks! I was able to get it to work by connecting my components pause-program output to the qtplasmac.ext_pause (I haven't updated yet to try to the ext_pause_only).

Worth noting that I added the _only pin with you in mind. It’s because the program can also be resumed if that pin you are currently using is triggered again somehow. I figured having the option to only pause no matter how many times the pin is hit may be handy.

Uthayne wrote:

I do have another question on why it can't go back further than the last M03 (or any M-code)

That is a limitation of the reverse run feature that was added to LinuxCNC a few years back. From memory it is in the trajectory planner.

Hello everyone,
I’m not sure if I posted this in the right section, but if I did, I’ll move it to the correct place if possible.
My name is Marco, and I recently came across LinuxCNC. I’m planning to build a new 3-axis CNC (which will be upgradable to 4 axes in the future) using LinuxCNC on a Raspberry Pi 4 or 5. I’ve found there are a lot of options available and would really appreciate some help deciding which one to pick.To clarify things a bit, here are some of my findings:These are some options I’ve looked at:
1) Linumeric V3
2) 
3) github.com/ChrisWag91/PI-LCNC
4) www.forum.linuxcnc.org/18-computer/51816...lug-and-play?start=0
5) github.com/jzolee/HAL2UDPI’ve tried to choose one, but I’m still quite confused, so I thought I’d ask someone with more experience than me.
Since I’m Italian and don’t speak English very often, there’s a chance I might have made some mistakes in this post.
Thanks a lot in advance for your patience and attention!

PS. in the past, i had the opportunity to work with a 3-axis cnc running on mach3 via the LPT port. If it matters by any chance.

endian wrote:

hi,

if you are building ethercat-master from source... there is possibility to disable eoe on master during ./configure script for example

./configure --sysconfdir=/etc/ --disable-8139too --enable-userlib --disable-generic --disable-eoe --enable-e1000e

but I am fighting with them right now to install non generic driver because in responsitories is only generic possible ..

 

Sorry for the basic questions.  Where do you enter that command?  Do you put it in a file during the build process?
And while I'm at it, what method do you use to build from source?  I'm new to this.  I'm just trying to disable EoE.

maybe... ill give it a shot, but I feel like the tip of the cone thing should be ON the actual tool path. and the toolpath itself shouldnt be below the min z level.