getting replicatorg v 4 to work

getting replicatorg v 4 to work

letsburn00 18 Jun 2009 14:19

I just installed the new firmware for the hardware, it took a while but all got going. I could use the old software (replicatorg 3) and old firmare and it would work fine for about a minute or two, then would crash with a bunch of errors.

Anyway, installed the new firmware, and then tried the new software. replicatorg can't seem to detect the new firmware though. it says I have Version .1 of the firmare installed, even though I have the new V 1.1 installed. any ideas on how to get it to not give this error? my temperature sensor still crashes after about 20 seconds from the control board, so i'm wondering if there is anything major that I've missed. For some reason when I test my extruder motor it works fine forward and back, but when it is set to stop the extruder doesn't stop but instead starts to reverse.

Oh and I'm using windows. replicatorg simply doesn't even want run in linux (kubunto) either in command or run from gui as root for some reason on my system.

Re: getting replicatorg v 4 to work

MaskedRetriever 18 Jun 2009 20:19

I recommend going to the Arduino console for debug. You can click the "serial monitor" button and see what the serial port is saying. (You may have to change the baud rate to see anything that makes sense.)

With this setup you can actually send gcodes and mcodes to the MakerBot directly, cutting out the (potentially broken) middle man of ReplicatorG. I had to do this because on the Gen2 hardware I ended up being totally unable to use ReplicatorG and with lots and lots of issues in the RepRap client.

The extruder motor issue looks like something I saw when I had my wires from the extruder motor crossed, but I don't know if that's even possible under the Gen3 electronics…

Re: getting replicatorg v 4 to work

phooky 19 Jun 2009 16:54

Hi;

It sounds like the 1.1 firmware didn't actually get installed. It can be a little tricky to get firmware up to the motherboard, since autoreset doesn't always work and the Arduino environment isn't particularly vocal when an upload fails.

I'd try these steps:

• Open the new firmware in the Arduino environment and check that it's indeed v1.1. The 1.1 firmware will include this line in SanguinoMaster.pde:

#define FIRMWARE_VERSION 101

• Make sure that the firmware got properly uploaded. Because autoreset doesn't always work on these boards, you may need to hit the reset switch at odd times. Here's our FAQ about updating the v1.1/1.2 motherboard firmware.

Also, can you give me some details as to what goes wrong when you try to run replicatorG in linux? I'm working towards an 0005 release in a week or so, and I'd love to get it working everywhere.