Successfully configured with stepconf: but +Y-axis "stutters" running G-code

tommylight wrote:

I use nano, daily!

I do sometimes, but not daily. Lack of mouse support is a nuisance. But the vi I know is pretty awful if I can remember right...

Rod,

I use vi because it's always there; no install. And no icon to click. And type two letters--which I've considered shrinking with an alias.

However, I am not proud of it. I have gedit defined as my editor in LinuxCNC, so I'm not opposed to using sane tools, but it's like I caught a vi-rus.

> But the vi I know is pretty awful if I can remember right...

Ahhh, yes. That's the calling card.

I have booted into Debian 10 from the drive out of the old controller computer and run LinuxCNC 2.8 from it.

(I had tried this before but couldn't get Lxcnc to come up.  This proved to be a syntax anomaly in the .ini file remaining after its auto-conversion from 2.7.  .INI lines like "HOME_SEQUENCE = 1 # 2nd" are treated as errors in 2.8 although they once worked.)

I edited 2.8's .hal file to change the parport reset to 5000 and its .ini file to change the BASE_PERIOD to 50000.

I noticed that the max velocity at LinuxCNC startup was listed as 240 ipm, which is what I remembered from the previous setup.

There was no need to run G-code to test because the machine stalled when attempting to jog the Y-axis at 240 ipm.

I believe this particular machine, Dell Optiplex 780, just won't cut LinuxCNC's mustard.

I just checked, and what I have is running a pre-empt RT 4.19 kernel.

I don't really know how to install the RTAI kernel. Is it a matter of patching what's installed?

Tommy,

Remember the prototype text-based "Adventure Game?"

"You are in a maze of twisty passages, all of which look alike."

Off I go to try that passage. (Thanks for doing my work for me and re-pasting the link; and repeating yourself.)

(I misremembered the name anyway; it was called "Colossal Cave" and it was played on pre-Commodore "mini-computers," like the PDP-11. I encountered it first on a VAX and then on a later port to the Zenith Z-100.)

Fear kept me dragging my feet on doing the RTAI install.  I am something of a fool however, as I quickly re-learned when finally forcing myself to the task.  One of the most trivial things I've done wrt to LinuxCNC.

Having followed the steps (Sec. 7.2) and rebooted, the 4.19.195-rtai kernel was not offered on the grub menu.

I located it on the boot partition associated with the version of Debian 10 I'd originally installed the RTAI on, but have not been successful getting it to be one of the menu choices. In trying to get it recognized (by update-grub) I managed to muck up the system so the original Debian 10 won't boot either.  (I am something of a fool...)

I still have a booting version of Linux Mint which I'm using to try to straighten out the booting.

(Debian's boot error says "file <old-vmlinuz-rt-amd64> not found" and that I have to "load the kernel first".)

When I learn how to edit a grub entry to add the paths to the rtai files, I'm sure it will boot again, after which I'll try to run update-grub again.