I’d say less than 5% chance it helps. But I REALLY don’t know exactly where the pipe is broken so I could be wrong.
OK….I’m in contact with support, but so far I’m only at the “Is your printer turned on” stage, so this could take a while.
I VERY MUCH appreciate your help and time and effort, so Thank You!
@DevildogMP This may be a reason to reflash the EMMC. I fail to see a direct correlation to your communication issue but it may help.
Well it is still able to “talk” to the buffer_mcu.
I’d run the last command again now that the updates are in place.
If that fails you’ll need to navigate to /home/sovol/build and look around. I use WinSCP which is super simple. You can SCP from the Mac terminal but I don’t know of a GUI for Mac.
don’t see a /home/sovol/build
Neither do I,
Also not on Sovol’s github
@sovol3d You advertise as an “Open Source” company. Where are the firmware .bin files?
Has anyone dug in and found the URL for the OTA updates? The ones for the Zero were hosted at Comgrow.
Okay I drilled into the image file and extracted the 3 build configuration files. I was able to get a good enough photo of the mainboard to be positive which MCU chip it had. Only one of the config files was for that chip. I then loaded that file into my klipper host and used kiauh + the build system built into klipper to roll a new .bin file
You’ll need to make a /build folder at the correct path and copy this in. Roll the dice and hope.
mcu_klipper.bin (42.0 KB)
It appears the script has a typo in the error message. It is actually looking for a different path.
Move the file to /home/sovol/printer_data/build/
Try
To stop the Klipper service, use the command sudo systemctl stop klipper. This will halt the Klipper service on your system.
then ./printer_data/build/mcu_update_fw.sh
@DevildogMP Has Sovol provided any solution path?
I’m out of ideas. The update script expects to find a serial port. @AlwinA ‘s functional machine doesn’t show a typical USB<>serial converter either. As far as I can see your device lists are identical.
It is possible that a programmer such as an ST-Link is needed in conjunction with the script.
If Sovol support isn’t providing satisfactory progress I recommend you create a synopsis of this thread and post it to https://klipper.discourse.group/c/general-discussion/6. You’ll get complaints that Sovol runs “dirty” Klipper and “support will be limited”. Hopefully one or 2 of the VASTLY more knowledgeable folks will take on the issue (very likely). Be sure to include your klippy.log.
Keep us posted on Sovol’s solution path.
Thank you for all the time you spent trying. So far Sovol is communicating about once every 2 days with what seems to be scripted responses….had this thing coming up on a week now and can’t even get it running. I realize they’re a big company, but they took my money and sent me a non-working unit and don’t seem to make it a priority to fix the machine. Again, thanks for your efforts. I’ll let you know what eventually comes of this.