Jump to content

Malcolm Crowe

Community Members
  • Posts

    1,729
  • Joined

  • Last visited

Previous Fields

  • Computer Brand/Model
    Dell Mobile Precision 7760
  • Processor type and speed
    i9-11950H, 2.60 - 5.0GHz
  • Amount of RAM
    64GB
  • IronCAD Version/Build #
    IC2023
  • Graphics card
    Nvidia RTX A3000
  • Graphics card driver version
    517.4
  • Operating System/version
    Windows 11 Professional

Contact Methods

  • Website URL
    http://www.james-forten.com
  • ICQ
    0

Profile Information

  • Location
    Taupo, New Zealand

Recent Profile Visitors

9,509 profile views

Malcolm Crowe's Achievements

TriBall

TriBall (9/9)

675

Reputation

  1. This is an interesting example from yesterday, where it was necessary to change from the ACIS kernel to the PARASOLID kernel for some Blends to work. This model was originally created 5 years ago (using the ACIS kernel), but after some very minor dimension changes yesterday, these Blends stopped working. Changing the kernel property of the Part to using PARASOLID solved the blending problem. Malcolm IRONCAD - Blend Problem Solved Changing from ACIS to PARASOLID Kernel - 20240313.mp4
  2. Hi Kim, IRONCAD (CAXA) 2024 introduced the capability to have multiple "Papers" within a single tab. This was introduced specifically with the "Model" tab in mind (like the example in your image), but it is also applicable to the "Layout" tabs as well. Attached is a video demonstrating the principle of how this works. Regarding what file format to use in CAXA, we normally use CAXA's *.exb file format. We only save as *.dwg when we need to collaborate with other CAD software (like BRICSCAD that we also use). This might not be 100% correct, but I've noticed that when *.dwg files are used (instead of *.exb), then the dimensions applied to Generated Views within CAXA are not associative. That is, if the 3D Model changes and the Generated View updates, then the dimensions in CAXA don't follow as they do for *.exb files. It's more efficient to annotate drawings of IRONCAD Scenes within CAXA (with full access to 3D properties as well), rather than externally referencing into other software for this purpose. However, when you need to incorporate associated Generated Views from CAXA within 2D Models of other CAD software (like AUTOCAD, BRICSCAD, MICROSTATION, etc.) then externally referencing *.dwg files from CAXA is a good option to have. Malcolm CAXA - Multiple Papers within Model Space.mp4
  3. Hi TaeGyu, The link below is to a new post created with your question in mind. 1. IRONCAD Scene (*.ics) 2. CAXA DRAFT Generated Views (*.dwg) 3. DWG Editor (BRICSCAD) externally referencing the Generated Views from the CAXA drawing. But why not just create the fully annotated drawing in CAXA? This would be more efficient, and you don't lose access to the 3D property information needed for BOMs. Externally referencing Generated Views from CAXA DRAFT is really useful if you're combining these within another drawing (like a building layout, etc.). But it is a more complicated workflow if all you are doing is annotating the Generated Views. Malcolm
  4. One of the strengths of DWG Editors (like CAXA, AUTOCAD, BRICSCAD, etc) is the ability to externally reference (XRef) other DWG files, in a similar way that we can externally reference other 3D Scene files within a 3D Scene. This is hugely beneficial when DWG files from multiple users (or engineering disciplines) are combined into a common layout. An example could be the layout of a machine or production line (designed in IRONCAD) that needs to be overlayed with a building layout (and other services). The attached video demonstrates how Generated Views in CAXA can be saved as a DWG file, that can then be externally referenced (XRef) into other DWG files, within another DWG Editor (in this case BRICSCAD). When the 3D Scene changes, the CAXA file needs to be opened so that it can be updated and saved. Then within the other DWG Editor the externally referenced CAXA file needs to be "Reloaded" to update the link. The XRef then needs to be "refreshed" by editing a property of the XRef (such as layer, color, etc.), so that any associated dimensions correctly update. Malcolm CAXA - Referencing Generated Views as XRefs within other DWG Editors.mp4
  5. Some DWG Editors (based on the ODA Drawing SDK) include two settings for fixing the length of Dimension Extension Lines, as an alternative to the normal offset from the selected geometry. While CAXA hasn't implemented these two settings (currently), the attached video demonstrates how to achieve the same end result by turning off the generated Extension Lines, and manually adding Fixed Length ones using CAXA Symbols (Library). Malcolm CAXA - Manually Adding Fixed Length Extension Lines.mp4
  6. Hi Peter, While there isn't a specific tool in CAXA for this, the attached video demonstrates how to create Visual Breaks in Extension Lines using Wipeouts (to create the same end result). Malcolm CAXA - Using Wipeouts to Add Visual Breaks to Dimension Extension Lines.mp4
  7. The "Structured Frame" tool is well suited for this. Create a new "Structured Part" and within that create a sketch of the "Path" that you want the Structured Frame to follow. Then use the "Structured Frame" tool to apply the desired section to that sketched path. See the attached video. Malcolm Rolled Structured Frame.mp4 Rolled Structured Frame.ics
  8. Hi Harley, I've tried to demonstrate how to control Bend Corner Reliefs via Parameters in the attached video. It's important to add the Parameter(s) first at the Feature (Bend) Level. Then you can reference that Parameter Name in the Bend Properties. Malcolm Sheet Metal Bend Corner Relief Parameters.mp4 Sheet Metal Bend Corner Relief Parameters.ics
  9. Hi Peter, I'm pleased to hear that it was helpful. For the sake of other users (who aren't necessarily interested in changing colors), the principles demonstrated in the video are applicable to any type of Design Variation (including sizing, suppression, and properties). Malcolm
  10. Hi Peter, The weather hasn't been favorable for cycling (one of my fun things to do), so I've been working today. It helps that my wife is away working this weekend as well. Attached is a video that I hope demonstrates well enough what is possible with "Design Configurations" and "Scene Configurations". I've also attached the Scene files used in the video. One of the great things about "Design Variations" is that they are saved with the Part (or Assembly), and not with the Scene. As a result, "Design Variations" are saved with the Part (or Assembly) when dragged into a Catalog. This is not the case with "Scene Configurations" (which are Scene specific). Malcolm IRONCAD - Design Variations - Applying Colors.mp4 ASSEMBLY.ics PIE.ics PYRAMID.ics SPHERE.ics SUB-ASSEMBLY.ics
  11. Hi Peter, If you're using externally linked Parts that are inserted into Assemblies, then the following might work for you. However, you need to be aware, that it's not possible to have different colors for the same Part within the same Scene. "Design Variations" allow you to assign specific colors to each DV if wanted. So, for your Parts you could have "Painted" and "Unpainted" DVs. Then when you insert one of these Parts within an Assembly, you could use "Add to Active Configuration" within the "Design Variation Dialog" to link the desired DV of the Part (Painted or Unpainted) to the current Configuration of the Scene (into which it has been inserted). Let me know if this doesn't make sense, as I can potentially make a video in the weekend. Malcolm
  12. This is an example of how to combine multiple Imported Parts (whether Innovative or Structured) into a single Part using the "Copy Body" tool. Malcolm Copy Body - Combining Multiple Parts into One.mp4
  13. This example involves the importing of a couple of *.stp files that behaved differently compared to other *.stp files received from the same manufacturer. To successfully import these particular files, it was necessary to either change an import setting (Combine all as reference geometry), or to change the Scene kernel from PARASOLID to ACIS. Malcolm IRONCAD - Importing STEP Files - Comparison of Settings.mp4
  14. I use the term "Pattern Group" as a Group (of Parts, Assemblies or Patterns) created using the "Linear Pattern" tool of the TriBall; where the pattern number has been set to "1" and the distance to "0" (zero). "Pattern Groups" are extremely useful for simplifying the assembly structure within the Scene Browser, without affecting the BOM (which would be affected if an Assembly was used). The attached video demonstrates how this can be used for grouping hundreds of fasteners to greatly simplify the assembly structure, without affecting the BOM in the associated 2D Drawing. It also includes placing Pattern Groups within other Pattern Groups. Malcolm IRONCAD - Pattern Groups - Alternative to Assemblies and Groups.mp4
×
×
  • Create New...