Advanced Search

A lot of the "TB 6600" drivers actually use a S109AFTG, why the vendors keep advertising the wrong chip and printing false technical data on the devices, I do not really understand. The box says 1/32 microstepping (?), so it is not a TB6600 (which only goes up to 1/16th)


For small motors S109AFTG is O.K.. for bigger motors I would not use them. ( TB6600 I would not use, no matter what motor )
 

As per the data sheet 3A is asking for trouble it is more like 1.5A. The 4A that everybody states (false, as fraud or due to ignorance remains a secret) is the Absolute Max. Rating. (magic smoke boundary?)
 
Quote from data sheet:" The absolute maximum ratings of a semiconductor device are a set of ratings that must not be
exceeded, even for a moment. Do not exceed any of these ratings.
Exceeding the rating (s) may cause device breakdown, damage or deterioration, and may result in
injury by explosion or combustion."

Greetings Timo

ps. my approach would be, a) reduce current to 1.5 A, b) if not working buy other driver.
 

Sorry, I use Microsoft Translator, I don't know if you can read it.

The existing interface with graphical previews is poor in terms of responsiveness for large files, and there are several GUIs that are better with preview disabled (e.g. gmoccapy qtdragon)

But they are also slow to manipulate the artifact coordinate offset after loading the G-CODE (the coordinates in the preview are updated).

Hello  andypugh 

How did you create that table for letting user to input that bending data ?
And how would linuxcnc interact with that data ?
I make a project with the same logic as you,making a tabel for inputting bending data,then i will convert them to Gcode and send to Linuxcnc
but dont know how to create the table for inputting data
Thanks so much
 

AXIS also takes a long time to open it, plus (AXIS, stop) is the same (BUG?), tklinuxcnc response is positive, whether it is loading G-CODE or artifact coordinate offset, but it only has 3 axes.

@meister Here is a python version of spiflash.sh that works on either the rpi4 or rpi5, except the resetting the target afterwards isn't quite working.

github.com/digiexchris/6x11-sg-grinder-l...reconfig/spiflash.py

Unloading and reloading the spi modules on the pi5 image doesn't bring /dev/spidev0,0 device back again on the pi5, so I removed that, and am just power cycling the board to reset the fpga after flashing (sudo halt, wait for it to stop, power cycle). Also it's not possible to manually toggle the state of gpio 7, becaues it's controlled by the spidev0,1 automatically. Is that why you unload and load the spi modules again on the 4, to allow you to manually control the flash chip select pin? It seems that the only thing needed for flashrom to work is just pulling the reset pin low. Not sure how to reset afterwards though. I wonder if I need to set active-low instead, and set it high to reset?

I think on a new version of the board I'm going to put a reset button to interrupt the power to the board in order to manually reset it, and perhaps put a dip switch to set it into flash mode.