Ummm, speaking of "on your toes", the jaguar_main_enclosure.prt is still not so nice to deal with. Not really a fan of totally imported geometry, but the fact that it doesn't have default datums or views is what really bugs me.
The color and weight is nice though
Hi Dan. The link has been updated on www.ptc.com/go/firstkop. Sorry for the confusion. Your team and the rest of the FRC teams will be able to download the latest kit and field. Good luck teams. Regards, Mark
Did you find a good way to upload the KOP and KOF into ProjectLink? I've only used Pro/E with PDMLink. Doesn't seem to be a good way to import the files to a workspace then check-in. What did you end up doing? I know for assemblies, you can bring them up in Pro, then add to workspace and check in, but what about all the other kit parts? Seems like a lot of clicking and no way to maintain the directory structures.
I don't remember how it got done last year and I haven't dug into it yet today.
I could have sworn I imported a zip file and it extracted everything to the folders defined in the zip. It wasn't working the last time I tried though.
Our challenge is that we have about 3 previous seasons' worth of data and there are naming conflicts. The biggest question is whether some of those things already there have been corrected or not. I was reviewing the quality of the PTC models to see if I could blindly overwrite what I already had, but it's starting to look like that won't be such a great idea.
Hi Dan and Josh,
The best method to check them in is via Creo Elements/Pro. While there are a lot of parts....you can open them and save them to the workspace. Then check in the whole workspace to a specific folder. This will also create the viewable version so you can see it in Creo Elements/View.
For the AndyMark models....you can try to open the 2011_c-base_long_with_wheels.asm or 2011_c-base_wide_with_wheels.asm. This is a predefined assembly of the models (most of them). This will help versus opening each one independently.
As for the field....you can open the master assembly and save that.
I realize you have a number of years worth of data in one project. If interested, we can create a new project for your team and you can maintain both. The nice thing is you can copy and paste between them.
If you would like a new project, let us know.
That does sound like the method I had used last year. In the back of my mind I'm still thinking there was a method I had used before to input data and create folder structures in one step (sometimes I get a little carried away with my imagination though! ).
For a moment, you had me thinking that we had a way to import a folder structure of CAD documents in one step, but then I remembered that import is in the workspace.
I agree that what you imagined sure would be slick.
Please see the attached document for a method of importing multiple documents to your workspace.
Much easier than the Pro/E interface, but still requires that it be uploaded to a ProjectLink Workspace.
Yep, that's it. I can't link a session from here at work so I'll have to wait till I get home to try this. I was hoping there was a "Pro/E Free" way to do this. Thanks, Dan
We've had this issue as well, having 2007, 2009 and 2010 robots on our project. What we did to correct the conflicts was name everything with the year leading the name.
This also made it easy to sort through our workspaces. Puts the robot at the top, and off the shelf parts that you will not be modifying at the bottom of the workspace list.
Thanks for the input Rob. That's a good approach.
I'm thinking of just going with the second project though. We have so data from training, etc. that it might be worth it to clean things up and start with a clean slate.
I will be uploading a new Kit of Parts and Field Kit this week. This new kits will address a number of identified issues - naming convention, family tables.
Please take a look at the new kits. I will let you know when they are uploaded.
There are a lot of fully-featured parts in the KOP, but not all of them. Things like the Jaguar are imported neutral files. It seems kind of random what's an imported neutral and what is a fully-featured native Pro/E model.
We have debated this many times at PTC and come to the decision that we only create native Pro/E models for the items students will be modifying. For instance, it is highly unlikely that anyone will need to make changes to a Jaguar, a pressure switch or the power distribution board. Since these objects are simply "placed" in an assembly, there is no point in creating native models for them. If there are specific objects that are import geometry now and you would like to have them converted to native, feature based models, please let us know.
Not trying to modify a Jaguar... had a student try to modify the Andy Mark frame components... All we get in the model tree is "Import Feature id 68." Sure, we can add sketches to the model and extrude/cut. So I guess I shouldn't have asked the question.