Marco_TvM

UM3 blue -> idle state, Print Core can be removed (safe to touch) Blinking orange -> heating up or cooling down (depending on the current temperature of the Print Core and the set target temperature) Continue orange -> hot White -> active during print that is, if I remember it correctly.

It would be an interesting feature, but We don't want to store videos in the printer (conflicting space requirements, management of files etc) It will also time to process the images and create the video, in which case this is a chance of the actual printing to be slower and thus possible artifacts. I'm sure nobody wants that. Hence the idea of just capturing images and put them together as a movie outside the printer is more beneficial.

I'm glad we could help making it easier for people to handle the printer! Have fun!

There have been no plans for that as far as I know, but I will inform our PO about the request.

Just used for some internal tinkering/testing.

I can say that we're discussing how to proceed with opening up the firmware to become Open Source. However, as @Daid mentioned, this can take some time to figure out the details and stuff.

Yes please. As @Daid mentioned, it would be interesting to figure out the source.

That would be great... Just use something like wetransfer and post the link here.

That's an interesting thing to note. I'm not aware that this happens in the cases we've seen and examined so far. If it would happen again (with the fixed testing firmware) I'd love to get some logfiles to analyze!

Nope that will not work. Technically speaking, a mouse probably will be detected, however the mapping to use it for input is completely missing. That might not work either... Similar to using a mouse(wheel), device mapping to input signals is not implemented.

There is a lot that can be done using the WEB API. Some things cannot - like manual leveling which uses the rotation to move the bed or move materials in the menu (again, rotation).

Keep us posted, please. Logs would be helpful. I just experienced something similar, but investigating didn't explain what the cause was. I will be monitoring and trying to reproduce the problem.

@Daid has found the culprit and most likely fixed it. It can be found in the TESTING release as we speak: 4.2.4.20121222.

Check the information using System -> Network -> Connection status. However, the 169 network is a fallback network when it cannot get a network address from a DHCP server (for whatever reason). If you can use a direct connection with a PC, setup a DHCP server on the PC. The printer will then get a valid IP address and you should be able to determine the MAC address.

I think that one printer had some minor disruption during the installation of the update. See also the following thread:

It's a micro-SD card. Insert the SD card and it should boot up and reinstall the firmware. After it's finished, you can remove the SD card. You can always download the firmware files onto a USB stick and update the firmware from stick instead of downloading directly.

Unfortunately, I think only this procedure, mentioned earlier by @robinmdh may solve this. Something went wrong during the update and you ended up with a bricked UM3.

Have you tried a different USB stick? Allways make sure to cleanly eject/unmount the USB stick before removing it from the PC/Mac.

that's already work - place some pancake dought at the build plate and give it some heat... :-) That's baking cookies... I'm talking So first layers of dough, then layers of niceness and finally some icing. With all the cookie hungry people here at the office, I think we need a few of those printing 24/7

that's already work - place some pancake dought at the build plate and give it some heat... :-) That's baking cookies... I'm talking So first layers of dough, then layers of niceness and finally some icing

To be able to print cookies!?

This would have put the log files onto the USB drive. Please send the log files to us, using WeTransfer, so we can analyze. But mostly, this is caused by some problem with the cable getting loose in the printhead. See http://ultimaker.com/ER18 for information and on the forum https://ultimaker.com/en/community/42426-print-head-error-communication

Keep us posted and keep an eye on the brick when starting the print to see if it turns off when you experience the problem. I'll be here to help.

I'm sorry to hear you experience issue with the UM3 after updating. What would help is if you can send the log files to us, using WeTransfer or something similar. You can get the log files using the menu: System -> Maintenance -> Diagnostics -> Dump logs to USB

It might help us if you can get us the logs of the printer using WeTransfer or something similar. You can get the log files using the menu: System -> Maintenance -> Diagnostics -> Dump logs to USB.