-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix mmu crc #1009
base: master
Are you sure you want to change the base?
Fix mmu crc #1009
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested on an mk3s+ fw 3.14.1-revo with mmu3 fw 3.0.3 by manually editing the files on the RPI zero 2w. This solves the "BUSY" problem in my case.
Here how you can manually solve the issue, until the release. Search for the file The path to the file may be different, depending on the Python version. I personally do not own a RPi, but have PrusaLink running on my PC with Ubuntu. I can find this file in but also in Search and replace in
with
again see my PR for the needed changes. There should be 6 lines that need to be changed. I also tested if PrusaLink and PrusaConnect work with the customized Hope that helps. Advantage of the manual change is that you don't lose your configuration you already have. In case you have ssh enabled on the RPi then you can connect to it and change it there. |
Email sent |
Looks like a small change, but crucial for MMU owners. Is there a way to upvote for it? I have 8x MK3S+ MMU3 and it's really annoying that I can't send MMU sliced gcode over prusaConnect due to this issue. I am familiar with git, but not familiar with Rpi images. |
Please send me an email. |
+1 on this issue |
See my comment above. Some users were able to modify the files and fix the issue |
I did, but I can't find any "regular_expressions.py" in the whole bootfs/rootfs of the PI's SD. that's why I was asking |
nevermind... I think I found it. for all others: in rootfs its |
I am very confused where I am supposed to search for the file to edit... Do I search in the rpi directories? I do not see any file that is labeled as "structures" or "expressions" when i search the SD card... The only files I am seeing on the SD card that I am able to edit on my Mac is are "config.txt", "cmdline.txt", "firstrun.sh", "issue.txt"... all others are .dat, .elf, .dtb and .dtbo which I cant open... please advise.. thanks I have also attempted to ssh to the rpi but am getting an error "port 22 connection refused" |
when plugging the sd into a card reader I got two partitions: bootfs and rootfs. rootfs should be the one. i also might have found a workaround: you can try to print directly from SD and cancel the print. that worked for me once |
@pjmoskowitz @sturze Please send me an email. |
User reported an issue with Prusa-Firmware 3.14.1 + MMU 3.0.3, PrusaLink 0.8.1 and PrusaConnect see prusa3d/Prusa-Firmware#4818
After troubleshooting I have found that the MMU 3.0.3 crc value is only one char long instead of being two chars. PrusaLink REGEX expected to have exactly two chars for the crc and so failed to get the correct MMU version including the build number. This causes PrusaLink and PrusaConnect to show the printer as "BUSY" and so not usable with PrusaLink and PrusaConnect.
Prusa-Firmware 3.14.0 with MMU 3.0.2 works fine as the MMU crc is two chars.
This fix accepts one AND two char crc which are 0-9 and a-f.
Changing the Prusa-Firmware and MMU3 firmware isn't a real option as this would also cause the need to change the Prusa-Firmware-Buddy and maybe other 3rd party solutions.
Test:
Before PR:
a. Both show
BUSY
state and the printer is "locked"After PR:
a. both show
IDLE
Also the log files of 0.8.1 in combination of FW 3.14.1+MMU3 shows
ERROR: Gather of mmu_version has failed