Advanced Search

With open loop, (stepgen feedback) you need to have a _much_ higher P term
(typically 1000 with a 1 ms servo thread period)

 

Yeah, the title is a bit misleading at this point, but not sure it's worth making another thread for this.

I see what you mean but I've tried vastly different acc/vel values on the joint and stepgen sections and it still has the same kind of behaviour.

If it was a physical issue that should be ruled out when using stepgen.position-fb instead of encoder feedback, I'm thinking so? But that makes no difference still...

I tried to figure out how the joint comes up with the position command but with no luck either.

Thanks for the help,
I'll go through this step by step and get back to you 

This retrofit is possibly the easiest retrofit of all mills. I used a 7I97T with the existing servo dives and VFD.Notes:1. Aside from the servos and VFD there are only five 24V miniature relays to control.2. Since the servos utilized a tach (Aka Resolver) drive tuning took minutes to tune.3. The only additional board I made was transistor board to provide a signal to the J425’s drive enable relay. The drive enable optocoupler on the 7I97T cannot provide sufficient current for this miniature relay. This board consisted of a P-Channel Mosfet and a 10Kohm pull up.4. On the J425 all of the axis limit switches and the Estop are all connected in series to a single relay.5. I was able to use all of the existing wiring. I didn’t have to cut or splice any of the existing wiring.6. Almost all of the wiring to the 7I97T was through the existing DB connectors.7. Just like any other CNC, you’ll need wiring diagrams. They are available from zpsusa.com/kneemills.html I did not have any issues with the installation or performance of the Mesa 7I97T. I was concerned on its ability to thread mill since it requires 3 axis’s synchronized. It wasn’t an issue at all, in fact I cranked it up to 120ipm without any following errors.

Good evening, has anyone tried the new fixes in Grandixximo v1.41.0-pre2?
Are the slave pin values ​​read quickly?

Yeah, that’s definitely part of it as well.

I’ve touched on 5-axis concepts too, mainly around coordinate systems, tool orientation, and how things behave behind the scenes — even if most of my hands-on work has been 3-axis and some 4-axis.

It definitely adds another layer compared to standard setups.

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.