rostock max v2 comunication problems

Having a problem? Post it here and someone will be along shortly to help
Post Reply
gurusonwheels
Plasticator
Posts: 13
Joined: Fri Sep 23, 2016 12:58 pm

rostock max v2 comunication problems

Post by gurusonwheels »

my rostock max v2 all of a sudden developed a issue of spitting out weird chars in the gcode log .

i have tried to reflash with usb cable hooked directly to rambo controller but it fails to connect with sync problems .
i even tried reflashing bootloader using a ardunio as isp programmer connected to icsp headder .

flashes fine with no errors .
but still can not flash firmware with cable connected to usb port of board .

tried flashing compiled rostock.hex file using programmer on icsp header
flashes fine .

system boots up display and menus all work including homeing and heating .
however when i connect something like simplify3d and watch the verbose log for a few secs this is what happens .

Code: Select all

Attempting connection at \\.\COM3...
READ: start
  Connected to machine!
SENT: T0
READ: Info:External Reset
READ: Transformation matrix: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000
READ: Free RAM:794
READ: Autoretract:0
READ: X:0.00 Y:0.00 Z:0.000 E:0.0000
READ: SpeedMultiply:100
READ: iis2dh accelerometer initializing...
READ: ok
READ: SpeedMultiply:100
SENT: M105
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
SENT: M105
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
SENT: M105
READ: wait
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
READ: wait
SENT: M105
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
SENT: M105
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
READ: wait
SENT: M105
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
SENT: M105
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
SENT: M105
READ: wait
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
READ: wait
SENT: M105
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
SENT: M105
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
SENT: M105
READ: wait
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
SENT: M105
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
READ: wait
SENT: M105
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
SENT: M105
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
SENT: M105
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
READ: wait
SENT: M105
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
SENT: M105
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
SENT: M105
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
SENT: M105
READ: ok
READ: T:20.86 /0 B:20.86 /0 B@:0 @:0
READ: wait
READ: wait
SENT: M105
READ: ok
READ: T:20.<6 /0 b:20.86</0 B@:0 @:0
READ: w}iw
SENT: M105
READ: okí
SENT: M105
READ: W;2°.<6?/0°z:²?.<¶¿/<¾C`º<<~;?Ëw}iwËok
READ: W;²8.¾6</8<r;2>/?6?/<>{|º? p:<
wymv
SENT: M105
SENT: M105
SENT: M105
SENT: M105
SENT: M105
SENT: M105
SENT: M105
SENT: M105
SENT: M105
SENT: M105
SENT: M105
Disconnected.
Attempting connection at \\.\COM3...
  Testing plaintext communication protocol...
  Testing binary communication protocol...
  Testing alternate communication protocols...
WARNING: Device unplugged while connected to port
Disconnected.
Attempting connection at \\.\COM3...
  Testing plaintext communication protocol...
  Testing binary communication protocol...
  Testing alternate communication protocols...
  Connection failed.


after that communications are dead again unless i re-flash with icsp header using programmer .
then it all repeats .

have not tried printing from sd card yet . but im assuming it will work as it seems it a communication issue
of some type .


any ideas? is it a dead board ?

i have the updated 280 head on it as well as the better arms .
Wilsonngu
Plasticator
Posts: 5
Joined: Wed Nov 18, 2020 9:48 pm

Re: rostock max v2 comunication problems

Post by Wilsonngu »

Try Mattercontrol, other slicing softwares if that does the same thing you can conclude it's the communication from Rambo-PC for sure. If you have a spare USB to Rambo cable I suggest replacing it otherwise that might be the issue.
Post Reply

Return to “Troubleshooting”