Hi, some reports of our experiences :
in short: gibberish is a baudrate problem,
-try decrease it using hex firmware "115200" in cura, uploading it using cura/expert/install custom firmware;
-you may parameter COM port in windows manage/hardware-manager/com-port/driver ... but I'm not convince that it is important here
-change cura file/preference/baudrate,
-and THEN you restart cura to clear any previous wrong connection
the long story
After we built the ultimaker,we tried the electronic board, managed to connect and start to print, but soon the board didnt respond.
a serial connection, or just a look at the debug log in cura shows gibberish,
as if the connection were too speed and de-synchronized.
so we recompiled marlin firmware using arduino,
with a slower connection baudrate in configuration.h
let try 9600 : ok, it responds.
but it does not print a star of 20mm, but a 2mm insect.
this was because of a loose screw in X motor. (oops,my)
and maybe (not so sure) also because of a wrong marlin firmware.
we took the original one instead of the ultimaker one (google mistaked us)
http://wiki.ultimaker.com/Marlin_firmware_for_the_Ultimaker
we tried then using the hex version given in cura/resources/firmware directory
but indicated with a baudrate 115200 : MarlinUltimaker-115200.hex.
It fixed the pb.
By the way we reprinted the little extruder gear we accidentally broke. self-repared.
remaining notes, just for curiosoty :
* is baudrate windows parameter important ?
* does any windows can use baudrate 250000 ?
* if we take the original marlin firmware, is it really different ?
* how can arduino or cura upload a firmware on a connection that has not an undefined baudrate ?
Thanks to Ultimaker for the help.
