{"id": "freecad-docs:wiki/3D_view.md", "text": "# 3D view\n## Introduction\n\n \n\nThe [3D view](3D_view.md) of FreeCAD is an instance of a Coin3D [scenegraph](Scenegraph.md) that forms the most important window in the [interface](interface.md). Coin3D is a library that implements the OpenInventor 2.1 scene description standard.\n\nCertain properties of the view, like background color, [mouse navigation](Mouse_navigation.md) style, and zooming steps, can be configured in the [preferences editor](Preferences_Editor.md).\n\n\n\n\n*The [Draft Workbench](3D_view]]_is_a_component_of_the_FreeCAD_[[interface]]. By default it shows a small widget with coordinate axes, and the navigation cube also with coordinate axes; the grid can be displayed and configured by loading the [[Draft Workbench.md).*\n\n## Context menu \n\nThe options in the context menu of the 3D view depend on the selected object(s) and the currently active workbench. To display this menu optionally select one or more objects and then right-click in the 3D view.\n\n## Details\n\nFreeCAD uses the Quarter library to use Coin3D in a Qt environment.\n\nIt is possible to interact directly with the 3D view scenegraph from the [Python console](Python_console.md) by using the Python library Pivy.\n\nFor more information see the power user documentation:\n\n- [Scenegraph](Scenegraph.md), description of Coin3D.\n- [Pivy](Pivy.md), usage of Coin3D from the Python console.\n- [Third party libraries](Third_Party_Libraries.md) used by FreeCAD.\n- [Coin3D](https://grey.colorado.edu/coin3d/index.html) C++ documentation.\n\n {{Interface navi}}\n\n\n---\n⏵ [documentation index](../README.md) > 3D view", "source": "freecad-docs", "added": "2026-11-07", "created": "", "token_count": 415, "license": "CC0-1.0", "author": "FreeCAD contributors"}
{"id": "grbl-docs:doc/csv/alarm_codes_en_US.csv", "text": "\"Alarm Code in v1.1+\",\" Alarm Message in v1.0-\",\" Alarm Description\"\n\"1\",\"Hard limit\",\"Hard limit has been triggered. Machine position is likely lost due to sudden halt. Re-homing is highly recommended.\"\n\"2\",\"Soft limit\",\"Soft limit alarm. G-code motion target exceeds machine travel. Machine position retained. Alarm may be safely unlocked.\"\n\"3\",\"Abort during cycle\",\"Reset while in motion. Machine position is likely lost due to sudden halt. Re-homing is highly recommended.\"\n\"4\",\"Probe fail\",\"Probe fail. Probe is not in the expected initial state before starting probe cycle when G38.2 and G38.3 is not triggered and G38.4 and G38.5 is triggered.\"\n\"5\",\"Probe fail\",\"Probe fail. Probe did not contact the workpiece within the programmed travel for G38.2 and G38.4.\"\n\"6\",\"Homing fail\",\"Homing fail. The active homing cycle was reset.\"\n\"7\",\"Homing fail\",\"Homing fail. Safety door was opened during homing cycle.\"\n\"8\",\"Homing fail\",\"Homing fail. Pull off travel failed to clear limit switch. Try increasing pull-off setting or check wiring.\"\n\"9\",\"Homing fail\",\"Homing fail. Could not find limit switch within search distances. Try increasing max travel, decreasing pull-off distance, or check wiring.\"\n\"10\",\"Homing fail\",\"Homing fail. Second dual axis limit switch failed to trigger within configured search distance after first. Try increasing trigger fail distance or check wiring.\"", "source": "grbl-docs", "added": "2026-11-07", "created": "", "token_count": 323, "license": "GPL-3.0-or-later; bundled Atmel files retain their BSD terms", "author": "Grbl contributors"}
{"id": "linuxcnc-docs:docs/src/common/linux-faq.adoc", "text": ":lang: en\n:toc:\n\n[[cha:linux-faq]]\n= Linux FAQ(((Linux FAQ)))\n\nThese are some basic Linux commands and techniques for new to Linux\nusers. More complete information can be found on the web or by using\nthe man pages.\n\n== Automatic Login(((Automatic Login)))\n\n=== Debian\n\nDebian Stretch uses the Xfce desktop environment by default, with the lightDM\ndisplay manager lightDM. To get automatic login with Stretch:\n\n* In a terminal, use the command:\n\n----\n$ /usr/sbin/lightdm --show-config\n----\n\n* Make a note of the absolute path to the configuration file lightdm.conf.\n* Edit that file with a pure text editor (gedit, nano, etc), as root.\n* Find and uncomment the lines:\n\n----\n#autologin-user=\n#autologin-user-timeout=0\n----\n\n* Set autologin-user=your_user_name\n* Save and reboot.\n\n=== Ubuntu\n\nWhen you install LinuxCNC with the Ubuntu LiveCD the default is to have to\nlog in each time you turn the computer on. To enable automatic login go\nto 'System > Administration > Login Window'. If it is a fresh install the\nLogin Window might take a second or three to pop up. You will have to\nhave your password that you used for the install to gain access to the\nLogin Window Preferences window. In the Security tab check off Enable\nAutomatic Login and pick a user name from the list (that would be you).\n\n== Automatic Startup\n\nTo have LinuxCNC start automatically with your config after turning on the\ncomputer go to 'System > Preferences > Sessions > Startup Applications',\nclick Add. Browse to your config and select the .ini file. When the file\npicker dialog closes, add linuxcnc and a space in front of the path to your .ini file.\n\nExample:\n\n----\nlinuxcnc /home/mill/linuxcnc/config/mill/mill.ini\n----\n\nThe documentation refers to your respective .ini file as INI-file.\n\n[[faq:terminal]]\n== Terminal\n\nMany things need to be done from the terminal like checking the kernel message\nbuffer with 'dmesg'. Ubuntu and Linux Mint have a keyboard shortcut Ctrl + Alt + t.\nDebian Stretch does not have any keyboard shortcuts defined.\nIt can be easily created with the 'Configuration Manager'.\nMost modern file managers support the right key to open a terminal just\nmake sure your right clicking on a blank area or a directory not a file name.\nMost OS's have the terminal as a menu item, usually in Accessories.\n\n[[faq:man-pages]]\n== Man Pages(((Man Pages)))\n\nA man page (short for manual page) is a form of software documentation\nusually found on a Unix or Unix-like operating system like Linux.\n\nTo view a man page open up a terminal to find out something about the\nfind command in the terminal window type:\n\n----\nman find\n----\n\nUse the Page Up and Page Down keys to view the man page and the Q key\nto quit viewing.\n\n[NOTE]\nViewing the man page from the terminal may not get the expected man page.\nFor example if you type in man abs you will get the C abs not the LinuxCNC\nabs. It is best to view the LinuxCNC man pages in the HTML documents.\n\n== List Modules\n\nSometimes when troubleshooting you need to get a list of modules that\nare loaded. In a terminal window type:\n\n----\nlsmod\n----\n\nIf you want to send the output from lsmod to a text file in a terminal\nwindow type:\n\n----\nlsmod > mymod.txt\n----\n\nThe resulting text file will be located in the home directory if you\ndid not change directories when you opened up the terminal window and\nit will be named mymod.txt or what ever you named it.\n\n== Editing a Root File\n\nWhen you open the file browser and you see the owner of the file is\nroot you must do extra steps to edit that file. Editing some root files\ncan have bad results. Be careful when editing root files. Generally, you\ncan open and view most root files, but they will open in 'read only'\nmode.\n\n=== The Command Line Way\n\nOpen a terminal and type\n\n----\nsudo gedit\n----\n\nOpen the file with File > Open > Edit\n\n=== The GUI Way\n\n. Right click on the desktop and select Create Launcher\n. Type a name in like sudo edit\n. Type 'gksudo \"gnome-open %u\"' as the command and save the launcher to\n your desktop\n. Drag a file onto your launcher to open and edit\n\n=== Root Access\n\nIn Ubuntu you can become root by typing in \"sudo -i\" in a terminal\nwindow then typing in your password. Be careful, because you can really\nfoul things up as root if you don't know what you're doing.\n\n== Terminal Commands\n\n=== Working Directory\n\nTo find out the path to the present working directory in the terminal\nwindow type:\n\n----\npwd\n----\n\n[[faq:cd]]\n=== Changing Directories(((Changing Directories)))(((cd)))\n\nTo change the working directory to the one one level up, i.e., the parent directory, in the terminal window type:\n\n----\ncd ..\n----\n\nTo move up two levels in the terminal window type:\n\n----\ncd ../..\n----\n\nTo move directly to your home directory, in the terrminal window use the cd command with no arguments:\n\n----\ncd\n----\n\nTo move down to the linuxcnc/configs subdirectory in the terminal window\ntype:\n\n----\ncd linuxcnc/configs\n----\n\n=== Listing files in a directory\n\nTo view a list of all the files and subdirectories in the terminal window type:\n\n----\ndir\n----\n\nor\n\n----\nls\n----\n\n=== Finding a File\n\nThe find command can be a bit confusing to a new Linux user. The basic\nsyntax is:\n\n----\nfind starting-directory parameters actions\n----\n\nFor example to find all the .ini files in your linuxcnc directory you\nfirst need to use the pwd command to find out the directory.\n\nOpen a new terminal window and type:\n\n----\npwd\n----\n\nAnd pwd might return the following result:\n\n----\n/home/joe\n----\n\nWith this information put the command together like this:\n\n----\nfind /home/joe/linuxcnc -name \\*.ini -print\n----\n\nThe -name is the name of the file your looking for and the -print\ntells it to print out the result to the terminal window.\nThe \\*.ini tells find to return all files that have the .ini extension.\nThe backslash is needed to escape the shell meta-characters. See the find\nman page for more information on find.\n\n=== Searching for Text\n\n----\ngrep -irl 'text to search for' *\n----\n\nThis will find all the files that contain the 'text to search for' in the\ncurrent directory and all the subdirectories below it, while\nignoring the case. The -i is for ignore case and the -r is for\nrecursive (include all subdirectories in the search). The -l option will\nreturn a list of the file names, if you leave the -l off you will also\nget the text where each occurrence of the \"text to search for\" is found.\nThe * is a wild card for search all files. See the grep man page for more\ninformation.\n\n=== Diagnostic Messages\n\nTo view the diagnostic messages use \"dmesg\" from the command window. To\nsave the diagnostic messages to a file use the redirection operator '>', like\nthis:\n\n----\ndmesg > bootmsg.txt\n----\n\nThe contents of this file can be copied and pasted on line to share\nwith people trying to help you diagnose your problem.\n\nTo clear the message buffer type this:\n\n----\nsudo dmesg -c\n----\n\nThis can be helpful to do just before launching LinuxCNC, so that there will\nonly be a record of information related to the current launch of LinuxCNC.\n\nTo find the built in parallel port address use grep to filter the information\nout of dmesg.\n\nAfter boot up open a terminal and type:\n\n----\ndmesg|grep parport\n----\n\n== Convenience Items\n\n=== Terminal Launcher\n\nIf you want to add a terminal launcher to the panel bar on top of the\nscreen you typically can right click on the panel at the top of the\nscreen and select \"Add to Panel\". Select Custom Application Launcher\nand Add. Give it a name and put gnome-terminal in the command box.\n\n== Hardware Problems\n\n=== Hardware Info\n\nTo find out what hardware is connected to your motherboard in a\nterminal window type:\n\n----\nlspci -v\n----\n\n=== Monitor Resolution\n\nDuring installation Ubuntu attempts to detect the monitor settings. If\nthis fails you are left with a generic monitor with a maximum\nresolution of 800x600.\n\nInstructions for fixing this are located here:\n\nhttps://help.ubuntu.com/community/FixVideoResolutionHowto[https://help.ubuntu.com/community/FixVideoResolutionHowto]\n\n== Paths\n\n.Relative Paths\nRelative paths are based on the startup directory which is the directory\ncontaining the INI-file. Using relative paths can facilitate relocation of\nconfigurations but requires a good understanding of linux path specifiers.\n\n....\n./f0 is the same as f0, e.g., a file named f0 in the startup directory\n../f1 refers to a file f1 in the parent directory\n../../f2 refers to a file f2 in the parent of the parent directory\n../../../f3 etc.\n....\n\n// vim: set syntax=asciidoc:", "source": "linuxcnc-docs", "added": "2026-11-07", "created": "", "token_count": 1963, "license": "GFDL-1.1-or-later", "author": "LinuxCNC contributors"}
{"id": "linuxcnc-source:configs/apps/parport/parport_test_es.xml", "text": "\n\n\n \n (\"Helvetica\",16)\n \n RIDGE\n 2\n \n \n \"led-01\"\n 25\n \"green\"\n \"red\"\n \n\n \n \n \"led-02\"\n 25\n \"green\"\n \"red\"\n \n \n\n \n RIDGE\n 2\n \n \n \"led-03\"\n 25\n \"green\"\n \"red\"\n \n\n \n \n \"led-04\"\n 25\n \"green\"\n \"red\"\n \n \n\n \n RIDGE\n 2\n \n \n \"led-05\"\n 25\n \"green\"\n \"red\"\n \n\n \n \n \"led-06\"\n 25\n \"green\"\n \"red\"\n \n \n\n \n RIDGE\n 2\n \n \n \"led-07\"\n 25\n \"green\"\n \"red\"\n \n\n \n \n \"led-08\"\n 25\n \"green\"\n \"red\"\n \n \n\n \n RIDGE\n 2\n \n \n \"led-09\"\n 25\n \"green\"\n \"red\"\n \n\n \n \n \"led-14\"\n 25\n \"green\"\n \"red\"\n \n \n\n \n RIDGE\n 2\n \n \n \"led-16\"\n 25\n \"green\"\n \"red\"\n \n\n \n \n \"led-17\"\n 25\n \"green\"\n \"red\"\n \n \n\n \n\n \n (\"Helvetica\",16)\n\n \n RIDGE\n 2\n \n \n \"led-10\"\n 25\n \"green\"\n \"red\"\n \n \n\n \n RIDGE\n 2\n \n \n \"led-11\"\n 25\n \"green\"\n \"red\"\n \n \n\n \n RIDGE\n 2\n \n \n \"led-12\"\n 25\n \"green\"\n \"red\"\n \n \n\n \n RIDGE\n 2\n \n \n \"led-13\"\n 25\n \"green\"\n \"red\"\n \n \n\n \n RIDGE\n 2\n \n \n \"led-15\"\n 25\n \"green\"\n \"red\"\n \n \n\n\n \n\n", "source": "linuxcnc-source", "added": "2026-11-07", "created": "", "token_count": 1692, "license": "GPL-2.0/LGPL-2.1; file-level notices govern", "author": "LinuxCNC contributors"}
{"id": "machinekit-cnc-source:configs/ARM/BeagleBone/BeBoPr++/BeBoPr.postgui.hal", "text": "# Include your customized HAL commands here\n# The commands in this file are run after the AXIS GUI (including PyVCP panel) starts\n\nnet e0.temp.set => pyvcp.E0.Temp.set\nnet e0.temp.meas => pyvcp.E0.Temp\nnet bed.temp.set => pyvcp.Bed.Temp.set\nnet bed.temp.meas => pyvcp.Bed.Temp", "source": "machinekit-cnc-source", "added": "2026-11-07", "created": "", "token_count": 84, "license": "GPL-2.0/LGPL-2.1; file-level notices govern", "author": "Machinekit contributors"}