Advanced Search

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!

Hello Tommylight thanks for your quick reply. Need to check it out, let you know. BR

This is the download link

drive.google.com/file/d/1pmV587gXFEvznQB...00x/view?usp=sharing

Something has changed on linuxcnc between then and now, but not much.
In particular, the function for using GPIOs which was previously hal_pi_gpio and is now hal_gpio
linuxcnc.org/docs/devel/html/drivers/hal_gpio.html
forum.linuxcnc.org/24-hal-components/504...-with-raspberry-pi-4

The image of RaspiOS with Linuxcnc is available in this link

forum.linuxcnc.org/9-installing-linuxcnc...pi-5?start=40#303752

Let me know if you need further guidance

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.

For your homing issue, set a home_offset to move the axis off the switch when homing otherwise the home/limit switch will be homed when homing of that axis is completed