Import A Cut List
-
Once you have all these groups in SketchUp are you planning to then assemble the parts into a cabinet or something?
-
Yes indeed, and also detect if anything is programmed wrong.
-
I see. Well, maybe one of our resident Ruby gurus will come up with something for. I must say I'm happy I don't have to build SketchUp models that way. It's a lot of work rearranging the parts. It makes me wonder if it might not be more efficient to build the model from Scratch in SketchUp and export a cutlist you could compare to the one from Cut Rite. I'm thinking with a few overall dimensions, you could model a cabinet pretty quickly.
-
Well Dave, I do most of my models from scratch, and I make them to dynamic components as well, but I have some old Cut Rite programs with lots of parts and would like to review them in SU.
-
Understood.
-
@vigy said:
Steve, thanks for your response!
My priority is to have simple rectangular boards, but I never wrote anything in Ruby so it's not that simple for me. and yes it would be nice to have them separated (I didn't want to complicate things)
Victor
I'll take a shot at it when I get a chance. Do you have a sample file you could upload?
Steve
-
-
@vigy said:
Hi Steve,
Attached a sample.
Thanks so much, Victor
Hi Victor,
Give the attached a try and let me know what happens. Put the rb file into your Plugins folder. It should add an item named "Import Cut List" to the Plugins menu in SketchUp.
This is written to import a csv, not an xlsx, so you will need to save your cut list that way first. xlxs is just way messier than csv, so I took the easy way.
This creates Components, not Groups, and spaces ComponentInstances out along the green (y) axis. I found that piling them all at the origin was hopelessly messy!
This ignores the material field (because there is not enough info to create a material). It also generates only quantity 1 of each part, though that could be changed fairly easily. All your examples were on Layer0, so I didn't co anything to create layers or place things on them. That also could be changed easily enough.
Steve
-
OOOH WOW! This is wonderful Steve, and it work great. Thanks a million!
As you mention, material not needed but layers would be nice if I'm allowed to have audacity to do so.
-
@vigy said:
OOOH WOW! This is wonderful Steve, and it work great. Thanks a million!
As you mention, material not needed but layers would be nice if I'm allowed to have audacity to do so. Try this one! It should handle layers (I hope
)Another word of warning: For simplicity, I didn't process the header line to find out what is in which column, so if you rearrange things this plugin will fail in strange ways!
Steve
-
Well, you wouldn't need to import anything into the model. The imported components could populate the Components dialog for manual placement after the import.
-
@jim said:
Well, you wouldn't need to import anything into the model. The imported components could populate the Components dialog for manual placement after the import.
True! That would handle cases with quantity greater than one too - just pull out however many you need (you can do that with my version too, since the components are there). I just followed the workflow Vigy requested.
Steve
-
Steve, It all work very well
Thanks Again!Victor
Advertisement