Extuder not Comunicating with Motherboard [Solved]

Re: Extuder not Comunicating with Motherboard [Solved]

Azdle — Fri, 23 Apr 2010 21:21:13 -0400

I've solved the problem, it ended up being a bad RS485 serial chip. Replaced that and it talks just fine. Now I just need to figure out why the thermocouple isn't reporting to the real firmware.

Re: Extuder not Comunicating with Motherboard

Mdbaughman2 — Wed, 21 Apr 2010 13:49:03 -0400

Azdle Wrote:
-------------------------------------------------------

> Should the i2c connection go to the i2c pins or
> the D9 and D10 pins, on the extruder controller?

the Ic2 of the motherboard connects to d9 & d10 of the extruder board... And the rs485 also needs to be hooked up... a to a, b to b, the comm is via rs-485... the I2c is to control the stepper... (please anyone correct me if I'm wrong..)

Note #(18) in this pic: [reprap.org]

Extuder not Comunicating with Motherboard [Solved]

Azdle — Wed, 21 Apr 2010 11:41:32 -0400

I've been battling with this for over a week now. No matter what I've done, I can't get the Extruder Controller Board to talk to the Motherboard.
Note: I'm using the tech zone remix boards
There are a few things that I'm not sure of:
Do I need the i2c line for simple serial communication? (as in to get any indication that it's working) Looking at the testing wiki page it seems that it should work w/o it, at least somewhat.
Should the i2c connection go to the i2c pins or the D9 and D10 pins, on the extruder controller?

Here's a bit of the comm debug output:

comms: G-code: M105 dequeued and sent [62.493s/0ms]
comms: GCodeWriter.waitForOK() - temperature reading: T:0 [62.503s/10ms]
comms: GCode acknowledged with message: ok EB [62.505s/2ms]
comms: G-code: T0 dequeued and sent [62.506s/1ms]
comms: GCode acknowledged [62.510s/4ms]

This is with everything connected up, but it seems like there is no communication at all.

If anyone has any insight into this, I'd greatly appreciate your input.