Advanced Search

Keyboard jogging issue
www.forum.linuxcnc.org/38-general-linuxc...elocity-fluctuations

The logic looks fairly simple, and is here:
github.com/LinuxCNC/linuxcnc/blob/2.9/sr...otion/control.c#L716

That only fails if "if (emcmotStatus->probing) {" (line 691) is false.

The confusion here is that I don't see any change in state in your motion.probe-in channel, it doesn't actually appear to be bouncing (or maybe only not in the plotted example?)

I don't know for sure that "SET_MOTION_ERROR_FLAG(1);" (line 726)drives motion.coord-error but it might be worth plotting that too.

As an experiment, is it all OK until you enter a decimal separator?

Do you definitely have a linuxcnc.var file in the config directory (ie the directory that the INI file is in?)

If you "ls -al" the config folder, do all the files belong to the same user?

There is something funny going on here, and it's not something we have seen before.

Unfortunately the documentation needs to be written by someone who understands how the configuration is supposed to be done. So, I can't help with that.

I saw that you had previously recommended testing the sim but it isn't clear how that is helpful. Does the sim work - well no, it doesn't control my machine, it can't do anything. It doesn't give any errors if that is what you mean?

Obviously most errors are going to be introduced by mis-configuration. But that problem will persist until the process is well documented.

Is it the intention that the user attempts to enter his machine specific configuration into the sim? If so, I missed this step, was it actually part of the instructions?

For the best chance of success, with the current code state, should I be trying the develop version then?

I did notice that when I tried to open one of the files it told me that it couldn't locate the src files (including these was not part of the normal install instructions).

Just to explain what was going on previously.

The config is set up with closed-loop control of spindle speed, using a PID component. You can look up PID elsewhere, but most references will tend to overcomplicate it. They have existed since long before digital computers. You run a PID controller in your head when you drive a car. Feedback is looking at the speedo, the command is how hard you press the pedal, and the output is how much power the engine makes.

To stretch the analogy, in your linuxcnc config you have a speedo that goes negative, but you are stupid (as you are a computer) and when told to do 70mph in reverse you see -70mph on the speedo, think "that's 140mph less than 70mph" and press the pedal to the floor.

You have to ensure that the domains of the signals are the same. If you are using single-sided speed command (spindle.0.speed-out-abs for example) then the PID neds to see a single-sided speed feedback, typically achieved by passing the measured encoder speed thorugh an "abs" component in HAL.

You might find it instructive to browse through the available HAL components, they are fundamental to the flexibility of lInuxCNC as you can do all sorts of manimpuations on the input and output signals.

You can see the list here:
linuxcnc.org/docs/stable/html/
if you scroll-down to "Realtime components and kernel modules" and (to a slightly lesser extent in this context) "Commands and userspace components"

I think that the 7i92 has bare IO pins, and in output mode I would expect them to be pulled-up to 5V when "on"

I would suggest testing with a multimeter.

Hello,I am in the process of getting 4x Lichuan LC10E drives running in CSP mode. I have also observed the behavior of a large following error in CSP mode, as user Sandro mentioned in his post on 14 Sep 2024. After many hours of trying to run CSP mode without encountering a large following error, I suspect that parameter 6068 "Position window time" is to blame. The default setting is 16 ms, which I interpret as the drive having 16 ms to reach the required position. Together with parameter 6067 "Position window", this allows for a large following error while the drive still believes it is operating correctly.

Unfortunately, I am unable to change these values. Initially, I tried reading them with:"<pdoEntry idx="6068" subIdx="00" bitLen="16" halPin="position-window-time" halType="u32"/>"

But this gives me a changing value in HAL show with strange behavior as I would expect a steady value of 16When I try to write to 6068, I get the following error:

hi guy's
i just finished flashing the firmware to my digital dream ec500v5 and upload the config file. now I'm i bit confused about proceeding and the documentation isn't making a whole lot a scene at the moment. I'm wondering do i need to make a hal file which contains the the pins from the ec500 and then let the main hal file call up the pin file?
I'm a total newby to this without any programming background. and the plan is to try and build a plasma table for my small buissnes.

thanks in advance