Advanced Search

No idea, also didn't see an option to compile for non lts, sometimes things are easier than they seem
Better to set isolcpus=5 or 2-5 because linuxcnc always takes the last core and the quad core a53 is after the 2xa72

Ideally you would set isolcpus=1 but then you need to set the rt tasks to core 1 manually, via a script or change the source of linuxcnc.

royka wrote:

You can try this image, with desktop and gpu hw acceleration but under 1GB:
drive.google.com/file/d/1PCetphqJUFfS3aL...eD7/view?usp=sharing

It's laughable...did not worked tweaking & reweaking to modified it for opi4 ...
your image simply worked as is ...lesson learned here..
i dont understand , if armbian image for opi4 lts work on opi4 why the hell armbian link to non lts ?!?
You tell me , because everything seem to be good .
Trying some isolcpu 1,2 , no latency miracle ,should be ok , cutting air .
Let'see if i can install 2.9.3 now.

Good job Roya ..

I try to get two tandem motor to work. But the moment one side hits the home/limit switch I get the error Cannot unhome while homing, joint 0. So to me it looks like he tries to unhome joint 1 while he still tries to home joint 0

And another question can I somehow let the motors move away from the limit/home switches once they are in a fail state. Because they are tandem I can't just use ignore limits option

So I installed the  SSC tool app on both my laptop- Windows 11 and PC- Windows 10[Intel Lan). The EEPROM app crashed when I tried to scan, it shows nothing connected on either interface. I have tried this as Admin as well.
DHCP is set and I've tried both lan sockets and different cables. The same lan sockets work fine for Internet and file transfer. 
 Could I have missed a network protocol that needs installing to see the servos? 

I have built a new stepdir driver,
with adjustable 'delay after dir' and adjustable pulse length (also 50% duty possible).

first tests are still running, but if you want to have a look at the branch: new_stepdir_fix_pulse_len_dir_delay

EDIT (there is also a test-bench for this driver):
 # (cd riocore/plugins/stepdir ; make testb)

 

The battery test requires you to:

1. Enable the drives ( how this is done depends on the drives )
2. Disconnect the drives from the 7I97

The is no frequency/LinuxCNC/7I97 involved

So... the tuning guide I keep finding when doing searches, but always stop when I can't jog properly forward and backwards. Forward is sometimes shaky, but last few times trying forward it usually moves and stops roughly when I do. 
Drives : Cleveland Machine Controls D41-17443C
Servo Motor : CMC MT2630-141AF 
Encoders : Dynapar 62525000330

I'll have to get back to you on the current ini and hal files when I get a chance later this week. I'm using the basic 7i97 file I found on here and edited very little. 

I've been off and on working on this when I get the chance, everything is apart and on my table right now so no worries of something running away and damaging anything. Before this machine was taken apart for moving, I powered everything up with the original controls and verified everything moved fine and worked. The only thing ive done is rewired the box to the 7i97 and then reused some of the wiring to hook back to the motors/encoders. 

The 1.5v test (I used a 9v bc its what i had) didn't do anything. Not sure if its a frequency thing or not. If I leave the stock 48000hz frequency in the hal file I get nothing as well. 
I've noticed when I tell linuxcnc to jog the motors the 7i97 sends anywhere between 0 to 10v to the motor and slowly back it down to 0 as it gets closer to where it expects the motor to be. Again jogging backwards I see the 7i97 send between -0 to 10v but I either get no movement or movement in the positive direction again. 




 

First verify that the drives work properly by supplying a known voltage to the inputs
(a 1.5V battery will work for this test) and make sure that the drives run in equal and opposite
speeds when the input polarity is reversed

It's best to disconnect the motors from the linear axis when doing open loop tests like this.

> With added null.ngc files and nc_files path, the said error removed
> however, the axix cannot be run still persists, as showed in first attachemts,  "joint 1 following error" appears whenever axis button is clicked. How can i resolve it?
> This time, i installed the r8168 driver for the Realtek network card as per the forum information 
> The latency test and latency-histogram results are shown in second and third attachments, the latter one seems have no improvement?

linuxcnc 2.10
no using a hand control to start it, for the most of the times

 

Note that I'm not sure about the encoder inputs. I am assuming both are A inputs
and that the rapidturn encoder is not correct as Tormach has special interpolation
code for this (1 PPR encoder)

My encoder now counts correctly, now I have to learn how to use it with LCN.

They are related, but not the same. You connect them together in the hal file, using the metalmusings_encoder comp.
Best is to look in the EaserCAT-2000 folder for how it is done there and replicate that, and adapt to your variable naming.
I see these lines in Turner.hal over there

As mentioned before, you compile the module with
Uncomment also this line in main.cpp

Thank you from the bottom of my heart. You are my hero.

tommylight wrote:

Looong thread about lathe macros here
forum.linuxcnc.org/41-guis/26550-lathe-macros
 

Long is good, lots of information.
This looks like exactly what I was hoping for.
LinuxCNC seems to have every possibility covered, just thrilled I decided to go this direction.

Thanks to all the contributors.