Hello everyone, I’m building a 600x800mm burner with autohoming and autofocus. I’m going to use a DLC32 v2, but I’m struggling with the programming.
1: Can I use it as is with the default settings?
If so, I don’t understand how to adjust the settings for my build; which values should I change?
If not, which firmware should I flash it with? On the board’s GitHub page, I only find firmware for boards paired with a monitor, and I don’t have one.
2: What’s the difference between XY and normal cores?
3: My board is equipped with TMC2209 chips; do I need to configure them on the board?
I saw on the board that there are switches under the TMC chips; do I need to change the default values? (All 3 are at the top)
My burner is based on a Twootree TS2; can I use its firmware?
The values you need to. It’s very hard to tell you without having the hardware. Unfortunately, this is part of your research / learning curve if you design your own hardware. Basically, you only need to adjust the directions of the steppers and the steps/mm values to make the firmware match the physics of the machine.
The monitor is not relevant; you can ignore it. But I suggest using FluidNC or grblHAL. The original firmware is not maintained very well, and configuration capability is reduced. I suggest starting with FluidNC (but you will need to dive into the configuration as well!!).
If you are building mechanics, you should have come across this. Google for “CoreXY mechanics”, you will find plenty of information. If you don’t know what it is, you probably didn’t use it But it’s impossible to tell without knowing your mechanics.
You can’t configure them at all. The only way is to use them as drop-in-replacements. They won’t provide any major advantage over A4988 drivers, but they won’t harm as well. You can make them software-configurable, but this includes soldering and (no offense) since you ask so many basic questions this will be task for later, once you understood the basics.
You don’t need to change them, that setting is ok.
No. A firmware is tied to the mainboard it runs on. The laser head doesn’t matter at all. It just gets a 5V PWM signal from any mainboard, which every firmware will provide. There is absolutely nothing specific about the laser head that the firmware would include.
And I suggest reading the wikis of the firmwares (FluidNC has a great wiki) as well. I know it’s a bit overwhelming in the beginning, but after some time it gets much easier
I configured my DLC32 V2.0 to run on my glass tube co2 laser. I used the steps and direction from the board, that have outputs, prior to the driver hardware.
There are a few issues.
my Ruida uses two control signals to the laser power supply. This doesn’t exist with a grbl or FluidNC firmware. They are usually connect to Laser enable and the pwm or IN of the lps is toggled by the cpu to control power. IMHO, this drives an analog device (glass tube) like it’s digital, never a good idea in my mind.
driving the motor stepper drivers are close to the maximum draw for a direct connection to the DLC32.
Do you have motor drivers or are you using the driver hardware that comes with the DLC32?
What kind of stepper motors do you have, with the stock drivers on the DLC32 support your motors, current wise?
But it’s impossible to tell without knowing your mechanics.
