Advanced Search

rodw wrote:

But none the less I too was gobsmacked when starting off to find the documentation runs to 1347 pages!

 

Yet people still sometimes complain that there isn't enough documentation....

And it's true, I think. For example we really could so with a section on toolchangers. 
 

Is there any indication what /STV stands for? Do you have something that makes you think that's the enable? If it is, then it is shown permananently wired, which seems a little unexpected.
I think you have the polarity right.
I am not clear if that (19) 15V is an output or not, but a multimeter would answer that question.

In theory you could write a new interpreter that takes an input formato other than G-code, but I suspect that would be a very large amount of work for little to no reward.

Hi,

I finally have some succes, after a long story.

The software is already pre-configured so that linuxcnc scurve runs.

This then is a debian 12 rt distribution running:

• linuxcnc scurve
• ethercat-master
• cia402
• linuxcnc-ethercat

Download mirror:
repository.qtpyvcp.com/repo/linux-distro/

README.md

1. The readme file informs how to extract the 2 archives of type .7z.
2. The readme file informs how to proceed with the .img files.

The user has 2 choices.

1. Using .img "debian_disk" wich can be loaded into a linux vm directly.
2. Using .img "debian_raw" wich can be copied to usb and is a bootable linux distro.

I had a Vcarve licence 10 years ago. Very unhappy buying crap for big money. Finally shredded the licence and software. No pros, just cons.

Even on the other motor ports the TMCs aren't responding.
The serial output didn't change.

 

Parts have arrived, here is my understanding of the wiring per 1 stepper:
meas card needs 5V supply
TB6600 should be powered with the voltage for the steppers (12V in my case to start with).

As I understand it the connections between TB6600 and mesa should be like in my bad sketch.

Thank you very much for your detailed explanation.
During testing, I tried using microstepping at 8, and I changed the scale in the ini file to 40. Then I set G-code "97: G1 X0 Y0 Z0 F300", and it ran successfully!
However, I don't understand why G-code "96: G1 X345 Y100 Z0 F600", runs properly with F600, but when I use G-code "97: G1 X0 Y0 Z0 F600", it fails to run. Why does line 96 run successfully with F600, but line 97 produces an error even though both use F600? Could you please help clarify this difference? Thank you.