OctoPrint / OctoPrint-FirmwareUpdater

OctoPrint plugin for flashing pre-compiled firmware images to a 3D printer.
https://plugins.octoprint.org/plugins/firmwareupdater/
GNU Affero General Public License v3.0
351 stars 76 forks source link

"Unable to transfer Firmware file to printer" Flashing method: marlinbft #333

Closed dlopez408 closed 1 year ago

dlopez408 commented 1 year ago

Hardware Setup RockPi 4b+ & Longer LK1

Describe the problem I am "unable to transfer firmware file to printer" using the marlinbft flash method. I have all prerequisites installed and enabled. I am not sure what the issue is.

I apologize if there is an obvious solution to this problem, I am still learning.

image

Log Files octoprint.log

Additional context I am trying to use the plugin for the first time. I have just installed it today.

benlye commented 1 year ago
2023-01-25 14:40:05,776 - octoprint.plugins.firmwareupdater - INFO - Transfering file to printer using Marlin BFT '/tmp/tmpuzcyoxo2' -> /firmware.bin
2023-01-25 14:40:05,818 - octoprint.plugins.firmwareupdater - ERROR - Flashing failed. Unable to transfer file.
Traceback (most recent call last):
  File "/home/dlo/OctoPrint/lib/python3.8/site-packages/octoprint_firmwareupdater/methods/marlinbft.py", line 105, in _flash_marlinbft
    filetransfer.copy(firmware, target, True, False)
  File "/home/dlo/OctoPrint/lib/python3.8/site-packages/binproto2/protocols.py", line 407, in copy
    self.open(dest_filename, compression_support, dummy)
  File "/home/dlo/OctoPrint/lib/python3.8/site-packages/binproto2/protocols.py", line 372, in open
    raise Exception("Cannot open file on client")
Exception: Cannot open file on client

I don't think it's a baud rate problem - the BFT protocol is connected and synced. Cannot open file on client means that the protocol was not able to create the target file on your printer.

Try going into the plugins options and enabling the Verbose file transfer progress logging option (it's on the 'Advanced 2' tab. Try to flash again and then upload the log. It may not tell us exactly what's going on, but it's worth trying.

Otherwise, it's possibly a combination of the SD card settings in your Marlin config.

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had any recent activity. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed in 5 days.

dlopez408 commented 1 year ago

Thanks for the replies! I will update with the new log soon

dlopez408 commented 1 year ago

Here is the log with the Verbose file transfer progress logging option enabled

octoprint verbose.log

benlye commented 1 year ago

Not much I can do to help with this - the protocol can't open the destination file on your printer. The binary file protocol is written and maintained by someone else.

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had any recent activity. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed in 5 days.

github-actions[bot] commented 1 year ago

This issue has been automatically locked because there was no further activity after it was closed. Please open a new issue for any related problems.