Advanced Search

Search Results (Searched for: )

  • oddwick
  • oddwick's Avatar
18 May 2025 03:37 - 31 May 2025 02:41

[SOLVED] MesaCT problems with 7i96 pwm spindle

Category: Configuration Tools

Having ome slight problems here and was looking to see if someone could give me a hand.  I am finishing up a build and the last piece of the puzzle is the spindle and some of the outputs.

I am using a 7i96 that was reused from another machine and was set up for 4 step 1 pwm.  not sure the version of the firmware, but it should not need to be changed.  The computer is a clean install of 2.9 and the original configs from the previous machine doesn't work.  It was made using jt's 7i96 tool and then heavily modified.  so as of right now, I have most everything set up using mesaCT with some generic general values just to make sure that i can move and home each axis. so far so good.  

The spindle is 2.2kw 220v using a huanyang ec01 vfd which takes a 10v pwm signal so i have it ran through a small analog converter from the mesa board.  Now when i try and add the spindle to the config in mesaCT, all of the spindle controls are greyed out even though in options i have it set as 4 step 1 spindle and in axis, there is no spindle option right now. 

also, for some reason i can not get axis to turn on my relays either using mesaCT.  I have them set as mist/flood right now for testing, but i get nothing.  are these some bugs with mesaCT or am i just missing something obvious?  Thanks!
  • aikiaviator
  • aikiaviator
18 May 2025 02:49
Replied by aikiaviator on topic spindle control of PM-728vt using linuxcnc

spindle control of PM-728vt using linuxcnc

Category: Milling Machines

Hi I have the same unit and on the high speed gearing, (up to 4000, I cant get to run below 500RPM. Are you finding that also?
  • rdtsc
  • rdtsc's Avatar
18 May 2025 02:19 - 18 May 2025 02:35

Linuxcnc 2.9.4 .iso on Rpi5: apt update does not build /boot/initrd.gz

Category: Installing LinuxCNC

Hi, have been using LinuxCNC since 2.9.0~pre1 on a Rpi4.  Now have 2.9.4 or an Rpi5 and things were working great, until I did a sudo apt dist-upgrade earlier today.  After, I cannot shut the Rpi5 off, because apt removed the /boot/initrd.gz file:
...
Setting up libmagickcore-6.q16-6-extra:arm64 (8:6.9.11.60+dfsg-1.6+deb12u3) ...
Setting up libpython3.11-stdlib:arm64 (3.11.2-6+deb12u6) ...
Setting up linux-headers-6.1.0-35-arm64 (6.1.137-1) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-35-arm64.
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area...
kernelver=6.1.0-35-arm64 ./dkms-make.sh.........................................
Signing module /var/lib/dkms/rtl8821cu/5.12.0.4/build/8821cu.ko
Cleaning build area...

8821cu.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/6.1.0-35-arm64/updates/dkms/
depmod...
dkms: autoinstall for kernel: 6.1.0-35-arm64.
Setting up python3.11 (3.11.2-6+deb12u6) ...
Setting up linux-headers-arm64 (6.1.137-1) ...
Setting up libpython3.11:arm64 (3.11.2-6+deb12u6) ...
Processing triggers for systemd (252.36-1~deb12u1) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for cracklib-runtime (2.9.6-5+b1) ...
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for libc-bin (2.36-9+deb12u10) ...
Processing triggers for initramfs-tools (0.142+deb12u3) ...
update-initramfs: Generating /boot/initrd.img-6.12.12+bpo-rt-arm64
update-initramfs: Generating /boot/initrd.gz
cp: target '/boot/initrd.gz': No such file or directory
cp: target '/boot/broadcom/initrd.gz': No such file or directory
linuxcnc@linuxcncpi:~$ what the...

See the rpi-1 attachment for the complete text:

File Attachment:

File Name: rpi-1_fail...mand.txt
File Size:17 KB


Note, the (highly finnicky) rtl8821cu wifi dongle driver was installed about a month ago.  Apt did attempt to rebuild this driver for kernel 6.1.0-35, but that was an old kernel and (now at least) no longer exists in /boot.  Now in there, are only 6.12.11 and 6.12.12+bpo-rt-arm64.  Note the latter is much larger than the previous:
linuxcnc@linuxcncpi:/boot$ ls -ag
total 170932
drwxr-xr-x 3 root 4096 May 17 16:16 .
drwxr-xr-x 18 root 4096 Mar 10 18:49 ..
drwxr-xr-x 3 root 16384 Dec 31 1969 broadcom
-rw-r--r-- 1 root 245283 Jan 26 07:36 config-6.12.11
-rw-r--r-- 1 root 332811 Feb 23 13:00 config-6.12.12+bpo-rt-arm64
lrwxrwxrwx 1 root 14 May 17 16:16 firmware -> /boot/broadcom
-rw-r--r-- 1 root 26624512 Jan 26 07:36 Image
-rw-r--r-- 1 root 22391722 May 17 16:16 initrd.img-6.12.11
-rw-r--r-- 1 root 71401400 May 17 16:15 initrd.img-6.12.12+bpo-rt-arm64
-rw-r--r-- 1 root 4085277 Jan 26 07:36 System.map-6.12.11
-rw-r--r-- 1 root 83 Feb 23 13:00 System.map-6.12.12+bpo-rt-arm64
-rw-r--r-- 1 root 9535537 Jan 26 07:36 vmlinuz-6.12.11
-rw-r--r-- 1 root 40374208 Feb 23 13:00 vmlinuz-6.12.12+bpo-rt-arm64
linuxcnc@linuxcncpi:/boot$

I can't get update-initramfs -c -k all -v to build the /boot/initrd.gz; it always complains with: cp: target '/boot/initrd.gz': No such file or directory

File Attachment:

File Name: rpi-2_upda...bose.txt
File Size:37 KB


I've updated the rtl8821cu driver, rebuilt and reinstalled it, but this did not help.  Then I removed it completely; same.  Thoughts?  Thanks much for taking a look.

P.S. A really, really good idea would be to, right now, sudo nano /etc/initramfs-tools/update-initramfs.conf and change backup_initramfs=yes
  • Thayloreing
  • Thayloreing
18 May 2025 02:09
Replied by Thayloreing on topic Remora - ethernet NVEM / EC300 / EC500 cnc board

Remora - ethernet NVEM / EC300 / EC500 cnc board

Category: Computers and Hardware

Please, I've been trying for months without success. Everything seems to be fine, but I can't compile it onto the board. I'm using v5 of the cloud. I have no idea what it could be. I see that everyone follows the steps and it works. However, I even had a lot of trouble installing pyocd, but with a lot of effort I finally managed to do it. Please, can someone tell me what I'm doing wrong?
  • Doc_emmet
  • Doc_emmet
17 May 2025 23:15 - 17 May 2025 23:26
Activate B-axis in Porbe Basic was created by Doc_emmet

Activate B-axis in Porbe Basic

Category: QtPyVCP

Hello, I have a machine with X, Y, Z, B, C. How do I change Probe Basic from A-axis to B-axis?

[DISPLAY]
GEOMETRY = xyzab
...

[KINS]
JOINTS = 5
KINEMATICS = trivkins coordinates=XYZAC
...

[TRAJ]
COORDINATES = XYZAC
...

If I change three "A"s to three "B," only the X, Y, and Z axes are displayed in Probe Basic. I also adjusted the range [AXIS_X] to [AXIS_C].
Can someone help me?
  • CORBETT
  • CORBETT's Avatar
17 May 2025 22:54 - 17 May 2025 23:12
Replied by CORBETT on topic el5151 reseting counts

el5151 reseting counts

Category: EtherCAT

@ Philip Lydin

You may have already done this, but you need to setup the EL5151 itself.  If you bought the terminal used, then I would do a factory reset to clear whatever someone did before you and then set it up.  Like Dominik Braun (DB1981) said years ago, you never know what someone has done before you.

If you don’t have Twincat, then you can do it from the command line (CoE).  Make sure to put the correct terminal number for the -p.  I have -p1 below as that would put it right behind the EK1100.  After the command, wait a few seconds, then power cycle the Beckhoff hardware.  (there are 2 hyphens before type)

sudo ethercat download -p1 0x1011 0x01 0x64616F6C --type uint32

The above will put it in quadrature.  If you want “counter mode”, then do the following command.  Don’t forget to wait and power cycle again after the new command.

sudo ethercat download -p1 0x8000 0x03 --type bool 1

If it’s already in counter mode with C reset, then you should be able to find out before doing the above commands with
sudo ethercat upload -p1 0x8000 0x01 - -type bool
If it’s in counter mode with C reset, then you should get something like  
0x01 1

Just don’t forget to put the correct terminal location for the -p as you don’t want to “brick” one of your other terminals.  Twincat is totally safe to do anything with the terminals, but you can permanently brick one doing CoE.  Even though Twincat is free, I still do CoE most of the time.


Like Hakan stated, Beckhoff’s manuals have everything, just a matter of finding the answer.


Hope it helps,
Robert
  • Giovanni
  • Giovanni
17 May 2025 21:48 - 17 May 2025 21:51
Replied by Giovanni on topic NativeCam on LinuxCNC 2.9.3

NativeCam on LinuxCNC 2.9.3

Category: NativeCAM

The file attached is a dirty patch to test only with qt_dragon interface.
The DISPLAY test function is disabled to allow NativeCAM to run.


If you would try NativeCAM with qt_dragon, follow the installation procedure (search in previous messages)
Replace the ncam.py file with the attached and add the line in green in the .ini file:

# required NativeCAM item:
EMBED_TAB_NAME = NativeCAM
EMBED_TAB_LOCATION = tabWidget_utilities
EMBED_TAB_COMMAND = gladevcp -x {XID} -U --catalog=mill /usr/share/linuxcnc/gladevcp/NativeCAM/ncam.ui

It will run in a strange way:
LinuxCNC will start with the NativeCAM error. Click OK
NativeCAM will start (not embedded)
LinuxCNC screen shows up.

The NativeCAM tab is empty and useless, but to use NativeCAM use ALT-TAB keys to bring its window up.
After sending the program to LinuxCNC, use ALT-TAB keys to bring  LinuxCNC up.

It's a terrible way to use it, but for now it at least  works.

Regards
Giovanni





 
  • Hakan
  • Hakan
17 May 2025 21:30

Effect of lengthening the servo thread period?

Category: Basic Configuration

Another way is to take a feedrate say 200 mm/min and divide that by 60 for seconds and 1000 for servo thread speed and you get 3.3 micrometers between position updates. 500 Hz servo thread gives 6.6 micrometers between position updates. No buffering, all real time.
I guess there are situations where this can make a difference, but normally not I would say.
  • PCW
  • PCW's Avatar
17 May 2025 20:45 - 17 May 2025 22:25

Effect of lengthening the servo thread period?

Category: Basic Configuration

With Mesa hardware (and most external hardware step/dir interfaces
or even EtherCAT drives), the velocity (step rate in this case) is updated
every servo thread.

This means that there is a constant velocity between updates. This constant
velocity means that that you will  have a small error (chord error) between a
desired curved path and the actual (linear interpolated) path.

This error is usually insignificant for most CNC machines at a 1 or 2 ms
servo thread period and typical CNC machine acceleration values.

For machines that are precise and fast (say with linear motors) you would likely
need  a faster than 1 KHz servo thread (or parabolic or cubic interpolation)

If you want to calculate the chord error here are some equations (at least for circles)

Chord error polygon vs circle =
R (1-cos(180/N))

R = radius
N = sides

R = Minimum Radius= V^2/A
N  = Sides = T_Circle/T_Sample

(a minimum radius circle at full speed is the worst case)

Using an example of 1 IPS (~25 mm/s) cutting speed and 40 IPS/S
acceleration (~ 1000 mm/s/s) and 2 ms servo thread,  the chord
error is about 0.00002" or 0.5 u.

If you increase the servo thread much longer you will start to have
issues on acceleration due to jumps between velocity steps, which
will limit your maximum acceleration setting.





 
  • Doc_emmet
  • Doc_emmet
17 May 2025 20:33
Replied by Doc_emmet on topic Install Probe Basic

Install Probe Basic

Category: QtPyVCP

Hello, I've finally found the error.
The problem is caused by importing entries from the "pb_required_ini_settings.ini" file.
This is the file:

[DISPLAY]
DISPLAY = probe_basic
OPEN_FILE = ~/linuxcnc/nc_files/pb_examples/blank.ngc
CONFIG_FILE = custom_config.yml
MAX_FEED_OVERRIDE = 2.000000            # Recommended Setting for Probe Basic
MAX_SPINDLE_OVERRIDE = 2.000000         # Recommended Setting for Probe Basic
MIN_SPINDLE_OVERRIDE = 0.500000         # Recommended Setting for Probe Basic
INCREMENTS = JOG .01in .001in .0001in   # REQUIRED Setting for Probe Basic
USER_TABS_PATH = user_tabs/             # REQUIRED Setting for Probe Basic
USER_BUTTONS_PATH = user_buttons/       # REQUIRED Setting for Probe Basic

[RS274NGC]
RS274NGC_STARTUP_CODE = F10 S300 G20 G17 G40 G49 G54 G64 P0.001 G80 G90 G91.1 G92.1 G94 G97 G98
PARAMETER_FILE = probe_basic.var
OWORD_NARGS = 1
NO_DOWNCASE_OWORD = 1
SUBROUTINE_PATH = subroutines

[HAL]
POSTGUI_HALFILE = probe_basic_postgui.hal
TWOPASS = on

And here's the error: USER_TABS_PATH = user_tabs/ # REQUIRED Setting for Probe Basic
There must be no comments after USER_TABS_PATH = user_tabs/, no "#" because that causes the error!!!
  • PCW
  • PCW's Avatar
17 May 2025 20:27
Replied by PCW on topic Index homing Heidenhain ls 403/exe602

Index homing Heidenhain ls 403/exe602

Category: Basic Configuration

It should be possible if there is only one index
rather than periodic index marks
  • Giovanni
  • Giovanni
17 May 2025 20:27
Replied by Giovanni on topic NativeCam on LinuxCNC 2.9.3

NativeCam on LinuxCNC 2.9.3

Category: NativeCAM

I've tried to run NativeCAM with qtdragon after a couple of changes:

# required NativeCAM item:
EMBED_TAB_NAME = NativeCAM
EMBED_TAB_LOCATION = tabWidget_utilities
EMBED_TAB_COMMAND = gladevcp -x {XID} -U --catalog=mill /usr/share/linuxcnc/gladevcp/NativeCAM/ncam.ui

And I copied an existing folder in qt_dragon config folder.

The NativeCam tab (empty) is shown, but NativeCAM wont'run cause it declares a DISPLAY problem.
I'll try to trick NativeCAM to avoid the display check, to see if it will run.

Regards
Giovanni
  • H-S-W
  • H-S-W
17 May 2025 20:24

Index homing Heidenhain ls 403/exe602

Category: Basic Configuration

Hi!
Is it possible to home a machine only using the scales and no other limit switches? Have found a bunch of posts regarding this, but none gave me enough clarity. In one i think Andypugh did some testing/developing to get this to work?

/Hampus 
  • tommylight
  • tommylight's Avatar
17 May 2025 19:59
Replied by tommylight on topic Effect of lengthening the servo thread period?

Effect of lengthening the servo thread period?

Category: Basic Configuration

You will most probably get stuttering if you do not also set the P value to 500 for each joint/axis in the ini file.
Those two are strictly related for normal stepper systems, for 1 million servo period the P value is 1000, for 2 million servo period the P value is 500, for half million servo period the P value is 2000, and so on.
And i am pretty sure Mesa controllers do not use buffers for the motion control in the normal sense of "mach3" boards, might use for IO, but i never checked, after over 10 years of using Mesa boards (probably over 80 by now) and never ever having a single issue with them, and most are on industrial machines in use 10 hours a day every day (never turn off, though), and having tailor made firmware to my needs, and having the best support on Earth, i absolutely stopped worrying about it.
:)
  • pgf
  • pgf
17 May 2025 19:50

Effect of lengthening the servo thread period?

Category: Basic Configuration

I meant to add:

But I'm more than happy with your answer! :-)
Displaying 4516 - 4530 out of 24148 results.
Time to create page: 0.271 seconds
Powered by Kunena Forum