Advanced Search

Hello,

I measure every tool after changing, this happens automatically. In principle, only an offset to the previous value is determined; I don't write anything into the tool table. That doesn't make sense to me either since I don't have an automatic tool changer.
Here's another link:
www.patreon.com/posts/29-linuxcnc-der-27282521?l=de
forum.linuxcnc.org/qtvcp/39423-qtdragon-...tool-change?start=30

Many greetings, Frank.

 

Do you want A to rotate around X?
if you load a tool and jog A is this what you see?
Can you test the simulated config?

It appears the core problem is that 2.9 requires a 64 bit processor and my antique is a 686. I guess I will be staying in the past untilll I buy a new desktop.

So, is RTAI over?

I'm already feeling nostalgic.

How difficult will it be to use RTAI from now on (from LinuxCNC 2.9.5 onward)?

The most recent setup I’ve been able to get working is kernel 5.4.258 + LinuxCNC 2.9.4, using the following .deb packages (with isolcpus=3):

linuxcnc.org/dists/bookworm/base/binary-amd64/
linux-image-5.4.258-rtai-amd64_5.4.258-rtai-amd64-2_amd64.deb
linux-headers-5.4.258-rtai-amd64_5.4.258-rtai-amd64-2_amd64.deb
rtai-modules-5.4.258_5.3.3-linuxcnc-delta_amd64.deb

linuxcnc.org/dists/bookworm/2.9-rt/binary-amd64/
linuxcnc_2.9.4_amd64.deb

I was not able to get 5.4.290 + 2.9.4 working, nor 5.4.279 + 2.9.2. (I will post the error messages later.)

The 2.9.7 release notes state: "RTAI is still supported, but in the short term, building from source is likely to be the most expedient way to get 2.9.7 on that platform."

I’m wondering whether this is a reasonably straightforward process, or if it requires deeper OS-level debugging knowledge.

Add # in front of the line starting with
UUID=63aa136.......
save and exit, then reboot.

LinuxCNC already has that feature, it is called POSITION_FILE and should be added to the ini file in the [TRAJ] section, something like this
POSITION_FILE = last_position.txt

You can look at the .pin files in the firmware directory
to choose a appropriate pinout

7i92t_5abob_encd.bin for example has 5 stepgens and 6 encoders

Note that if you connect directly to encoders and motor drives:


1. The 7I92T I/O pins are like a bare parallel port pins and will be instantly damaged if connected to a voltage outside the -0.5 to +7V range. This is easy to do if system grounding is not 100% correct.

2. If you use bare 7I92T outputs to connect to step motor drives, they should be used in a a sinking configuration, as that is the only way to get full 5V drive:

DRIVE 7I92T
PUL+ +5V
PUL- 7I92 STEP PIN
DIR+ +5V
DIR- 7I92 DIR PIN

What is Flex GUI?
It's a drag and drop GUI that requires no programming knowledge to build a GUI using the latest PyQt6.

Where are the Documents?
gnipsel.com/linuxcnc/flexgui/index.html

Where is the Flex GUI repository?
github.com/jethornton/flexgui

Where can I ask for feature requests or report a bug?
Here or on the repository github.com/jethornton/flexgui/issues or Libera.Chat channel #flex-dev

Are there any videos showing how to build a Flex GUI?
Version 1.3 www.youtube.com/playlist?list=PLzYeNVt90...b9GL6SDnoM1ItneA3s-K
Version 1.1 www.youtube.com/playlist?list=PLzYeNVt90...qACmFKau-nfGDKv-8WsD
Note: some items may have changed since doing these videos as we tested the snot out of Flex GUI
Version 1.0 www.youtube.com/playlist?list=PLzYeNVt90...FzJMaZwycZuHITzFxHgW

JT

Thanks for your help. But position-log.txt doesn't show up to record.

I'm using LinuxCNC 2.8.4 Debian Buster.

  Hallo tommy,ich habe sudo nano /etc/fstab ausgeführt und
das sieht dann so aus:
siehe Foto
der uuid  / ext4  errors=remoundas sollte der sein. der gelöscht werden kann? 
karlhe

better use python3

Hello! Thank you for your support! I only use 7i91th.

Can someone help me create a Python script to record positions in the event of a power loss or LinuxCNC error?

I plan to create an external real-time position logger with an update interval of 0.001 seconds. I use this feature for a wirecut machine. I'm using a Python script and have tried activating log_position_to_txt.py with the M-code command, but the position logging process results in a code overflow, causing the .txt file to grow uncontrollably.

Here's the code for log_position_to_txt.py:

##############################
#!/usr/bin/env python2.7
import linuxcnc
import time

stat = linuxcnc.stat()

with open("position-log.txt", "w") as outfile:

while True:

stat.poll()
x,y,z,a,b,c,u,v,w = stat.actual_position

outfile.write("X ")
outfile.write("{:.4f}\n".format(x))
outfile.write("Y ")
outfile.write("{:.4f}\n".format(y))

time.sleep(0.001)
####################################


Can someone help me fix my Python script so that... position recording does not result in code accumulation?

I'm afraid we really don't have enough information to help you.

We have to assume that the new drive isn't configured the same as your old one. Are both the new and old drives the same model and version? (There are different models of Delta Servos that are the same size and look simular, but the motors from an older one are not compatible with a newer drive or vice versa.)

Do you have a back up of all of the parameters from the old drive? Assuming that your new drive is the same model as the old one, you would need to load the parameter settings from the old one to the new one in order for it to behave as before. If you don't have either a software backup of the parameters, or written down paper copy of the parameter settings, then you will have to figure out what they need to be. We can't really help you with that though unless you tell us how the motor/drivev is mis behaving.