Advanced Search

I had trouble installing Verser's v2.9 probing screen for the Axis GUI.  Eventually I decided to try EasyProbe.  Easy enough, except that the pocket probing function has a constant that only works for metric.  But if you change ff_distance from 5 mm to 0.2, it appears that everything works.

EasyProbe allows you to calibrate the probe tip, which avoids the complication of using an indicator to get the probe tip colinear with the axis of the spindle.  The drawback is you must measure with the probe oriented as it was during calibration.  Here's my calibration setup

 

The ring gage is 1.0060 inches
 

After calibration, the I probed the pocket a few times.  The measured diameters varied from the standard by

1. 0.000,014 inches
2. 0.000,006 
3. 0.000,114
4. 0.000,097

I would only believe this to a tenth (+/- 0.000,1 in).  But it's not bad for a probe tip that is off axis by almost 2 thou.

While working with EasyProbe, I encountered manual tool changing for the first time, with rapids set to 200 IPM.  I had also set TOOL_CHANGE_QUILL_UP, which almost smashed the probe into the table.  I had set up the axes using the right hand rule, with +Y moving away from the operator.  This requires that +Z is up.  I turned off the quill-up setting but had several close calls because M6 rapids the spindle to the tool change location, not caring about the Z position.  So I've got to reverse the Y axis so I can take advantage of the quill-up setting.  

Hi, I am just on the way to start my ethercat adventure.
I received my ethercat servos and some beckhoff ethercat interfaces as well.
Now i recognize that I still need something to control my Optidrive E3 VFD over modbus.
Can I use the El6001 Serial Interface or wich Interface do I need?

I would really appreciate any help or hint

best Kai

Hi,

i think you need to update local git clone first. It needs latest updates.

Then build_cmake.

It is capable to switch between the two modes but it is not a 'normal' setup.

Because there are different setups there isn't a 'one size fits all' solution to do this.
In your case I would wire the DC drive as the spindle and the servo as a rotary axis (eg 'C').
Solutions will largely depend on what kind of encoder signal(s) you have and whether those track spindle position at all times or only in either turning or milling modes.
If you have encoder and index feedback from the same source and the encoder position isn't lost when operating the the spindle at max speed then you can home the rotary on startup and don't need to rehome when switching from turning to milling. There is 'caxis.comp' to prevent the spindle unwinding the accumulated rotations for this case. The original version of this can be found in the zip folder in this thread:
forum.linuxcnc.org/10-advanced-configura...ling?start=50#288345

If you do need to rehome the rotary due to lost encoder position then make sure to take note of the bug described in this thread and the workaround presented:
forum.linuxcnc.org/38-general-linuxcnc-q...blem?start=20#324276

Are you Chinese? If yes, add me on QQ: 304394405

why not use the native driver
<slave idx="3" type="EL2809"/>

Hi,
I´ve got a lathe with a DC Spindle drive that has an extra servo driver for milling operations. So the spindel would work as servo driven axis, let´s call it C-Axis. Simoreg 6RA26.
I´m not at that part yet, but i´d like to know before i start working on it, what´s best practice to implement that.
I´d like to have the spindel working as spindle with +-10V for RPM as a normal lathe and in milling mode it should switch to the servo driver, that works with +-10V too. I think i have a closed loop there too. Should i wire them up as if i had one physical spindle and one physical servo ?
So is Linux capable of switching mid program between the two modes ? is that a normal setup ?

Do you mean the hal_inertia_factor parameter?
Sorry, but I can't find this parameter (neither in halshow nor in the source code).

"Also, the program execution time should be faster."
Are you suggesting lowering this value: SERVO_PERIOD = 1000000,
or this one:
[TASK]
TASK = milltask
CYCLE_TIME = 0.001
I performed the above-mentioned tests with these settings.
 

When I was testing this signal input, I found that when I turned on LED0, the corresponding IO PIN was lit up at pin number 16. Similarly, the output position was also the same. In summary, the data I currently receive has been shifted by 16 bits. Additionally, I have attached my XML and the test results from Beckhoff (they are all OK). Could someone kind-hearted please tell me why?

I guess ChatGPT looked at this thread to come to that answer.
I read more than half of this thread yesterday. Some 8 pages or so in there are many working configurations, and people with success.

@John,

Maybe that's the case, but this is solvable.

I am writing some new code. We are free to change the state machine transitions for Lichuan.
Here you can see how to set states. In fact it's just a matter off setting a combination off bits in a sequence.

Currently i am waiting for a new servo drive, so my code is halted. I dont have a Lichuan here, so i can not write code for it
to solve any problems.
 

Told you, was just to sit back and wait
That milling machine looks and sounds great.

Can you share the ecat-conf.xml file you ended up with? Can help the next guy out.

And don't forget that "ethercat for dummies" post, greatly needed.

Thanks. When I use the naming in the linked config instead of the naming from docu it works!
I can see dir and step signals now on the correct pins.
One last problem before I can test with the machine. I use an enable signal for the stepper driver. I see it on the pin, but inverted. Is there a possibility to invert output pins at raspberry pi 5 or should I better do it in hardware?

It is a RPI. 
When I run the yzEllipse75.ngc, the machine encounters an error related to IMG_6867.JPG, IMG_6868.JPG, and IMG_6869.JPG.

Brilliant, that makes complete sense now. I'm a Linux noob so I'll probably ask a bunch of questions with seemingly obvious answers. I do know how to search so I try to keep it to a minimum.