Advanced Search

read the comments on the downloads page. menu-config should do it for you.

In my case, it would be ethernet, I need the configuration area for the IP/Gateway address, that way, I can study the connection with ethernet cards.

IN the gmocappy source there is a screen handler written in Python. There is also a glade screen definition, You probably just need to modify the handler for the exit button or even better move it to the already password protected area. Sorry its been 7 or 8 years since I modified gmocappy

cncmiljc wrote:

Could anyone help, I made the image for the pi4 following the image on the official page, but it doesn't have the area for ethernet configuration, how can I solve this problem?

The current 2.9.2 image  needs updating to 2.9.3 but we no longer install Ethercat repositories for the Raspberry pi.
I am not sure if the pi is supported in their repos for Debian 12 at all
Also I doubt that a linuxcnc-ethercat driver is built for the pi either
Right now your option is to build from source
I have raised an issue with Ethercat to explore a solution for this.

 

Spumco,

Hi...thanks for reply!...it will be wood lathe and I am wanting to do the equivalent of straighten,rough shape, then skew cut any geometry that may come...not easy by hand and involves much simultaneous movements as well as loading etc.
So I understand correctly...you list 3 boards with one having two options correct?

Thanks again,

Rick

The config file for the NVEM has the information you are looking for.

github.com/scottalford75/Remora-RT1052-c...xCNC/nvem-rt1052.txt

Example:

{
"Thread": "Servo",
"Type": "Digital Pin",
"Comment": "IN01",
"Pin": "P4_26",
"Mode": "Input",
"Data Bit": 4,
"Invert": "True"
},

This is the IN01 input and it is remora.input.04 . The Data Bit key sets the Remora input number. You can either use the these numberings or change these to your liking.

Please remind us to git-checkout when you think there are improvements we'd be interested in. I membership to The RIO Cult!!

i.e. exaggeration. See by yourself. Those are fairly impressive figures for what it is, Oliver. And so quit being humble about it and hard-push RIO out to the greater community. We NEED it, such options are highly valued. (Thanks 10000x again btw). 

 

spi speed field is new and maybe i have not pushed it yet to github.
i have done also some critical changes and have to test it all before i set it live

No exaggeration. It is what it is. In fact it works so well it's creating a huge dilemma for myself at this point. The end goal is about to shift from having a simple dumb 3axis/3switches co2 laser retrofit, extended to having my parport milling machine reworked entirely also. It's getting even more confusing as I trial the plugins you've written. (addictive).

How did you get the w5500 spi speed field turned on? So much injustice going on. I see I see.

All that scale x60 stuff has been obsolete for a long time
Since the -rpm velocity pin from the encoder was added:

hm2_7i95.0.encoder.02.velocity-rpm

The previous hal file without the scale stuff was much closer
 

Mega M4 does almost what it's supposed to do,
still can't get the spindle at speed but the speed is just a little bit higher.

the problem was in the Hal, I deleted it.

I also changed the tuning as you suggested

This did the strange run up for CCW

---

# Use ACTUAL spindle speed from spindle encoder
# Spindle speed jumps back and forth, so we filter it with low pass
# Spindle speed is signed, so we use an absolute component to remove the sign
# ACTUAL speed is in RPS, not RPM, so we scale it.
setp scale.spindle.gain 60
setp lowpass.spindle.gain 1.000000
net spindle-vel-fb-rps => scale.spindle.in
net spindle-fb-rpm scale.spindle.out => abs.spindle.in
net spindle-fb-rpm-abs abs.spindle.out => lowpass.spindle.in
net spindle-fb-rpm-abs-filtered lowpass.spindle.out

---

 

Thanks !!!

but you're exaggerating a bit, let's agree, it works


Normal way to change the ip is the rio-setup tool:

 

as a rule, the code does not need to be changed

 

The spindle PID settings are odd.

Normally you would start with:

P = 0
I = 0
D = 0
FF0 = 1
FF1 = 0
FF2 = 0
BIAS = 0
DEADBAND = 0
MAX_OUTPUT = 6000

== open loop

Once open loop is working and the feedback RPM is correct
Then it is appropriate to worry about  closing the loop (if that's even needed)

also
net spindle-vel-cmd-rpm => pid.s.command
is correct for a -10 to +10 controlled device

(I guessed wrong that you had a more common 0 to 10V controlled  VFD)
 

Thanks a lot

Can you compile LCNC yourself from source codes? You have to master it so that when someone helps you, you can use it.

This is first step:
linuxcnc.org/docs/stable/html/code/building-linuxcnc.html