Advanced Search

What is the actual command are you using for ping

So with the official image if I install Network Manager then it fails at between 50k and 70k pings... However if I leave the network bone stock like the image (so using commandline and config files to manage) then 100000 pings at 1ms/ping and a response time of 0.105ms so yah... I think it was Network Manager that was the problem.

Thank you. I made onother step towards spinning this motor because of that for sure!
I thing I got my XML wrong now.
Slaves:
cnc@raspberrypi:~/dev/hal-cia402$ ethercat slaves
0 0:0 PREOP + EK1100 EtherCAT-Koppler (2A E-Bus)
1 0:1 PREOP + EL1008 8K. Dig. Eingang 24V, 3ms
2 0:2 PREOP + EL2008 8K. Dig. Ausgang 24V, 0.5A
3 0:3 PREOP + AS715N_sAxis_V0.10

XML I got from MWalz but I changed slave idx from 0 to 3
I'm not sure but it is looks like logical thing to me.

<masters>
<master idx="0" appTimePeriod="1000000" refClockSyncCycles="1">
<slave idx="3" type="generic" vid="00400000" pid="00000715" configPdos="true" name="A6">
<dcConf assignActivate="300" sync0Cycle="*1" sync0Shift="25000"/>
<watchdog divider="2498" intervals="1000"/>
<syncManager idx="2" dir="out">
<pdo idx="1600">
<pdoEntry idx="6040" subIdx="00" bitLen="16" halPin="control-word" halType="u32"/>
<pdoEntry idx="607A" subIdx="00" bitLen="32" halPin="target-position" halType="s32"/>
<pdoEntry idx="60B8" subIdx="00" bitLen="16" halPin="touch-probe-function" halType="u32"/>
</pdo>
</syncManager>
<syncManager idx="3" dir="in">
<pdo idx="1A00">
<pdoEntry idx="6041" subIdx="00" bitLen="16" halPin="status-word" halType="u32"/>
<pdoEntry idx="6064" subIdx="00" bitLen="32" halPin="pos-actual" halType="s32"/>
<pdoEntry idx="60BA" subIdx="00" bitLen="32" halPin="touch-probe-1" halType="s32"/>
<pdoEntry idx="60BC" subIdx="00" bitLen="32" halPin="touch-probe-2" halType="s32"/>
<pdoEntry idx="60B9" subIdx="00" bitLen="16" halPin="touch-probe-status" halType="s32"/>
<pdoEntry idx="603F" subIdx="00" bitLen="16" halPin="fault-code" halType="s32"/>
<pdoEntry idx="60FD" subIdx="00" bitLen="32" halPin="DI-status" halType="u32"/>
<pdoEntry idx="60F4" subIdx="00" bitLen="32" halPin="follow-error" halType="s32"/>
</pdo>
</syncManager>
</slave>
</master>
</masters>

And I got this report

Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/lib/tcltk/linuxcnc/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.9.3
Machine configuration directory is '/home/cnc/linuxcnc/configs/v2xt'
Machine configuration file is 'EtherCat_2025-01-13.ini'
INIFILE=/home/cnc/linuxcnc/configs/v2xt/EtherCat_2025-01-13.ini
VERSION=1.1
PARAMETER_FILE=linuxcnc.var
TPMOD=
HOMEMOD=
TASK=milltask
HALUI=halui
DISPLAY=axis
COORDINATES=X
KINEMATICS=trivkins coordinates=X kinstype=BOTH
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
emc/iotask/ioControl.cc 786: can't load tool table.
Starting HAL User Interface program: halui
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Found file(REL): ./Basic.hal
Shutting down and cleaning up LinuxCNC...
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
Note: Using POSIX realtime
HAL: ERROR: duplicate component name 'lcec_conf'
lcec_conf: ERROR: hal_init failed
./Basic.hal:6: waitpid failed lcec_conf lcec_conf
./Basic.hal:6: lcec_conf exited without becoming ready
6928
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

Should I change something in Basic.hal or this is my XML wrong?
Will appreciate any help guys.

Samba (SMB) is pretty easy to install. Just set it up to share your home folder. Plenty of online tutorials
The sneaky bit is by default Windows disables access and you have to change a policy to enable it.
I like to map a share to my Linuxcnc home folder on a windows box so you can save gcode straight to the ~/linuxcnc/gcode folder from Fusion360 and Sheetcam.

Samba was the next thing I was going to address.
Simple sharing by using the file manager no root intervention required .
Tho if you need file sharing from Linux to Linux NFS is a far far better solution.

I couldn't get wpa_supplicant to work at my site. Being the lazy ass I am I found it easier to just edit the interfaces file.
Then working out I was even more lazier, and I like to enable and disable wifi on the fly, I installed network-manager-gnome.
To be honest I'm thinking that building an update image for the RPi 5 with network-manager might be worth it. If users want to use the gpio driver they'll have to disable it
Why didn't someone read the info with the download ?
1: people are lazy
2: people don't pay attention they just want the instant reward
3: they just download from a link.

I put up a link to the Debian way of setting up networking, but I don't think people read this thread or read a thread from the beginning.

Why didn't you follow the instructions on the Downloads page to setup wireless networking and simply type:
sudo menu-config ?

Re a fixed IP wired connection for Mesa Ethernet card, follow the directions in the man page for hm2_eth (type man hm2_eth) or follow this link.
linuxcnc.org/docs/stable/html/man/man9/hm2_eth.9.html
If you are using a wired connection for internet, there should be nothing to set up as it will get an IP address from your router automatically using DHCP. 

Hi,

Still in regard to the image linuxcnc.org/iso/rpi-4-debian-bookworm-6...25-01-27-0404.img.xz, I have found the following information useful:

1. The desktop is XFCE, we can find out using the command echo $XDG_CURRENT_DESKTOP.

2. In regard to enabling Wifi.

This image comes with no network manager tool, nmcli is not available.

ChatGPT suggests the following steps. And I have carried them out successfully.

Please note, I had to switch to superuser to run the below commands.

To switch to superuser, use sudo su -.

a. Connect Using wpa_supplicant (If No NetworkManager).

b. Generate a configuration file:

[
wpa_passphrase "<WIFI_NETWORK_NAME>" "<WIFI_PASSWORD>" | sudo tee /etc/wpa_supplicant/wpa_supplicant.conf
]

c. Start wpa_supplicant:

[
wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
]

Please note, wlan0. I think this is called network device name. We can find it out using the command ip link show, there are several output entries, I just guessed which on is the Wifi one, and lucky it was correct

d. Obtain an IP address via DHCP:

[
dhclient wlan0
]

e. Persist WiFi Connection (For Boot Time). Ensure it's enabled at boot:

[
systemctl enable wpa_supplicant
systemctl start wpa_supplicant
]

f. Test connectivity:

[
ping -c 4 8.8.8.8
]

It should give successful responses.

g. I restarted the machine. And still have Wifi, but there is no Wifi icon. I have not been able to get it to display.

3. In regard to Remote Desktop Connection.

I followed this article phoenixnap.com/kb/debian-remote-desktop and get it to work successfully.

Connecting from my Windows 10, the desktop just displays rubbish. It is not usuable.

4. In regard to directory sharing.

Samba works successfully, just like in Ubuntu and Raspbian. The setting up process is pretty much the same.

Thank you and best regards,

...behai.

Hi,

Thank you for the thread. It is very informative.

In regard to the image linuxcnc.org/iso/rpi-4-debian-bookworm-6...25-01-27-0404.img.xz
and locale, I have been able to verify that locale en US.UTF-8 works for PNCConf.

And after using menu-config to set the locale, I had to restart the machine for it takes effect.

After machine restarted, we should verify the locale. On a terminal window type locale the output should match.

-- I did try to set the locale to en AU.UTF-8 and it did not work.

Thank you and best regards,

...behai.

 

(Sorry for double posting. Cant edit last post, can only see the block quote when i try to edit)

I found a solution for my missing WiFi connections.
Second method mentioned in the top reply. (first method didn't work for me)
askubuntu.com/questions/71159/network-ma...s-device-not-managed

***
.....
Then open the file:
sudo nano /etc/network/interfaces
Delete everything in that file and copy and paste the following:

auto lo
iface lo inet loopback

Save, stop and start network manager:

sudo service network-manager restart
***
I had to reboot my whole system but after that WiFi works like expected.

I can at least confirm a pi 5 that is able to find WiFi networks. In my case nmtui did work I chose something I remember was called ‘activate network’ and it would show a bunch (and prompt for password).

With kind regards,
Jairo 

edit: this is on the latest linuxcnc image 2.9.4 by rodw 

Thanks for the reply jairobbo!
That is really weird. I did exactly that but my list appear empty. Fresh install 2.9.4 and thensudo apt install network-manager
Did you use the 2.9.4 from downloads page, I think thats rodw's, right? Version of Rpi5? (I have the 4GB)

I also tried sudo apt install network-manager-gnomeAnd when I pop down the little menu there is a grayed out text "device not managed" and under that is only VPN connections. Any idea what might be off on my system?

Yeah the whole switch from Ubuntu to Debian cost me a ton of money. I'm a Linux guy myself and I can work in any Linux distro even if it hurts my eyes, but we couldn't do that to our customers, most of whom are scared of Linux in the first place. We stayed on 2.6 until UEFI forced us to update to 2.8 and then again when parallel ports finally dried up and mesa cards forced us onto 2.9. Now PC motherboards are almost obsolete in general, and the switch to rpi was forced, but has actually been pleasant thanks to a lot of yours efforts

And finally for up to date info on the RPi and the images please jump to:
forum.linuxcnc.org/9-installing-linuxcnc...the-rpasberry-pi-4-5

Hopefully this will end up as a one stop for most issues and advice.

Regarding Network Manager

This will install the panel applet and network-manager making managed networking easier to setup.

For a description on networking the debian way.
wiki.debian.org/NetworkManager

I'll admit I'm not a huge fan of the std xfce panel setup, but that's easy enough to change.
Actually I prefer MATE and have made images for myself with the MATE desktop without any of the XFCE4 hangover, but it is simple enough to install MATE on the std linuxcnc image, whether amd64 or arm64.

With regards to wifi & networking in general.installs network manager & the gnome applet. The reason this has been left out is because there were some latency issues, I think with the 12.x series being far better this is not such an issue.
I like the gnome applet as I like to turn wifi off when running Linuxcnc.

If a touch screen enumerates as HID it will just work. As the images we build use the RPi-Linux sources it may be a kernel module that isn't included in our build to support non HID touchscreens.
On screen keyboard, just a package we don't include.
Reasons for not using RPIOS, the fact that it uses wayland as a default and X compatibility layer is very slow, so slow that there is a significant difference when running latency tests between wayland (as stock) and changing to X.
Branding is also an issue, something I really want to deal with. Debian isn't so restrictive, hence the reason the PC images changed from Ubuntu to Debian.

There is also a thread some where on the forum regarding Linuxcnc on RPIOS. The topic author slips my mind at this moment.