Using 3.0.9 GA on current gen MK2
M301 submission to update P receives gibberish in response followed by echo back that the new value was received, but M504 shows values unchanged. Using M500;M501 shows same unchanged values:
Send: M301 P35
Recv: )}f7}_]
z^{Z]v=^sG$^kxrx_{/lk-9W;V6f{_fnq_!5?wO;e,NetO>7wj8>u|Z/^~i>Nz
~}w+{N7|{?z]Uku_;G{rT2s*?~n?zI])v/-k(tl(r]g\ytJh.mw?{
U:i7/OHlmwE9mG~`bwg$/:)7=gcIuk}?X{4_MV8M[li(GtWL}sN_<\;s_gi_Zw^#W|u|D9p17q}n9BQvV_wVgc~vg+-Yv]{-weq{9vl7k}w9?#}}>/}z~u<?qyf_m*UO4o{}%o`o<T0}?wY;=%~j^g3e|OBz.(]?p=;Wex?Vitm~q-t};w:6ppf}1c6xoK}L}DUln}p?>Ta\8QSwfUw
Recv: ;_r8{h-w )3}5Wo[gg~_y_cOg3_e6d~l81W5|~qy=u7?^w/mW'{/RiYaO^iVOVb/]5Q_zi^p[?53M..?9xg:K4/W/#nYwZ'w^1Y'u}?~>~}hylo}-7{9Qy)f{Ts?>7e.Uquv0yO9r##87Dc?;rx}no'[{'i.FzkW=]~_GzGy}N__ue/y_[mvfv`/o={o_h|i}..fo_wll/r}VK7X=/Og&/+jM_&p}.g/u:ua)u7s};9[[{}xnpKy6Zo\~3y.Xk{f?&{=lkO$j_j/>=7?2W^{+s*^_Z}Vs/SM}7!y[_@[o p:35.00 i:4.88 d:86.08 c:1.00
Recv: ok
I have this issue as well.
Send: M301 P35
Recv: =g�f����/
���w\���.���w^_?^�>N���}#���6.��Z�����6~=[��v���9=���������_g�����g����/�G�vn��k�Y�k/�������8�����x�+>9��}�Z��rW]����<qzQ�jN|�^
���G���~�S[��e��Y��J��\�����
��l����J�������<���{��s�i������^��MhX�ysV��=o���m������B������
�������}
&c����-O�p����=��yM�
����d���k;�L�ogv�K��xM�F�����^��qfg
V�v��f=��8�(����i������q5v���"��_�v����g�5@�����.��?)�i@+��U���I����.�m�}S�k�}�����]n����W7�k���3��{kg?����7�3�9�����v]������������}
�i�+[&��u�WC?��h��{
���~��K;m9���o>���^���L��N��Z��mw}�_���:��^������}�����?}����F���c�qHq��cOE����z���J���7���;��]_�$������Se��W�j���o�����q����Qo�T��n�������k�a�2y#|��9~R'�������?��^���=r{����;0��?WJ�����Nn|pn�sb�_0�{H�~����w�����u����L�Y�^���u�m1+������W��w����?����R�w?���s{�n��t��G����d�����~?����;��������ZO�}��(����B;p�k}�Xw�Y�ZY�-7��gw��o��/�/���[���,�G����,S~i���&^yg��?Ou��}�������e�mUj>o|�d���
��o���e�%
��-�y'�.�]de���*q�lc�����u]�|aL�&�o��(_�����6���=���?��=���7k��~���7��cR!�|���fu�>/P��X������F��o�����Jr���7{������;�
���XH���m\������mc=��
��p���
�|_���_�6�w�y]_�g�wN�����{�{�����v��V���O'�o�J�r����q��'�pLj�u��8��������w�������S���L����w�x������&���k�b���o�MS�qKZV�t������mO��H�?G�����b��������������;������7��^����|�k��:�����l�_
Q��t���;(hY ���n�Hy
Recv: ?O�~�������K��O{(a��=^��\���m��s>|�X�����9�j��7�[������8U������\�};6�f�_�[�2��zQ�����=����6?�����n�~7����\�J7�?�������G�����dw
����}�z������������q��}�o������c������~���%�][�o��I����^_����l��<�Wy����#�_�~��������l������8/����{����������=����������;��lqvc
^���zLC��<_X3���W�_�a]��\���[
�d
w
� p:35.00 i:4.88 d:86.08 c:1.00
Recv: ok
Interesting how it's a completely different response.
Are you running 3.0.9 @nicw ?
@fiveangle yes, 3.0.9
It appears that even if they address this issue, we will not be able to save the corrected settings since EEPROM is disabled (see #21), so we will have to use slicer Start GCODE script to accomplish.
It seems the correct path Prusa Research expects is for us to submit a support ticket to have them start replacing hardware if the hotend or heated bed cannot stay regulated.
I am seeing this problem as well. I have gone back to the older firmware and am able to put my PID settings into Slic3r to set before the print starts. My extruder temps have gone from +-4C to +-0.5C.
Which FW did you downgrade to @bcheck555 ? 3.0.8 ?
@fiveangle Correct I am running v3.0.8 currently.
Problem occurs in 3.0.9 as well
Thank you very much for reporting this. M301 and M304 has been fixed in https://github.com/prusa3d/Prusa-Firmware/commit/fcce374a14b94ae6dc01466d9262a92d3ae1bf50. Now it is also possible to store PID settings using M500.
Did I understand this correctly: Has been fixed in 3.0.10_alpha?
If yes, when can we expect the update?
M304 is not saving with the m500 this is still a bug. m301 does save however
terminal output from octoprint
`
[...]
Send: M301
Recv: ok p:18.11 i:1.38 d:59.35 c:1.00
Recv: ok
[...]
Send: M304
Recv: ok p:126.13 i:4.30 d:924.76
Recv: ok
m301 is the current tuning for the hotend
m304 is the firmware values
prior to reboot
Send: M304 P59.44 I2.43 D362.74
Recv: ok p:59.44 i:2.43 d:362.74
Recv: ok
[...]
Send: M500
Recv: echo:Settings Stored
Recv: ok
[...]
after reboot
Send: M301
Recv: ok p:18.11 i:1.38 d:59.35 c:1.00
Recv: ok
[...]
Send: M304
Recv: ok p:126.13 i:4.30 d:924.76
Recv: ok`
Most helpful comment
Thank you very much for reporting this. M301 and M304 has been fixed in https://github.com/prusa3d/Prusa-Firmware/commit/fcce374a14b94ae6dc01466d9262a92d3ae1bf50. Now it is also possible to store PID settings using M500.