Advanced Search

Looks reasonable.

One thing: never disconnect a stepper motor from the drive with the drive powered up. I don't know for sure that that will blow up a TB6600, but it's definitely not somethng that a TB6560 could survive.

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.

If there was an issue with the motor0/1 not working at all, that could explain why the TMC drives werent working but maybe not. Just start up and check the remora serial output as you have been doing, and look for " TMC drivces OK" or something like that.

If the TMC drives dont get configured, they load the default settings, so your microsteps and current might not be what they are supposed to be.

Hey folks,

I’ve been using Vectric Aspire 12 recently for my CNC projects and thought I’d bring it up here in case anyone’s been thinking about jumping into it or has questions about setup, workflow, or even just getting access.

It’s been super handy for both 2D and 3D carving, made a noticeable difference in my sign work and custom routing gigs.

If you’re messing around with Aspire or thinking about it, feel free to hit me up. Happy to share what I’ve learned or point you in the right direction.

Cheers!

I decided to create this topic because I want to assemble a metal laser cutting machine. I want to achieve functionality as close as possible to FSCUT. As I understand it, working with vectors in a straight line will not work without converting to G code (the machine will operate using G-code generated in Pronest). As I understand, there is already a QtPlasmac interface, which has a nice and user-friendly design. For now, my plans are as follows:

1. Development of the machine's mechanics
2. Development of the machine's electronics
3. Development of a high-speed height sensor
4. Improvement of the interface

Here I will share my progress in assembling the machine. English is not my native language, so there may be some misunderstandings

Torque commanded servo control is working perfectly fine on my cnc router with Linuxcnc. But a good fast low latency PC is required for good results.

The trigger level is greyed out if the source channel is monitoring a simple bit (on/off) signal or pin. To enable the trigger level slider select a pin or signal that is a float or integer value for the source channel for trigger.

Got it working. Will share a working config soon, for future reference!