> My rep 1 mightyboard finally had its last run a while back and I ordered a
> FlashForge rev d board for the replacement.
>
> Got all my stuff out and quickly ran into problems. Learned to become
> proficient in removing and desoldering clips and pin connectors! Switched the
> screw downs from my old rep board for whatever clips were on the flashforge.
>
> Wired everything back up! Realized the power supply doesnt connect. Cut the
> cord and wired a + and - to the power and a + and - to the CS. (thanks, i found
> that info here!)
>
> Shut my eyes and crossed my fingers and plugged it in......
>
> It worked!
>
>
> So far so good... the system booted up and even printed out a nice little
> calibration cube.
>
> But I noticed a problem... my HBP bed was coming in at around 138/110 which
> seems pretty hot?
>
> I plugged the USB into the computer and fired up Replicator G 0040 and plugged
> my device in. I had to switch the extruder count from 2 to 1 on the LCD of the
> Bot then it seemed to read and connect!
*** NOTE ***
RepG 0040 was released in Nov 2012 by MakerBot and then promptly abandoned.
It has some serious bugs. Bugs which will corrupt portions of the EEPROM
on ANY printer running a firmware with a version number of 7.0 or later.
I'll spare you the details: it's been posted about at least a hundred times.
So, if you connected RepG 0040 to your printer over USB, then you likely corrupted
some of youre EEPROM. You will need to wipe the EEPROM. You can do that with the
Sailfish firmware from the LCD display,
http://www.sailfishfirmware.com/doc/ui-utilities-menu.html#x17-540003.7.18
And then, if you need to connect over USB from RepG, run the correct RepG....
Namely, RepG 40r33 - Sailfish which is a download of the Sailfish Thing
at
thingiverse.com.
> So heres where i hit my next hurdle: I tried to print from RepG and the machine
> goes to "home" then heats up then goes to the about to begin position but then
> nothing. It just sits there. Something on the LCD screen along with the temps
> says Z location, dont quite remember? and flashes ?
Anyone's guess if you caused corruption of the EEPROM.
> Then the only other line in repG says the offsets are deprecated?
Sounds like you were trying to run some old RepG 39 or earlier gcode
through RepG 40. Or you have some old starting gcode files of your own
about (perhaps and old slicing profile).
Dan