Jump to content

Perchik

Member
  • Posts

    30
  • Joined

  • Last visited

Everything posted by Perchik

  1. I've also tried using Xloader to upload the firmware and it also just hangs on "Uploading...." If I click automatically update firmware in Cura 3.6 instead of providing the Tinker .hex file, Cura crashes instantly. When I get to the point it hangs on any of these approaches, the machine's LEDs turn off briefly and turn back on, the display switches to "printing from usb" and then immediately back to Print | Material | Maintenance. What should the display show when the firmware is updating? And roughly how long should it take?
  2. The chip on the Ultimaker is Atmega2560. Using firmware updater with "Wiring" mode from octoprint acted like it was doing something and then never did anything (I let it sit for 2hrs) I found https://ultimaker.com/en/resources/18627-change-arduino-drivers which suggested my windows had bad arduino drivers. Updating the arduino drivers didn't fix it. Cura just hangs forever on "Updating firmware"
  3. Although, now I'm unclear if the MCU I care about is on the UM or on my raspi ?
  4. Hmm, this is what I've been trying recently but you have to pick the correct MCU. How can I tell what the MCU is on the main board? My computer initially connects to the UM, the display on the UM switches to "printing from USB" then almost immediately disconnects and it goes back to the normal "print | material | maintenance display". The computer still shows the UM connected on COM4.
  5. I am trying to switch to the tinker firmware and I have the new .hex file. When I connect the printer to the computer via usb, cura see the printer, but when I click upload firmware, it fails do to "communication error." I replaced the usb cable with a brand new one and it still fails to communicate. I can print from octoprint via usb with no problems, so I thought about updating the firmware from octoprint. My octoprint instance is running on a Raspberry Pi 3 B and I found the firmware updater plugin, but it requires avrdude or bossac and neither seems to make sense for my raspi (although I'm less sure what I'm doing on that side of things.) Any ideas on what might be wrong w/ the UM communication, or any other ways to update firmware (sd card?) Thanks!
×
×
  • Create New...