{"id":2143,"date":"2019-03-17T08:00:00","date_gmt":"2019-03-17T07:00:00","guid":{"rendered":"https:\/\/camilion.dms3labs.cat\/2019\/03\/17\/autocad-bind-mode-explained\/"},"modified":"2024-02-14T17:02:01","modified_gmt":"2024-02-14T16:02:01","slug":"autocad-bind-mode-explained","status":"publish","type":"post","link":"https:\/\/camilion.eu\/es\/2019\/03\/17\/autocad-bind-mode-explained\/","title":{"rendered":"AutoCAD: bind mode explained"},"content":{"rendered":"<p>As expert users of <a href=\"https:\/\/autodesk.com\" target=\"_blank\" rel=\"noopener\">Autodesk\u00ae<\/a> software like <a href=\"https:\/\/www.autodesk.com\/products\/autocad\/overview\" target=\"_blank\" rel=\"noopener\">AutoCAD\u00ae<\/a>,<br \/>\nwe sometimes receive very specific questions or requests from our clients.<\/p>\n<p>One of the most recent ones has been related to external reference management and<br \/>\nthe differences between the <code>bind<\/code> modes in <a href=\"https:\/\/www.autodesk.com\/products\/autocad\/overview\" target=\"_blank\" rel=\"noopener\">AutoCAD<\/a> software, particularly,<br \/>\nhow one of <a href=\"https:\/\/camilion.eu\/en\/apps\/\">our apps<\/a>: <a href=\"https:\/\/camilion.eu\/en\/apps\/RefMan\/\">RefMan<\/a> interacts with that.<\/p>\n<p>When we discovered that the problem of our client came from a lack of understanding of the process,<br \/>\nwe decided to document it and explain it for whoever is interested.<\/p>\n<h2 id=\"what-is-bind\">What is <code>bind<\/code>?<\/h2>\n<p>When working with  <a href=\"https:\/\/www.autodesk.com\/products\/autocad\/overview\" target=\"_blank\" rel=\"noopener\">AutoCAD<\/a> software in major projects, using external references is mandatory  for correct workload distribution and to avoid information duplication.<\/p>\n<p>Unfortunately, even to this day external references are frowned upon for several reasons.<br \/>\nFor example: the drawing has to be exported to a software that doesn&rsquo;t support external references, the project&rsquo;s contractual terms specifies that external references may not be used, contractors ask for a single file, etc.<\/p>\n<p>To get the best of both worlds, it&rsquo;s possible to work with external references and prior to handing the work over to the next phase we can perform a <code>bind<\/code> of all external references in order to have all the graphical information in one single DWG file.<\/p>\n<blockquote>\n<p><a href=\"https:\/\/camilion.eu\/en\/apps\/RefMan\/\">RefMan<\/a> can handle this process seamlessly for<br \/>\nhundreds or thousands DWG files.<br \/>\nTo know more about this process, <a href=\"https:\/\/camilion.eu\/en\/blog\/2019-autocad-refman-1000-bind\/\">read this article<\/a>.<\/p>\n<\/blockquote>\n<h2 id=\"graphical-example\">Graphical example<\/h2>\n<p>To aid us in the explanation, we are going to generate a fairly easy example. The working files can be <a href=\"https:\/\/camilion.eu\/en\/blog\/2019-autocad-bind-mode\/RefMan_Bind_Insert.zip\">found here<\/a>.<\/p>\n<p>In this example, there are two references (<code>Ref1<\/code> y <code>Ref2<\/code>) and a drawing (<code>Dibuix<\/code>).<\/p>\n<table>\n<thead>\n<tr>\n<th>Ref1<\/th>\n<th>Ref2<\/th>\n<th>Montaje<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><img decoding=\"async\" alt=\"Referencia &quot;Ref1&quot;\" src=\"Ref1.png\" title=\"\"><\/td>\n<td><img decoding=\"async\" alt=\"Referencia &quot;Ref2&quot;\" src=\"Ref2.png\" title=\"\"><\/td>\n<td><img decoding=\"async\" alt=\"Montaje &quot;Dibuix&quot;\" src=\"https:\/\/camilion.eu\/wp-content\/uploads\/2024\/02\/Dibuix.png\" title=\"\"><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3 id=\"layers-structure\">Layers structure<\/h3>\n<p>In the drawing the two references are inserted, each reference has a <code>Layer<\/code> with different visibility and colour properties.<\/p>\n<p><img decoding=\"async\" alt=\"Dibuix_layers\" src=\"https:\/\/camilion.eu\/wp-content\/uploads\/2024\/02\/Dibuix_layers.png\" title=\"\"><\/p>\n<p>It&rsquo;s worth mentioning that <a href=\"https:\/\/www.autodesk.com\/products\/autocad\/overview\" target=\"_blank\" rel=\"noopener\">AutoCAD<\/a> uses the <code>|<\/code> symbol to differentiate the layers that belong to an external reference. This way, in the list of layers we see:<\/p>\n<ul>\n<li><code>0<\/code>: Layer belonging to the drawing<\/li>\n<li><code>Ref1|Layer<\/code>: Layer belonging to the <code>Ref1<\/code> external reference<\/li>\n<li><code>Ref2|Layer<\/code>: Layer belonging to the <code>Ref2<\/code> external reference<\/li>\n<\/ul>\n<h2 id=\"the-bind-modes-insert-and-merge\">The <code>bind<\/code> modes: <code>insert<\/code> and <code>merge<\/code><\/h2>\n<p>When our drawing is ready to bind all it&rsquo;s external references, the first question that comes to mind is: what type of <code>bind<\/code> shall we use?<\/p>\n<h3 id=\"binds-merge-mode\"><code>Bind's<\/code> <code>merge<\/code> mode<\/h3>\n<p>This mode imports all layers from the external references as new layers, making sure that the layer names are unique.<\/p>\n<p>This is achieved by <a href=\"https:\/\/www.autodesk.com\/products\/autocad\/overview\" target=\"_blank\" rel=\"noopener\">AutoCAD<\/a> by swapping the <code>|<\/code> symbol by the <code>$<\/code> symbol. This symbol separates the name of each layer from it&rsquo;s previous external reference.<\/p>\n<p>Thus, the result of executing a <code>bind<\/code> in <code>merge<\/code> mode for this example will produce the following output:<\/p>\n<ul>\n<li><code>0<\/code>: Layer belonging to the drawing (existing)<\/li>\n<li><code>Ref1$Layer<\/code>: Layer belonging to the drawing (new)<\/li>\n<li><code>Ref2$Layer<\/code>: Layer belonging to the drawing (new)<\/li>\n<\/ul>\n<h3 id=\"binds-insert-mode\"><code>Bind's<\/code> <code>insert<\/code> mode<\/h3>\n<p>This mode is the simplest at first sight and produces the &ldquo;cleanest&rdquo; results regarding the final layer output.<\/p>\n<p>This is due to the fact that <a href=\"https:\/\/www.autodesk.com\/products\/autocad\/overview\" target=\"_blank\" rel=\"noopener\">AutoCAD<\/a> imports each of the layers from the external references and treats it as if it were a layer belonging to the drawing itself.<\/p>\n<p>This way, executing a <code>bind<\/code> with <code>insert<\/code> mode on the previous example would produce the following output:<\/p>\n<ul>\n<li><code>0<\/code>: Layer belonging to the drawing (existing)<\/li>\n<li><code>Layer<\/code>: Layer belonging to the drawing (new)<\/li>\n<\/ul>\n<h2 id=\"issues-of-bind-in-insert-mode\">Issues of <code>bind<\/code> in <code>insert<\/code> mode<\/h2>\n<p>As we can see, the last example returns a wrong output and the loss of information, weather it be run from <a href=\"https:\/\/camilion.eu\/en\/apps\/RefMan\/\">RefMan<\/a>, or from <a href=\"https:\/\/www.autodesk.com\/products\/autocad\/overview\" target=\"_blank\" rel=\"noopener\">AutoCAD<\/a>.<\/p>\n<table>\n<thead>\n<tr>\n<th>Queuing<\/th>\n<th>AutoCAD<\/th>\n<th>RefMan<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><img decoding=\"async\" alt=\"Montaje &quot;Dibuix&quot;\" src=\"https:\/\/camilion.eu\/wp-content\/uploads\/2024\/02\/Dibuix.png\" title=\"\"><\/td>\n<td><img decoding=\"async\" alt=\"Dibuix_Bind_AutoCAD\" src=\"https:\/\/camilion.eu\/wp-content\/uploads\/2024\/02\/Dibuix_Bind_AutoCAD.png\" title=\"\"><\/td>\n<td><img decoding=\"async\" alt=\"Dibuix_Bind_RefMan\" src=\"https:\/\/camilion.eu\/wp-content\/uploads\/2024\/02\/Dibuix_Bind_RefMan.png\" title=\"\"><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong><a href=\"https:\/\/www.autodesk.com\/products\/autocad\/overview\" target=\"_blank\" rel=\"noopener\">AutoCAD<\/a>:<\/strong> the right half is not visible. This is because <a href=\"https:\/\/www.autodesk.com\/products\/autocad\/overview\" target=\"_blank\" rel=\"noopener\">AutoCAD<\/a> used the properties defined in the reference <code>Ref1<\/code> for the newly created layer <code>Layer<\/code> (<strong>blue<\/strong> and <strong>frozen<\/strong>).<\/p>\n<p><strong><a href=\"https:\/\/camilion.eu\/en\/apps\/RefMan\/\">RefMan<\/a>:<\/strong> the left half should not be visible (and it should be blue). This is because <a href=\"https:\/\/camilion.eu\/en\/apps\/RefMan\/\">RefMan<\/a> used the properties defined in the reference <code>Ref2<\/code> for the newly created layer <code>Layer<\/code> (<strong>magenta<\/strong> and <strong>not frozen<\/strong>).<\/p>\n<h2 id=\"real-world-example\">Real world example<\/h2>\n<p>Unfortunately the issues illustrated above are not theoretical. In large scale projects, a seemingly innocuous operation can result in the loss of vital information causing great detriment to the project.<\/p>\n<p><img decoding=\"async\" alt=\"Layers Montaje\" src=\"https:\/\/camilion.eu\/wp-content\/uploads\/2024\/02\/018_M-ANM-3C1VD1-CLSW-EDR-100003-P1_MEP_IRR_SECTION_02_Layers.png\" title=\"\"><\/p>\n<h1 id=\"conclusion\">Conclusion<\/h1>\n<ul>\n<li>This issue does not only affect layer visibility; colour, line type and other properties are affected as well.<\/li>\n<li>The only way to avoid this conflict is to have <strong>always<\/strong> the same properties for layers with the same name in all the different references. This is hard to guarantee and the risk or error is very high.<\/li>\n<li>A workaround would be to create new layers for each reference. This is what the <code>bind<\/code> in <code>merge<\/code> mode does. This would produce two layers with respective names <code>Ref1$0$Layer<\/code> and <code>Ref2$0$Layer<\/code>.<\/li>\n<\/ul>\n<p>Any solution (different from the <code>merge<\/code> mode) would produce an incorrect output in these cases.<br \/>\nOn request from our clients, we have updated <a href=\"https:\/\/camilion.eu\/en\/apps\/RefMan\/\">RefMan<\/a> so that the user is warned whenever there are any layer properties that conflict with one another.<\/p>\n<p>Would you like to know more about <a href=\"https:\/\/camilion.eu\/en\/apps\/RefMan\/\">RefMan<\/a> or do you have a more specific request? Feel free to contact us.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>As expert users of <a href=\"https:\/\/autodesk.com\">Autodesk\u00ae<\/a> software like <a href=\"https:\/\/www.autodesk.com\/products\/autocad\/overview\">AutoCAD\u00ae<\/a>,<br \/>\nwe sometimes receive very specific questions or requests from our clients.<\/p>\n<p>One of the most recent ones has been related to external reference management and<br \/>\nthe differences between the <code>bind<\/code> modes in <a href=\"https:\/\/www.autodesk.com\/products\/autocad\/overview\">AutoCAD<\/a> software, particularly,<br \/>\nhow one of <a href=\"https:\/\/camilion.eu\/en\/apps\/\">our apps<\/a>: <a href=\"https:\/\/camilion.eu\/en\/apps\/RefMan\/\">RefMan<\/a> interacts with that.<\/p>\n<p>When we discovered that the problem of our client came from a lack of understanding of the process,<br \/>\nwe decided to document it and explain it for whoever is interested.<\/p>\n","protected":false},"author":1,"featured_media":1458,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[192,156],"tags":[],"dipi_cpt_category":[],"class_list":["post-2143","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-howto-es","category-refman-es"],"acf":[],"_links":{"self":[{"href":"https:\/\/camilion.eu\/es\/wp-json\/wp\/v2\/posts\/2143","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/camilion.eu\/es\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/camilion.eu\/es\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/camilion.eu\/es\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/camilion.eu\/es\/wp-json\/wp\/v2\/comments?post=2143"}],"version-history":[{"count":3,"href":"https:\/\/camilion.eu\/es\/wp-json\/wp\/v2\/posts\/2143\/revisions"}],"predecessor-version":[{"id":2205,"href":"https:\/\/camilion.eu\/es\/wp-json\/wp\/v2\/posts\/2143\/revisions\/2205"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/camilion.eu\/es\/wp-json\/wp\/v2\/media\/1458"}],"wp:attachment":[{"href":"https:\/\/camilion.eu\/es\/wp-json\/wp\/v2\/media?parent=2143"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/camilion.eu\/es\/wp-json\/wp\/v2\/categories?post=2143"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/camilion.eu\/es\/wp-json\/wp\/v2\/tags?post=2143"},{"taxonomy":"dipi_cpt_category","embeddable":true,"href":"https:\/\/camilion.eu\/es\/wp-json\/wp\/v2\/dipi_cpt_category?post=2143"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}