Advanced Search

Now all these errors appear indicating that some strings are already in the ini file:
Error modifying ini file
While reading from '<string>' [line 24]: option 'position_feedback' in section 'DISPLAY' already exists
error modifying ini file
While reading from '<string>' [line 24]: option 'position_feedback' in section 'DISPLAY' already exists
Error modifying ini file
While reading from '<string>' [line 37]: option 'program_extension' in section 'FILTER' already exists
Error modifying ini file
While reading from '<string>' [line 71]: option 'halfile' in section 'HAL' already exists
Error modifying ini file
While reading from '<string>' [line 94]: option 'tool_table' in section 'EMCIO' already exists
Error modifying ini file
Source contains parsing errors: '<string>'
[line 291]: '= \n'
/usr/bin/ncam:346: PyGTKDeprecationWarning: The keyword(s) "type, message_format" have been deprecated in favor of "message_type, text" respectively. See: wiki.gnome.org/PyGObject/InitializerDeprecations
dlg = gtk.MessageDialog(parent = None,
/usr/bin/ncam:346: PyGTKDeprecationWarning: The "flags" argument for dialog construction is deprecated. Please use initializer keywords: modal=True and/or destroy_with_parent=True. See: wiki.gnome.org/PyGObject/InitializerDeprecations

Good morning everyone. But does this conversational lathe software only work with Axis or does it have its own native GUI?

Hello,
I still work on the 'sedm' project on GitHub.
But there were questions about the technology';s origin. 
So i took a week (so far) to resurrect the tools I used to generate tech.
The premise is that a discharge of N amperes at Vdischarge voltage,
for T uSecs can be calculated.
It's been a challenge, as the code is Excel 4 XLM ( the pre VBA language).
It's a work in progress. I was pleased to see the inputs were Idischarge Vdischarge Tduration,
making the relationship OverBurn is proportinal to joules.
I was also pleased it listed RMS,RA,Rz and VDI surface finish values for
each discharge energy.
Is this project wanted as a Github repo?
I'll need to translate it from Excel4 with XLM 
to LibreOffice(current) with Python as the macro language.
lemmeknow
Tomp tjtr33 

excellent.

You might have to do some testing, EK1100 works fine as the first DC with Beckhoff servos, but I don't know how your servos will like it, to be tested, possibly fine, but I wouldn't finalize anything before testing is done.

So, even if you switch to the EK1100 as a coupler and related I/O on the EK1100 backplane, it is not recommended to use them as the first slave. Is it better to install the drives first and then the EK1100?

Verify Pr0.04 with inertia identification.
Zero Pr2.22 and Pr2.23.
Raise Pr1.10 to ~500, see if small moves land correctly.
Bring Pr1.12 up in 10-point steps with Pr1.13 ≈ 50.
Measure breakaway torque per direction (d04 monitor) and set Pr6.08/Pr6.09.
Only then, if still imperfect, enable Pr2.50 (ZTC).

Exist a model one 5 volt TTL with 1 channel encoder or 2 channel encoder , with really Z index signal ?

EL5101 is 5V with the Z index

That's exactly what I'm looking for. Perhaps someone has already made such adjustments to the driver and can say which parameters need to be adjusted.

I'll try your latest patch from this morning later today or tomorrow. If the axes make noise, I'll move the first current slave to last, so we'll have the 3 drives first, then the I/O.

Also new 2.10 will not start with your .ini configuration having names with hyphens, use underscores

Some booster parameter for micro increments?

Never mind, I had the name of my handler file wrong in the ini file.
It works! 

Thank you

 
 


And the INI lines to add it to a tab in Axis.

Tha model EL5152 is for 24 volt encoder , we normally use 5 volt TTL encoder, because normally use emulated endoer out the drive .

Exist a model one 5 volt TTL with 1 channel encoder or 2 channel encoder , with really Z index signal ?

No, not that.

So, if I tap just once, for example 0.1 mm, the axis moves 0.09 mm and it takes about 1-2 seconds for it to adjust.
It's exactly the same at 0.01 mm.
At 0.001 mm, I have to tap several times before anything moves, and it takes quite a while for the axis to adjust.
I did some calculations:
17Bit encoder and 10mm spindle:
1mm = 13107,2 inc = 35,38°
0,1mm = 1310,7 inc = 3,5°
0,01mm = 131,0 inc = 0,35°
0,001mm = 13,1 inc = 0,035°

The A6 should easily manage that.I don't think autotuning alone will be enough.
You'll probably have to adjust some settings in the driver.