4

My employer has had me create a model of a vendor product (using OnShape) and make a simple drawing with some overall dimensions that we can hand to customers. However, they want to include the firmware revision of this product in the drawing. I'm not sure how often this firmware will update, but the plan is to eventually buy the chip from the vendor and load it with our own firmware. I've done a lot of solid modeling, but actually have very little drawing/drafting experience. Wondering what best practice is?

My initial thought was to add a revision table with firmware version + date changed, but that could potentially balloon beyond control. The next idea I had was to rely on onshape's version history. Just create a note of the firmware revision number, then update the note and release a new revision every time it increments.

As I've thought about it, it really doesn't make sense to track the firmware in a mechanical drawing, but they're pretty adamant about this (most of them are electrical engineers, I'm the only mechanical - none of us know what we're doing)

Thanks for any advice!

Optimum
  • 141
  • 3

1 Answers1

3

Add the revision table, but make it a rolling table with e.g. max 5-10 rows, or whatever fits neatly on your drawing, where the oldest information gets pushed off the bottom/top of the table once it's full.

It's OK for the latest drawing to not show a full history of all firmware changes, as long as its easy to find an older drawing that has that information on, if you need it.

Jonathan R Swift
  • 7,811
  • 1
  • 16
  • 30