i2C malfunction

Having a problem? Post it here and someone will be along shortly to help
Post Reply
Axlspinedoc
Plasticator
Posts: 10
Joined: Wed Oct 05, 2016 11:59 am
Location: Mexico

i2C malfunction

Post by Axlspinedoc »

Good day everybody. Name's Axl and I'm new in the forums. I have read before about i2C problems, but I still can't resolve this. I hope somebody can help and, if it does, I will be forever grateful :D :D

So, at my work we have 4 Rostock's. We recently updated each one from V2 to V3 (HE280, Ball-cup joint arms, Injection Molded Cheapskate Carriage Set, and the PSU). All of them worked like a charm, but one. This one has been a nightmare.

First, when I tried running the calibration routine the extruder moved normally until the part where it positions just above the first probing point. The extruder comes down reaaaally slow. I thought it wasn't reading the accelerometer correctly, but when I connect the printer through Matter Control to my PC, the first readings I get are:

Code: Select all

->Communication State: AttemptingToConnect

->M105

<-start
->Communication State: Connected

<-
->M115

<-Transformation matrix: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000
<-
<-Free RAM:833
<-
<-Autoretract:0
<-
<-X:0.00 Y:0.00 Z:0.000 E:0.0000
<-
<-SpeedMultiply:100
<-
<-iis2dh accelerometer initializing...
<-
<-read reg 15 value: 51
<-
<-read reg 49 value: 106
<-
<-read reg 32 value: 156
<-
<-read reg 32 value: 156
<-
<-read reg 34 value: 64
<-
<-read reg 34 value: 64
<-
<-read reg 37 value: 0
<-
<-read reg 37 value: 0
<-
<-read reg 35 value: 48
<-
<-read reg 35 value: 48
<-
<-read reg 36 value: 74
<-
<-read reg 36 value: 74
<-
<-read reg 48 value: 32
<-
<-read reg 48 value: 32
<-
<-read reg 49 value: 21
<-
<-read reg 50 value: 20
<-
<-read reg 50 value: 20
<-
<-read reg 51 value: 0
<-
<-read reg 51 value: 0
<-
<-read reg 52 value: 0
<-
<-read reg 52 value: 0
<-
<-read reg 54 value: 50
<-
<-read reg 54 value: 50
<-
<-read reg 55 value: 0
<-
<-read reg 55 value: 0
<-
<-read reg 56 value: 16
<-
<-read reg 56 value: 16
<-
<-read reg 57 value: 0
<-
<-read reg 58 value: 50
<-
<-read reg 58 value: 50
<-
<-ok 0
<-
<-FIRMWARE_NAME:Repetier_0.92.2 FIRMWARE_DATE:20161227 MACHINE_TYPE:Rostock MAX v3 
<-
<-Printed filament:11213.76m Printing time:57 days 8 hours 41 min
<-
->M114

<-ok 0
<-
<-X:0.00 Y:0.00 Z:0.000 E:0.0000
<-
->M105

<-ok 0
<-
<-T:0.00 /0 B:0.00 /0 B@:0 @:0
<-
<-wait
I only have checked the wiring at this moment, but everything is correct (checked continuity with the connector of the HE280 and the terminal at the Rambo and everything is connected properly). I have flipped the i2c connector twice hoping it was a problem at the connector but when I flip it I get the send/recieve error at the terminal.

Please if somebody knows what could it be I would be really really happy, as this machine was printing fairly well before and all the others are already working well.

Firmware 0.92.2 with the date 20161227
RAMBo model...I'm not sure which model is but it is the one with the screw terminals that came with Rostock's V2
Here's a photo of the same board I have (Image found on google search)
[img]http://i.imgur.com/I4RdKtd.jpg?1[/img]
Eric
Printmaster!
Posts: 717
Joined: Sat Aug 18, 2012 4:09 am
Location: Chula Vista, CA

Re: i2C malfunction

Post by Eric »

What makes you think it's an i2c error? If I read correctly, the only failure symptom you've mentioned is that it's moving really slow. That sounds more like a configuration issue to me. Make sure your eeprom values seem correct and any firmware mods have been applied.

Are all of your printers actually of identical vintage? Same motors, same version of the rambo, etc? If you must, you have the advantage of being able to swap parts with a working printer until you identify which part(s) the problem follows.
Dale Eason
Printmaster!
Posts: 191
Joined: Fri Mar 06, 2015 8:56 pm

Re: i2C malfunction

Post by Dale Eason »

There is a probe speed value in the eeprom I think or at least in the configuration.h file. I would try clearing EEPROM and reload the firmware.

Dale Eason
Axlspinedoc
Plasticator
Posts: 10
Joined: Wed Oct 05, 2016 11:59 am
Location: Mexico

Re: i2C malfunction

Post by Axlspinedoc »

What makes you think it's an i2c error? If I read correctly, the only failure symptom you've mentioned is that it's moving really slow. That sounds more like a configuration issue to me. Make sure your eeprom values seem correct and any firmware mods have been applied.
Holy Guacamole, it was the configuration!
I exported the EEPROM Settings from one machine to this one, and I noticed that these values were off:

z- Probe Speed: 2mm/s (on the other, it was 50mm/s)
x y probe speed: 150mm/s (on the other, 90mm/s)
Autoleveing: 0 (on the other, 1)

I ran the calibration routine and it worked like a charm!
Thank you very much guys! Next time I won't focus only on electronics but also in the eepromm ;)
Have a good day
Post Reply

Return to “Troubleshooting”