Advanced Search

Does LinuxCNC find the card?

Got it! Now that I had RPM control forward and reverse with a bonus green GUI scale in both directions it was just a matter of adjusting this:

setp scale.0.gain 0.00275

To this:

setp scale.0.gain 0.008

Which so far is the closest to s300 command. I'll know more when I get an RPM gauge on it.

It may require some adjustments in the VFD. But I'm content with the progress so far.

I think I'll have to go back a couple of steps and try to fix my probe basic config before I continue work on this.

I seem to be having the same trouble as this other user...

forum.linuxcnc.org/qtpyvcp/56674-probe-b...-parameter-variables

I was able to get basic probing routines working by manually editing the parameters in the var file. However, the link between values entered in the ui boxes and the var file seems to be broken. If you try to change a value by entering it in a box it just doesn't do anything.

Is there a place where all the necessary configuration steps are a set out clearly?

I was trying to follow these but evidently they are not totally clear and a bit lacking:

kcjengr.github.io/probe_basic/index.html

I think my config got messed up a couple of times, e.g. by copying values for an imperial machine into my metric machine's setup. The parts that need editing could be made a bit clearer.

Good point tommylight Though I may modify the models for CNC machining .

I have a small HP ProDesk 400 G3 SFF. From your suggestion i have looked at both devices (same pc type) bios settings, as of now nothing sticks out yet.

One step forward. After some digging on the internet I went into custom_postgui.hal and changed this:

net spindle-vel-cmd-rpm gmoccapy.spindle_feedback_bar

To this:

net spindle-vel-cmd-rpm-abs gmoccapy.spindle_feedback_bar

And it now shows a green status bar in the GUI in forward and reverse.
Still working on the rpm issue.

I had a couple of Mesa cards laying around for years and finally found some time to put it into operation.
Especially because the RPi5 comes with this massive performance boost <3
It’s all basically working, except for the pinout (had to solder an adapter), and everything seems to work in auto or MDI mode,
although I only tested a few moves; but manual control is extremely choppy.

The constant movement is just interrupted, as I would have stopped pushing the the button.
Acceleration/deceleration is working, so it’s not a communication issue.

Here: 


Probably unrelated, but strange:

At the end of rapid moves, controlled via MDI, the controller or LinuxCNC creates some extra steps.
I did not count them yet, but will check this after the rest is okay:

 


Are these “user space” issues? Currently I exclusively have older RTAI setups working;
never used this one kernel thingy.

Did I set up anything incorrectly?


thx
AS

 

You are correct, Peter. When pncconf generates the configuration HAL file it include two lines that prevent LCNC from launching. A search on the forum identified the culprits and suggested the two lines be commented out. In my zeal to get on with my project, I commented out the wrong lines. Correcting the issue resolved the problems.

Kind Regards -