3Dconnexion input devices\n\n \n\n## Driver installation \n\n### Linux\n\nFreeCAD supports drivers from project [Spacenav](http://spacenav.sourceforge.net/). This is a project aiming to create an open-sourced driver which is compatible with the proprietary drivers from 3Dconnexion.\n\n#### Install from repo \n\n##### Ubuntu\n\n \n```python\nsudo apt-get install spacenavd\n```\n\nNote, however, that version 0.6 available on Ubuntu 20.04 (and probably older ones) does not seem to work. You then have to compile spacenavd from source as explained below.\n\n##### Fedora\n\n \n```python\nsudo yum install spacenavd\n```\n\n##### Debian\n\n \n```python\napt-get install spacenavd libspnav-dev\n```\n\nSpacenav needs these permissions:\n\n\n: \n \n```python\n cp ~/.Xauthority /root/\n \n```\n \n\n\nRestart spnavd and FreeCAD\n\n\n: \n \n```python\n /usr/bin/spnavd_ctl x11 stop\n /usr/bin/spnavd_ctl x11 start\n \n```\n \n\n\n##### openSUSE\n\n \n```python\nsudo zypper install spacenavd\n```\n\n#### Compile Spacenav from source \n\nThis is recommended if your distribution might provide an outdated version.\n\n- Download the following files:\n - [spacenavd](https://sourceforge.net/projects/spacenav/files/latest/download) (latest version)\n - [libspnav](https://sourceforge.net/projects/spacenav/files/spacenav%20library%20%28SDK%29/) (get latest libspnav version)\n - [spnavcfg](https://sourceforge.net/projects/spacenav/files/spacenavd%20config%20gui/) (get latest libspnav version)\n- Unpack the archives into a folder in your home directory.\n- Enter the spacenavd-x.x directory and run the following commands:\n\n\n: \n \n```python\n ./configure\n make\n \n```\n \n- If this was successful, run the following commands **as root** (or prefix with sudo.)\n\n\n: \n \n```python\n make install\n ./setup_init\n /etc/init.d/spacenavd start\n \n```\n \n- This installs the spacenav daemon, configures it to automatically load on system boot, and starts the daemon without having to reboot.\n- Now it is time to check that your device is properly detected. With your device unplugged, run the following command and then plug it in.\n\n\n: \n \n```python\n tail -n100 -f /var/log/spnavd.log \n \n```\n \n- If the output looks something like this, you can continue.\n\n\n: \n \n```python\n Device detection, parsing /proc/bus/input/devices\n trying alternative detection, querying /dev/input/eventX device names...\n trying \"/dev/input/event1\" ... Power Button\n trying \"/dev/input/event2\" ... 3Dconnexion SpaceNavigator\n using device: /dev/input/event2\n device name: 3Dconnexion SpaceNavigator\n \n```\n \n- Now enter the directory named libspnav-x.x.x and run the following commands:\n\n\n: \n \n```python\n ./configure\n make\n \n```\n \n- If make fails with the following error: \\...\n\n\n: \n \n```python\n fatal error: gtk/gtk.h: No such file or directory\n \n```\n \n- \\... then you need to install **libgtkmm-2.4-dev**. Under Ubuntu, this is done like this:\n\n\n: \n \n```python\n sudo apt-get install libgtkmm-2.4-dev\n \n```\n \n- When make has completed successfully, run the following command **as root** (or prefix with sudo.)\n\n\n: \n \n```python\n make install\n \n```\n \n- Look in the directory libspnav-x.x.x/examples/. If you want to test your device, compile and run either one of the two examples.\n\n- Follow the same pattern to compile and install **spnavcfg**. Make sure to run spnavcfg as root, or no settings will be saved!\n\n#### Starting spacenavd as a systemd service at boot \n\nIf you want to start spacenavd at boot using systemd, do the following:\n\n- Go to the directory where you clone the spacenavd repository (to the root of the repository)\n- \\\"sudo cp contrib/systemd/spacenavd.service /usr/lib/systemd/system/spacenavd-local.service\\\".\n- \\\"sudo systemctl enable spacenavd-local.service\\\".\n- \\\"sudo systemctl start spacenavd-local.service\\\", if you want to start it right away.\n\nThis is only necessary for the installation from source.\n\n#### Restarting spacenavd \n\nIf sometimes SpaceNavigator stops working, it is good to restart driver. To restart it, go to Terminal and execute:\n\n \n```python\nsudo xhost +\nsudo /etc/init.d/spacenavd restart\n```\n\nAfter that restart FreeCAD. On some distros this is necessary at each boot.\n\n#### Known Issues \n\nA user reported on the [forum](https://forum.freecadweb.org/viewtopic.php?p=341327#p341327) they saw the following:\n\n Spacenav daemon 0.6\n failed to open config file /etc/spnavrc: No such file or directory. using defaults.\n adding device.\n device name: 3Dconnexion SpacePilot\n using device: /dev/input/event5\n No protocol specified\n failed to open X11 display \":0.0\" \n\nThe workaround that worked for them:\n\n \n```python \nsudo cp ~/.Xauthority /root/\nsudo spnavd_ctl x11 start\nsudo systemctl restart spacenavd \n```\n\n### MacOS\n\n3Dconnexion input devices are supported on macOS, provided FreeCAD is built and used on a system with the 3Dconnexion drivers installed. You may need 3DxWare 10.7.2 or greater for macOS 12 Monterey.\n\n### Windows\n\nAs of version 0.13, 3D mouse is supported under Windows. You need to have 3Dconnexion drivers installed. In FreeCAD version 1.0 a [new integration with 3Dconnexion devices](https://github.com/FreeCAD/FreeCAD/pull/12929) has been introduced. If compiled with that integration, only recent hardware is supported: to support older devices users will need to self-compile with the FREECAD_3DCONNEXION_SUPPORT cMake variable set to \\\"Raw Input\\\". Windows users should be aware that 3Dconnexion\\'s driver (*not* the code in FreeCAD) contains a telemetry package that communicates information about your installed software back to 3Dconnexion.\n\n#### Known Issues \n\n- In FreeCAD version 1.0 and later changing settings in the 3DX config window may not have the expected results ([issue](https://github.com/FreeCAD/FreeCAD/issues/14044)). To fix this:\n 1. Stop the driver (by running Stop 3DxWare).\n 2. Go to **..
\n\n### Spaceball Motion \n\nIn this tab you have ability to set up some of general space mouse settings. They include:\n\n- Global Sensitivity - Slider with ability to set global sensitivity\n- Dominant - if you enable dominant mode, only axes with highest move will be considered\n- Flip YZ - This option enables you to flip Y and Z axes on 3D mouse\n- Enable Translations - easy way to enable/disable translations\n- Enable Rotations - easy way to enable/disable rotations\n- Calibrate - enables you to calibrate space navigator. It is pressed while space navigator is not moved.\n- Set To Default - removes all settings and sets them to default.\n\nOther than this, for each axes you have ability to set:\n\n- Enabled - Enable/Disable axes\n- Reverse - Reverse movement on axes\n- Sensitivity - slider with ability to set sensitivity\n\n### Spaceball Buttons \n\nWhen you open this tab for the first time, it will be empty and unavailable. To activate it, you must press one of your space mouse buttons. After you do, list of buttons will appear on the left side, and list of commands will be available on the right side.\n\nTo connect certain command with a button, select button on the left side, and it\\'s command on the right side. To clear commands from button, press \\\"Clear\\\".\n\n### Troubleshooting\n\nCheck if your FreeCAD installation links to the spacenav library. The best way to check this is by running FreeCAD from the command line terminal `FreeCAD --log-file /tmp/freecad.log` and close it immediately again. Then open the file **/tmp/freecad.log** and search for the messages:\n\n \n\nor\n\n \n\nIf none of them appears then your FreeCAD build doesn\\'t link to the spacenav library. If the former message appears then it basically works. The latter message means there is probably a problem with the spacenav daemon.\n\n## Related\n\n- Forum thread [spacenav on Windows](https://forum.freecadweb.org/viewtopic.php?f=3&t=51023)\n- Forum thread [Space navigator axis confusion](https://forum.freecadweb.org/viewtopic.php?f=8&t=57188)\n\n\n---\n⏵ [documentation index](../README.md) > [User Documentation](Category_User%20Documentation.md) > [3rd Party](Category_3rd%20Party.md) > 3Dconnexion input devices\n", "source": "freecad-docs", "added": "2026-11-08", "created": "", "token_count": 2275, "license": "CC0-1.0", "author": "Open-source contributors"}
+{"id": "freecad-docs:wiki/A2plus.md", "text": "# A2plus\n1. REDIRECT [A2plus_Workbench](A2plus_Workbench.md)\n\n\n---\n⏵ [documentation index](../README.md) > A2plus\n", "source": "freecad-docs", "added": "2026-11-08", "created": "", "token_count": 41, "license": "CC0-1.0", "author": "Open-source contributors"}
+{"id": "freecad-docs:wiki/A2plus_Workbench.md", "text": "#
to execute the script (also called macro).\n4. Change to the tab of the assembly to see the rotation.\n\nTo practice, just change something in the script and execute it afterwards. For example increase *step* to *5*.\n\nThis is the result of the example animation:\n\n\n\n#### Interactive Script Example \n\nThe first script example demonstrated how to create an animation without any user feedback. For most applications you need to interact with the animation. For example the interesting issue in the example is to see how the driving pins cross the center groove of the wheel. To have a closer look you might present this detail to your colleagues or boss. Therefore you need an interactive solution.\n\nThis can be done by using a custom animation dialog with a slider. By moving the slider you can set the rotation angle and therefore rotate back and forth at interesting position.\n\nWe use the same assembly file: [A2p_animated-example.FCStd](https://forum.freecadweb.org/download/file.php?id=97554) and this Python script: [A2p_animation-example-script.py](https://forum.freecadweb.org/download/file.php?id=97982).\n\n\n
About FreeCAD\n\n**FreeCAD** is a general purpose [open source](http://en.wikipedia.org/wiki/Open_source) parametric 3D [**CAD**](http://en.wikipedia.org/wiki/CAD) modeler licensed under the [LGPL License](License.md). FreeCAD is aimed directly at [mechanical engineering](http://en.wikipedia.org/wiki/Mechanical_engineering) and [product design](http://en.wikipedia.org/wiki/Product_design) but, being very generic, also fits in a wider range of uses around engineering, such as architecture, finite element analysis, 3D printing, and other tasks.\n\nFreeCAD features tools similar to [CATIA](https://en.wikipedia.org/wiki/CATIA), [SolidWorks](http://en.wikipedia.org/wiki/Solidworks), [Solid Edge](http://en.wikipedia.org/wiki/Solid_Edge) or [Revit](https://en.wikipedia.org/wiki/Autodesk_Revit), and therefore also falls into the category of [**CAD**](http://en.wikipedia.org/wiki/CAD), [**PLM**](http://en.wikipedia.org/wiki/Product_Lifecycle_Management), [**CAx**](http://en.wikipedia.org/wiki/CAx), [**CAE**](http://en.wikipedia.org/wiki/Computer-aided_engineering) and [**BIM**](https://en.wikipedia.org/wiki/Building_information_modeling). It is a [feature based parametric modeler](http://en.wikipedia.org/wiki/Parametric_feature_based_modeler) with a modular software architecture making it possible to provide additional functionality without modifying the core system.\n\nAs with other CAD modelers it has many 2D components in order to sketch planar shapes or create production drawings. However, direct 2D drawing (like [Inkscape](https://inkscape.org/) or [AutoCAD LT](http://en.wikipedia.org/wiki/AutoCAD#AutoCAD_LT)) is not the focus, neither are animation or mesh editing (like [Blender](https://www.blender.org/), [Maya](http://en.wikipedia.org/wiki/Maya_(software)), [3ds Max](http://en.wikipedia.org/wiki/3ds_Max), or [Cinema 4D](http://en.wikipedia.org/wiki/CINEMA_4D)). Nevertheless, thanks to its wide adaptability, FreeCAD is useful in a much broader area around its base feature set.\n\nFreeCAD makes heavy use of open-source libraries that exist in the field of [scientific computing](http://en.wikipedia.org/wiki/Scientific_Computation). Among them are [Open Cascade Technology (OCCT)](http://OpenCascade.org), a powerful CAD kernel; [Coin3D](https://github.com/coin3d/coin/wiki), a toolkit for 3D graphics development compatible with [Open Inventor](http://en.wikipedia.org/wiki/Open_Inventor); [Qt](http://www.qt.io/), the world-famous user interface framework; and [Python](http://www.python.org), a modern scripting language. FreeCAD itself can also be used as a library by other programs.\n\nFreeCAD is also [multi-platform](http://en.wikipedia.org/wiki/Cross-platform), and currently runs on Linux/Unix, Windows, and macOS systems with the same look and functionality on all platforms.\n\nFor more information about FreeCAD\\'s capabilities, take a look at the [feature list](Feature_list.md), the [latest release notes](Feature_list#Release_notes.md), and the [getting started](Getting_started.md) articles, or see more [screenshots](Screenshots.md).\n\n### About the FreeCAD project \n\nThe FreeCAD project was started as far back as 2001, as described on the [history](History.md) page.\n\nFreeCAD is maintained and developed by a [community of enthusiastic developers and users](contributors.md) and is built through the patient work of hundreds of contributors, some regular, some occasional. Most work on FreeCAD as volunteers. The [FreeCAD forum](http://forum.freecad.org) is where most of the ideas and decisions are discussed, and the [GitHub repository](https://github.com/FreeCAD/FreeCAD) is where the code is being kept, shared, discussed and worked on. Anybody is [welcome to participate](Help_FreeCAD.md).\n\n### About the FPA \n\nThe FreeCAD project is also supported by a non-profit organization, the [FreeCAD project association (FPA)](https://fpa.freecad.org). The FPA is an independent body created by some FreeCAD veterans in 2021 to collect [donations](donate.md) and other resources to support the project and its community, to help protect that community and allow it to continue developing in the best conditions, and to represent the project against other bodies such as companies and institutions.\n\n\n---\n⏵ [documentation index](../README.md) > [User Documentation](Category_User%20Documentation.md) > About FreeCAD\n", "source": "freecad-docs", "added": "2026-11-08", "created": "", "token_count": 1051, "license": "CC0-1.0", "author": "Open-source contributors"}
+{"id": "freecad-docs:wiki/Add_Button_to_FEM_Toolbar_Tutorial.md", "text": "---\n TutorialInfo:\n Topic: FEM\n Level: Advanced\n Time: 60 min\n Author: User:JohnWang\n FCVersion: 0.19\n Files: \n---\n\n# Add Button to FEM Toolbar Tutorial\n\n \n\n\n## Introduction\n\nThe FEM workbench has toolbars and menus. This tutorial shows how to add a test button to a toolbar. It also shows how to add a menu item to a menu.\n\nThe task can be split into four parts:\n\n- **Create a new icon file**.\n- **Register the new icon file**. Modification needed to `src/Mod/Fem/Gui/Resources/Fem.qrc`\n- **Create a new command class**. Modification needed to `src/Mod/Fem/femcommands/commands.py`\n- **Add new command to workbench**. Modification needed to `src/Mod/Fem/Gui/Workbench.cpp`\n\n## Create a new icon file \n\nFor the button, we need an icon file. You can use any of your favorite tools to create it, but it must be in the SVG format. Here we will use the **FEM_testButton.svg** file as an example.\n\nIt must be placed in: `src/Mod/Fem/Gui/Resources/icons/`.\n\n## Register the new icon file \n\nThe new SVG icon file has to be registered for the GUI button by inserting it in `src/Mod/Fem/Gui/Resources/Fem.qrc`:\n\n {{code|code=\n
\n*The objects in initial position*\n\n## Introduction\n\nThis demonstration addresses the use of the OYX attachment mode to adjust the position of the origin of a sketch as described in [Part:Attachment](Part_EditAttachment.md), it is not comprehensive, but hopefully will help users experiment.\n\nThe image above shows the geometry used in this demonstration.\n\nThe lower right frame shows the top view of the scene. Note the scene includes a sketch containing a square and text indicating the vertical (Y), horizontal (X) axes of the sketch. The lower left corner of the square is located at 0,0,0 of the sketch (the origin of the sketch).\n\nThe origin of the sketch and the global origin (designated by the red, green and blue [axis cross](Std_AxisCross.md)) are the same. In the other frames of the image we can see that the square is at Z=0, so the sketch is in the XY plane.\n\nThere are two other sketches which include geometry that will be used to re-position the sketch containing the square. One sketch contains an orange line that is oriented along the global Z axis in the XZ plane. The other sketch contains a yellow line in the XY plane.\n\n## Discussion\n\nAttachment mode Align O-Y-X is defined as follows in [Part:Attachment](Part_EditAttachment.md): *Matches object\\'s origin with first referenced vertex and aligns its vertical and horizontal plane axes toward vertex/along line.*. It also notes there are several reference combinations.\n\n:; Reference combinations:\n\n: Vertex, Vertex, Vertex\n: Vertex, Vertex, Edge\n: Vertex, Edge, Vertex\n: Vertex, Edge, Edge\n: Vertex, Vertex\n: Vertex, Edge\n\nLets start with *Vertex, Vertex, Vertex*.\n\nIf we match the definition to the reference:\n\nThe first vertex selected will position the origin of the sketch to the selected vertex.\n\nThe second vertex selected will align the vertical axis of the sketch (in the demo setup this axis is indicated with **Y**).\n\nSo, if we select the upper left/upper vertex of the yellow edge (as seen in the larger right frame) and the lower/right vertex of the yellow edge the sketch is positioned like this:\n\n
\n\n:; Notes:\n\n: The Align O-Y-X is selected in the Attachment dialogue.\n: The sketch origin is now at the upper left/upper vertex of the yellow line.\n: The Y axis of the sketch is now aligned with the yellow line.\n: The Z axis of the sketch is perpendicular to the yellow line.\n\nNow if we add a third reference by selecting the upper vertex of the orange edge the scene changes to:\n\n
\n\n:; Notes:\n\n: Now the X axis of the sketch is aligned in the direction of the selected vertex of the orange edge.\n\n\n---\n⏵ [documentation index](../README.md) > Advanced Attachment OYX\n", "source": "freecad-docs", "added": "2026-11-08", "created": "", "token_count": 717, "license": "CC0-1.0", "author": "Open-source contributors"}
+{"id": "freecad-docs:wiki/Advanced_TechDraw_Tutorial.md", "text": "---\n TutorialInfo:\n Topic: Modeling\n Level: Experienced User\n Author: domad\n FCVersion: 0.19.23300 or higher\n---\n\n# Advanced TechDraw Tutorial\n\n\n \n\n\n## Purpose in Brief \n\nCreate points, lines, circles, arcs, etc. in TechDraw views and/ or entire \\\"cosmetic\\\" drawings with absolute precision, suitable for the dimensioning tools that the workbench is equipped with, to generate compliant and detailed technical drawings.\n\n## Introduction\n\nThis tutorial introduces the experienced user to some advanced use of existing tools and techniques from other workbenches to extend actually missing functionality in
\n\nIf you are unfamiliar with the XYZ axes then have a play with the numbers in the Translation box. When finished playing click on the **Reset** button.\n\n## Second Steps \n\n
\n\nWe are now going to rotate the cylinder so that it is lying along the X axis. To do this it needs to be rotated around the Y axis. The Rotation box should say \\'Rotation axis with angle\\' so change the Axis to Y and increment the Angle until it reaches 90. Click on **OK**.\n\nI like to play with rotating the view at this point (and often!) so by all means do so. You should find the \\'seam\\' of the cylinder on the underside.\n\n
\n\nWe are now going to add and modify a box so click on the
\n\nI think the wings need to be moved forward a bit but if I select Aeroplane and try changing its Placement X Translation the whole thing moves. I only want to move the wings so cancel the Placement.\n\nExpand Aeroplane (click on the **[+]** beside it) and expand Fusion.\n\nClick on Box and get its [Placement into Tasks](Placement.md). Notice it already has Y: -10 and Z: -1 in the Translation. Change the X translation to 3 and click on **Apply**. That\\'s better. Click **OK**.\n\n\n## Rotations\n\nClick on Aeroplane and get its [Placement into Tasks](Placement.md). In the Rotation section change where it says \\'Rotation axis with angle\\' to \\'Euler angles\\' because they\\'re a lot easier to work with.\n\n**Yaw** is the rotation about the **Z axis**, that is to say a rotation from left to right. (The yaw angle is the **Psi ψ**). **Pitch** is rotation about the **Y axis**, that is to say nose-up and nose-down. (The Pitch angle is the **Phi φ**). **Roll** is rotation about the **X axis**, that is to say wing up and down. (The Roll angle is the **Thêta θ**). \n\nHowever, even here there are some important things to remember:\n\n- Positive Rotations are clockwise when viewed from the Origin outwards along a positive axis. Or to put it another way: Positive Rotations are anticlockwise when viewed from a positive axis towards the Origin.\n\n- Although the three labels are Yaw, Pitch and Roll that\\'s not really what they are. Yaw, Pitch and Roll are references to the *body coordinates* of an object in 3D space. The labels should be Heading, Elevation and Bank or even Azimuth, Inclination and Bank because they actually refer to the *space coordinates* of the 3D system. These are the **Tait-Bryan angles**. If you want more information then try [Euler Angles](http://en.wikipedia.org/wiki/Euler_angles#Tait-Bryan_angles).\n\n- With the Aeroplane in its present position simple rules apply. Yaw is rotation around the Z axis, ie left and right. Pitch is rotation around the Y axis, ie nose up and down. Roll is rotation around the X axis, ie wings up and down. That\\'s fine to start with but it\\'s not going to be true later!\n\nHave a play with the three YPR numbers. You only need to change things by a few degrees to get the idea. Reset when you finished.\n\nNow we\\'re going to see why the Yaw-Pitch-Roll labels are not really suitable. Change the Roll number to 90°. Yaw should move the nose of the aeroplane up and down and Pitch should move it side to side *as viewed from outside the aeroplane* which is where we are. Do they? No they don\\'t! Pitch changes the yaw and Yaw changes the pitch. OK, Reset.\n\nSo, a better way of thinking about rotations is that Yaw changes your Longitude, Pitch changes your Latitude and Roll changes the direction (NSEW) that you\\'re facing. Or you could check out [Axes conventions](http://en.wikipedia.org/wiki/Axes_conventions) for other descriptions.\n\nRight, back to work. Change Yaw to 45° and Pitch to -30°. Click on OK to show that the operation has been completed. Now get back the [Placement Task](Placement.md) and look at the Rotation box. It has reverted to \\'Rotation axis with angle\\' and has some wierd numbers Axis and Angle boxes. Mine had Axis: (0.219493,-0.529904,0.819161) and Angle: 53.65°. The three numbers in brackets are the XYZ components of a unit vector in the 3D space. It is the axis about which our original Aeroplane was rotated to get our final Aeroplane. The angle is how much it was rotated. Clever, huh, but not very friendly! It was Euler who showed that you could combine a series of XYZ rotations into one rotation about one axis.\n\nHere\\'s some more suggestions for playing with the Aeroplane:\n\n- Change the Z Location (and Apply) then change the YPR numbers and see what the effect is. Then try changing the X and Y Locations and rotating.\n- Change the X Centre (and Apply) then change the YPR numbers and see what the effect is. Then try changing the Y and Z Centres and rotating.\n\nI hope this little tutorial has helped you to get a feel for rotations.\n\n\n---\n⏵ [documentation index](../README.md) > [Part](Category_Part.md) > Aeroplane\n", "source": "freecad-docs", "added": "2026-11-08", "created": "", "token_count": 1993, "license": "CC0-1.0", "author": "Open-source contributors"}
+{"id": "freecad-docs:wiki/Analysis_of_reinforced_concrete_with_FEM.md", "text": "---\n TutorialInfo:\n Topic: Reinforced concrete with FEM\n Level: Intermediate\n Time: 60 minutes\n Author: User:HarryvL HarryvL, https://forum.freecadweb.org/memberlist.php?mode: viewprofile&u=18062 HarryvL\n FCVersion: 0.19 or newer\n Files: \n---\n\n# Analysis of reinforced concrete with FEM\n\n \n\n\n## Background\n\nThe [FEM Workbench](FEM_Workbench.md) has the capability of estimating the level of reinforcement required in a concrete structure to prevent brittle failure under tension or shear.\n\n
\n\nThis is done with the method described in [\\\"Computation of reinforcement for solid concrete\\\", P.C.J. Hoogenboom and A. de Boer, HERON Vol. 53 (2008) No. 4](http://heronjournal.nl/53-4/3.pdf). In essence, it is a post-processing routine for CalculiX, which calculates the principal tensile stresses in the concrete from an elastic analysis and uses those to determine the minimum reinforcement in the three coordinate directions required to prevent failure. In the analysis, it is assumed that the concrete material cannot carry tensile stresses, whereas the steel is utilized to its maximum capacity (i.e. reaches yield).\n\nThe required reinforcement is expressed in terms of a reinforcement ratio. This is the ratio of steel to concrete area. For example, a reinforcement ratio of 0.01 in the x direction (rx=0.01) means that the total cross-sectional area of reinforcement bars running in the x direction should be 1% of the concrete cross-sectional area they are passing through. A hypothetical cross-section of 1mx1m should in that case contain 0.01 m2 steel, which could be achieved by using 90 reinforcement bars of 12mm diameter each (steel area = 90\\*PI\\*(0.012)\\^2/4=0.0102 m\\^2). If the required reinforcement ratio over this concrete cross section is uniform then the bars could be placed at an equidistance 9x10 grid with a center-to-center distance of approximately 10cm. This is still a practical number where sufficient space between bars is left for the concrete to pass through and ensure a high-quality cover. Much higher values would lead to a very dense reinforcement grid with potential quality issues, whereas much lower values could lead to large tension cracks in the cross-section between the bars. A typical range in practice is from 0.002 to 0.02 (= 0.2% to 2%). Further guidance can be found in design codes.\n\nIf the required reinforcement ratio is not uniform over the full cross-section then the cross-section can be divided into pragmatic sub-sections with more or less uniform ratio and reinforcement applied to those cross-sections. An example will be given later on.\n\nAs a word of caution, it takes much more to design a safe and durable concrete structure than what the FEM Workbench can currently provide. For example, the method does not calculate crack width (important for durability and functionality), accurate deformations (FEM results for concrete are simply linear-elastic) or take account of reinforcement anchoring requirements (causing an increase of required reinforcement ratios in anchoring zones). It also doesn't predict concrete crushing (although an indication of that can be obtained by plotting the Mohr-Coulomb stress - see further), which could mean that the concrete fails before the reinforcement yields, causing brittle failure of the overall structure. These and other limitations mean that the FEM concrete functionality can only be used to assess conceptual designs, whereas detailed design decisions critical to safety and performance should be left to qualified professionals.\n\n## Model geometry, loads and supports \n\nAlthough the FEM concrete routine does not have any additional requirements for geometry, loads and supports, it should be borne in mind that sharp corners and supports on edges or vertices can introduce stress concentrations that will lead to extremely high and unrealistic reinforcement ratios at or near those locations.\n\n## Material Parameters \n\nFEM Workbench has a special material object for reinforced materials, which combines a matrix material (e.g. concrete) and a reinforcement material (e.g. steel). For the analysis of reinforced concrete with FEM, the following parameters need to be specified, as a minimum:\n\nfor concrete:\n\n- Young's modulus (used in the CalculiX analysis to calculate elastic deformations and stresses)\n- Poisson ratio (same)\n- uniaxial compressive strength (used during post-processing in FEM to calculate the Mohr-Coulomb stress as an indicator for crushing or shear failure in concrete)\n- friction angle (same)\n\nfor steel:\n\n- yield strength (used during post-processing in FEM to calculate reinforcement ratios)\n\nPlease note that three types of analysis are performed:\n\n1. An elastic analysis using CalculiX (only utilizing the elastic parameters for concrete)\n2. A post-processing step to analyze the required reinforcement (only utilizing the yield strength of steel)\n3. Calculation of the Mohr-Coulomb stress (only using the strength parameters of concrete, i.e. uniaxial compressive strength and friction angle). The Mohr-Coulomb stress can be reviewed in the VTK pipeline.\n\n## Application\n\nIn the remainder of this article, a few practical cases will be analyzed to discuss the application of the method.\n\n### Simply supported beam with uniform load \n\nA 4.0x0.1x0.3m concrete beam is loaded by self-weight and a 100kN (25kN/m) distributed load.\n\nThe material parameters are as follows:\n\nfor concrete:\n\n- Young's modulus = 32 GPa (as per CalculiX default for concrete)\n- Poisson ratio = 0.17 (as per CalculiX default for concrete)\n- uniaxial compressive strength = 30 MPa (concrete type C30/37)\n- friction angle = 30 degrees\n\nfor steel:\n\n- yield strength = 500 MPa\n\nThe specific weight of the concrete is taken as 24kN/m\\^3\n\nThe required reinforcement in the x direction is very high (5.4%) and exceeds the typical maximum percentages allowed by code to prevent brittle failure. The high shear stresses at the supports also lead to a requirement of high reinforcement:\n\n
\n\nThe Mohr-Coulomb plot shows that the beam is indeed prone to crushing on the compression side (Mohr-Coulomb stress \\> 0.0), as would be expected with a very high reinforcement percentage:\n\n
\n\nBoth the reinforcement ratio and Mohr-Coulomb stress indicate that we have an issue and that we need to rethink our conceptual design. Potential solutions are to increase the beam dimensions or use pre-stressed concrete. Further details can be found in the following post:\n\n
\n\nThe required area of steel at the central support can be obtained with a ParaView integration filter applied to the mid-section of the beam:\n\n
\n\nThe panel at the bottom of this picture shows that the total required steel area at this cross section is 389.6 mm\\^2. As one reinforcement bar of diameter 12mm has a cross-sectional area of 113mm\\^2, it means that 4 bars would be required, giving a cross-sectional area of 452 mm\\^2. These would need to be placed near the top of the beam while maintaining sufficient concrete cover. The theoretical center of gravity for the reinforcement can be found by integration:\n\nCoG_y = Integrate (rx \\* y dy dz) / Integrate (rx dy dz)\n\nCoG_z = Integrate (rx \\* z dy dz) / Integrate (rx dy dz)\n\nThese integrals can also be determined with ParaView and give for the present case (see bottom panels in the above picture):\n\nCoG_y = 38961 / 389.6 = 100.0 mm\n\nCoG_z = 134917 / 389.6 = 346.3 mm\n\nwhich is, as expected, center-width and near the top.\n\nThe reinforcement requirement found above agrees well with that obtained using traditional methods:\n\n
\n\nThe above picture shows possible zones of constant reinforcement ratio for the design of reinforcement. Although a minimum reinforcement percentage of 0.2% is chosen, it will be hard to achieve such a low value in practice, given that the spacing should not exceed a practical limit (say 300mm). Even with a light reinforcement grid of 10mm bars (cross-sectional area = 78mm\\^2), the reinforcement ratio would then be 2 \\* 78 / (150 \\* 300) = 0.0035 (0.35%). (Note: factor 2 stems from the fact that the grid will be placed at both faces of the wall). If we add one more bar to the grid (halving the distance) the reinforcement ratio would double to 0.7% and one more would give approximately 1%. So most of the reinforcement requirement could be achieved by starting with a grid of d=10mm at 300x300mm spacing and adding bars in horizontal or vertical direction, as required. This would cover all but the requirement at the bottom of the wall, where we could add 3 bars d=12mm, giving a horizontal reinforcement ratio of 3 \\* 113mm\\^2 / (150mm \\* 150mm) = 0.015 (1.5%). Here it is assumed that the height of the bottom zone is 150mm. Alternatively, we could choose 2 bars of 16mm diameter, achieving the same reinforcement ratio for a zone of 180mm height.\n\nFinally, a review of the Mohr-Coulomb stress shows that no concrete crushing is expected in the wall.\n\n
\n\nThe required horizontal reinforcement (below in red) is determined by integration of the horizontal reinforcement ratio over the vertical cuts of interest (below in black). This is done using a Paraview integration filter.\n\n
\n\nThe insert to the above figure shows a comparison of reinforcement requirements (in mm\\^2 of steel) determined with FreeCAD to those in the FIB report.\n\nThe following shows how the integration over lines of interest works in Paraview:\n\n
\n\nFinally, a plot of compressive and tensile principal stresses to demonstrate how stresses flow through the beam.\n\n
\n\nThe tensile stress pattern suggests an alternative design concept using pre-stressing cables (superimposed in white). This concept is further elaborated in the following post:
**Mover**: moves objects during a time intervall along the motion Vector.\n-
**Rotator**: rotates objects during a time intervall. Further parameters are Rotation Axis/Direction, Center of Rotation and Angle.\n-
**Tranquillizer**: slows the render process if the animation runs to fast.\n-
**Photographer**: creates a picture of a given format and size to a render directory for every time step.\n-
**Plugger**: connects a newly created object to an already animated shuttle object or to a vertex of an animated sketch to enable using sketcher to calculate complex transformations with some constraints by means of the shuttle object.\n-
**Adjuster**: enables to calculate a value by a basic linear function. Now sketches can become animated by changing values in constraints.\n-
**Styler**: controls the Gui-object. Visibility, Transparency and Shape Color can be changed on the fly.\n-
**Billboard**: Billboard and Moviescreen are features to display extra information like texts or images during the animation.\n-
**Moviescreen**: Billboard and Moviescreen are features to display extra information like texts or images during the animation.\n-
**Extruder**: can be used to demonstrate the functionality of a miller or a 3D printer.\n-
**Viewpoint**:\n-
**Manager**:\n-
**Bounder**: limits the values of the Placement to an intervall. It is the projection of a motion to a min/max limited space.\n-
**Filler**: can be used to fill the volume of a part from bottom to top like to fill a bottle with wine. It can work as running slice trough the part like a ct scan.\n-
**Gearing**: animates the rotation of 2 or 3 gears or a star-planet-moon system.\n-
**Kartan**: animates a Kardan joint.\n-
**Scaler**:\n-
**Placer**:\n-
**Diagram**:\n-
**Collision**:\n-
**Combiner**:\n-
**AnimationControlPanel**:\n-
**Pather**:\n-
**Snapshot**:\n-
**ViewSequence**:\n-
**Speeder**:\n-
**Toucher**:\n-
**Trackreader**:\n-
**Abroller**:\n-
**Delta**:\n-
**Sum**:\n-
**Assembly2Controller**:\n-
**Connector**:\n\nOther\n\n-
**Animation**:\n-
**Case action**:\n-
**False action**:\n-
**Follow me**:\n-
**Loop action**:\n-
**Query action**:\n-
**Repeat action**:\n-
**Script action**:\n-
**True action**:\n-
**While action**:\n-
**Reset**:\n-
\n*Left: The [tree view](Tree_view.md) showing three objects that use Origin objects. Right: Representation of the Origin elements in the [3D view](3D_view.md).*\n\nThe axes and planes are objects of type `App::Line` and `App::Plane` respectively. Each of these elements can be hidden and unhidden individually with the **Space** bar. This can be useful when selecting the correct reference for creating other objects e.g. [Sketches](Sketch.md).\n\n
\n*A box added to a wall as a component.*\n\n## Usage\n\n1. Select the objects to be added together. The last object selected will be the host Arch object.\n2. Press the **
\n*Two axes objects positioned perpendicularly to each other to create a grid*\n\n## Usage\n\n1. Press the **
\n*Three [Arch Axis](Arch_Axis.md) objects combined into one [Arch AxisSystem](Arch_AxisSystem.md). An [Arch Structure](Arch_Structure.md) object uses this system as its **Axis* property, to have its shape duplicated at each intersection point.**\n\n## Usage\n\n1. Optionally, select the [Arch Axis](Arch_Axis.md) objects you wish to include in this system.\n2. Press the **