Advanced Search

ok great!

I would not use stable in the repositories because the os can change next time debian is released. Better to use trixie... to bad debian doesn't do something sensible like using numbers.

JT

Yes, the EL5151 provides integer counts, which get converted to float by the LinuxCNC EtherCAT driver.
So with the misconception of floats having only 32bit being resolved, everything makes sense now.

Hello,

I am currently also in the process of setting up an AX5112 servo drive. Unfortunately, there does not seem to be any newer firmware available for my device that would allow me to use Drive Manager 2, so I have to stick with Drive Manager Classic.

My problem is that I cannot see the Drive Manager at all in the tabs of the drive/motor configuration. At the moment I am only supplying the drive with 24 V so that I can familiarize myself with it.

Does anyone have an idea what could be wrong here? I can hardly find any documentation on how to use Drive Manager Classic in TwinCAT 3. The Drive Manager Classic itself is installed via the package manager.

A friend of mine helped me and adjusted the source.list accordingly. Now the Mesa Configuration Tool works.

 

I bought a cheap Ethercat servo from Aliexpress and trying to make it working Linuxcnc. The servo is PFDE ethercat 400W and it is almost the same like Lichuan A5 (I'm using Lichuan manual because original i got is only in Chinese language). Generaly servo is working with linuxcnc, but once per many times it is not going to OP mode. I started debugging and it turned out that it has DC sync problems. Usually after 5s timeout, syncronization is failing, but still it is going to OP mode and I can operate it from Linuxcnc. 
Can anyone help me with this problem? Generally it is working, but I dont want situation that I have to start linuxcnc few times to make it working.
I have xml configuration file from seller, but they don't provide any application to program EEPROM, but when I'm checking slave version, it is the same that I got from seller. The dmesg output is:

Yeah the raspi-image thing was related to a config issue and the version of live-build being used.

Thanks Tommy,

I have worked through troubleshooting, and have the machine up and running again.

The EXE's are not powered by the Indramat power rails. The Indramat received 2x 90VAC (X and Y) and 2x 140VAC (Z) from a transformer straight off the mains. The X axis EXE still uses an original lane of the old three axis EXE board, and thus needs both 5VDC and 12VDC supplies, which are powered downstream of the main isolation transformer.  X and Y are on 601D EXE's which only need 5VDC, on the same PSU as the Z.

It seems like a combination of issues.
1/ I had an addition relay so LinuxCNC can also control the Z axis brake, which in the original set up was only controlled by the Indramat. The consequence is that the motor was fighting the brake briefly on every start up. Not sure if that has caused further issues.
2/ Errors in setting Ferror verse Ferrormin, Leaving Ferrormin too tight.

Axis    fError.    fErrorMin
X.           0.5           0.2
Y            0.5           0.2
Z             20             1

The 20 was obviously an oversight which I forgot to set after finishing pid tuning.
Question: What would be a typical value for fError and fErrorMin for a machine like set with 2400mm/min max rapids? Is 0.2 and o.5 really that tight?

3/ Not adding any intergral in the pid tuning, once I had P, FF1 and FF2 set. There is a constant offset in steady state motion.

4/ Suspect that using the 220 weight way oil recommended in the MAHO manual might be too thick in winter.

I have removed that 19K2 relay, removing linuxCNC from the brake control and returning it solely to the Indramat.
I have opened up the fError and fErrorMin values, and am now working to find sensible values.
Just playing around to find the right value of I for each axis.
Cheers,
Mark


 

I did notice on a previous installation that the sources only included the CD.

Let me investigate further.

Hello rody,
thank you for your input.
The old way is working too. Synaptic use the old one if you add there sources, too

Debian trixie uses the new deb822 format so sources.list is no longer used.
Instead  look in /etc/apt/sources.list.d/debian.sources for the sources in the new format

there is the package "python3-distro" in Trixie.
But you have to configure the sources correct.
Please look here:
forum.linuxcnc.org/9-installing-linuxcnc...e-with-debian-trixie

I don't see any Debian repositories how did you install the OS?

I'm downloading Debian 13 and installing that on  SSD for testing.

JT

Hello,
i installed the new LinuxCNC 2.9.8 Image with Debian Trixie and think the installation is not "ready to use" and need work.

First add the Debian repositories:
With
sudo nano /etc/apt/sources.list
add the lines:

deb deb.debian.org/debian stable main contrib non-free-firmware
deb-src deb.debian.org/debian stable main contrib non-free-firmware
deb security.debian.org/debian-security stable-security main contrib non-free-firmware
deb-src security.debian.org/debian-security stable-security main contrib non-free-firmware

After that:
sudo apt update
sudo apt upgrade
sudo apt autoremove

Select and activate your language:
sudo dpkg-reconfigure locales

and your timezone:
sudo tzselect

Best regards

Michael

P.S.: With this Trixie-Image the old raspi-firmware bug seems to be away.  

We already tried that yesterday. But then a new error message appears:

available from another source

Error: Package 'python3-distro' has no installation candidate

cnc@cnc:~$

in a terminal