Advanced Search

cmorley wrote:

I would think (in general) encoder resolution, axis acceleration and trajectory servo update rate all have potential to improve the tracking.

but changing the speed significantly is not going to track in the same place with the current code. I wouldn't think it would be hard to code absolute position tracking, but I bet it has some corner cases.
 

If that's the case, it's crazy and broken as any speed variation would  cause threading inaccuracies.
The time to get into sync with spindle rotation can of course vary, but the target Z position must be
synchronized to the spindle angle for the actual cutting path (or it's not spindle synchronized motion at all)
 

I have a two questions I hope someone can answer.

I have a Omron spindle encoder with single ended A,B and I signals, plan to connect these to ENCA, ENCB and ENCIndex.
1) Unless Linux only needs the Ix input?

I also have two scales on my lathe:
The Z scale has single ended quadrature signals "A" & "B" and I plan to use the first two isolated inputs for these IP0, IP1.

The X scale uses differential signalling "A+". "A-", "B+", "B-". I suppose I could connect this single ended to IP2, IP3 but I loose the benefit of the differential signaling. However if Linux only needs the Ix signal (and not the quadrature A and B signals) from the spindle, I suppose I could use ENC A and ENC B for the differential signalling from the X scale.
2) I'm not sure if encoder A, B, and Index are all needed for spindle feedback to Linux? If only the index signal is required can I use ENCA and ENC B for my X scale quadrature signals?
 

kimkar wrote:

Are the QA, QB, IDX pins on the 7i85 equivalent to the A, B, Z signal in line driver encoders?

Yes.
QA = quadrature signal, A channel
IDX = index signal

You are welcomed, always.
Happy new year to all.

Hello,
is it possible and if so how can I read values ​​from qtdragon.pref and use them in a macro or an MDI call, for example?
Best wishes and a happy New Year to everyone. Frank

now, the i2c-bus is merge into the dev branch

many thanks to 'Schoch' , for the quadencoder(z) fixes and the much better rps/rpm calculations.

and many thanks to all other people that helps here, in github and in the discord chat.

epineh wrote:

That is really cool, once I have my existing machine fully tested I intend to start playing around with all the extra stuff you've implemented. When you say several devices per bus, is that now as per the standard i2c protocol, so 128 devices ? I understand that lots of i2c devices only have a couple of address options so that doesn't help.
 

if you have multiple devices that have the same address, you can still use multiple busses on different pins.

but there is also easy support for i2c multiplexer (PCA9548A/TCA9548A) now.



 

and the last files....

This is the file:
399555845-Sd-b3-031-030-00-000-Bosch-Servo-Motor-Manual

split up in 2 sections

 

I wil try to split up the other files, duo to the maximum file size...

these are the files:
Datakabel en Verbinding informatie
Maschinen Datenblatt
Motor Module Parameters

and the:
Elektrodokumentation FP3-50 2860 DIALOG12
Split up in 4 sections

Friendly regards,

Ronny

Hello everyone,As I will soon be starting the conversion of an amazing milling machine myself, I’ve been looking for information about it.
Since there is very little available about the materials and components used, I’m sharing the information I’ve gathered, in the hope that it can help others as well.It’s a machine that uses Bosch equipment, and I’ve uploaded the complete manual, schematics, and everything I have on it.

 Kind regards,
Ronny 

Hi, just wondering if you ever made progress on this? Also looking at EtherCAT drives from that manufacturer.

Are the QA, QB, IDX pins on the 7i85 equivalent to the A, B, Z signal in line driver encoders?

Hello Tommylight, yes this advices fixed my problem the THC is now working how it should.
Thanks once more and Happy new year!