Bed levelling wizard can't connect to the printer

[brunogirin 0]

Hi,

I just finished assembling my Ultimaker and am running through the different setup wizards. The "first run" wizard updated the firmware and otherwise ran flawlessly, connecting to the printer fine. However, the "bed levelling" wizard claims that it cannot connect to the printer. When I run it, the printer makes a noise as if one of the motors was trying to turn but nothing happens. So I'm not sure if it's a software or hardware problem.

Any help would be very much appreciated. I am running Cura on Ubuntu 12.10 and the output of the console is:

 

Log: Changing monitoring state from 'Offline' to 'Detecting serial port'Log: Serial port list: [u'/dev/ttyACM3', '/dev/ttyACM2', '/dev/ttyACM1', '/dev/ttyACM0']Log: Connecting to: /dev/ttyACM3Log: Connected to: Serial(port='/dev/ttyACM3', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=1, xonxoff=False, rtscts=False, dsrdtr=False), starting monitorLog: Changing monitoring state from 'Detecting serial port' to 'Detecting baudrate'Log: Recv: startLog: Recv: echo: External ResetLog: Recv: Marlin 1.0.0 RC2Log: Recv: echo: Last Updated: Marlin-Mon, 11 Jun 2012 17:33:42 +0200 - b67dacdc8f1bd489e058e16d92ba29c364b2a8e5 | Author: Build-Me-MarlinLog: Recv: echo: Free Memory: 4494  PlannerBufferBytes: 1232Log: Recv: echo:Using Default settings:Log: Recv: echo:Steps per unit:Log: Recv: echo:  M92 X78.74 Y78.74 Z533.33 E865.89Log: Recv: echo:Maximum feedrates (mm/s):Log: Recv: echo:  M203 X250.00 Y250.00 Z5.00 E45.00Log: Recv: echo:Maximum Acceleration (mm/s2):Log: Recv: echo:  M201 X9000 Y9000 Z100 E10000Log: Recv: echo:Acceleration: S=acceleration, T=retract accelerationLog: Recv: echo:  M204 S3000.00 T3000.00Log: Recv: echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum xY jerk (mm/s),  Z=maximum Z jerk (mm/s)Log: Recv: echo:  M205 S0.00 T0.00 B20000 X20.00 Z0.40 E5.00Log: Recv: echo:PID settings:Log: Recv: echo:   M301 P22.20 I1.08 D114.00Log: Trying baudrate: 115200Log: Send: M105Log: Baudrate test retry: 4Log: Send: M105Log: Baudrate test retry: 3Log: Send: M105Log: Baudrate test retry: 2Log: Send: M105Log: Baudrate test retry: 1Log: Send: M105Log: Baudrate test retry: 0Log: Send: M105Log: Unexpected error while setting baudrate: 250000 ValueError: 'Failed to set custom baud rate: 250000' @ machineCom.py:_monitor:355Log: Trying baudrate: 230400Log: Send: M105Log: Baudrate test retry: 4Log: Send: M105Log: Baudrate test retry: 3Log: Send: M105Log: Baudrate test retry: 2Log: Send: M105Log: Baudrate test retry: 1Log: Send: M105Log: Baudrate test retry: 0Log: Send: M105Log: Trying baudrate: 57600Log: Send: M105Log: Baudrate test retry: 4Log: Send: M105Log: Baudrate test retry: 3Log: Send: M105Log: Baudrate test retry: 2Log: Send: M105Log: Baudrate test retry: 1Log: Send: M105Log: Baudrate test retry: 0Log: Send: M105Log: Trying baudrate: 38400Log: Send: M105Log: Baudrate test retry: 4Log: Send: M105Log: Baudrate test retry: 3Log: Send: M105Log: Baudrate test retry: 2Log: Send: M105Log: Baudrate test retry: 1Log: Send: M105Log: Baudrate test retry: 0Log: Send: M105Log: Trying baudrate: 19200Log: Send: M105Log: Baudrate test retry: 4Log: Send: M105Log: Baudrate test retry: 3Log: Send: M105Log: Baudrate test retry: 2Log: Send: M105Log: Baudrate test retry: 1Log: Send: M105Log: Baudrate test retry: 0Log: Send: M105Log: Trying baudrate: 9600Log: Send: M105Log: Changing monitoring state from 'Detecting baudrate' to 'Closed'Log: Changing monitoring state from 'Closed' to 'Error: No more baudrates to...'Log: Connection closed, closing down monitor

 

[cantconfirmordeny 0]

This is exactly the problem I'm having also. My log looks exactly the same (see attached). The "First Run Wizard" works fine ... it uploads the Marlin firmware, then runs through the limit switch checks and head heater tests just fine. But - cannot connect the bed-leveling wizard.

I figured ... what the heck, just level the bed manually and try to print. This turned out to be a very bad idea. It does not "home" the bed and printer head, but instead, slams the head into to stops. Had to yank the power cord to avoid disaster.

 

[Daid 260]

The "bed leveling wizard doesn't home" is an unfortunate bug that got into the wizard.

It's fixed for the 13.03 release. It will be announced soon, but for linux you can already download the .deb from http://software.ultimaker.com/Cura-13.03-debian.deb (The new .deb saves a lot of problems for linux users)

The connection problems with the wizard seem to be related to the Linux release.

 

[cantconfirmordeny 0]

Well, sadly, the 13.03 can't even open the USB port. Here's the whole log: (remember, the 12.12 version on this same machine opened the port, uploaded the firmware, and ran the "first run" wizard with no problems)

Changing monitoring state from 'Offline' to 'Detecting serial port'

Serial port list: ['/dev/ttyACM0']

Connecting to: /dev/ttyACM0

Error while connecting to /dev/ttyACM0: 'Timeout'

Failed to open serial port (AUTO)

Changing monitoring state from 'Detecting serial port' to 'Error: Failed to autodetect...'