Serial communications with MMU3/MK3S+ (echo:MMU2 and trying to send M707 A0x22)
I am trying to adjust the PTFE tube length for my MMU3. I understand I have to send M707 A0x22 to find the current length or M708 A0x22 415 where 415 is the length in mm. I have two problems.
First, any time I try to connect to the printer over serial, I get flooded with line after line of
echo:MMU2:<R1c A5*f6.
echo:MMU2:>R4*7b.
While the part after the MMU2: varies from line to line, it's non-stop.
Why does it say MMU2 when it's an MMU3? Is this just a artifact I can/should ignore?
What can I do to stop this flood of information? Since it's just flooding the screen, any command I type in is off the screen before I can read it.
My second issue is that when I do give the command M707 A0x22 I get back "ResetRetryAttempts" followed by an OK.
I read somewhere that this is because I'm sending the command over OctoPrint which converts the A0x22 to A0X22, which isn't valid. So I opened a terminal and entered it in the correct case. I still received "ResetRetryAttempts".
What am I doing wrong in issuing the M707 Ax022 command?
Finally, I want to say that I know I can put the gcode into a print and have it execute there. I'm messing with the firmware's setting, so it makes me uncomfortable sending it with a print, and not seeing any kind feedback.
Thank you in advance for your help.
PS: If you happen to know the proper settings to use in minicom or putty so the it displays a linefeed and carriage return and not just a linefeed when getting data back from the printer, I would love to know what that setting is. I can live without it, but it would be nice to have.
RE: Serial communications with MMU3/MK3S+ (echo:MMU2 and trying to send M707 A0x22)
I had the same issuse, but I tried to send M707 A0X22 at OctoPod App by iPhone, I did get some recv info from MMU. The way I adjust the Bowden tube length is recompile the firmware of MMU3 by changing the value of Prusa-Firmware-MMU/src/config/config.h
#95 static constexpr U_mm defaultBowdenLength = 360.0_mm; /// ~360.0_mm - Default Bowden length.
@RickSeiden, tell me the length, I could make you a firmware includes the change of BowdenLength
RE: Serial communications with MMU3/MK3S+ (echo:MMU2 and trying to send M707 A0x22)
So, you have a Bowden tube that’s actually 415mm instead of the standard 360mm? I assume there’s some reason for that, like you’ve mounted the MMU in another location further away from the extruder? Otherwise, you could just shorten the tube to 360mm, obviously.
One thing that interests me about this is whether or how this will impact the CoreOne’s implementation of the MMU. I guess it remains to be seen, what Prusa comes up with.
The other thing that interests me is the ability to compile custom firmware. I’ve done some coding, but am a little intimidated as to how to set up a dev environment for that. Any tips for that would be appreciated, although I know it’s off topic here, sorry.
MK4S/MMU3
RE: Serial communications with MMU3/MK3S+ (echo:MMU2 and trying to send M707 A0x22)
I’m guessing, but would this work?
M707 A0x22 ;Read Bowden Length
M708 A0x22 X0x19F ;Write persistent Bowden Length 415mm
I am trying to adjust the PTFE tube length for my MMU3. I understand I have to send M707 A0x22 to find the current length or M708 A0x22 415 where 415 is the length in mm. I have two problems.
First, any time I try to connect to the printer over serial, I get flooded with line after line of
echo:MMU2:<R1c A5*f6.
echo:MMU2:>R4*7b.While the part after the MMU2: varies from line to line, it's non-stop.
Why does it say MMU2 when it's an MMU3? Is this just a artifact I can/should ignore?
What can I do to stop this flood of information? Since it's just flooding the screen, any command I type in is off the screen before I can read it.
My second issue is that when I do give the command M707 A0x22 I get back "ResetRetryAttempts" followed by an OK.
I read somewhere that this is because I'm sending the command over OctoPrint which converts the A0x22 to A0X22, which isn't valid. So I opened a terminal and entered it in the correct case. I still received "ResetRetryAttempts".
What am I doing wrong in issuing the M707 Ax022 command?
Finally, I want to say that I know I can put the gcode into a print and have it execute there. I'm messing with the firmware's setting, so it makes me uncomfortable sending it with a print, and not seeing any kind feedback.
Thank you in advance for your help.
PS: If you happen to know the proper settings to use in minicom or putty so the it displays a linefeed and carriage return and not just a linefeed when getting data back from the printer, I would love to know what that setting is. I can live without it, but it would be nice to have.
MK4S/MMU3
RE: Serial communications with MMU3/MK3S+ (echo:MMU2 and trying to send M707 A0x22)
I had the same issuse, but I tried to send M707 A0X22 at OctoPod App by iPhone, I did get some recv info from MMU. The way I adjust the Bowden tube length is recompile the firmware of MMU3 by changing the value of Prusa-Firmware-MMU/src/config/config.h
#95 static constexpr U_mm defaultBowdenLength = 360.0_mm; /// ~360.0_mm - Default Bowden length.
@RickSeiden, tell me the length, I could make you a firmware includes the change of BowdenLength
Recompiling would work, of course, but I'd rather not have to recompile every time a new firmware is released.
I appreciate the offer for the firmware, though. Thanks.
RE: Serial communications with MMU3/MK3S+ (echo:MMU2 and trying to send M707 A0x22)
So, you have a Bowden tube that’s actually 415mm instead of the standard 360mm? I assume there’s some reason for that, like you’ve mounted the MMU in another location further away from the extruder? Otherwise, you could just shorten the tube to 360mm, obviously.
Yes, my tube is longer because I found that the bend in the tube up towards the selector was too severe and wanted it be be gentler. So I cut a piece of tubing that was longer.
I’m guessing, but would this work?
M707 A0x22 ;Read Bowden Length
M708 A0x22 X0x19F ;Write persistent Bowden Length 415mm
That is the problem I'm having. I send the M707 and it doesn't return anything. I don't want to send the M708 without reading the M707 first, or knowing that I can set it back.
RE:
Today I was able to connect my laptop to the MK4S xBuddy serial port using Putty. Here’s (I hope) a screenshot showing how I interrogated the Bowden Length, changed it, rebooted, confirmed it was still valid, then changed it back. It was a little different than what I had suggested before, sorry, but this is confirmed. Actually turned out simpler than I expected. I hope this helps!
MK4S/MMU3