Advanced Search

Hey,

da ich nicht so oft mit dem Linux Rechner arbeite fällt mir so etwas nicht immer sofort auf.Allerdings habe ich den Eindruck, dass auf dem Rechner einiges nicht mehr stimmt, da auch der Firefox auf einmal in Englisch ist. und ich ihn nicht umgestellt bekommen habe, ohne ihn zu deinstallieren und neu zu installieren. jedoch funktioniert das System im Moment und ich hoffe, dass das auch so bleibt, ich habe keine Lust schon wieder das System neu aufzusetzen, da das echt viel Arbeit für mich ist, da ich nicht weiß, was ich wie machen soll.

VG Mücke

It could be a wiring/noise issue but typically this is because of the relatively
instantaneous velocity estimation (typically updated every ms), which tends
to accentuate the encoder inaccuracies. This fast update is important if a feedback
loop is used but a nuisance for a human readable display.

The way this is typically fixed is by low pass filtering the encoder velocity signal
before displaying it. If this has already been done, you might increase the time
constant of the filter

If the HOME_SEARCH_VEL and HOME_LATCH_VEL are positive, the axis will move to the switch, back off it, and re-engage it at LATCH_VEL until the signal changes state (again).

If the HOME_LATCH_VEL is negative, the axis will move off the switch and stop as soon as the signal changes state.  No 2nd move back on to the switch, so potentially done slightly faster if your LATCH velocities are really slow.

I think one of the contributing reasons LCNC's homing is so confusing is simply the terminology selected by the developers years ago.  The terms made sense to them, of course, but I think more differentiation in terms would make homing configuration more intuitive.

Such as changing HOME_OFFSET to HOME_SWITCH_LOCATION or similar.

And of course, the current terms make sense to some people so changes would make things confusing to them.  There's no perfect answer when it comes to preferences.

I'm not sure if this is the right place to ask about this issue, but I'm experiencing a strange and potentially dangerous problem.

I was running the same program all day without any issues. However, I had to stop the program halfway through due to a broken insert. First, I paused the program, then stopped the spindle, and finally stopped the G-code execution. The spindle was running with G96 (constant surface speed).

After fixing the issue, I reloaded the same G-code. But when the machine started moving with a G1 command, it moved at maximum speed right away. I couldn’t get it to execute G1 correctly until I restarted the LinuxCNC software.

Does anyone know what might be causing this? I was very lucky there was no damage.
I've also uploaded a video showing the problem.




Adding my configuration :


 



Is there anything wrong there?

Hi all 
I'm trying to piece together a boxford 160 to standard.
almost there I have all axis wired up and runing.
anyone know where I can find the correct one of these?
it's a minefield looking on rs components
it's a microsensor but looking at specs they dont macth what I think I need. any advice would be great..