Advanced Search

Hi,
Great tool but I'm having a problem. I'm running Linuxcnc 2.9.2 on a RPi5 with MESA 7i76E and 7i85S boards. In the Setting/Jog Slider Settings the three Angular Velocity setting are greyed out so I can not enter values. The result of Build Config is a message in the Info tab :Settings Tab:Default Linear Jog Velocity must be greater than zeroMaximum Linear Jog Velocity must be greater than zero

Is there something I've missed in the settings somewhere?
Regards,
Nigelp, li { white-space: pre-wrap; }

LinuxCNC 2.9.2 auf RPi4 (RPi 400) + MESA 7i76e
Nachtrag:

Inzwischen habe ich das Komando <menu-config> gefunden.
Dieses ist im <.img.xz> enthalten und ist vergleichbar mit <raspi-config>.
Somit kann der Abschnitt mit <raspi-config> entfallen.
<menu-config> zeigt nach Beenden einige nützliche Infos an.


cnc@raspberrypi:~$ menu-config
Generating locales (this might take a while)...
de_DE.UTF-8... done
Generation complete.

Current default time zone: 'Europe/Berlin'
Local time is now: Wed Mar 13 00:34:39 CET 2024.
Universal Time is now: Tue Mar 12 23:34:39 UTC 2024.

Debian GNU/Linux 12 (bookworm) 6.1.54-rt15 #1_RT Fri Nov 17 17:02:27 AEST 2023
aarch64
Raspberry Pi 4 Model B Rev 1.5
== DISK
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 28G 3.6G 23G 14% /
/dev/sda1 508M 89M 419M 18% /boot/broadcom

== NETWORK
Hostname: raspberrypi
Wired: eth0 UP 192.168.0.132

== SYSTEM
Processor: Cortex-A72 @ 1800MHz 35.5°C
Online: 0-3
Governor: performance
Memory: 3.7G 482M
Entropy: 256
Uptime: 00:35:27 up 8 min, 1 user, load average: 1.01, 0.98, 0.62

sudo apt update && sudo apt full-upgrade
sudo reboot

Weitere System-Infos kann man mit diesen Komandos erhalten:

uname --help
uname -a
(Kernel-Version)

hostnamectl -h
hostnamectl
(System-Info)

df --help
df -h
(Dateisystem-Info)

lsusb -h
lsusb
(USB-Info)

rpi-eeprom-update
(Liste mit EEPROM-Info)

stz60

Yeah it did believe it or not. 

I'd probably report that as a bug? 

Too weird... 

Did that solve the out of range spindle speed error?

Ok, all I did was add those params as described above and everything words as described. 
Here's what I did:

OUTPUT_MIN_LIMIT = 5000   <<-- I changed this from zero to 5000
 OUTPUT_MAX_LIMIT = 24000    <<-- no change to this line
 MIN_FORWARD_VELOCITY = 5000
 MAX_FORWARD_VELOCITY = 24000
 INCREMENT = 200

I added the latter 3 lines in green.

Thanks to those who responded with feedback!

No, those are hardware setup parameters and necessary.

Ok, I just added the green FORWARD stuff to my config.. Should I remove the red print?

[SPINDLE_0]
 P = 0.0
 I = 0.0
 D = 0.0
 FF0 = 1.0
 FF1 = 0.0
 FF2 = 0.0
 BIAS = 0.0
 DEADBAND = 0.0
 MAX_OUTPUT = 24000
 OUTPUT_SCALE = 24000
 OUTPUT_MIN_LIMIT = 5000
 OUTPUT_MAX_LIMIT = 24000
 MIN_FORWARD_VELOCITY = 5000
 MAX_FORWARD_VELOCITY = 24000
 INCREMENT = 200
 

Those are hardware settings, I would think pyvcp would use
the ini file spindle settings here:

linuxcnc.org/docs/2.9/html/config/ini-co...:ini:sec:spindle-num

3000 RPM is probably the default value if not specified. This does seem like
a pncconf bug to leave out the generic spindle ini settings

Change it to 24000, save and test.

What I have yet to understand is that the pyvcp-panel.xml file uses a value of 3000. Why is that?

I would expect to see these INI values which I assume are RPM?
OUTPUT_MIN_LIMIT = 0.0
OUTPUT_MAX_LIMIT = 24000

 

NT4Boy wrote:

Another stupid question from me. When you say:-
"Connect the 7I83 analog out hal pins to the PID outputs"
Is that a physical wire, or something to be written in the hal file?

In hal, make a new config for 7i76E with 7i77, that should get you all the pins for everything, then make a copy and edit the copy to match the Mesa naming and pins:
Stepgens change from 7i76E to 7i95
Encoders change from 7i77 to 7i95
analog out/pid change from 7i77 to 7i83

Thanks PCW, it's very clear.
the goal is for the milling machine to stop if for some reason the z axis stalls.
otherwise, a rapid crossing with the z in the wrong position can cause a disaster

Not sure what the issue is but looks GUI related
My guess would be the the pyvcp spindle speed
display doesn't have the maximum spindle speed set right

Attached
 

That's possibly an ini file or GUI setup error.
Can you post your main hal file, ini file, and any postgui hal file?

Sounds like you have a maximum spindle speed limit
somewhere in your configuration files