CNC-cut table for LowRider v3 (parameterized, for cutting full sheets+)

Since the Fusion file is designed to be driven by parameters, it should be doable to edit the params to change the size. The two params in focus here are:

PARAM NAME UNIT EXPRESSION VALUE COMMENTS
Width_Cut_Size_X in 49 49 AKA width of MDF TopSkin. Default 49" which is width of a full sheet of MDF that’s 49" x 97" (one inch wider and longer than 4’ x 8’ full sheet)
Length_Cut_Size_Y in 97 97 AKA length of MDF TopSkin. Default 97" which is length of a full sheet of MDF that’s 49" x 97" (one inch wider and longer than 4’ x 8’ full sheet)

Couple of thoughts:

49" x 97" = 1244.6 x 2463.8 mm

1220 x 610 mm = 48.0315" x 24.0157"

If you change Width_Cut_Size_X to 48", and change Length_Cut_Size_Y to 24"…

…you get this result, which needs at least 4+ steps taken (see below) to be a “whole” design makeover.

Below are the steps, but first …

A. Some of the steps are needed simply because in Fusion 360, the “move” steps in the timeline history seem to not be parameter driven, despite a parameter having been used in the original move. This is disappointing, and I don’t yet know of a fix, so manual additional “moves” are the workaround.

B. For the other steps (not related to moves) this tells me I need to revise how the params interact with each other to get better functionality.

C. A key question here is: do you indeed want the X-gantry on the 48" axis? If not, you would want a variation of this design that has a LowRider v3 on only a 24" wide X-axis, which is doable I suppose. That would require flipping the values in the two params above, and it would alter the fix steps below.

Steps needed to fully implement this design change:

1. Edit the param named “Pattern_Interval_Max_Between_Torsion_X_Ribs_On_Center” to change the “/7” part (which yields 7 X-ribs) to some lower number, perhaps “/3.”

BEFORE:


AFTER:


2. two of the sketches made for exporting DXFs, lose their plane of reference. One is “Sketch3 LR3 Riding Plate, X-min for DXF” and the other is “Sketch3 LR3 Riding Plate, X-max for DXF” — there is an easy fix. In the timeline history, you right click on a sketch that’s lost its plane of reference, and choose “Redefine Sketch Plane” — and note that a visual cue for which plane is discernible because clicking on the sketch icon in the timeline history highlights the sketch itself, which is laying on the face of the “body” that is the plane that it needs connected to again. See screen shots for me making this fix for “Sketch3 LR3 Riding Plate, X-min for DXF”:

Screen Shot 2023-04-18 at 2.41.18 PM

… I then repeated for the other side, “Sketch3 LR3 Riding Plate, X-max for DXF.”

3. While the slot cuts in the X-ribs (for the Y spars to fit in) seem to have shifted appropriately (yay to me), the location of the Y spars themselves did not appropriately shift (boo to F360).

As seen here:

and here:

…This needs fixed by moving the first one, and having that movement be in the timeline prior to the pattern step that “repeats” the one on the left to create the other Y-spar bodies. :slight_smile:

To measure the distance by which the one on the left needs moved, press the “i” hotkey, and click on the lines as shown, letting us know it’s off by 0.5". This make sense, since we shortened the usable width by 1" — and that 1" gets divided “by 2” (i.e. on both sides of the table).

… And finally, to fix that,

…first activate the component named “Main Y Spars” by hovering over its name:

Screen Shot 2023-04-18 at 2.54.12 PM

…and then clicking the radio button that appears:

Screen Shot 2023-04-18 at 2.52.36 PM

…Note that this will give a filtered timeline history that shows only history steps related to this component:

Screen Shot 2023-04-18 at 2.55.53 PM

And the “move” icon in that history can be right-clicked and edited to input 0.5"

— note that for some reason (i.e. in F360 the move steps seem to not be parameter driven, despite a parameter having been used in the original move.), the previous move’s distance parameter is not shown as an editable bit of history. Any new inputs are seen as in relation to zero at the current location, and the new move results in a “cumulative” move distance, in which the newly inputted amount results in a new move based on the current location. I am disappointed that this is how F360 seems to work, and it’s the reason I have not yet figured out a way to avoid such move “fixes.”

4. This step is similar to #3 step above, but this time activating the component named “Minor Y Spars for Extensions” in order to move the two bodies named “Body20 Minor Y Max Flange” and “Body20 Minor Y Max Flange (1)”. This distance by which they are now off is 73". (Used “i” hotkey to measure.) A difference here, is that these flanges being out of place seems due to a sketch element (somehow) not honoring the change in params, despite the fact that the rest of the “Minor Y Spar” elements changed as desired. This means the flanges being out of place is due to a sketch issue, and not due to the “moves in history are not parameterized” issue. Bottom line: there is no “move” icon in the history to edit. Simply highlight the two bodies, press the “m” hotkey" and input the 73" in the right direction (in this case negative, so -73").

BEFORE:

Highlight the two bodies:

Input -73:

and…

AFTER:

Now, the good news is that I did all these steps as I went, so I can now save a copy and provide it for you. I will probably make a new post with that attached. If so, I will edit this post to add the link.

1 Like

In relation to my last post, above, did you indeed want the X-gantry on the 48" axis?

If so, I can save a copy of my steps to produce it. If not, I could redo the fixes, with the values in the two top params flipped.

@vicious1

Was just working to improve the parameters and the resulting functionality, and wished for a way to export / import params. Found this “app” for doing so:

Worked a treat. Linking both for record here and in case it helps (if you don’t already have something like it).

Interesting, that might actually help with sub assemblies. That is Solidworks default behavior, it looks for a sheet when it builds. More of what I am used to.

1 Like

I wanted to search for all expressions (aka formulas) where a certain param was being used. Opening the list in Excel made it easy to do!

1 Like

For more parametric CNC-cut tables for LowRider v3 (full sheet+): 3.625", 6", and 8" tall versions — click here: More parametric CNC-cut tables for LowRider v3 (full sheet+): 3.625", 6", and 8" tall versions

Thanks, that’s all great help.

Re the brace differences, I was more talking along the Y-axis and slotting together rather than lots of screws.

Re the rail widths, I did look at that and was a touch concerned about going wider towards the centre of the table and potential clearance issues with the vac shield etc but it looks like 10-20mm would be safe.

Re the metric conversion, I was able to change the units with ease by right clicking on the document settings and changing to mm which worked fine for overall dimensions. but when I tried to adjust the values in the change parameters section to match local material thickness etc is where I ran into issues as that all stays as inches, my work around was to convert my figures to inches but it seemed to create rounding errors so when checking final dimensions things like overall width weren’t whole numbers. (Im pretty green when it comes to fusion360 so this could be 100% user error)

1 Like

Hey, regarding the steps I mentioned before… I had made a newer version of the table that has its parameters interacting with one another a little bit better. So I whipped out two more versions of the table, one at 24" x 48" and one at 48" x 24" — here’s the download link:

For two more parametric CNC-cut tables for LowRider v3 — click here: Two more parametric CNC-cut tables for LowRider v3 — 24"X48" and 48"x24" versions, at 3.625” tall

1 Like

I think i broke your f360 file lol. Was trying to see if a 2meters wide torsion box was posible

Hi Doug,

I didn’t have time to read your post until now. I´m not sure about the X-gantry on the 48" axis.

It seems like this is not recommended?

Thank you for the steps. I don’t have a router yet so I think I’ll build a table that can cut the struts in the Y-axis

If you wanted to build a wide X with a short Y, because of planning a long Y later… it’s not a bad way to go. But unless you have a reason like that, putting the X gantry on the shorter axis has a little better rigidity. I made table versions going either way:

For two more parametric CNC-cut tables for LowRider v3 — click here: Two more parametric CNC-cut tables for LowRider v3 — 24"X48" and 48"x24" versions, at 3.625” tall

1 Like

Hi Doug,

I have my tubes cut at 1400 mm and a wide X and a short Y is what I can make room for right now.

I don’t have Fusion 360 yet. How much material would a wide X and a short Y take?

I am not sure if the belt moving towards me (wide X) is easier to use?

If you begin with the 8" tall version I posted here: More parametric CNC-cut tables for LowRider v3 (full sheet+): 3.625", 6", and 8" tall versions

… It widens to 2 meters with only two quick fixes needed.

Here’s a Fusion 360 file I’ve done that to:

CNC Table for LR3, WOOD RAIL, v2, 78.74’ x 97’', 8in tall (v6).f3d.zip (504.4 KB)

There are 2 major reasons why it is recommended to make the X axis your shorter one.

  1. The beam is the weaker link. While the brace and rail structure is strong against sag, it can twist, resulting in dimensional inaccuracy.

  2. If you plan to cut the strut plate on the machine, the X axis is definitionally not long enough to do it. You need a Y axis longer than X in order to be able to cut the struts on your machine without tiling.

I was thinking about strategies to tile the strut plates, and it’s kind of tricky. The best I could come up with is to use the holes for the bolts, but bootstrapping that is troublesome. Alternately using the machine to cut blocks to position a strut cut to width on a table saw with an index for position could work. It isn’t that there aren’t ways, but I like to try to let the machine provide the accuracy rather than have it manual.

2 Likes

Re: tubes:

My plan that can cut to the very edges of a 49" wide MDF sheet calls for X-tube length of 56.102362". So, with your X-tube length at 55.11811", you’ll be able to cut a full 48" wide sheet, maybe a tad more.

Re: “How much material would a wide X and a short Y take?”

I have not had time to calculate that. Will try to do it over time.

Re: “I am not sure if the belt moving towards me (wide X) is easier to use”

It’s really up to your preference.

I think my biggest issue at the moment is that I lack a preference since all this is new to me!

I was only asking about material since in your thread with 3",6" and 8" tall tables you had that in there.

How would you compare the 3", 6" and 8" tables? Is 6" a good middleground?

I know the shorter one (3.625" version) can have its torsion box cut out of a single sheet. I know that any taller than that and it spills over to another sheet. Quick guess-timate, I’d suspect two sheets would do it.

Yes, I would expect the 6" to be a good middleground.

This basically means that my Y-axis has to be atleast 1400 mm usuable working area?

The thicker the torsion box the stronger the table. If it is just going to hold material for cutting, any thickness is more than enough. If you plan on using it for other uses that will carry weight, like an assembly table, thicker is nice.

More ribs is also equivalent to a thicker table.

If you want a 1400mmX strut plate yes.

2 Likes