Thanks. I'm almost solving this problem and finalize my project. After that, I'm planning to share my "Lichuan-EtherCAT" project .

Hi all!

well i would like to change the toolpath colors in probe basic... is there any "easy" way to do that?

i´m on the Probe Basic stable channel... on LinuxCNC 2.97

and a second question... i read about "multitool color" what does it mean?

thanks for helping...

cheers 

miniwini

Hi Hakan, I got busy but I got some time today to try this. The drive is still not switching to OP

I am running the r8125 driver and getting these:

[ 1725.792847] IPv6: ADDRCONF(NETDEV_CHANGE): wlxd46e0e7f5d03: link becomes ready
[ 1742.191452] EtherCAT 0: Master thread exited.
[ 1742.191457] EtherCAT 0: Releasing main device D8:43:AE:B4:C2:68.
[ 1742.236333] ec_generic: Unloading.
[ 1742.310752] EtherCAT: Master module cleaned up.
[ 1743.441583] EtherCAT: Master driver 1.6.8 1.6.8.g2543cc5-1+27.2
[ 1743.441688] EtherCAT: 1 master waiting for devices.
[ 1743.447406] ec_generic: EtherCAT master generic Ethernet device module 1.6.8 1.6.8.g2543cc5-1+27.2
[ 1743.447433] EtherCAT: Accepting D8:43:AE:B4:C2:68 as main device for master 0.
[ 1743.447444] ec_generic: Binding socket to interface 7 (enp37s0).
[ 1743.488318] EtherCAT 0: Starting EtherCAT-IDLE thread.
[ 1743.488359] EtherCAT 0: Link state of ecm0 changed to UP.
[ 1743.496263] EtherCAT 0: 1 slave(s) responding on main device. Re-scanning on next possibility.
[ 1743.496265] EtherCAT 0: Slave states on main device: PREOP.
[ 1743.496266] EtherCAT 0: Re-scanning now.
[ 1743.496332] EtherCAT 0: Scanning bus.
[ 1743.889188] EtherCAT 0: Bus scanning completed in 392 ms.
[ 1743.889192] EtherCAT 0: Using slave 0 as DC reference clock.
[ 1825.874690] EtherCAT ERROR 0-0: Failed to set SAFEOP state, slave refused state change (PREOP + ERROR).
[ 1825.874715] EtherCAT ERROR 0-0: AL status message 0x001E: "Invalid input configuration".
[ 1825.875641] EtherCAT 0-0: Acknowledged state PREOP.
[ 1839.603079] EtherCAT: Requesting master 0...
[ 1839.603084] EtherCAT: Successfully requested master 0.
[ 1839.603187] EtherCAT 0: Domain0: Logical address 0x00000000, 23 byte, expected working counter 3.
[ 1839.603190] EtherCAT 0: Datagram domain0-0-main: Logical offset 0x00000000, 23 byte, type LRW.
[ 1839.603205] EtherCAT 0: Master thread exited.
[ 1839.603207] EtherCAT 0: Starting EtherCAT-OP thread.
[ 1839.691541] EtherCAT ERROR 0-0: Failed to set SAFEOP state, slave refused state change (PREOP + ERROR).
[ 1839.693540] EtherCAT ERROR 0-0: AL status message 0x001E: "Invalid input configuration".
[ 1839.695540] EtherCAT 0-0: Acknowledged state PREOP.


I am getting the same result with both the pdoindex

very nice, why not ethercat for all 9 motors?
Do you have a link to the ethercat I/O boards?

I suspect your issue is you are trying to use pncconf to set things up but I highly doubt it supports advanced kinematics models like scarakins.
You need to build your hal and ini files by hand in a text editor from the base xyz config you have.

Ok I have looked further into it and the problem doesn't seem to be related to the configuration as it is now happening with both configurations.

I am running from a parallel port on linuxCNC 2.8.1

What was happening is that when I start up AXIS, I can move the dual X axis, the Y axis and I can move the Z in one direction and as soon as I move the Z axis all axes will only move in one direction (and if I try and move it in the other direction the numbers in AXIS increase but the axis doesn't move. In fact it has happened to one axis all the other axes start behaving the same.

The motor drivers don't seem to be lighting up any error lights. I am using a cheap eBay 5 axis parallel port breakout.

After putting an oscilloscope on the pulse pins I eventually worked out what was happening. The voltage of the pulses was consistent when it was moving in one direction but if you looked in the opposite direction they were getting weaker after a period of time. So it would work in one direction but in the other it might move a couple of steps and then stop.

The core of the problem was that those breakouts need 5V and I had assumed if I gave it 12V instead (which the inductive sensors wanted) it would make 5V from it... they don't, so it was scavenging a tiny current from somewhere and for some reason if the direction pin was high it used less current to make the pulses on the pulse pins than if it was low so it only went in one direction.

It was all the more opaque because the inductive sensors obviously somehow drew more current in some way so it worked better with switch end-stops than with inductive ones, which made me think that the problem was software not hardware... that's a day I won't get again.

probably because after homing you need to move axes not joints. I think what you are describing is expected behaviour.
If you run the axis gui, the display changes from reporting joint dro's to axes dro's on homing.
Just install home switches to all axes and get in the habit of homing as soon as you turn the machine on.

Hello,

I'm currently working with the probe and the toolsetter (Renishaw type).

Both work very well.

I'd like to be able to measure the tool diameter with the toolsetter.

I started looking into it and saw that this function isn't implemented. And to be honest, I don't really have the skills to do it myself.
Has anyone implemented this function?

Laurent

Hello Frank,

thank you for your Answer.
I am using FreeCAD for CAD and CAM. FreeCAD always usese the tool table to set the tool offset after changing the actual tool (M6 in the g code). So I wrote my own script for dynamic tool change, that writes the measured tool length into the tool table. FreeCAD can use it than after Tool change within the g-code.
For getting the z-level I change to any tool (M6 Tx), that starts my Script to measure the tool. After that I want to touch the plate. The program works fine until it substracts the tool length as its last step (if i would add the tool length from tool table again, i have the correct value for the hight fof my tool above my workpiece.

Perhaps you have an idea for that issue?
Many greetings from Germany, Klaus

Out of curiosity what model and specs do you look for in your Lenovos? How often to you come across one that's just not suitable?

Das war die Lösung!
Jetzt ist alles wieder da.