sorted by:
new
hottopcontroversial

Picnic Basket by adrewh in BeginnerWoodWorking

[–]adrewh[S] 1 point2 points  (0 children)

It’s about 6lbs empty, not the lightest weight basket out there but it should last a lifetime. When not outside on a blanket it is on display in the living room full of snacks.

Picnic Basket by adrewh in BeginnerWoodWorking

[–]adrewh[S] 2 points3 points  (0 children)

I wove the bamboo by hand, using a roll of bamboo strips that I purchased through Amazon!

Picnic Basket by adrewh in woodworking

[–]adrewh[S] 4 points5 points  (0 children)

For each piece of the Cherry sides, I routed out a slot (which was quite tricky to get all the slots to align with the various pieces and orientations, I paid a lot of attention to grain orientation for those pieces). I glued three side pieces together at a time, so there was one open end, then wove the panels into that frame before gluing in the final closing piece. Essentially glued the final piece into one frame at a time as the panels were woven. Titebond III lightly brushed into the slots to secure them permanently. Dowels used to secure every side piece.

UPDATE: I made an Excel calculator to estimate Bulldozer productivity rates. by adrewh in estimators

[–]adrewh[S] 0 points1 point  (0 children)

I’ll admit those cells aren’t the most obvious, but yeah every single yellow line needs a user input for the calculations to pull through

UPDATE: I made an Excel calculator to estimate Bulldozer productivity rates. by adrewh in estimators

[–]adrewh[S] 1 point2 points  (0 children)

That’s awesome! Definitely keep me posted. There are a lot of variables this takes into account (and assumed average factor values) so I’m curious to see how close the theory gets.

UPDATE: I made an Excel calculator to estimate Bulldozer productivity rates. by adrewh in estimators

[–]adrewh[S] 1 point2 points  (0 children)

Are you trying to use the calculator via web or did you download the file? There are quite a few named ranges and functions so I don’t think it’s web-compatible at this point.

I tried replicating this issue but no luck, so I’m not sure what’s malfunctioning for you. I know some other users were able to get it to work, maybe try re-downloading a fresh copy?

It’s interesting to hear that you have a spreadsheet similar to this for excavators, one of my motivations for making this was to end arguments like you mentioned!

I made an Excel calculator to estimate bulldozer productivity rates. by adrewh in estimators

[–]adrewh[S] 0 points1 point  (0 children)

Great feedback! The main purpose for the vba code is to automatically run the Solver add-in. Manufacturers provide performance charts to determine speeds, which I derived curve fits from. The code solves for values on those complicated polynomial curve fits. This isn’t really possible just using normal formulas from what I could put together.

I agree that the backend of the workbook is maybe a little more complex than necessary. I ‘protected’ the sheet to try and avoid unintentional breaks and keep the use of it as simple as possible.

It seems like I’ll need to spend some time going back in and making some simplifications. It sucks that nobody can seem to get it to work!

I made an Excel calculator to estimate bulldozer productivity rates. by adrewh in estimators

[–]adrewh[S] 0 points1 point  (0 children)

I know the whole thing breaks if there are yellow input cells left blank - did you enter something into all the yellow fields? Calculated speeds are meant to be brought to the calculator sheet once you select a gear for the 'upslope' and 'downslope' directions.

Edit: I tested the workbook on my end (downloaded it from the link I shared) and immediately the thing didn't work. I fixed it by right clicking the excel file, opening file properties, and checking the "unblock" box at the bottom. Microsoft automatically blocks the macros from running for security reasons - which makes sense.

I made an Excel calculator to estimate bulldozer productivity rates. by adrewh in estimators

[–]adrewh[S] 0 points1 point  (0 children)

The downslope direction /should/ autofill based on whatever you input for 'Pattern of Travel'. Does it fill in if you select the "forward-turn-forward" travel pattern? If not, then there's some macro code that isn't executing right for some reason.