MMU2s selector stepper not moving at all and flashing mmu2 impossible
 
Notifications
Clear all

MMU2s selector stepper not moving at all and flashing mmu2 impossible  

  RSS
viralata
(@mathieu-d2)
New Member
MMU2s selector stepper not moving at all and flashing mmu2 impossible

Hello all, herer are the troubles I have with my mmu2:

I managed to print some small files with 3 colors, then started to have difficulties with a bigger one, the famous stripped lizard:

  • inversions of colors on some layers,
  • multiple "mmu2 needs your attention" error until I finaly restarted the printer

I checked all the filaments and the pinda, everything is fine but the selector engine was not moving at all anymore., then I realized that on of the cables of the pinda was broken on the pin, I soldered it back, but still no selector move:

  • the mmu2 starts, the idler stepper motor moves, but not the selector one at start
  • the selector stepper is blocked when powered but free to move when the printer is off
  • if I change the filament manually by pressing one of the mmu2 button, I have the 5 leds blinking red
  • I tried to flash the mmu2 with the firmware (though I was using the latest one (1-0-5) but I have 2 types of error on my linux with slic3r 1.42.0.beta2:
    • "avrdude-slic3r: ser_open(): can't open device "/dev/ttyACM0": Permission denied avrdude-slic3r: Could not open port: /dev/ttyACM0
    • "Error: open: Device or resource busy"

I have no idea what to do now:

  • could I invert the stepepr motors on the mmu2 card to check if it's a stepper problem or a card one ?
  • how can I flash the mmu2 ?

Thanks for your answers

 

Opublikowany : 24/04/2019 9:55 am
viralata
(@mathieu-d2)
New Member
Topic starter answered:
RE: MMU2s selector stepper not moving at all and flashing mmu2 impossible

Update: I ran slic3r with sudo for the permission problem, the flash failed but after a longer time and here is the log:

Flashing Prusa MMU 2.0 Control, looking for VID/PID 0x2c99/3 or 0x2c99/4 ...
Found VID/PID 0x2c99/4 at `/dev/ttyACM0`, rebooting the device ...
Found VID/PID 0x2c99/3 at `/dev/ttyACM0`, flashing ...
avrdude-slic3r -v -p atmega32u4 -c avr109 -P /dev/ttyACM0 -b 57600 -D -U flash:w:0:/home/mat/Téléchargements/prusa3d_fw_3_7_0_MK3S_1_0_5_MMU2S(1)/prusa3d_fw_MMU2board_1_0_5.hex:i

avrdude-slic3r: Version 6.3-20160220-prusa3d, compiled on Apr 14 2019 at 10:44:13
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch

Using Port : /dev/ttyACM0
Using Programmer : avr109
Overriding Baud Rate : 57600
AVR Part : ATmega32U4
Chip Erase delay : 9000 us
PAGEL : PD7
BS2 : PA0
RESET disposition : dedicated
RETRY pulse : SCK
serial program mode : yes
parallel program mode : yes
Timeout : 200
StabDelay : 100
CmdexeDelay : 25
SyncLoops : 32
ByteDelay : 0
PollIndex : 3
PollValue : 0x53
Memory Detail :

Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
eeprom 65 20 4 0 no 1024 4 0 9000 9000 0x00 0x00
flash 65 6 128 0 yes 32768 128 256 4500 4500 0x00 0x00
lfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
hfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
efuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
lock 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
calibration 0 0 0 0 no 1 0 0 0 0 0x00 0x00
signature 0 0 0 0 no 3 0 0 0 0 0x00 0x00

Programmer Type : butterfly
Description : Atmel AppNote AVR109 Boot Loader

Connecting to programmer: Found programmer: Id = "CATERIN"; type = S
Software Version = 1.0; No Hardware Version given.
Programmer supports auto addr increment.
Programmer supports buffered memory access with buffersize=128 bytes.

Programmer supports the following devices:
Device code: 0x44

avrdude-slic3r: devcode selected: 0x44
avrdude-slic3r: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude-slic3r: Device signature = 0x1e9587 (probably m32u4)
avrdude-slic3r: safemode: hfuse reads as D8
avrdude-slic3r: safemode: efuse reads as CB
avrdude-slic3r: reading input file "/home/mat/Téléchargements/prusa3d_fw_3_7_0_MK3S_1_0_5_MMU2S(1)/prusa3d_fw_MMU2board_1_0_5.hex"
avrdude-slic3r: writing flash (20422 bytes):

Writing | ########################avrdude-slic3r: error: programmer did not respond to command: set addr
#avrdude-slic3r: butterfly_recv(): programmer is not responding
avrdude-slic3r: error: programmer did not respond to command: write block
***failed;
######################### | 100% 14.13s

avrdude-slic3r: failed to write flash memory, rc=-1

avrdude-slic3r: butterfly_recv(): programmer is not responding
avrdude-slic3r: safemode: hfuse reads as D8
avrdude-slic3r: safemode: efuse reads as CB
avrdude-slic3r: safemode: Fuses OK (E:CB, H:D8, L:FF)

avrdude-slic3r done. Thank you.

 

Opublikowany : 24/04/2019 10:22 am
Roy
 Roy
(@roy)
Eminent Member
RE: MMU2s selector stepper not moving at all and flashing mmu2 impossible

The error message can have two reasons:

1. The port is already in use. Do you have any other software running which might use the port?

2. The user has no rigths to access the port.

Opublikowany : 24/04/2019 12:17 pm
viralata
(@mathieu-d2)
New Member
Topic starter answered:
RE: MMU2s selector stepper not moving at all and flashing mmu2 impossible

I finaly managed to flash the MMU2 board thanks to a post here. But it did'nt solve my othe problem:

The selector stepper is not moving at all for a week now, neither at start, nor if I press the buttons to change filament manualy.

 

Opublikowany : 09/05/2019 8:56 am
gnat
 gnat
(@gnat)
Noble Member
RE: MMU2s selector stepper not moving at all and flashing mmu2 impossible

Sounds like you are using Linux. I ran into the same issue as your second problem. There is a simple fix, but it sounds like you already found and got past that.

According to the manual the selector will not attempt to move at start up (in the event that there is filament in it already, though I don't know why it can't check the FINDA for that...).

I had similar issues when I first connected mine up and no matter what I did it wouldn't move at all. What finally worked for me was to connect to the printers serial port (screen /dev/ttyACM0 11520) and I issued the T0, T1, T2, T3, and T4 commands a few times to get the selector moving and it's mostly been OK since then.

If you can't get it to move that way, I'd suggest double checking your connections to make sure it is plugged into the board and the board is plugged into the Rambo securely. Next up, unbolt the motor and pull it free to make sure that the selector itself isn't seized up on a piece of filament or the blade hasn't come loose and bound things up.

MMU tips and troubleshooting
Opublikowany : 09/05/2019 2:16 pm
Share: