Advanced Search

kcjengr.github.io/probe_basic/probe_basic_parameters.html

these are all the parameters used by probe basic, they need to be listed in the var file for them to be persistent otherwise they will be volatile per linuxcnc docs.

please feel free to rewrite the docs, i absolutely would love for someone to handle that aspect as its not the easiest to find a way that everyone understands and clearly my approach could use some expert assistance!

the docs also are meant for the develop version. I have gotten a bit side tracked on another project and haven't had time to update the release from develop to stable, but it is what will soon be the stable version. when in doubt, its always best to check and see if the sim works, if it does but your machine config does not, you can move forward knowing their is an issue with your configuration files. you can always compare to the sim config files that do work and those should give you a working installation.

The jogging issue is probably the standard problem with KB repeat


The overshoot is likely a tuning issue, I would use the standard velocity mode/PID stepgen control
(use a pncconf created configuration for an example) Also make sure to use the DPLL for stepgen
configurations (use pncconf again as an example here)

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 -

 

Hallo zusammen,ich stehe am Anfang eines Projekts ähnlich dem von Rüdiger und möchte meine gebrauchten Rexroth IndraDrive HSC01 in LinuxCNC über EtherCAT betreiben. Aktuell sind die Antriebe jedoch mit PROFINET-Firmware ausgestattet, weshalb ich dringend die korrekte EtherCAT-Firmware benötige.Folgende Eckdaten zu meinen Regler:

• Typ: HSC01 E1 W0003 A02 B ET EC PB L3 NN FW
• Aktuelle Firmware: FWA INDRV MPB 20V28 D5 1 NNN NN

Meine Fragen an euch:

• Ist R911330278  "FWS INDRV MP* **VRS NN ETHERCAT" tatsächlich die passende EtherCAT-Firmware für diese HSC01-Variante?
   

Rexroth selbst hilft mir nach  Nachfragen nicht weiter. Ich freue mich über jede Bestätigung, Quelle oder Hinweise zum Vorgehen!Vielen Dank im Voraus für eure Unterstützung.Viele Grüße Thomas

Hi, yes that is possible. I would actually reccommend the esp32 over the Arduino, as if I remember correctly the ADC resolution is better on the ESP.
I only ever used it with USB interface.
If you know what you are doing I guess you can run it in ttl2USB too.

Memory at d1000000 (32-bit, non-prefetchable) [disabled] [size=64K]

is suspicious, Sometimes this is BIOS option related.

Not entirely sure if this is the correct category of the forum for this question, but here goes:I've just done a completely fresh install of LinuxCNC and I'm running into a few issues — some related to EtherCAT, but also with.I'm trying to usewith a 5i25 board. I installed it and ran the following command:But I get this error:The 5i25 itself isn't broken — I’ve tested it on another PC and it works fine.When I run, I can see the board:It feels like something went wrong during the software installation. Has anyone seen this before or know what might be wrong?

As Tommy said, it's difficult to say without seeing all of your settings and such.  The sputtering is likely a connection issue of some sort, but the dive looked to me like there's something set incorrectly.  Looked like a move to cut height that was in the part rather than above the part.