Complete upgrade - result: Printer does nothing!!! Please help!

[rabbit]

Hello everybody,

I wanted to give my Rostock V2 a nice upgrade and installed the new Cheapskate Carriage Set, the SeeMeCNC EZR Struder,
the HE280 Hotend, the Rostock MAX Ball-Cup Delta Arm Kit and the Hotend Whip.

I assembled everthing thoroughly according to the plan. But after I switched the printer on and installed the new firmware the printer does not react to any commands!!! The screen on the printer just shows firmwaredate and modelltype. The knob has no more function and if I try to home the towers through Mattercontrol nothing happens!!! The only thing running are the fans.

I don't know if that gives a hint but on the left upper corner of the ramboboard is an orange led blinking 2 times and then pausing.
right above a green one that is constanly shining.

Any suggestions what I can do??? I am so desperate...

Thank you

the screen stays this way

the GCode Terminal shows this:

->Communication State: AttemptingToConnect

->M105

->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:879
<-
<-Autoretract:0
<-
<-X:0.00 Y:0.00 Z:0.000 E:0.0000
<-
<-SpeedMultiply:100
<-
<-iis2dh accelerometer initializing...
<-
<-start
<-
->M114

<-Transformation matrix: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000
<-
<-Free RAM:879
<-
<-Autoretract:0
<-
<-X:0.00 Y:0.00 Z:0.000 E:0.0000
<-
<-SpeedMultiply:100
<-
<-iis2dh accelerometer initializing...
<-
<-start
<-
->M105

<-Transformation matrix: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000
<-
<-Free RAM:879
<-
<-Autoretract:0
<-
<-X:0.00 Y:0.00 Z:0.000 E:0.0000
<-
<-SpeedMultiply:100
<-
<-iis2dh accelerometer initializing...
<-
<-start
<-
->G28 X0


...
...
...

[mhackney]

I'm guessing the whip wiring to RAMBo is not corr cut. We've seen similar lock up issues reported here recently and they all resolved to wiring. Specifically the red and black I2C wires and or the blue interrupt wire.

[mhackney]

I'm guessing the whip wiring to RAMBo is not correct. We've seen similar lock up issues reported here recently and they all resolved to wiring. Specifically the red and black I2C wires and or the blue interrupt wire.

[rabbit]

thank you for the quick response mhackney!!! that was a great hint!
I checked a little and it seems like you have a crystall ball.
there is a problem with the i2c wiring. I will replace that tomorrow.

by the way: which is the right machine to choose in the firmware? the v3 or v2?

[mhackney]

Choose V3 but you also have to change the direction of the Y stepper since they are different from the V2 printer to the V3 printer.

[mhackney]

Like a broken clock, I'm right about twice a day

[rabbit]

I checked all the wires and found 2 failures!
...twisted the thermistor and the fan wiring with the TO!

I fixed everything and it seems to be good now.
But before I risk anything else...
Where do I have to switch the the Y stepper???
I didn't find anything in the instructions about that?!

Big thanks to your great help! you made my day

[rabbit]

in the firmware under "configuration.h" I found these lines:

// ###### Inverting Axis Settings for Orion/Rostock MAX v2/DropLit
#if PRINTER == 1 || PRINTER == 2 || PRINTER ==4
#define INVERT_X_DIR 1
// need to invert Y axis for newer PSU Orions
#if POWER_SUPPLY == 2
#define INVERT_Y_DIR 1
#else
#define INVERT_Y_DIR 0
#endif
#define INVERT_Z_DIR 1
// ERIS Delta
#elif PRINTER == 3
#define INVERT_X_DIR 0
#define INVERT_Y_DIR 0
#define INVERT_Z_DIR 0
// Rostock MAX v3
#elif PRINTER == 5
#define INVERT_X_DIR 1
#define INVERT_Y_DIR 0 (changed it from 1 to 0)
#define INVERT_Z_DIR 1
#endif


is this right so far?

[LAGR]

I'd like to piggyback on to this, I just installed probe board and i'm getting the same boot loop. I've double checked all my wiring, tried swapping the thermistor leads and double checked my firmware changes and can't find any issues so i'm pretty much out of ideas.

This is what my terminal shows if that's any help
http://imgur.com/a/obyhe

[mhackney]

Safe money says you have a wiring problem. Quadruple check those wires on both the HE280 connector and on RAMBo. I'd recommend disconnecting everything and doing it all over. Sometimes it's difficult to see a problem staring right at you!

[Jimustanguitar]

I'd like to piggyback on to this, I just installed probe board and i'm getting the same boot loop. I've double checked all my wiring, tried swapping the thermistor leads and double checked my firmware changes and can't find any issues so i'm pretty much out of ideas.

I'll +1 this as well. I did the upgrade on Thursday, and haven't gotten usable results yet. The printer never leaves the boot screen with the version number, and the yellow USB rxtx LED is blinking rapidly. If I unplug the i2c connector, the light doesn't flash and it boots 'normally' and moves to the next screen, allows me to connect, etc.

Do the USB and the i2c share communication in some way that's changed over the different RAMBO versions? I've got a v1.1b. Is the i2c pinout the same across all the versions?

I'll double check my wiring this evening, but I'm fairly confident that I don't have things flipped. I'll also check the connector's pinout, if that doesn't uncover a smoking gun.

[mhackney]

I just looked at the 1.1b and 1.3 schematics and the I2C pinouts are the same and there is no interaction with USB. However, there is a comment on the 1.3 schematic "*Ignore 1 on silkscreen, use X10 as X10-1 position." but I don't think that is material. On both schematics:

X10-1 is VCC
X10-2 is GND
X10-3 is SCL
X10-4 is SDA

SCL and SDA are the I2C pins.

Double check your SDA and SCL wire colors and pins at both ends (HE280 connector and RAMBo connector).

[mhackney]

Oh, and post a photo of the connector on RAMBo if you can.

[Jimustanguitar]

I might have had a breakthrough. It appears that the position of pins 1-4 are reversed in regards to the shape of the connector housing between versions 1.1 and 1.3.

On the version 1.1, if the 'key' of the connector faces you, pin #1 is on the left side.

[img]http://i.imgur.com/tcTKYDn.jpg?1[/img]



And on the version 1.2+ diagram, pin #1 is to the right.

[img]http://i.imgur.com/mLv4w4f.jpg?1[/img]



I haven't tested it yet, but that may be it. On the older Rambo's, you need to flip the stock connector pins on the pre-made harness.

Am I crazy, or could that be it?



***edit***
I can say that after flipping the i2c connector around, the machine boots past the splash screen, so that's good! No idea about probing yet, but one problem checked off the list.

The next problem is that I'm getting a temp def. For about a second both temps read between 15 and 25 (need to change the firmware for the E3D thermistor) but right after that it goes into default. If I flip the polarity of the thermistor wires, it reads -50c before going to def, so I want to believe that I had it right the first time... I'll try it again after I invert the Y axis in the FW and change the thermistor value. Stay tuned!

[mhackney]

Great work! Are the pins in the same order with respect to the key or opposite?

[Mac The Knife]

Gotta love open source.

[Jimustanguitar]

Well... I'm a little less sure now. When I look at the silkscreen for the 1.2+ boards, there are two #1 markings.
I don't dig into schematics like this very often, so I don't know which one is right.

[img]http://i.imgur.com/xnTqzKR.png?1[/img]

Is there a significance to whether a mark can be seen, or if it gets covered up by its connector?

Interestingly, both #1's are on top of each other on the 1.1 boards' silkscreening.

[img]http://i.imgur.com/hRMeQGo.png?1[/img]

[Eric]

I can visually see that pin 2 in that last image is ground. Note that it's connected to pin 2 in the endstop connectors, which are also ground. You can confirm this with a meter...you should get a 0Ω reading between that pin and any known ground pin. Ditto for pin 1 and any known VCC pin. Whereas pins 3 and 4 should have close to a 10KΩ resistance reading between each pin and VCC because of the pullup resistors on the data lines (R44 and R45 on your images).

Also, there's a note on the schematic from the rambo 1.3 wiki page: http://reprap.org/mediawiki/images/d/d0 ... c-note.png, by the I2C connector, which reads: "*Ignore 1 on the silkscreen, use X10 as X10-1 position."

[Jimustanguitar]

I can visually see that pin 2 in that last image is ground. Note that it's connected to pin 2 in the endstop connectors, which are also ground. You can confirm this with a meter...you should get a 0Ω reading between that pin and any known ground pin. Ditto for pin 1 and any known VCC pin. Whereas pins 3 and 4 should have close to a 10KΩ resistance reading between each pin and VCC because of the pullup resistors on the data lines (R44 and R45 on your images).

Also, there's a note on the schematic from the rambo 1.3 wiki page: http://reprap.org/mediawiki/images/d/d0 ... c-note.png, by the I2C connector, which reads: "*Ignore 1 on the silkscreen, use X10 as X10-1 position."

You are correct. I can measure +5VDC potential between 1 and 2... That means that the SeeMeCNC harness is correct, and my confusion was caused by a misprint on the Rambo silk. Nice catch on the note in the schematic. I was looking right at it today, and didn't even notice that it was there.

What's more puzzling is the fact that the correct wiring and pinout, that I tried first before changing anything, is what was causing my printer to hang. I suspect that my clock and data are flipped. I'll check back later, when I've inspected it.

[Jimustanguitar]

Found it!!!

The white wire in my harness was open at one of the splice blocks that I'm using up top. (which are pretty cool, by the way)
I'm anal about never seeing copper on my wiring connections (fixed too many jobs where idiots have shorted things), so I tend to under strip wires ever so slightly, and that's how I shot myself in the foot this time with the spring connectors.

MHackney's right 3x. Check your wires!

The white wire of the harness is one of the ones that goes to the thermistor on the Rambo, and that one in particular is also what the accel board is using as an unswitched ground. Now everything makes sense. The thermistor was open which caused the odd temperature errors, and since the board wasn't receiving a ground signal, I presume that it was trying to ground through the i2c clock and data wires, which would explain the rapid flashing.

On to (hopefully) calibration!

[nrbelk]

I'm having this problem as well.

At first I was getting no change in my Int 1 (I read that on a nudge it should go to int 0)

So someone suggested that I had the T0 wiring backwards (I was still getting correct temperatures).

I swapped them and I started getting the exact error as above.

I've checked all my wires (visually, my multimeter is in storage from a move and I can't get to it) and by swapping them around. I think they are both getting electrical signal as I'm getting the temp correctly when I have them wired in the old way (not swapped).

Any ideas?

[nrbelk]

Just to see what happened, I removed the blue wire (from the wiring harness) from the rambo and swapped it to the other pin. Nothing changed. Should I have seen changes if that pin wasn't connected at all (or swapped like I did)?

[nrbelk]

I swapped my T0 wires back to their stock position and this is the result I get at startup. So maybe my problem isn't similar...

<- start
<-
<-Transformation matrix: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000
<-
<-Free RAM:830
<-
<-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: 0
<-
<-read reg 32 value: 7
<-
<-read reg 32 value: 156
<-
<-read reg 34 value: 0
<-
<-read reg 34 value: 64
<-
<-read reg 37 value: 0
<-
<-read reg 37 value: 0
<-
<-read reg 35 value: 0
<-
<-read reg 35 value: 48
<-
<-read reg 36 value: 0
<-
<-read reg 36 value: 74
<-
<-read reg 48 value: 0
<-
<-read reg 48 value: 32
<-
<-read reg 49 value: 106
<-
<-read reg 50 value: 0
<-
<-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: 0
<-
<-read reg 54 value: 50
<-
<-read reg 55 value: 0
<-
<-read reg 55 value: 0
<-
<-read reg 56 value: 0
<-
<-read reg 56 value: 16
<-
<-read reg 57 value: 0
<-
<-read reg 58 value: 0
<-
<-read reg 58 value: 50

[nrbelk]

The problem was that the wiring whip was shipped with the blue wire (PS_ON) wired incorrectly at the connector that connects to the rambo.