FirmwareUpdater "crashes" with uncaught node.js error
 

FirmwareUpdater "crashes" with uncaught node.js error  

  RSS
martinmajewski
(@martinmajewski)
Trusted Member

Hi all,

I wanted to reflash my printer to see if I could get around some weird behaviour but the FirmwareUpdater fails as soon as I press Update with an Uncaught Node.js error. The printer's LCD screen turns off and on again and everything is as it was before.

I've attached a screenshot of it.

I am running macOS Sierra and my i3 MK2 is at 3.0.8. currently.

Any suggestions?

Bye,
Martin

-- www.martinmajewski.net --
Thingiverse: www.thingiverse.com/MartinMajewski
Instagram: www.instagram.com/martinjmajewski
Twitter: www.twitter.com/MMajewskiNet
YouTube: www.goo.gl/QJTQKv...
Posted : 21/10/2016 12:41 am
martinmajewski
(@martinmajewski)
Trusted Member

So yeah... I will catch a Windows notebook tomorrow... Let's leave my problem on macOS unresolved, this is always a good choice in the software industry... 🙄

-- www.martinmajewski.net --
Thingiverse: www.thingiverse.com/MartinMajewski
Instagram: www.instagram.com/martinjmajewski
Twitter: www.twitter.com/MMajewskiNet
YouTube: www.goo.gl/QJTQKv...
Posted : 24/10/2016 12:51 am
JohnOCFII
(@johnocfii)
Estimable Member

I wanted to reflash my printer to see if I could get around some weird behaviour but the FirmwareUpdater fails as soon as I press Update with an Uncaught Node.js error. The printer's LCD screen turns off and on again and everything is as it was before.

Do you have a space in the path name of the directory where the firmware is located, or any parent directories? That is a common cause of that node.js error. Someone on the FaceBook forum had a similar issue, and I suggested he look for spaces. He had one, he removed it, and then the updater worked for him.

John

https://3dprinting.community/login #Community Discussion for 3D Printing...
Posted : 24/10/2016 2:46 am
Omikron
(@omikron)
Estimable Member

So yeah... I will catch a Windows notebook tomorrow... Let's leave my problem on macOS unresolved, this is always a good choice in the software industry... 🙄

I think it should be possible to just flash it through the Arduino IDE as well. I will confirm as soon as I get back home and post steps.

...
Posted : 24/10/2016 3:29 am
josefprusa
(@josefprusa)
Member Admin

I didn't upgrade to Sierra as it always breaks some stuff when I upgrade OSX. We will look into it :-/

Founder and owner / Majitel a zakladatel...
Posted : 24/10/2016 9:33 pm
Omikron
(@omikron)
Estimable Member

I didn't upgrade to Sierra as it always breaks some stuff when I upgrade OSX. We will look into it :-/

Unfortunately you have to remember that most of your users WILL upgrade. If not for new features, then for the fact that there are literally dozens of kernel-level security vulnerabilities that were patched in Sierra that will NOT be patched in 10.11. That's why the development builds are made available in advance - so that developers can test it and ensure compatibility before general availability of the software.

...
Posted : 25/10/2016 5:44 am
Omikron
(@omikron)
Estimable Member

Interestingly, it appears that the reason I am not having any problems with the firmware updater is that because I am using an older version of the OS X binary, compiled sometime in late May. The tool included with the current version of the firmware indeed gives me the same error.

For now, I would advise rolling back to the early summer update tool.

...
Posted : 25/10/2016 8:20 am
martinmajewski
(@martinmajewski)
Trusted Member

I didn't upgrade to Sierra as it always breaks some stuff when I upgrade OSX. We will look into it :-/

Thanks Josef for the replay - and also to the other users as well! 🙂

I already had renamed the firmware file to simply fw.hex and I also have not a single space character in my path to that file. So that is not the cause, unfortunately (would have been too easy, wouldn't it?).

I think there could be some Node.js version issue with Sierra.
As a macOS developer, I am very prone to updating my os frequently... 😀

But with all the MK2s being sold the last couple of months there should be a coin or two for one more Mac at your facilities with the lastest macOS on it! Am I right?! 😉 😎

-- www.martinmajewski.net --
Thingiverse: www.thingiverse.com/MartinMajewski
Instagram: www.instagram.com/martinjmajewski
Twitter: www.twitter.com/MMajewskiNet
YouTube: www.goo.gl/QJTQKv...
Posted : 25/10/2016 8:45 am
Omikron
(@omikron)
Estimable Member

Just to clarify, for those who didn't catch my previous comment:

If you are having problems updating firmware on OS X, try this older version of the updater: http://prusa3d.com/downloads/drivers/prusa3d_mac_1_7_4.zip

Use the updater contained in the driver package rather than the one that comes with the firmware. The newer binary crashes for me as well. The old one does not.

...
Posted : 26/10/2016 1:29 am
malcinator
(@malcinator)
Trusted Member

I had the exact same problem and I am using MacOS Sierra Problem and solution are here - http://shop.prusa3d.com/forum/prusa-i3-kit-building-calibrating-first-print-main-f6/firmware-update-error-t2036.html

...
Posted : 26/10/2016 10:54 am
martinmajewski
(@martinmajewski)
Trusted Member

I had the exact same problem and I am using MacOS Sierra Problem and solution are here - http://shop.prusa3d.com/forum/prusa-i3-kit-building-calibrating-first-print-main-f6/firmware-update-error-t2036.html

Thanks... It was the space inside the "Macintosh HD"...

This is sooo stupid, because being a developer myself I had this kind of path-space-char-handling problems as freshman in university - it seems so unrealistic that applications in 2016 still have this kind of issues... 🙄 *blamingnodejs

So yeah... move the updater to a partition / disk / location without spaces and it will work...

Thank you malcinator and the others for helping me out!

-- www.martinmajewski.net --
Thingiverse: www.thingiverse.com/MartinMajewski
Instagram: www.instagram.com/martinjmajewski
Twitter: www.twitter.com/MMajewskiNet
YouTube: www.goo.gl/QJTQKv...
Posted : 26/10/2016 8:18 pm
malcinator
(@malcinator)
Trusted Member

Couldn't agree more.

...
Posted : 27/10/2016 5:05 pm
jonathan.b4
(@jonathan-b4)
Active Member

For the benifit of future travelers I report that I have tried removing the space in my root drive, as well as moving the installer and firmware to the SD card and runing it from there, and I still get this error when trying to update to 3.0.9 on Sierra.

I also tried using the FirmmwareUpdater from the driver package, and running the updater from the SD card, and it is not giving me the error, but it is also not successfully performing the update. It just says "Updating Firmware! DO NOT DISCONNECT ANY DEVICE!!". Thats been going on for about 15 minutes which I know is way too long. So I am crossing my fingers now that I do not brick the printer when I give up and decide to disconnect it.

Update: I quit that updater after about 30 mins. Then switched off the machine, then back on again, then made sure it was on the main info screen(not the calibrate message, dont know if that matters), then ran the old updater again from the SD card on my Mac and it flashed successfully after about 20 seconds.

Joseph, consider making this a purely on device procedure where one puts the firmware on the SD, puts the SD in the printer, then uses the printer menus to perform the update.

...
Posted : 29/10/2016 7:43 am
brett.n2
(@brett-n2)
New Member

I had the issue and even tried to upgrade from my second HDD which has no spaces. Still had no luck.

I eventually just used the latest CURA to do the flash, and all went well and am running the 3.0.9 without issue.

...
Posted : 03/11/2016 1:32 am
stephen.e3
(@stephen-e3)
Estimable Member

This needs resolving. Doesn't work with Sierra.

I have tried 1.7.4 and renaming HD to remove a space. Always get the same Node.js error. Poor.

UPDATE: Just tried with version 1.7.0 and it worked!

...
Posted : 05/11/2016 12:10 pm
jamie.v
(@jamie-v)
New Member

I moved both the hex file and the app to an external drive (in my case a network drive mapped to /Volumes/media) and it worked.

I hope that helps someone.

Update: To clarify, I'm on Sierra.

...
Posted : 20/11/2016 12:58 am
marco.t
(@marco-t)
New Member

Tried renaming Macintosh HD to MacintoshHD (fail), tried to execute updater from SD card and to load from SD (fail), tried updater from older version (fail)... Every time the same EROFS error. However I managed to update the firmware running the updater from command line as root

sudo FirmwareUpdaterV2.app/Contents/MacOS/node-webkit

And yes, I'm running macOS Sierra.

...
Posted : 29/11/2016 6:30 pm
daniele.p
(@daniele-p)
New Member

I am having the same issue (and freaking out)

running Sierra 10.12.3

moved the firmware (10.0.10) to a USB drive, it doesn't work.

is there any way to fix this?

...
Posted : 25/02/2017 6:57 pm
JohnOCFII
(@johnocfii)
Estimable Member

I am having the same issue (and freaking out)

running Sierra 10.12.3

moved the firmware (10.0.10) to a USB drive, it doesn't work.

is there any way to fix this?

There is a new updater to try. This is a release candidate, but it worked for some people I know.

https://github.com/cleanflight/cleanflight/releases/tag/v2.0.0-RC1

https://3dprinting.community/login #Community Discussion for 3D Printing...
Posted : 26/02/2017 3:56 am
david.b14
(@david-b14)
Honorable Member

If you are running OctoPrint, you can have it do the firmware update.

http://shop.prusa3d.com/forum/original-prusa-i3-mk2-f23/octoprint-firmware-upgrades-t3460.html

...
Posted : 26/02/2017 4:22 pm
Share:

Please Login or Register