Avisos
Vaciar todo

New firmware 3.0.11- MK2S/MK2  

Página 2 / 3
  RSS
jon.m
(@jon-m)
Eminent Member
Re: New firmware 3.0.11- MK2S/MK2

...does it mean that whenever I change filament types, I will need to rerun PID tuning, using values of 210 if using PLA and 255 if using ABS?

That is exactly the reason why I have the PID values in filament GCode and not EEPROM...

Peter

I am so confused. I too did separate PID tunes for different filaments and then added them to a specific profile with it's own GCode. All I have heard is, "you only need to do it once" and, "that is dumb to send it with the GCode."

I wish I had the right answer.

Respondido : 24/05/2017 11:17 pm
PRGeno
(@prgeno)
Active Member
Re: New firmware 3.0.11- MK2S/MK2

...does it mean that whenever I change filament types, I will need to rerun PID tuning, using values of 210 if using PLA and 255 if using ABS?

That is exactly the reason why I have the PID values in filament GCode and not EEPROM...

Peter

I am so confused. I too did separate PID tunes for different filaments and then added them to a specific profile with it's own GCode. All I have heard is, "you only need to do it once" and, "that is dumb to send it with the GCode."

I wish I had the right answer.

I can only share my experience and cannot state that this is "the right answer" but I had temperature fluctuation with all filaments types at all the various temperatures. I only did one PID calibration only at the temp I used for PLA and the temps are now very stable for all filaments at all temps.

The right answer for me was to do it once at one temp and store it in EEPROM. Done!

Respondido : 25/05/2017 12:16 am
frans.k
(@frans-k)
New Member
Re: New firmware 3.0.11- MK2S/MK2

After upgrading to 3.0.11, the bed stops responding, returning to 3.0.10.3 is the only option. Who can help me

Respondido : 25/05/2017 4:42 pm
PJR
 PJR
(@pjr)
Antient Member Moderator
Re: New firmware 3.0.11- MK2S/MK2

I am so confused. I too did separate PID tunes for different filaments and then added them to a specific profile with it's own GCode. All I have heard is, "you only need to do it once" and, "that is dumb to send it with the GCode."

I wish I had the right answer.

Whatever you do is the right answer.

And don't forget that the bed also needs PID tuning and that is not included in the firmware. The bed PID requirement will vary depending on ambient temps (the extruder will as well but not by very much).

Peter

Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…

Respondido : 25/05/2017 5:04 pm
Allen8355
(@allen8355)
Estimable Member
Re: New firmware 3.0.11- MK2S/MK2

Could anyone suggest the download location for the firmware downloader (Mac preferably) that the support page mentions? You would think there would be a link there, but don't see it.

Respondido : 25/05/2017 6:34 pm
Allen8355
(@allen8355)
Estimable Member
Re: New firmware 3.0.11- MK2S/MK2

For me, 3.0.11 seems to have fixed my ever increasing Z level problem. Looks like this solution warms the PINDA sensor rather than keeping it cool, which is interesting. I have a bit thicker than standard PEI, but my starting Live Z Level went from -0.250 with 3.0.10 to about -0.950 with 3.0.11 Not a big deal as long as it stays there. I tried raising the PINDA just a bit, but then with calibration the nozzle presses on the bed.

For future firmware, it would be great if the XYZ calibration didn't bring the nozzle any lower than its print position. Maybe this isn't possible, but it would be nice if it was.

Also the direct Z axis adjust is REALLY NICE. Thanks. Now how about an option to heat the nozzle to X temp on the Load Filament page, so I can heat the nozzle and load the filament all in the same place. And how about this. When you hold the button, it goes to the Z Axis when it ISN'T printing (like it does) and it goes to the Live Z Adjustment when it IS printing. Right now it STILL goes to the Z axis adjustment when it IS printing, which is WEIRD.

Respondido : 26/05/2017 12:40 am
dapug
(@dapug)
Eminent Member
Re: New firmware 3.0.11- MK2S/MK2

I had to flash it twice because the first time resulted in a self test Fail saying hotend is unplugged (erroneous, I had just finished a print and nothing was wrong with electronics).

Now it works. But I did notice one strange minor thing. It displays endstop test, but then does nothing, and then moves right to hotend test, and THEN proceeds to do the endstop test. Weird.

I was plagued with preheat errors, so hopefully this update helps me out!

Respondido : 26/05/2017 10:42 am
javier.c3
(@javier-c3)
New Member
Re: New firmware 3.0.11- MK2S/MK2

For me, 3.0.11 seems to have fixed my ever increasing Z level problem. Looks like this solution warms the PINDA sensor rather than keeping it cool, which is interesting. I have a bit thicker than standard PEI, but my starting Live Z Level went from -0.250 with 3.0.10 to about -0.950 with 3.0.11 Not a big deal as long as it stays there. I tried raising the PINDA just a bit, but then with calibration the nozzle presses on the bed.

I'm experiencing a similar behaviour but depending on the bed temp.
@55C my live Z is -.415
@100C my live Z is -1.1 !!!

Is this normal?

Respondido : 27/05/2017 1:06 am
LDoubleE
(@ldoublee)
Eminent Member
Re: New firmware 3.0.11- MK2S/MK2

What is the difference between PID, PID bed and temperature calibration?

Respondido : 28/05/2017 11:31 pm
christopher.d3
(@christopher-d3)
Estimable Member
Re: New firmware 3.0.11- MK2S/MK2

What is the actual version that is current? The web page says 3.0.11, but what is packaged in the ZIP file is 3.0.10a and 3.0.13a

Respondido : 31/05/2017 6:15 pm
christopher.d3
(@christopher-d3)
Estimable Member
Re: New firmware 3.0.11- MK2S/MK2

Nevermind. I didn't realize that the numbers in the file names refer to the miniRAMBo board version.

Respondido : 31/05/2017 6:52 pm
amprint
(@amprint)
Trusted Member
Re: New firmware 3.0.11- MK2S/MK2

After upgrading to 3.0.11 I don't see the elapsed time on the LCD screen when printing via OctoPrint. It just displays --:--
Has somebody else seen this behavior, too? As far as I remember the elapsed time has been displayed in the previous firmware version when printing via USB (correct me if I'm wrong).

When printing via SD Card the elapsed time is displayed correctly.

Design, Print, Repeat

Respondido : 07/06/2017 11:09 am
Magnazan
(@magnazan)
Active Member
Re: New firmware 3.0.11- MK2S/MK2

I'm missing the elapsed time too when using octoprint - I don't know if it was there before hand though as I only just started using it.

Respondido : 10/06/2017 7:01 am
Boby
 Boby
(@boby)
Active Member
Re: New firmware 3.0.11- MK2S/MK2

I'm using the octoprint plugin "detailed progress" and I do see ETL, ETA, etc in the display with the latest firmware.

Respondido : 11/06/2017 5:33 pm
Chris Abbey
(@chris-abbey)
Eminent Member
Re: New firmware 3.0.11- MK2S/MK2

I'm missing the elapsed time too when using octoprint - I don't know if it was there before hand though as I only just started using it.

Just checked, while my printer is running from octoprint over USB, on the previous release of the firmware, I see the elapsed time of the print on the front panel of the display.

After this print finishes I'll be flashing 3.0.11 on. (working on figuring out how to do that from the octopi now....)

Respondido : 12/06/2017 6:03 am
jonnieZG
(@jonniezg)
Trusted Member
Temperature Calibration

The temperature calibration does not work so great for me. In order to achieve approximately the same result, I have to set Z correction to -0.250 when printing with PLA (@215 C), and -0.550 with ABS (@240).

Respondido : 14/06/2017 9:57 pm
shane.t
(@shane-t)
Eminent Member
Re: New firmware 3.0.11- MK2S/MK2

This firmware has some major Z level issues. My Z live went from -.400 to -2.00+ and I still have not been able to get it low enough to actually print something... insane.

So far I have:
redone xyz calibration
redone z calibration
ran PID calibration

Been adjusting the z level but cant get even close. This firmware has made this printer pretty much so useless.

Respondido : 16/06/2017 3:16 am
shane.t
(@shane-t)
Eminent Member
Re: New firmware 3.0.11- MK2S/MK2

Actually I think I figured out what is going on, and there will need to be a bugfix for this. It appears that the printer does not honor live z settings until you are in a print. Then any changes you make to live z will get added to the current config. Almost like... the live z setting when you start a print is overridden by the pre-print calibration, then it will honor anything you add in afterwards.

I can demonstrate this because I am set live z to -4mm. That should crash it for sure, and yet, it doesn't even come close. Then if I adjust it to -0.400 while in the middle of a print... wala! It prints fine.

This needs to get chased down.

Respondido : 16/06/2017 3:26 am
nedz-man
(@nedz-man)
Active Member
Re: New firmware 3.0.11- MK2S/MK2

Actually I think I figured out what is going on, and there will need to be a bugfix for this. It appears that the printer does not honor live z settings until you are in a print. Then any changes you make to live z will get added to the current config. Almost like... the live z setting when you start a print is overridden by the pre-print calibration, then it will honor anything you add in afterwards.

I can demonstrate this because I am set live z to -4mm. That should crash it for sure, and yet, it doesn't even come close. Then if I adjust it to -0.400 while in the middle of a print... wala! It prints fine.

This needs to get chased down.

I had this problem before too. What you need to do is re-run the V2Calibration.gcode. Then it will save the live adjust values that you adjust during the code calibration. After running the the XYZ calibration it tells you to follow the first steps in the manual. I think Prusa Research should make this more intuitive...

Respondido : 17/06/2017 6:14 am
shane.t
(@shane-t)
Eminent Member
Re: New firmware 3.0.11- MK2S/MK2

Hmm.. I will try again, but it doesn't seem to be working. Seems like it is applying the Z live level before the preprint calibration instead of after. Let me give it another shot.

Respondido : 17/06/2017 8:12 pm
Página 2 / 3
Compartir: