Advanced Search

the latest stable version DOES work, but it is not working for you currently. what i am saying is i have no idea why you are getting that error and i cannot reproduce it here, so without knowing where or why that error is happening for you specifically and not here or being complained about elsewhere, the next logical step would be to update and make sure its not something wrong with your install or a change made that you may not remember making or be aware had effect that was made without your knowledge.

Before i spend any time troubleshooting with such little data on the problem, it would be prudent to know for certain that it's in probe basic/qtpyvcp and not an issue elsewhere.

I would also test the probe basic sim to see if the issue is there as well, if it is then it is probably an internal error issue and not a configuration issue. from there we can figure next steps. but identifying where the issue stems from is in my opinion the first step, so i would test in the sim and see if you can reproduce the error there. if not, then its a configuration change, maybe a stray typo from your editing? if you can reproduce in the sim, then i would say the next step is removing and reinstalling the stable branch and testing or testing, or testing the develop version. the develop version has file changes for the work coordinate system table and the dro's which may be a resolution. it also has a fix for running on linuxcnc version 2.10. i'm not sure what version you are running on, but if it is 2.10 it NEEDS the develop version.

tommylight wrote:

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

Grundgütiger. Lol; thx!

Maybe I should borrow $CHILD2's gaming keyboard and set the polling rate 
to 20kHz. I bet that the movement then cannot be stopped in time, hehe.

PCW post=332736 userid=481[...]  
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)

I created the config file with pncconf and left the

The units all seem to have changed from 2.8 to 2.9. Instead of periods/time we now have rates/frequency.  
I have 20+ years experience with running everything through the parallel port but 0 with Mesa cards.  

I also noticed that the former "BASE_PERIOD" (forgot what the name is now and I currently do not have
access to the new config; forgot them in the workshop) is not in the ini-file anymore.  
Not sure if this value can be changed at all. The Mesa docs are more than sparse, imho.

I must admit that I don't know exactly understand what you mean.  
Is there also an "extraordinary velocity mode"? And what is DPLL?


thx
AS
 

you need the subroutines from the rack atc sim, they are specific to rack atc, the subroutines in the standard probe basic file are default for carousel type. copy over the complete subroutine folder from rack atc config sim folder to your machine config folder. should work then.

Sorry, I forget to mention I'd started working on this, only saw you'd self-assigned the issue once I'd nearly finished!
But I see you've seen my pull request now, just linking it here for anyone else since I'll carry on discussion there.
github.com/LinuxCNC/linuxcnc/pull/3534

The test above doesn't show the probe bouncing, it just shows that motion.motion-type remains 5 (Probing), which is what I initially wanted to test.

In hindsight I should've just looked at control.c first, because the logic in there fully explains why the probe bouncing during probe move deceleration causes the issue.

Currently, after the probe is first triggered from a probe move, it doesn't matter what the motion type is, because it's either the first and only valid trigger during a probing move, or a trigger during a non-probe coordinated move.

So the simplest fix to just give an accurate error message which checks the motion type to determine the error message (which is where having confirmed that the motion.motion-type remains as probing for the entire probe move is ideal).

We need more info about the machine, size on all axis, gear ratio, final drive, where are the switches mounted and what type, etc.
Is the scaling correct?
etc etc.

i found some really odd namings in the ui for the widgets, it is very confusing and appears to be unfinished or a the very least very poorly internally connected. i'm not sure where some of the parameters are coming from or if they were intended to be hard coded only in the var file or not. I don't think this is actually a finished project from the looks of it, at least not from the link you posted above. you may want to try contacting zmrdko.

from my scan through the ui, subroutines etc, things do not match up and widget names are duplicated as if copied and pasted but not correctly named so it's hard to follow the parsing flow correctly.

there is also no custom_config.yml setup instructions for the ui widgets to be stored in and saved and loaded on startup which means everytime you startup probe basic, those variables in the ui will be dumped and set to placeholder text (0.0000) which will be unsynchronized with the persistent var file data.

these are things that can be resolved in the upcoming release as i created a new var line edit widget that will not rely on subs to store and load variable from the var file.

some of the numbered parameters you listed above are linuxcnc params:

linuxcnc.org/docs/stable/html/gcode/over...:numbered-parameters

any params used in probe basic or any other add on would be between 3-5000 as these are user configurable parameters. anytime you see one 5001 or higher it will be a dedicated parameter used in linuxcnc.

I would say that this project is still a work in progress from my look into it.here is my mapping of everything, you could probably fix it and ask the developer for a pull request if you wanted, that would be the course i took,but as it stands i don't think you will be able to get it working as is.