Advanced Search

Es riecht stark nach zu hoher Latenz. Wie sind die Werte vom Base und Servo-thread?

I don't think moving back to the original position after an M6 is standard practice, all post should have safe move inserted after a tool change, this is not something dealt with on the machine side IMO
If your post expects the tool change to happen and the machine to not have moved and does not give you a way to implement safety moves to re-approach the work-piece after a tool change, this is just bad design of the CAM/Post the fix should be there IMO

Not that i know of, except the included with LinuxCNC, but i can prove some for plasma and for engravers/scratchers i build:
forum.linuxcnc.org/show-your-stuff/46752...ver-etcher-scratcher

current CPU frequency: 2.10 GHz (asserted by call to kernel)

All is good, move on to testing on a machine.

Uthayne wrote:

This also occurs with Qtplasmac. I can replicate it if I use the keyboard to jog and click to another tab while jogging. It loses focus/control even if I release the keyboard jog arrow and I have to go back to the main tab and tap a jog button again to get it to stop jogging.

I never realized this. I can replicate.

I will definitely be working on a fix for this. "Stay tuned."

I tried to compile this old working 4Axis kinematics (originally 5Axiskins) but getting compiling errors

forum.linuxcnc.org/10-advanced-configura...p-with-rtcp?start=80

Not able to understand current 5Axiskins

Can you throw some example? Zero in what?

Hello,

is there any gentelman which has running Xenomai or Cobalt kernel for his iron?

I need some inspiration or talk what, how, prons and cons ... experiences !

thanks 

Tool changers are often more difficult than the test of the machine, if only because there are more variations.
What do the two motors do? What manner of toolchanger is it?

This also occurs with Qtplasmac. I can replicate it if I use the keyboard to jog and click to another tab while jogging. It loses focus/control even if I release the keyboard jog arrow and I have to go back to the main tab and tap a jog button again to get it to stop jogging.

I would leave the kinematic as is and simply set the unused joint position to zero.

Private messages are disabled in this forum.

An der Dokumentation der 'devel' Version wird zur Zeit in grösserem Umfang gearbeitet.

Wenn du 2.9.8 verwendest solltest du sowieso die 'stable' Version der Doku verwenden: (beachte then Unterschied im Link)
linuxcnc.org/docs/stable/html/de/gui/pyvcp.html

Signal wire colors default to color codes representing the signal type, but can be edited. If the rat's nest is a confusing mess of same-colored wires, double-click or right click a wire to edit its color. All wires connected to the same output are synced and will change to your edit.

You can also change the wire (hal signal) name, but the current version of halflow gives you no capability to load your edits back into your linuxcnc hal config.

Also not sure about the frequency on cpu 1. The governor looks right but current freq = 400Mhz. This doesn't seem good if I understand it right. (again very new to this)

$ sudo cpupower -c all frequency-info
[sudo] password for cnc:
analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 2.10 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 2.10 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 2.10 GHz (asserted by call to kernel)
boost state support:
Supported: no
Active: no
analyzing CPU 1:
driver: intel_pstate
CPUs which run at the same hardware frequency: 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: Cannot determine or is not supported.
hardware limits: 400 MHz - 2.10 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 2.10 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 400 MHz (asserted by call to kernel)
boost state support:
Supported: no
Active: no