Advanced Search

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!

Ah okay, so just because the motors are moving doesn't mean the firmware configured right?
So the problem is still there

I thought I'd add some pictures - PSU - Dinkle terminals - relay - lazy wiring board - contactor - Monetary NO push button to energise relay (SW1in schematic), rotary type switch to control power to circuit (SW2 in schematic). In my control panel the contactor is not mounted close to the relay but closer to the power supply supply minimizes the length of the AC power cables. This was just quickly thrown togther for demo purposes, in the cabinet it's more professional looking.

 

And a close up of the lazy wiring board, diodes are snubber diodes. Wiring is so much easier. Relay & contactor can be same or different voltages, hence the R+ & R- and C+ & C- points on the board. The 240AC is wired directly to the terminals on the contactor.

 

 

Sorry... that was a test i did.
Its set to 1000 usually. (Same problem ocours)
(1000 [PPR] x 4) / (4 [mm/rev]) = 1000 [Pulses/mm]
(Is this correct, when seeing in the halshow, that the encoder counts 4000 counts per rotation?)

But it seems, to not even use the encoder_scale, because i can just comment it out, without it throwing me an error at the start-up...

ENCODER_SCALE = 1
????
This should be 4 times the encoder PPR divided by the total distance moved for one rotation.

I've been following this excellent step-by-step guide, but I'm currently stuck with a problem: the DRO is off by a factor of 1000. When I move the machine by one leadscrew rotation—which should be 4 mm (since it's a 4 mm/rev leadscrew)—the DRO now shows 4000 mm instead.Previously, it correctly showed 4 mm, so something must have changed, but I can't figure out what. Could someone please take a look at my configuration files?