This firmware take as base the @PRUSA3D firmware developed for the MK3S+, we started to develop the firmware for the Vertex XL but finally we decided to be out of that project and continue to develop the firmware for the community without any kind of brand/company behind us. Because of that this is a fork of the Vertex XL firmware repository, just to save all our developments and continue the work which was done with many efforts. I want to say thanks to @Dainse and to many other people/users whose have been testing and proposing new features to the firmware in the past years.
- Reprint option, there is no need to navigate to the g-code anymore,just select on REPRINT.
- SteelSheet alert If you have more than 1 steel sheet defined then you will be notice of which sheet is selected before to start the print job. There is a configuration menu to disable this alert.
- Enable disable MMU A config menu to disable/enable MMU (if the mmu is connected) in order to be able to print flexible filament without phisically disconnect the MMU
- First layer flow adapted to noozle The flow is automatically adapted during the first layer calibration in function of the selected nozzle
- Custom Heatbed Custom Heatbed and axis size support, you can build the printer of the size of you want, there is no restrictions to use the MK52 Heatbed anymore.
- Bearmera support Now the Bearmera extruder is fully compatible, Selftest, beltest, XYZ calibration, ...
- MMU dinamic number of extruder support Now you are able to choose the number of extruders which support your MMU always between 5 and 10. This firmware will be a perfect fit for the @Ryper3D MMU upgrade which is available on PrusaPrinters
-
The first time after flash YOU HAVE TO configure the numbers of filaments that use your MMU device / La primera vez tras flashear el firmware SE TIENE que configurar el número de filamentos que usa tu dispositivo MMU. Go to Settings / Ir al menú Configuración:
Go to "Tune MMU" / Ir a Tune MMU:
Select Nr extruders (5 by default) / Seleccionar Nr extruders (5 por defecto):
And select the number of filaments / Y seleccionar number of filaments:
This setting is automatically stored on the EEPROM / Esta configuración se guarda automáticamente en la EEPROM:
-
Now we are ready to go to the "Filament Actions" Menu / Ahora estamos listos para usar el menú Filament Actions:
Select the filament of your needs using the filament selection menu (is limited to the number of filaments stored on the EEPROM) / Selecciona el filamento que necesites usando el menú de selección de filamento (está limitado al número de filamentos configurados en la EEPROM):
And perform any of the listed actions over that filament / Y ejecuta cualquiera de las acciones listadas sobre el filamento
This repository contains the source code and the development versions of the firmware running on the Original Prusa i3 MK3S/MK3/MK2.5S/MK2.5 line of printers.
The latest official builds can be downloaded from Prusa Drivers. Pre-built development releases are also available here.
The firmware for the Original Prusa i3 printers is proudly based on Marlin 1.0.x by Scott Lahteine (@thinkyhead) et al. and is distributed under the terms of the GNU GPL 3 license.
- Linux build
- Windows build
- Automated tests
- Documentation
- FAQ
-
Clone this repository and checkout the correct branch for your desired release version.
-
Set your printer model.
- For MK3 --> skip to step 3.
- If you have a different printer model, follow step 2.b from Windows build
-
Install GNU AWK
sudo apt-get install gawk
If you use mawk instead of gawk you get strange errors when multi language support is generated like:
awk: line 2: function strtonum never defined sed: couldn't write 4 items to stdout: Broken pipe ./lang-build.sh: 121: ./lang-build.sh: arithmetic expression: expecting EOF: "0x"awk: line 2: function strtonum never defined sed: couldn't write 4 items to stdout: Broken pipe tr: write error: Broken pipe ./lang-build.sh: 121: ./lang-build.sh: arithmetic expression: expecting EOF: "0x"awk: line 2: function strtonum never defined sed: couldn't write 4 items to stdout: Broken pipe tr: write error: Broken pipe tr: write error cut: write error: Broken pipeNG! - some texts not found in lang_en.txt! updating binary: primary language ids...awk: line 2: function strtonum never defined sed: couldn't flush stdout: Broken pipe -
Run
./build.sh- Output hex file is at
"PrusaFirmware/lang/firmware.hex". In the same folder you can hex files for other languages as well.
- Output hex file is at
-
Connect your printer and flash with PrusaSlicer ( Configuration --> Flash printer firmware ) or Slic3r PE.
- If you wish to flash from Arduino, follow step 2.c from Windows build first.
Notes:
The script downloads Arduino with our modifications and Rambo board support installed, unpacks it into folder PF-build-env-\<version\> on the same level, as your Prusa-Firmware folder is located, builds firmware for MK3 using that Arduino in Prusa-Firmware-build folder on the same level as Prusa-Firmware, runs secondary language support scripts. Firmware with secondary language support is generated in lang subfolder. Use firmware.hex for MK3 variant. Use firmware_\<lang\>.hex for other printers. Don't forget to follow step 2.b first for non-MK3 printers.
Note: Multi language build is not supported.
a. Install "Arduino Software IDE" from the official website https://www.arduino.cc -> Software->Downloads
It is recommended to use version "1.8.5", as it is used on our build server to produce official builds.
b. Setup Arduino to use Prusa Rambo board definition
- Open Arduino and navigate to File -> Preferences -> Settings
- To the text field
"Additional Boards Manager URLSs"addhttps://raw.githubusercontent.com/prusa3d/Arduino_Boards/master/IDE_Board_Manager/package_prusa3d_index.json - Open Board manager (
Tools->Board->Board manager), and installPrusa Research AVR Boards by Prusa Research
c. Modify compiler flags in platform.txt file
-
The platform.txt file can be found in Arduino installation directory, or after Arduino has been updated at:
"C:\Users\(user)\AppData\Local\Arduino15\packages\arduino\hardware\avr\(version)"If you can locate the file in both places, file from user profile is probably used. -
Add
"-Wl,-u,vfprintf -lprintf_flt -lm"to"compiler.c.elf.flags="before existing flag "-Wl,--gc-sections"For example:
"compiler.c.elf.flags=-w -Os -Wl,-u,vfprintf -lprintf_flt -lm -Wl,--gc-sections"
Notes:
In the case of persistent compilation problems, check the version of the currently used C/C++ compiler (GCC) - should be at leas 4.8.1;
If you are not sure where the file is placed (depends on how "Arduino Software IDE" was installed), you can use the search feature within the file system
Name collision for "LiquidCrystal" library known from previous versions is now obsolete (so there is no need to delete or rename original file/-s)
a. Clone this repositoryhttps://github.com/prusa3d/Prusa-Firmware/ to your local drive.
b. In the subdirectory "Firmware/variants/" select the configuration file (.h) corresponding to your printer model, make copy named "Configuration_prusa.h" (or make simple renaming) and copy it into "Firmware/" directory.
c. In file "Firmware/config.h" set LANG_MODE to 0.
d. Run "Arduino IDE"; select the file "Firmware.ino" from the subdirectory "Firmware/" at the location, where you placed the source code File->Open Make the desired code customizations; all changes are on your own risk!
e. Select the target board "Tools->Board->PrusaResearch Einsy RAMBo"
f. Run the compilation Sketch->Verify/Compile
g. Upload the result code into the connected printer Sketch->Upload
- or you can also save the output code to the file (in so called
HEX-format)"Firmware.ino.rambo.hex":Sketch->ExportCompiledBinaryand then upload it to the printer using the program"FirmwareUpdater"
note: this file is created in the directory"Firmware/"
notes: Script and instructions contributed by 3d-gussner. Use at your own risk. Script downloads Arduino executables outside of Prusa control. Report problems there. Multi language build is supported.
- follow the Microsoft guide https://docs.microsoft.com/en-us/windows/wsl/install-win10 You can also use the 'prepare_winbuild.ps1' powershell script with Administrator rights
- Tested versions are at this moment
-
Ubuntu and Debian, other may different
-
After the installation and reboot please open your Ubuntu bash and do following steps
-
run command
sudo apt-get update -
run command
sudo apt-get upgrade -
to install zip run
sudo apt-get install zip -
to install dos2unix run
sudo apt-get install dos2unix -
run
dos2unix PF-build.shto convert the windows line endings to unix line endings -
add a few lines at the top of
~/.bashrcby runningsudo nano ~/.bashrcexport OS="Linux" export JAVA_TOOL_OPTIONS="-Djava.net.preferIPv4Stack=true" export GPG_TTY=$(tty)
use
CRTL-Xto close nano and confirm to write the new entries -
restart Ubuntu/Debian bash
-
Now your Ubuntu/Debian subsystem is ready to use the automatic
PF-build.shscript and compile your firmware correctly
-
- Linux is case sensitive so please don't forget to use capital letters where needed, like changing to a directory
- To change the path to your Prusa-Firmware location you downloaded and unzipped
- Example: You files are under
C:\Users\<your-username>\Downloads\Prusa-Firmware-MK3 - use under Ubuntu the following command
cd /mnt/c/Users/<your-username>/Downloads/Prusa-Firmware-MK3to change to the right folder
- Example: You files are under
- Unix and Windows have different line endings (LF vs CRLF), use dos2unix to convert
- This should fix the
"$'\r': command not found"error - to install run
apt-get install dos2unix
- This should fix the
- If your Windows isn't in English the Paths may look different
Example in other languages
- English
/mnt/c/Users/<your-username>/Downloads/Prusa-Firmware-MK3will be on a German Windows/mnt/c/Anwender/<your-username>/Downloads/Prusa-Firmware-MK3
- English
- open Ubuntu bash shell
- change to your source code folder (case sensitive)
- run
./PF-build.sh - follow the instructions
notes: Script and instructions contributed by 3d-gussner. Use at your own risk. Script downloads Arduino executables outside of Prusa control. Report problems there. Multi language build is supported.
- Download and install the 64bit Git version https://git-scm.com/download/win
- Also follow these instructions https://gist.github.com/evanwill/0207876c3243bbb6863e65ec5dc3f058
- Download and install 7z-zip from its official website https://www.7-zip.org/ By default, it is installed under the directory /c/Program\ Files/7-Zip in Windows 10
- Run
Git-Bashunder Administrator privilege - navigate to the directory /c/Program\ Files/Git/mingw64/bin
- run
ln -s /c/Program\ Files/7-Zip/7z.exe zip.exe - If your Windows isn't in English the Paths may look different
Example in other languages
- English
/mnt/c/Users/<your-username>/Downloads/Prusa-Firmware-MK3will be on a German Windows/mnt/c/Anwender/<your-username>/Downloads/Prusa-Firmware-MK3 - English
ln -s /c/Program\ Files/7-Zip/7z.exe zip.exewill be on a Spanish Windowsln -s /c/Archivos\ de\ programa/7-Zip/7z.exe zip.exe
- English
- open Git-bash
- change to your source code folder
- run
bash PF-build.sh - follow the instructions
- c++11 compiler e.g. g++ 6.3.1
- cmake
- build system - ninja or gnu make
Create a folder where you want to build tests.
Example:
cd ..
mkdir Prusa-Firmware-test
Generate build scripts in target folder.
Example:
cd Prusa-Firmware-test
cmake -G "Eclipse CDT4 - Ninja" ../Prusa-Firmware
or for DEBUG build:
cmake -G "Eclipse CDT4 - Ninja" -DCMAKE_BUILD_TYPE=Debug ../Prusa-Firmware
Build it.
Example:
ninja
./tests
run doxygen in Firmware folder or visit https://prusa3d.github.io/Prusa-Firmware-Doc for doxygen generated output
Q:I built firmware using Arduino and I see "?" instead of numbers in printer user interface.
A:Step 1.c was omitted or you updated Arduino and now platform.txt located somewhere in your user profile is used.
Q:I built firmware using Arduino and my printer now speaks "Klingon" (nonsense characters and symbols are displayed @^#$&*°;~ÿ)
A:Step 2.c was omitted.
Q:What environment does Prusa use to build its official firmware releases?
A:Our production builds are 99.9% equivalent to https://github.com/prusa3d/Prusa-Firmware#linux this is also easiest way to build as only one step is needed - run a single script, which downloads patched Arduino from GitHub, builds using it, then extracts translated strings and creates language variants (for MK2x) or language hex file for external SPI flash (MK3x). But you need Linux or Linux in a virtual machine. This is also what happens when you open a pull request to our repository - all variants are built by Travis http://travis-ci.org/ (to check for compilation errors). You can see, what is happening in .travis.yml. It would be also possible to get hex built by Travis, only the deploy step is missing in .travis.yml. You can find inspiration on how to deploy hex in Travis and how to setup Travis in https://github.com/prusa3d/MM-control-01/ repository. The final hex is located in ./lang/firmware.hex - community reproduced this for Windows in https://github.com/prusa3d/Prusa-Firmware#using-linux-subsystem-under-windows-10-64-bit or https://github.com/prusa3d/Prusa-Firmware#using-git-bash-under-windows-10-64-bit .
Q:Why are build instructions for Arduino a mess?
Y:We are too lazy to ship a proper board definition for Arduino. We plan to switch to CMake + ninja to be inherently multiplatform, easily integrate build tools, suport more IDEs, get 10 times shorter build times and be able to update compiler whenever we want.