Advanced Search

How low did you adjust P?
 What is the oscillation frequency?

Could you share with me your configuration to use the servo that controls the spindle and also to use it with the C axis?

Lowering P does nothing further, at this point oscillation occurs and F error is displayed. Pastes my configuration files for reference. I tried to power the 7i77 from a separate power supply, it didn't change anything.

 
 

Right. Is there RB Pi oriented ISO image for Linuxcnc? I'm thinking about RB Pi5 + Mesa combo and QtPlasmaC. I can see RB Pi5 8GB RAM version is now USD 100.

I deleted xhc-whb04b-6.hal still an error
I no longer have the problem of " MOTION: num_joints is 33, must be between 1 and 16" 
I post you the .ini and .hal files in 

   

LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.9.0~pre1+git20230208.f1270d6ed7
Machine configuration directory is '/home/manu/linuxcnc/configs/NVEM'
Machine configuration file is 'NVEM.ini'
INIFILE=/home/manu/linuxcnc/configs/NVEM/NVEM.ini
VERSION=1.1
PARAMETER_FILE=linuxcnc.var
TPMOD=
HOMEMOD=
TASK=milltask
HALUI=halui
DISPLAY=qtvcp qtplasmac
COORDINATES=X Y Z
KINEMATICS=trivkins coordinates=XYZ
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Found file(REL): ./NVEM.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
motmod: already exists
./NVEM.hal:6: waitpid failed /usr/bin/rtapi_app motmod
./NVEM.hal:6: /usr/bin/rtapi_app exited without becoming ready
./NVEM.hal:6: insmod for motmod failed, returned -1
8403
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime
 

A RPI5 would be a better choice, the RPI4 is a bit marginal speed wise.

Im confused --
RPI5 - linuxcnc 2.9.2 (from iso on linuxcnc download page)  I get same results on linux on a x86 system
I have a Novusun V5 that I loaded with ....Remora-RT1052-cpp/blob/main/Firmware/remora-rt1052-3.1.3.bin
I've run halcompile on remora-nv in Remora-NVEM-main/LinuxCNC/Components/Remora-nv

i can ping 10.10.10.10
I can tfpt put the python processed config.txt ...  I cant load tftpy for some reason so save & use the file created in /tmp

using the remora-nvem-basic when I take it out of E-Stop I get 
Bad payload = 0

any suggestions 

thanks 
Les

I'm trying to figure out when iocontrol.0.tool-change is on so I can pop up a window similar to the Axis pop up for tool change.

I'm looking at hal_manualtoolchange.py but not understanding it fully so I'm a bit stumped... any clues?

JT

Could you share with us your complete configuration?

Seems to work for me:
 

Gents,
what about using SBC with LinuxCNC and Mesa cards? That would be so nice and compact build. Will, say RB Pi4 handle Mesa 7i96 with no issues? Recently i've tried to hook 7i96 up to my laptop - Lenovo Legion Y530 and i failed. Ethernet connection was so laggy that Mesa kept throwing errors. i was kinda shocked as i thought that ethernet based controllers have no timeout related issues.

Hello everyone, im having a hard time setting up SPI on the raspi 5 running a  rpi-5-debian-bookworm image, i thought it would be relevant to ask here. For context, im trying to use some TMC5160T Pro stepper motor drives but to run them in the step/dir config i need to establish a spi connection with the drive to get the step/dir mode active. (i found this information online so i might be wrong)

I have enabled SPI in the /boot/firmware/config.txt and i have also confirmed that /dev/spidev1.0 and 0.0 are active but when i run "gpioinfo | grep spi" i only see the CS pins which (by the logic of chatgpt) is incorrect, i am assuming that i should be seeing the mosi miso and sclk pins in there too.

would love some help setting this up since its just been a headache for someone with as little experience with this stuff as i have.

 

You need to rethink your security model, stop worry about commands being echoed, that's the least of your problems. Once the database server is compromised every other machine on the network will be compromised. SSH isn't going to save the day. All that will do is encrypt the data between A & B.