LowRider v3 CNC - Tramming & Squaring with Jackpot controller
ฝัง
- เผยแพร่เมื่อ 9 ก.พ. 2025
- For more on use of the Jackpot controller with a LowRider v3 CNC, watch these other short videos:
• LowRider v3 CNC with J...
• LowRider v3 CNC with J...
• LowRider v3 CNC - Squa...
For more on squaring (for either a Jackpot or a Marlin based board), and how software-based "pull off" is done on Marlin-based controller boards, watch this video:
• LowRider 3 CNC - check...
Buy the Jackpot controller board from V1 Engineering here:
www.v1e.com/pr...
Buy the Tiny Touchplate (for probing) from V1 Engineering here:
www.v1e.com/pr...
Download the printable "magnetic tip for touch plate wire" (v1.0) for CNC machines here:
www.printables...
V1E's documentation for the Jackpot board is available here:
docs.v1e.com/e...
...and if you search that page for instances of the word "probe" you will see several mentions. Among them is the fact that a probe routine is present in the "Lowrider Starting Gcode" - which by the way, if you have probing scripted in that way, the gcode outputted by whichever CAM software you use (ESTLcam etc) will account for probing as part of each job. The "Lowrider Starting Gcode" is below, and it can be used for creating your own Probe Macro button on the Jackpot. Below, I have added "remarks" (commented out so they don't get acted on) to explain what the result of each gcode command would be:
G21 ; (assume part programs are Metric, as opposed to Imperial, which would have been G20.)
G90 ; (absolute positioning, as opposed to incremental, which would have been G91.)
G94 ; (interpret feed commands as inches/min or mm/min for linear moves.)
G92 X0 Y0 ; (set current position to values specified - and there are other code options for this.)
M0 (MSG Attach probe) ; (issue a message to operator to attach probe.)
G38.2 Z-80 F200 P0.5 ; (probe down to get thickness, allowing 80mm travel, speed 200, plate thickness 0.5 mm.)
G1 Z10 F900 ; (move upward in Z axis by 10mm at a speed of 900)
M0 (MSG Remove probe) ; (issue a message to operator to remove probe.)
M62 P1 (If used start spindle pin27 )
For clarity and convenience, I'm using my Jackpot with hard limits enabled and soft limits enabled, and my table size included in my config.yaml file, and the following is the exact script I'm using for my Probe macro (except I have the M0 commands commented out by starting those lines with a semi-colon, and I also don't use the last line for spindle start):
G21 (MSG G21: Metric mode)
G90 (MSG G90: Switching to absolute positioning)
G94 (MSG G94: Feed = per minute)
G92 X0 Y0 (MSG G92: Setting current XY position as workspace origin 0,0)
M0 (MSG Attach probe)
G38.2 G91 Z-124.9 F400 (MSG G38.2: Fast probing to material)
G1 Z5 F400 (MSG G1 move Z up by 5mm, speed 400)
G38.2 G91 Z-6 F100 P0.34 (MSG G38.2: Slow probing to material. Plate thickness: 0.34)
G90 (MSG G90: Switching to absolute positioning)
G1 Z30 F900 (MSG G1: go to Z30, speed 900)
M0 (MSG Remove probe)
M62 P1 (If used start spindle pin27)
A huge "shout out" and thank-you to Ryan Zeller @vicious1 over at V1 Engineering Inc, and all the helpful crew at the V1E forum! Also to Bart Dring & Mitch Bradley & BrianD & Michael Melancon of the Fluid NC dev team!
Your videos are pacing my build perfectly😂
Cool!
Another informative and timely video...tomorrow i was going to tackle this...now i know exactly what to do. Thanks again
Glad to be a help!
I have been so much happier with this Jackpot board. I am in the process of changing out the Makita Router to the Kobalt Router.
Thanks for watching and I hope you enjoy your machine!
@@design8studio also I am really impressed with the dust show you came up with as well, I did make a small modification to it, my shoe kept on sliding off. So I put a boot through both the mount and shoe. Next I am going try your unistrut mod.
Thank you for all of your great work!
@@ronaldmckenzie1 I put some strips of ultra high molecular weight tape (amzn.to/3TQ0USh) onto the shoe mount area where the dust shoe slides on, to get a tighter fit...I have been thinking about two possible improvements to the floating Z dust shoe: a "click and lock" way to keep the shoe on, and a set of one or more marbles or large ball bearings or printed globes on the bottom of the shoe, to let it "sled" higher up without the bristles being crushed, and with less resistance. I will probably tackle it one day soon. Have too much going on.
How do you find and set the hard and soft limits for your table? I am having trouble finding information on this. I assume it prevents crashes at the extremes.
The way I did it was to home my machine, zero out at the homed location, then move (jog) to the X max and Y max extremes, and carefully note how far I could go before making contact, then back off from that just a smidge, and see what the values are. Then, after saving a backup copy of your config,YAML file, edit the config file and input those values into the max_travel_mm value per axis. Then, also per axis, enable soft limits. I used to also enable hard limits, but unless you have limit switches on both sides and end stops at both ends, you’re not going to get a hard stop limit action at both ends, And I actually had my dust hose get against a limit switch blade during movement and it made the machine instantly and needlessly halt because it thought a hard stop had been reached and threw an alarm. So I no longer have hard stops enabled. But all this is done in the config file. Then connect and upload your new config file. Reboot. Then test and adjust if needed. You can also do Z, I do. It’s a little different. I guess you would remove the bit from the router and find how much the travel you have, enable soft limit to prevent crashes at the max location.
LOL, i was just doing this the manual way with a vernier, but I like this much better. But just a comment, if you look under FluidNC tab, then under the "config items" radio buttons just under the restart and other buttons, the pull-off is also listed there for each axis
Cool. Good to learn!
can you run Nema23 steppers with the provided TMC 2209 Drivers on the Jackpot controller ?
This (or something very similar to it) was asked and answered on the V1E.com forum: “You can use TMC 2209 drivers with your NEMA 23 steppers, but it is likely the NEMA 23 steppers could take significantly more current than the TMC 2209 can provide, largely negating the reason to go to NEMA 23 steppers in the first place. Stepper drivers limit the current going to the stepper motor.” forum.v1e.com/t/nema-23-vs-nema-17-for-z-axis/34157
Our NEMA17 steppers are quite powerful and commonly used for LowRider builds.
Hey Doug, recently i saw a CNC Router with a Diode Laser attachment. Curious if you did something like that in one of your videos
A lot of guys on the V1E forum have put diode lasers on their LowRider CNC. I have plans to add one to mine, but I haven’t gotten to that point yet.
Hi Doug, is there a way to check what offset I have already saved on SKR? Also if I save an offset twice will the original offset number be overwritten or will it add the two inputted offsets that have been entered, thanks!
These would be good questions to pose on the V1E forum. It’s been a long time since I used the SKR, which uses the Marlin firmware. I’ve been using the Jackpot board, which uses FluidNC firmware, for a while now. So we need to get help from someone who is either an expert with Marlin, or has a very good memory.
Jackpot ? FluidNC? What is the difference? Is there any explanantion about this? :) thanks
Jackpot is hardware (main board) and FluidNC is the firmware that runs on it. The Jackpot controller board can be ordered from V1 Engineering here: www.v1e.com/products/jackpot-cnc-controller?_pos=1&_psq=jack&_ss=e&_v=1.0 - and the docs for it are here: docs.v1e.com/electronics/jackpot/ (and from there you can get into docs about FluidNC).
Thank you :)@@design8studio
Thank you :)@@design8studio
So I'm using your script, but for some reason my Jackpot is not giving me a 'PRB' Value. It's giving me a 'Hold' value. Am I missing something here in the gcode?
I'm not sure what's going on there. If you are looking at the right place in the console's feedback, then it may be that some difference in the firmware version affects the formatting of the output. I can scarcely imagine any valid reason for describing a probe value as a hold value.??
@ I just DM’d you on the V1E forum with a screenshot. Maybe you can see something I don’t.