Advanced Search

You should be able to use pncconf to setup your spindle
The firmware does not affect the spindle setup as the analog
spindle setup would be the same regardless of firmware.

A possible exception would be if you used the breakout board
to generate the analog spindle control voltage, but this would
really only make sense if you needed two analog outputs.
 

Hi everyone, I hope you’re doing well.

While going through the electrical diagrams of my machine, I noticed something I don’t fully understand. The schematics show a clutch on each axis. Could someone explain what exactly this means and what role the clutch plays? Is it connecting or disconnecting the motor from the ballscrew, or something else?

I’ll attach the diagrams for reference.

The spindle part I’ve already figured out, since I found out how the connections and control signals are set up. Right now, I’m working on counting all the inputs I will need to make sure the Mesa board I choose has enough capacity. Fortunately, the linear scales output 5V signals, so that part looks straightforward too.

Thanks a lot in advance — I’d really appreciate your input and experience on this.
 
 
 
 
 
 
 
 

This is the output of ip a

cnc@linuxcnc1:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 2c:cf:67:3a:15:bb brd ff:ff:ff:ff:ff:ff
    altname end0
    inet 192.168.0.153/24 brd 192.168.0.255 scope global dynamic eth0
       valid_lft 799842sec preferred_lft 799842sec
    inet6 fdce:a2be:2d61:0:2ecf:67ff:fe3a:15bb/64 scope global dynamic mngtmpaddr
       valid_lft 7124sec preferred_lft 3524sec
    inet6 2003:e4:9741:1e00:2ecf:67ff:fe3a:15bb/64 scope global dynamic mngtmpaddr
       valid_lft 7124sec preferred_lft 1191sec
    inet6 fe80::2ecf:67ff:fe3a:15bb/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether aa:57:f1:85:a9:88 brd ff:ff:ff:ff:ff:ff
    altname enp1s0
4: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 2c:cf:67:3a:15:bc brd ff:ff:ff:ff:ff:ff

When connecting the eth1 port to my network switch I got an information from my router, that it assigned a new IP adress to the ethernet card with the MAC adress of eth1. So I assumed that it should be possible to reach that port via ping. This ping was done from a windows PC in my network. All four tries timed out. But looking to the result of ip a above, the IP adress is not shown on Linux side. This I did not see before.

The reason why I would like to use this second ethernet is because my workshop is in the basement of my house and the RaspberryPi is in a metal housing within a metal cabinet. Finally I like to use my devices hardwired instead of using WIFI. I thought it would be straight forward to put in an additional ethernet card, activate PCIe and then be able to use it.

Unfortunatelly I am not an Linux expert and I am not a native english speaker, so if I miss something from your advices please give me a hint. I will try to make it. 

I throw this here because someone will need it, they removed it from the product page: software stepperonline OMC A6 help.stepperonline.com/en/article/how-to...series-servo-edqavw/

I've already mentioned that Realtek NICs can cause latency issues and the dkms package may need installing.
I kind of the OP skipped over that part or just ignored it. Anyways I think the issue at hand is to get the interface up and running and cross the Realtek driver later.
As it was the OP was claiming the Linuxcnc image was not recognising the interface and after digging that was found not to be the case.
To tell the truth the wifi adaptor of the RPi5 is quite good, even within the confines of a metal case, and is more than enough for transferring files via samba, nfs or sftp (which is my preferred method). Ssh sessions are a non issue as well.
Given the choice of Nvme or a second NIC, Nvme will win, if a second wired network interface is needed a usb3 one will be fine, probably better if you can find one that isn't Realtek based.

You can download the software in the same page where you buy them. I throw this here because someone will need it, they removed it from the product page:  software stepperonline OMC A6 help.stepperonline.com/en/article/how-to...series-servo-edqavw/

I still don't get how to auto tune them even if there is an autotuning section inside the software.
Oh and try different USB cables, some doesn't just work, the software is straight on if the servo is usb connected it recognize it if you select the right port of your computer. Please update here if you succesfully auto tune them and explain. Thanks

I'm trying to get the nvpmg to work. In halshow the inputs 1 to 9 are switching. But when the counts for the mpg are not working. Encoder.0. does not count when the mpg is moved. I have tried both input.19 -- input 25 and input 27 and 28 in the nv-mpg.hal but still nothing , should the switch be set the nv or std ? 

^^^^^
Have it sorted encoder inputs were on 20 and 21

Headers are already installed, and because of the kernel coming from the RPi GitHub repo, there are no Debian packages to suit the installed kernel.
will inform you of the info, including addresses, of all your network adapters.

If you could try that as well as the output of the ping command to that IP would be helpful. "It doesn't work" or some other statement along those lines without any additional information makes it very difficult and time consuming to help.

If the second NIC is for ethercat or a Mesa Card, I would use the on board Broadcom NIC for it and the Realtek card for internet connectivity.
The DKMS driver should exist for the Pi on Debian. You may have to edit /etc/apt/sources.list to add non-free to the Deb stanzas so it can find DKMS.
Worst you can do is break it again...
sudo apt update
sudo apt install linux-headers r8168-dkms

Hmm, Debian's wiki is as out of date as Linuxcnc's.

Untested, but I think the the correct way to bring a interface up should be:
ip link set dev enp2s0 up

So I think the interfaces file should be
pre-up /sbin/ip link set dev $IFACE up
post-down /sbin/ip link set dev $IFACE down

I did find a igc kernel patch Intel was involved in so I think its OK to ignore:Subject: [PATCH] net/igc: disable EEE by default on I225/226
>
> I226-V devices can hang when EEE is enabled. Explicitly disable EEE during
> initialization of the device, as the Linux and FreeBSD kernel drivers do.Also, I think we should disable all power mangerment in grub:
pcie_aspm.policy=performance pcie_port_pm=off

So many gotchas!

No, up to now I did not configure anything. I installed the Gnome network manager and plugged the network cable to the ethernet port. I got an information from my router that it assigned a new IP to that ethernet port, so I tried to ping on that IP.
As I wrote, I will take my time and try to read and understand how to configure the new NIC in Linux. I have worked with Linux several times in the past, but I am more a noob than an expert in Linux.

Have you configured the waveshare NIC to get an address via dhcpd ?
Have you done anything to configure that interface ?

Using dmesg gives information if I unplug and plug the network cable on eth0 and eth1:

cnc@linuxcnc1:~$ sudo dmesg | grep eth
[51259.808328] r8169 0000:01:00.0 eth1: Link is Down
[51334.956935] macb 1f00100000.ethernet eth0: Link is Down
[51336.323225] r8169 0000:01:00.0 eth1: Link is Up - 100Mbps/Full - flow control rx/tx
[51431.494868] r8169 0000:01:00.0 eth1: Link is Down
[51433.262584] macb 1f00100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control tx

If I connect the port to a network switch it is getting an IP from the router, but it is not possible to ping to that ip. I will try to read some more about how to get that working.

Hello , i've got the same Problem but the manual doesn't help me.
Have you solved this problem?

Hi,

So I got my spindle and VFD wired up as you mentioned but as I am new to LinuxCNC I don't know how to set up my LinuxCNC to run my spindle. I am using 7i96s_5abobd.bin firmware if that has any impact on this. Thank you for being so helpful.