That’s why I’m going up to 3500 in 500 steps. I have 7 lines, 500 and adding 500 each time
Those tests all passed, no detected stall or perceived stall in melamine covered particleboard, need to up the depth or switch to harder material. Will be a few days before I can do more testing
I saw you originally noted issues with plywood. Plywood can be a bit of a wild card.
I’ve very rapidly learned this… it doesn’t make so much of a difference when hand cutting but it’s very noticeable on the machine.
“Weezer” cuts like butter, baltic birch cuts pretty nice, and the random mystery stuff is like trying to cut concrete…
“Plywood” is such a broad category of material at this point I suppose - so many different woods, adhesives, layer thicknesses etc…
Interesting, I think I could add that to the list of updates for a future version. I will have to look into it some more.
So it is using homing so it can be used for sensorless homing I imagine. But for fault detection in this case we would really need, current feedrate or G1 value.
That would make sense, at least how I would love to see it work. When the value is lower than 200 for example, turn up the current. Obviously this still has the problem I mentioned above, I am not sure how quick top react it would be but if it worked fast enough we could really really crank up things like travel speed. Or, what most want to push the steppers even harder without a heat penalty (stallguard / coolstep).
I started a list of things that make a jackpot update interesting to me. This thread has three separate entries!
Intentional support for external drivers would be awesomesauce.
Honestly, I thought we already did. I had no idea it didn’t work.
I could be wrong. Hardware is not my strong suit but I think the TMC2209s are 3.3v while most external drivers are 5v (or at least support 5v). I haven’t actually seen anyone get external drivers working on the Jackpot.
I’m looking at the schmatic right now. Having an option for 5V seems simple enough for me to add. And While I was poking around…it seems we can actually accept up to 50V input, free upgrade, maybe I need to test it.
Nearthental Cesar likes where this conversation is going! Uga uga!

it seems we can actually accept up to 50V input
50v and external drivers. Now I’m just imagining someone using NEMA 34s at 48v and have the core knock off a YZ plate and send the core flying without any skipped steps.

50v and external drivers. Now I’m just imagining someone using NEMA 34s at 48v and have the core knock off a YZ plate and send the core flying without any skipped steps.
You know it will happen eventually.
I was just poking at all the components and realized they all seem to be 50V rated, on the high side at least. I need to check but I remember Bart asking me about this, I swear there was a capacitor or something that needs to be swapped.
Public service announcement - I have 100% made some that are not 48V ready. I have swapped the regulator a few times when inventory ran out at LCSC. So do not test this unless you know what regulator you have.
As someone else mentioned it appears that SG_Val is very speed dependent. At just 500mm/min it hovers around 100. At SG_Setting 15 a stall is triggering 1/4in bit 1/4in depth at 500mm/min and up. Increasing SG_setting to 30 appeared to make no difference, still stalled quickly. At some point you would think you could set SG_setting so high that it would effectively be turned off but I don’t know.
Obviously, this is just for my material
1/4 bit 1/8 depth 500, 1000,1500,2000,2500,3000,3500mm/min no stall SG Setting 15
1/4 bit 1/4 depth, 500+ stalls SG Setting 15, 30

I think the TMC2209s are 3.3v while most external drivers are 5v
Most 5V circuits will tolerate 3.3V input for digital circuits. 3.3V is greater than 2.5V, so it considers it a high signal. The reverse is less often true. Sending 5V into a 3.3V circuit could release the magic smoke.
But fast electronics, like ws2815 leds, need 5V. Otherwise, it doesn’t reach the threshold fast enough.
An easy test or workaround is to use a logic level converter. A breakout board logic level converter is pretty cheap.
I think I have a spare external driver here I could try at some point, but
Could you not just skip this pin and use one of the 5V pins, and still use the regular step, dir, enable pins?

Could you not just skip this pin and use one of the 5V pins, and still use the regular step, dir, enable pins?
Jackpot is missing ESD protection for external drivers. That’s why I stopped working on my test setup and started playing with the Boxer board.
ESD protectoin for the expansion headers and maybe these stepper signals if we bring them out should be something we’re thinking about.

ESD protectoin for the expansion headers and maybe these stepper signals if we bring them out should be something we’re thinking about.
Ahhhhh, okay that makes more sense. Felt weird for it to be so simple.
Since I am poking around in the Jackpot I think I am going to start a new thread with some EE and jackpot NG related questions if you guys wanna help me out.
External drivers are supplied with their own power supply ideally anyway. So you’ve got a small 24V for the board and an 36 or 48 for the stepper drivers.
Also, external drivers use 5V logic (or 24 for closed loop, but that’s rarely used).

As someone else mentioned it appears that SG_Val is very speed dependent. At just 500mm/min it hovers around 100. At SG_Setting 15 a stall is triggering 1/4in bit 1/4in depth at 500mm/min and up. Increasing SG_setting to 30 appeared to make no difference, still stalled quickly. At some point you would think you could set SG_setting so high that it would effectively be turned off but I don’t know.
If this is the case there is no safe way to use it for any real meaningful safety. Either this is not true or it just is not implemented all the way or incorrectly in the firmware? I know these drivers have a ton of features that are not used in most firmware so they are probably not been even close to fully tested.
I didn’t hit a stall trigger at 1/8 depth. At 1/4 I can tell the router is stressed so it makes sense that it is kicking in. This isn’t an ideal bit, 1/4 compression 2 flute. I need to mess with the value more and the home speed. According to the code it calculates a lot based on the homing speed.
An entire surfacing pass it never kicked in, except when vectors gcode generator put a -20 X at the start for some reason and crashed into X min. Then it kicked in and stopped the grind