Next Zenxy build ideas

vicious1 · April 28, 2021, 7:04pm

V2 has built in 2209’s

jeffeb3 · April 29, 2021, 1:50am

Did you try sending $Stepper? Maybe it is one if those settings.

vicious1 · April 29, 2021, 2:24am

Hmmm, no Let me try that.

vicious1 · April 29, 2021, 2:57am

Nope nothing fun in there.

ddbuster · April 29, 2021, 1:12pm

Don’t know if this helps but Bart says “The TMC2209 stepper drivers run your stepper motors super quietly and you can completely configure them via software (no more pots and jumpers)”.

In his default config he has:
#define TRINAMIC_RUN_MODE TrinamicMode :: StealthChop // Optional TrinamicMode :: CoolStep or TrinamicMode :: StallGuard
#define TRINAMIC_HOMING_MODE TrinamicMode :: StealthChop // Optional TrinamicMode :: CoolStep or TrinamicMode :: StallGuard

And Trinamic says:
Unlike other voltage-mode choppers, StealthChop2 doesn’t require configuration. Instead, it automatically learns the best settings during first motion following power-up and optimizes settings further in subsequent motions. An initial homing sequence is sufficient for this learning process.

So to me it reads like no current setting at all, no pots, no software, it just takes care if it automatically.

Jerome · April 29, 2021, 1:44pm

One note here for TMC2209 StealthChop mode, when enable it reduce the noise by reducing the torque, just be aware

vicious1 · April 29, 2021, 2:35pm

That is great to know! Thank you!

vicious1 · May 16, 2021, 6:18pm

I have been working on it for the last few days. There are a few minor tweaks I want to make. It is soooooo good this time around I really want to put some finishing touches on the actual table design on this one.

I had some friends stop by and give me honest feedback, the biggest one was what to do with the edge beyond the “sand”. I have tried printed parts, lightly dusting, combing…might just have to add a border again not sure.

I have plan to hook up the end stops to the GRBLesp32 board today fingers crossed.

vicious1 · May 20, 2021, 1:17am

I have been banging my head on the wall trying to figure out what the heck I could possibly be doing wrong.

I have learned a lot about GRBL, that is the good part.

It turns out…the issue I was having my printed parts are invisible to the optical endstops. I was trying to be cute and use semi transparent red like the rendering. Big thick part absolutely no trigger. I dabbed an ancient fluid on there, white out. Couldn’t find any nail polish. Triggers perfectly now.

So any GRBL guru’s out there? I have an idea, it is absolutely not needed, we discussed this before about the unique homing requirements of the ZenXY v2. It can absolutely be done in the starting Gcode.

…but, I thought since we have these custom homing routines available I might give it a shot.
I need to use a large Homing pulloff in case the X axis is at home (#define DEFAULT_HOMING_PULLOFF 15.0 // mm) The bad part is right now if I home it also parks at X=10. So anyone know how to do a custom homing routine so if you home with the buttons in the gui it homes and parks at 0 but still keeps the pulloff?

The actual issue is if you home Y, then X it parks at Y=10 and the X trigger will not hit. Again, this is not the case with starting Gcode we can easily(I think) just tell it to home Y move to 0, then home X and move to 0.

jeffeb3 · May 20, 2021, 2:47am

I think what you want is:

Move Y in the negative direction until it triggers.
Move X in the negative direction until it triggers. (both of these would exit immediately if they were already triggered).
Move to (10,10).

Is that right?

Corexy has a long custom homing function. Much longer than I would expect. It looks like it mostly handling lots of potential user choices.

github.com

bdring/Grbl_Esp32/blob/main/Grbl_Esp32/Custom/CoreXY.cpp#L76


    motors[Y_AXIS] = geometry_factor * position[X_AXIS] - position[Y_AXIS];
    position[X_AXIS] = motors[X_AXIS];
    position[Y_AXIS] = motors[Y_AXIS];
    // Z and higher just pass through unchanged
}
// Cycle mask is 0 unless the user sends a single axis command like $HZ
// This will always return true to prevent the normal Grbl homing cycle
bool user_defined_homing(uint8_t cycle_mask) {
    uint8_t n_cycle;                       // each home is a multi cycle operation approach, pulloff, approach.....
    float   target[MAX_N_AXIS] = { 0.0 };  // The target for each move in the cycle
    float   max_travel;
    uint8_t axis;
    // check for multi axis homing per cycle ($Homing/Cycle0=XY type)...not allowed in CoreXY
    bool setting_error = false;
    auto n_axis        = number_axis->get();
    for (int cycle = 0; cycle < n_axis; cycle++) {
        if (numberOfSetBits(homing_cycle[cycle]->get()) > 1) {

I think the main piece from a regular $H is just calling limits_go_home, but I am not sure, and I am not at my computer right now. It may also be in the end of that for loop. Maybe we can just move some of the approach stuff into a separate loop to get what we want.

vicious1 · May 20, 2021, 3:24am

Still monkeying around with it. I tried a few things something is still wrong.

Reflashing.

What I want is
Move Y, negative, until it triggers, then (either stay there, or move -2 so the X flag will catch).
Then move X, negative, until trigger, (the x trigger is 12mm or so early so it will either need to move -12 or just set it’s position to x=12.

Two catches.
1-when powering up and it is already at machine minimum X is about 12mm from releasing the trigger, so that is easy to handle with the pull off value. it will move at least 12mm in the positive direction before it throws an error.
2-For whatever reason If I “home all” Y goes negative, triggers, then moves an additional 12mm away (the pull off distance), then starts homing X. This could possibly be a bug.

vicious1 · May 20, 2021, 4:13am

Hmmmm seems to have something to do with work offsets I think. I am not used to grbl at all. Getting closer.

vicious1 · May 21, 2021, 3:42am

Well, This works manually.

$HY
G92 X0 Y0
G0 Y-18.5
$HX
G0 X-28
G92 X0 Y0

Homing either axis resets each axis to the pulloff distance (in this case 15), even if it was not homed. So you have to G92 it each time.

Different from Marlin, I am pretty sure it is intended to use work coordinates at all times, not the standard coordinates. Kinda funky, at least I think I worked it out this way. I will try to really nail down the work coordinate thing another time.

This big table is coming up X692 Y1306…anyone want me to run a pattern you create?

vicious1 · May 21, 2021, 4:06am

Well that didn’t work in the starting Gcode…this does

$HY
G92 X0 Y0
G0 Y-18.5
G92 X0 Y0
$HX
G0 X-28
G92 X0 Y0

vicious1 · May 22, 2021, 4:02am

OMG, this thing is sweeeeeet! I will get together a build thread at some point soon.

I know this has taken forever but I have learned a lot and it was worth it!

Sandify is super simple and amazeballs at this point. So needed on a giant table and very rectangular lets you do some fun stuff. The table is looking fantastic, I have a cool pattern running now.

The pen laser board from Bart Dring is stupid awesome. I can make a pattern, and upload it from any device that I am on, I can even start it. Chaneg accel and speed settings, as well as all sorts of other things…

Then, Change the mood with the WLED setup and the lights…

This is what I wanted the Zen to be. You can run it crazy crazy fast, or silent and extra zen.

I am as happy with this as I am with the Primo. I will start getting some pictures now.

vicious1 · May 22, 2021, 4:03am

Sandify for the win!

This morning’s coffee and breakfast pattern.

vicious1 · May 22, 2021, 4:53am

jeffeb3 · May 22, 2021, 12:55pm

That is so big. Very cool to see such detail on the large patterns. The lighting Looks awesome too. Very nice work.

Wolfspaw · May 22, 2021, 2:50pm

This looks fantastic! I have my 3-D prints complete and my V1 mechanical components order arrives today. Is the plan to have a control board flashed with the firmware in the store in the near future? (My weakness is in the electronics…specifically the coding)

vicious1 · May 22, 2021, 3:52pm

Thanks!

Currently, the only way to get this board is direct from the source, https://www.tindie.com/products/33366583/tmc2209-penlaser-controller/. Any board will work really but This does seem like a great fit for this application and I will make the config public once I am sure I did it right.