MM-control-01

MMU 3-axis stepper control

Latest stable versions & link to RELEASES for Precompiled HEX files.

MMU: V#: 2.1.8 RC2 B#: 304
MK3: B#: 2386

https://github.com/TheZeroBeast/MM-control-01/releases

Points of Notes

You DO NOT have to reset to factory settings, all the same EEPROM data structures are used as STOCK-PRUSA-FW
Bowden Length is still important as load is optimised to minimise the posibility of grinding in the event of the
MK3-FSensor not triggering, rare if setup correct, dust/particles still build up over time.
DEFAULT FACTORY BOWDEN LENGETH OF 350mm
POWER PANIC is now operational and will allow autorecover/continue when SD Printing
Jam Detection is now able to be enabled for any filament with start gcode M219 E and will
aim to catch when a jam occurs usually resulting in missed layer/s. No longer requiring a Slic3rPE-Alpha slice.
Action commands added for failure states that can be used for notifications in Octoprint

1. // action:m600
2. // action:mmuAttention
3. // action:mmuFailedLoad1
4. // action:mmuFailedLoad2
5. // action:mmuFailedUnload
6. // action:jamDetected

Compatibility

At this time only the MK3 is compatible with this firmware. If there are any AVR programmers that could
help make this compatible with the MK2S or MK2.5, your help would be greatly appreciated. If you are so inclined,
you could potentially compile this code for your hardware and have a 24v 5a supply powering the MMU2 unit.
Then it will work the same as the MK3.

STEPS TO FIRST GET SETUP AND PRINTING WITH MY FW

1. Adjust BOWDEN_LENGTH in SETUP menu (MK3 LCD Messages to guide you will appear)
   (NOTE ONLY FIRST FILAMENT CHANNEL IS CALIBRATED)

   1. Move selector all the way to the RIGHT with RIGHT button to Position 6 which is SERVICE POSITION
   2. Enter SETUP menu using MIDDLE button while on SERVICE POSITION
   3. As per STOCK FW, use LEFT button to move LED to fourth position
   4. Use MIDDLE button to enter calibration
   5. Use MIDDLE button again to load for Bowden Length Calibration
   6. Use LEFT/RIGHT buttons to adjust until flush with end of tube when detatched from extruder
   7. Use MIDDLE button to unload
   8. Use LEFT button to save and exit

2. Adjust FSensor to BONDTECH Steps in SETUP menu (MK3 LCD Messages to guide you will appear)

   1. Move selector all the way to the RIGHT with RIGHT button to Position 6 which is SERVICE POSITION
   2. Enter SETUP menu using MIDDLE button while on SERVICE POSITION
   3. As per STOCK FW, use LEFT button to move LED to fourth position
   4. Use MIDDLE button to enter calibration
   5. Use RIGHT button to load for FSensor to BondTech Length Calibration
   6. Use LEFT/RIGHT buttons to adjust until end of filament is in middle of BondTech gears
   7. Use MIDDLE button to save and exit

3. Update Slic3r Load/Unload Speeds & MMU Printer Parameters, add M219 E in filament start gcode if desired

• Note that from previous versions the cooling length is reduced to increase distance to heatbreak
  This means the cooling move count needs to double from what you have to have same amount of cooling time.
  

4. Blade isn't being used and can be removed. It has been known to add resistance to selector.

5. Get familiar with the differences in failure states and recovery procedures from STOCK

6. Happy PRINTING!

When in error state Active Extruder & or Previous Extruder LED/s will blink

RED and GREEEN Idicate F.I.N.D.A. State @ Load Failure

• Troubleshoot issue, usually was due to being caught on an edge or ground section of filament
  • Note: Failed LOAD where filament is found partly in Extruder requires a burst of air to clean MK3-FSensor
  • RIGHT Button can now be used to retract slowely back to park (LED goes green to advise you can try load again)
• If printer has shut down heaters, click MK3 wheel before clearing MMU2 issue with middle button
• ALWAYS ensure filament pulled clear of selector (Auto as above or manually)
• Push middle button to rehome and continue
  • If nothing happens, filament is in FINDA, check again
  • If load fails again, give MK3-FSensor another burst of air and try again
  • IF FSENSOR FAILED/DEAD LCD WILL DISPLAY FSensor Disabled (Stop Print and Diagnose FSensor Fault)

RED and GREEEN Idicate F.I.N.D.A. State pluss GREEN for next extruder @ Unload Failure

• Troubleshoot issue, usually was due to ground section of filament
  • Note: If fail on UNLOAD the LED will show on the next extruder instead of current
• If printer has shut down heaters, click MK3 wheel before clearing MMU2 issue with middle button
• ALWAYS ensure filament pulled clear of selector.
• Push middle button to rehome and continue
  • If nothing happens, filament is in FINDA, check again

Example Octoprint Serial Communications for a successful load using MK3-FSensor

Building this custom setup

This is configured to work directly with MMU2 with matching MK3 FW at link below to load filament to Extruder Laser Filament Sensor and unload to FINDA Sensor.

https://github.com/TheZeroBeast/Prusa-Firmware

Table of contents

• Building
  • Cmake
    • Automatic, remote, using travis-ci
    • Automatic, local, using script and prepared tools package
    • Manually with installed tools
  • Arduino
  • PlatformIO
• Flashing
• Building documentation

Building

Cmake

Automatic, remote, using travis-ci

Create new github user, eg. your_user_name-your_repository_name-travis. This step is not mandatory, only recomended to limit access rights for travis to single repository. Grant this user access to your repository. Register this user on https://travis-ci.org/. Create API key for this user. In Github click on this user, settings, Developer settings, Personal access tokens, Generate new token, select public_repo, click on Generate token. Copy this token. Login into https://travis-ci.org/ enable build of your repository, click on repository setting, add environment variable ACCESS_TOKEN. As value paste your token.

Each commit is build, but only for tagged commits MM-control-01.hex is attached to your release by travis.

Automatic, local, using script and prepared tools package

Linux

You need unzip and wget tools.

run ./build.sh

It downloads neccessary tools, extracts it to ../MM-build-env-<version>, creates ../MM-control-01-build folder, configures build scripts in it and builds it using ninja.

Windows

Download MM-build-env-Win64-.zip from https://github.com/prusa3d/MM-build-env/releases. Unpack it. Run configure.bat. This opens cmake-gui with preconfigured tools paths. Select path where is your source code located, select where you wish to build - out of source build is recomended. Click on generate, select generator - Ninja, or <Your favourite IDE> - Ninja.

Run build.bat generated in your binary directory.

Manually with installed tools

You need cmake, avr-gcc, avr-libc and cmake supported build system (e.g. ninja) installed.

Out of source tree build is recommended, in case of Eclipse CDT project file generation is necceessary. If you don't want out of source tree build, you can skip this step.

cd ..
mkdir MM-control-01_cmake
cd MM-control-01_cmake

Generate build system - consult cmake --help for build systems generators and IDE project files supported on your platform.

cmake -G "build system generator" path_to_source

example 1 - build system only

cmake -G "Ninja" ../MM-control-01

example 2 - build system and project file for your IDE

cmake -G "Eclipse CDT4 - Ninja ../MM-control-01

Invoke build system you selected in previous step. Example:

ninja

file MM-control-01.hex is generated.

Arduino

Recomended version is arduino 1.8.5.
in MM-control-01 subfolder create file version.h
use version.h.in as template, replace ${value} with numbers or strings according to comments in template file.
create file dirty.h with content if you are building unmodified git commit

#define FW_LOCAL_CHANGES 0

or

#define FW_LOCAL_CHANGES 1

if you have uncommitted local changes.

Adding MMUv2 board

In Arduino IDE open File / Settings
Set Additional boards manager URL to:
https://raw.githubusercontent.com/prusa3d/Arduino_Boards/master/IDE_Board_Manager/package_prusa3d_index.json
Open Tools / Board: / Boards manager... Install Prusa Research AVR Boards by Prusa Research
which contains only one board:
Original Prusa i3 MK3 Multi Material 2.0

Select board Original Prusa i3 MK3 Multi Material 2.0

Bootloader binary is shipped with the board, source is located at https://github.com/prusa3d/caterina

Build

click verify to build

PlatformIO

PlatformIO build is not supported by Prusa Research, please report any PlatformIO related issues at https://github.com/awigen/MM-control-01/issues

Flashing

Windows

Arduino

click Upload

Slic3er

Hex file needs to be edited to be recognized as for MMUv2 in case of Arduino build. This is done automatically in cmake build.

Add following line to the begining of MM-control-01.hex:

; device = mm-control

Avrdude

Board needs to be reset to bootloader. Bootloader has 5 seconds timeout and then returns to the application.

This can be accomplished manually by clicking reset button on MMU, or programmatically by opening and closing its virtual serial line at baudrate 1500.

Than flash it using following command, replace <virtual serial port> with CDC device created by MMU usually com<nr.> under Windows and /dev/ttyACM<nr.> under Linux. -b baud rate is don't care value, probably doesn't have to be specified at all, as there is no physical uart.

avrdude -v -p atmega32u4 -c avr109 -P <virtual serial port> -b 57600 -D -U flash:w:MM-control-01.ino.hex:i

Linux

Same as Windows, but there is known issue with ModemManager:

If you have the modemmanager installed, you either need to deinstall it, or blacklist the Prusa Research USB devices:

/etc/udev/rules.d/99-mm.rules

# Original Prusa i3 MK3 Multi Material 2.0 upgrade
ATTRS{idVendor}=="2c99", ATTRS{idProduct}=="0003", ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="2c99", ATTRS{idProduct}=="0004", ENV{ID_MM_DEVICE_IGNORE}="1"

$ sudo udevadm control --reload-rules

A request has been sent to Ubuntu, Debian and ModemManager to blacklist the whole Prusa Research VID space.

https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1781975

https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=modemmanager

and reported to https://lists.freedesktop.org/archives/modemmanager-devel/2018-July/006471.html

Building documentation

Run doxygen in MM-control-01 folder. Documentation is generated in Doc subfolder.