Overbraid Datatable

[ruhall04]

What is the proper way to set up an overbraid datatable?  I am trying to add overbraid to various types of pre-defined cables and I keep getting errors when I try to export the design to xml.

I'm not sure where I have gone wrong and I can't find any examples of overbraid datatables.

[ajoler]

Overbraids do not need Datasets.  The only time an Overbraid needs a Dataset is if you run a shield off of the Overbraid, then you only need to apply a dataset to that Shield or Drain Wire.

[BranDune11]

Why would you not make a datatable for an overbraid? If a dataset is applied to an overbraid you don't have to type in all the properties for a heat shrink, snakeskin or spiral wrap everytime you use one in your design.  I only mention this because I am in the middle of making one right now and I would like to re-start discussions on this topic.

[ajoler]

The purpose of the Overbraid (as I understand it) is just to group all of the Wire & Cables together as 1 bundle.  So instead of creating many different datasets for every possible combination, you simply create a new cable as an overbraid and all of the wires/cables will be included in it.  RSD does not require a dataset for an Overbraid.  When you export your XML and you verify it, it will be fine.  If you add a drain (shield) wire to the Overbraid, this single wire will need a dataset.  This will be included in your Physical routing, so do not make the diameter of this wire the actual diameter of the sleeving that goes over all of the wires and cables, make this diameter closer to the thickness of the sleeving so your overall bundle is not too large.

[BranDune11]

My intention for using overbraid is mostly for drawing purposes.  My habit is to create a model with everything required to populate a complete parts list and live balloons for harness production.  Unfortunately I have discovered that cabling features(e.g. Markers, Tape, Overbraid...) cannot be refered to in a repeat region. So maybe bundling is good enough for graphical representations and just use bulk items in my table, but if I do have the overbraid in my logical info(.xml), or model tree, it will be there for reference.
I just think the central catalog should include everthing needed to get a complete schematic without a lot of input from the user.  It all starts here in RSD and it makes it much more efficient to get it all here and show it in cabling automatically.