Advanced Search

Thanks for the documentation and this details, I'll read it carefully.

As for G-code, I'll have to delve deeper into it; for now, I'm far from mastering it.

I put a simple stepper motor in the last row to show visitors that it can drive Ethercat motors along with stepper /dir motors.

YOu can find detailed information at;
www.egerobotics.com/ethercat-dig32-io-interface
www.egerobotics.com/ethercat-digital-analog-io-board
www.egerobotics.com/ethercat-encoder-interface
www.egerobotics.com/ethercat-pwm-rc-servo-interface

try 

then 

show current config 

Doesn't anyone use a rotary axis anymore, and does no one know what the problem might be?

Not really, it's codes in Python in the vtk, and any updates will over write your edits.

Because there are different methods to measure diameter and different toolsetter types, it's a very per situation basis. You just need to write in the macro code for it. There is allot of previously functionality for it already in basic. Start by reading the rs274ngc code documents and looking over the existing subroutines for probing. It's really not too difficult if you have a decent gcode understanding. Nothing like writing program python for example.

The manual is short, look at the section reviewing subroutines. I have attached it for your reference. Also view the linuxcnc docs section regarding owords.

 
 

daveansell2 wrote:

Thanks, chips are being made as we speak. And I am feeling more comfortable now it is working again (it is amazing how edgy having bits of the workshop broken makes me feel.

 

You are welcomed, and i am glad.
As for edgy, have you seen my shops? I am edgy all the time, one of them is organized chaos:

The other is in much better condition:

Thanks, chips are being made as we speak. And I am feeling more comfortable now it is working again (it is amazing how edgy having bits of the workshop broken makes me feel.
 

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

daveansell2 wrote:

... that's a day I won't get again.

Yes, but you did learn something, so not wasted.
Report back when making chips.

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.