Pin Mapping refers to the relationship between assigned “pin numbers” and the actual hardware ports on the CPU. Marlin uses FastIO macros whenever possible because direct port manipulation is many times faster than the pin functions provided by Arduino.h. FastIO and Pin MappingįastIO is a set of macros that allows Marlin to read and write pins quickly, using the same code on all processors. See the boards list at the bottom of this page for a complete list of boards supported in the latest release of Marlin. This example selects a RAMPS 1.4 board with the 12V power MOSFET connectors arranged in Extruder, Fan, Bed (EFB) order: To build Marlin for a specific board, set the MOTHERBOARD option in Configuration.h. Some boards will need a new PlatformIO environment with custom build settings. Most pins files stand alone, but some form the basis for related pins files. Pins files define which Marlin functions use which board pins. Manages pin definitions, including the appropriate pins_BOARD.h file for the specified MOTHERBOARD. Set MOTHERBOARD to one of the boards listed here. Several files in the Marlin source code provide hardware support, but the files supporting the core electronics are: FileĬontains the full list of boards supported by Marlin. The Hardware Abstraction Layer created for Marlin 2.0 provides a consistent set of interfaces, making it much easier to add support for new platforms. Originally Marlin was designed to run on low-powered 8-bit AVR boards, but starting with Marlin 1.1.9 it has gained support for dozens of ARM-based boards. Marlin supports a wide variety of 3D printers, including all RAMPS variants, and is adaptable to virtually any Arduino/Genuino-based electronics through pin-mapping - associating pins with their functions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |