Judogido

This implies a different gcode flavour for printing from SD card. Is that correct?

Well, apparently the default setting for G-code as "Ultimaker-2" is wrong. After my question yesterday I tried to figure it out myself since I had no responses. I uninstalled Cura. Restarted the computer. Reinstalled Cura. Restarted the computer. Updated the firmware again. The problem remained. I then discovered if I home the printer and preheat the nozzle, the unit will start to print OK, albeit with poor quality. On a hunch I changed the G-code flavour to "Marlin" and it is now printing directly from Cura. Is that the correct setting for the UM2+?

I have a brand new UM2+. Aside from some freezing of the firmware during setup it has printed from the SD card very well. However, I have no card reader so I wanted to print directly from Cura 3.4.0. Instead of heating up and raising the bed, the printer immediately starts to print in the air in the corner. I updated the UM2+ firmware and updated Cura to 3.4.1. Same problem. Below is a link to a short video showing the issue. UM2+ not printing correctly from Cura Am I missing a setting or configuration somewhere? The "machine" is correctly set to UM2+ and the material correctly set to PLA.

Just purchased a brand new UM2+. Arrived Tuesday and I am setting it up today. I unpacked, removed the cable tie, switched on the unit and began to run through the "first use" guided sequence. As I scrolled the wheel to raise the bed for the first 1mm to nozzle adjustment, the firmware froze and became unresponsive. Button press did not work and scrolling did not work. So I restarted the unit and all went OK. Next I had issues with printing directly via USB connection from Cura 3.4.0. Therefore I updated the firmware to _3.3.0 and Cura to 3.4.1. While scrolling through the menu it again froze and needed a restart. I have since reset the unit to factory settings and had to run through the setup sequence again. So far no locking up, however I am concerned that it has now frozen twice. Is this just a normal thing for the UM2+ machines?