Advanced Search

Mwchanical issue maybe or backlash of your acis settings are correct.

Your approved, the move to private was not my doing, FB forced group chats to private chats last month i think.

Thanks for the info. I sent a request to join the probe basic facebook group. It appears to have gone private in a new group that is members only.

Give this a try
forum.linuxcnc.org/9-installing-linuxcnc...an-edition-6?start=0
or if you are OK with 2.10 version dating nearly a year back, try this
forum.linuxcnc.org/9-installing-linuxcnc...-1-linuxcnc-2-10-iso

thank you I decided to take a few days brake on this reinstall.. "note to myself dont touch things that work lol"

Tried first reinstall 2.9.4, that did not help. then i installed "linuxcnc_2.9.3-amd64.hybrid" same problems as before+ expkey signature not valid due to age, but that's ok ish.. . I think there are a "update" being loaded on install or right after that bugs it. .
one thing i don't get also is when i installed 2.9.7 first time it showed Debian 13 with "red theme" ??
...... i think i will put the install on pause for some days because i am going insane lol .. thx for helping

Now added to my mirror.

The offical download site should really have the md5 or at least some checksum for all the files.

The files on my mirror are identical to those on linuxcnc.org/iso though only 2.9.4 (Bookworm), 2.7.14 (Wheezy), and an rPi version are available from my mirror.

I'd be tempted to try setting C007 to 14, but it will spin the motor opposite.

Hello community!
I have a Mesa 7i76e running, the wiring is correct except for the alarm loop. Using a Lenovo ThinkCentre M910q with i7 4-core, 256/GB NVMe SSD, i7 16GB RAM WLAN Intel Core i7-6700T 4x 2.80 - 3.60GHz with Linuxcnc 2.9.4, Probe Basic V.5 on Debian 12. No latency problems.

Once again, I'm here with a big problem. My DIY milling machine (1000x500x220 with aluminum profile frame, 20mm HGR, 1605 ball screws, 3 axes, 2x OMC Stpperonline 400W integrated servo, 1x JMC CL Stepper 3.5Nm, set 2000 steps/rev) is now mechanically finally assembled. I also got a lot of help from this forum in setting up LinuxCNC, eliminating latency problems and spindle control problems, but now I have a milling problem that I can't solve.

I have milled several test parts with drill holes, 2 circular pockets, and a rectangular outer contour, and have noticed that my circular pockets are becoming elliptical. The deviations in Y are approximately +0.35 mm at 45° and approximately -0.38 mm at 135°. The X values for the rectangular contour are perfect to within 0.01 mm in X and 0.09 mm in Y, X I consider to be acceptable, but Y is over tolerance. However, the circular movements contain deviations I cannot tolerate. I will show you a photo of the last test piece. After each individual test part, I made changes to rule out certain things.
The first change was to replace a simple Chinese C7 ball screw with a ground C5 spindle with double nuts. This reduced the originally even higher values by almost half. However, the deviations described above remained. After the next test part, I replaced the 400 W servo with a 3.5 Nm JMC CL stepper motor. The results remained almost the same. As a final attempt, a few days ago I replaced the spindle's fixed bearing with a new one, with 7002AC angular contact bearings in an O-arrangement with a 1 mm spacer ring between the outer rings. I inspected the previous fixed bearing and found no faults. There was a 1mm spacer also and the O arrangement was the same.  I had also taken measurements at the spindle end earlier and actually and found no backlash.

Yesterday, moving away from mechanical faults, I noticed a difference in the motor definitions for the X and Y axes in the .ini file. The Ferror and min_Ferror points differed by one decimal place. X was set to 0.1 and 0.01, while the Y axis was set to 1.0 and 0.1. After I corrected this difference, the motor on the Y axis went into alarm mode after a few position changes.

What could be the reason for this? How can it be that one motor runs perfectly with much lower tolerance values, while the other quickly goes into alarm mode with less load? The motor in question has the same power supply and is certainly less demanding in terms of starting currents than the servo on the X-axis. With the higher tolerance values, the Y motor runs without alarm, but has these deviations. Are these tolerance values in the .ini file responsible for these deviations?
The mechanics of the Y and Z axes are flawless, as checked with a dial gauge, and the repeat accuracy is also very good, less than one hundredth. 
Do you have any ideas about this? Where can I look further?
Thanks for your time and hints    

 

I tried
C07 --> 2. The VFD no longer started the motor.
C07 --> 1. Same behavior as CO7 - 0.

Terminal E3 and E2 are unpopulated, but always have been. In the video link above, it was ramping down when I first tested it, and I am pretty sure I found a way to turn that off.
C007 is assigned option 0.

Sorry, meant C007. QSB is not selected by default. Default is DC braking. Page 7-78.

Thanks for taking a look. And yeah, that manual sucks

I have no C107. It jumps from C106 to C108.

C105, I have tried different values, like 5Sec or 1.5Sec. It makes no difference. The drive is not ramping down, it got straight to 0A, and OFF as soon as it is commanded off.

I guess you're installing on Trixie.

Install
sudo apt install python3-zombie-imp

Then if you try to run you'll get another error which is related to libqt5quickwidgets5
sudo apt install libqt5quickwidgets5

Are your input terminals configured for QSP? C107
Also check C105 which is QSP decel time.

That manual is awful.

BR