Advanced Search

Some of these things were not well known and understood when 2.91 was released

PCW post=307735 userid=481This brings up the question is why in the world is ethtool not included in the
LinuxCNC distribution (plus the RT8168 DKMS driver should be as well)

These affect all LinuxCNC Ethernet connected motion devices, not just Mesa

You can send a PR adding ethtool to here github.com/LinuxCNC/linuxcnc-live-build/...sts/desktop.list#L49

The R8168-dkms driver is a bit of a funny one. Its excluded from the default kernel. I suspect the reason is political. I suspect it includes Realtek binaries so not technically open source. But where do you stop? What about the R8125dkms driver many of the recent  micro PCs like the Odroid H3 need?

Plus I am not sure the dkms drivers are benign where no realtek hardware is installed and it then needs compiling on every kernel upgrade

Hello, 
Can I change the axis limits, maximum speed and ramp with the variable addresses I wrote in the G-code file or with classicladder without entering the ini file?
For example :
eg.ngc
℅ 
#100 = 1000 (x-axis positive limit) 
#101 = 200 (ramp) 
m2
℅
Or can I do it with the Classic Ladder?

As Cakeslob mention, the RP2040 fork does not currently have encoder (software or hardware) support. It wouldn't take much to port over the software encoder module to the RP2040 though. Limited to base thread frequency.

github.com/scottalford75/Remora/tree/mai...-OS5/modules/encoder

If someone was keen they could also potentially look at the PIOs to increase the capable frequency.

github.com/p-o-l-e/quadrature-decoder

You might take a LED+resistor or DVM and check that the
direction pin changes state when jogging in different directions.

I would probably also change:

loadrt hm2_rpspi config="firmware=hm2/7c81/5ABOBX3.BIT num_encoders=1 num_pwmgens=3 num_stepgens=10"

to:

loadrt hm2_rpspi config="num_encoders=1 num_pwmgens=0 num_stepgens=3"

Unless you need a PWMgen or encoder or 10 stepgens

Ok upped the Step ON-Time for my X axis  to 20000 and still no movement.

Here is the BOB I am using www.amazon.com/gp/product/B0093Y897A/ref...h_asin_title?ie=UTF8

I am going to attach my hal, ini and pncconf files.  Hopefully, someone can get me out of the ditch.



 

In the file. Ini include KEYBOARD_JOG=1

I've heard that ethtools been replaced by ip but AFAIK ip
does not have low level driver control options so cannot
change IRQ coalescing for example.

Just saying that regardless of distribution used, a LinuxCNC
ISO should include it.

Now the files are OK, the first round they were redacted and actually had a written line claiming that.
Files seem OK, so it should work, but i know it will not, forgot why as it was a long while ago, but i did manage to get it working, i think, i will have to check the configs of some small machines that only use 2 axis, later.

Just checked, not included in Mint 22.

I posted the original hal and INI files.  But I'm not sure if there are other files you were referring to.  

Right now the files are for a 2 AXIS setup with a pair of Y joints.  I'm just trying to get jogging to work for these axis' before adding the Z axis.  

This brings up the question is why in the world is ethtool not included in the
LinuxCNC distribution (plus the RT8168 DKMS driver should be as well)

These affect all LinuxCNC Ethernet connected motion devices, not just Mesa

Find a USB-wireless dongle and connect to internet.

Attach the proper files, what are we supposed to do with crippled files?

ip a
 

I'm new to LinuxCNC and hobbyist machining.  For some reason, jogging isn't working on my 3 Axis setup. I feel like I'm just missing one critical configuration but can't figure it out.  I got homing to work from the Axis GUI, but jogging doesn't work. 

I've posted my INI files and HAL files.  I've only included X axis configurations for brevity.  Any tips ?

System Details
* Raspberry Pi 5 
* LinuxCNC 2.9.3