Jump to content
Ultimaker Community of 3D Printing Experts
Sign in to follow this  
xyzlord

communication problems

Recommended Posts

i seem to have some kind of communication problem with my ultimaker since the new cura (updateted from 12.08 to 12.12A).

this is my communication log.

"Changing monitoring state from 'Offline' to 'Opening serial port'

Connecting to: COM11

Connected to: Serial(port='COM11', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=2, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor

Changing monitoring state from 'Opening serial port' to 'Connecting'

Recv: ?nP

Recv: =?j??Jl?J%[LZ?k%aL)?&>|Y?V?n6

Recv: J?Z?z?J?z?J?J?{?X?:&?+^>H?$P|?%?%?%H%?x??+^^J??^IJO.X?+^^X?J?j?AHJ?aHJP|@_a?&&??$

M6CL

Recv: IM^+

Recv: ?6L

Recv: I?6XH^C??&h?H

Recv: I?&(^l

Recv: x?

Recv: ?Zb?Jj?J?J?Hj??*'

Recv: joV?F?

Recv: H??J?5?-?

Send: M105

Recv: ']h?

Changing monitoring state from 'Connecting' to 'Closed'

Connection closed, closing down monitor"

i tryed upgradeing the marlin software againg but doesnt seem to make a difrence when i did.

changing the baud rate from 250000 to 115200 didnt work. swamping usb ports didnt work and neither did changing the usb cable itself for anothere one.

hopefully somebody knows what to do since im a bit at a dead end.

Share this post


Link to post
Share on other sites

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

Connecting to: COM11

Connected to: Serial(port='COM11', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=0.1, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor

Changing monitoring state from 'Opening serial port' to 'Detecting baudrate'

Trying baudrate: 250000

Send: M105

Baudrate test retry: 4

Send: M105

Baudrate test retry: 3

Send: M105

Baudrate test retry: 2

Send: M105

Baudrate test retry: 1

Send: M105

Baudrate test retry: 0

Send: M105

Trying baudrate: 230400

Send: M105

Baudrate test retry: 4

Send: M105

Baudrate test retry: 3

Send: M105

Baudrate test retry: 2

Send: M105

Baudrate test retry: 1

Send: M105

Baudrate test retry: 0

Send: M105

Trying baudrate: 115200

Send: M105

Baudrate test retry: 4

Send: M105

Baudrate test retry: 3

Send: M105

Baudrate test retry: 2

Send: M105

Baudrate test retry: 1

Send: M105

Baudrate test retry: 0

Send: M105

Trying baudrate: 57600

Send: M105

Baudrate test retry: 4

Send: M105

Baudrate test retry: 3

Send: M105

Baudrate test retry: 2

Send: M105

Baudrate test retry: 1

Send: M105

Baudrate test retry: 0

Send: M105

Trying baudrate: 38400

Send: M105

Baudrate test retry: 4

Send: M105

Baudrate test retry: 3

Send: M105

Baudrate test retry: 2

Send: M105

Baudrate test retry: 1

Send: M105

Baudrate test retry: 0

Send: M105

Trying baudrate: 19200

Send: M105

Baudrate test retry: 4

Send: M105

Baudrate test retry: 3

Send: M105

Baudrate test retry: 2

Send: M105

Baudrate test retry: 1

Send: M105

Baudrate test retry: 0

Send: M105

Trying baudrate: 9600

Send: M105

Changing monitoring state from 'Detecting baudrate' to 'Closed'

Changing monitoring state from 'Closed' to 'Error: No more baudrates to...'

Connection closed, closing down monitor

this is what happens

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

Terms of Use Privacy Policy