On Dec 23, 2009, at 12:58 AM, beverageexpert <beerm...@gmail.com>
wrote:
> --
>
> You received this message because you are subscribed to the Google
> Groups "MakerBot Operators" group.
> To post to this group, send email to make...@googlegroups.com.
> To unsubscribe from this group, send email to makerbot+u...@googlegroups.com
> .
> For more options, visit this group at http://groups.google.com/group/makerbot?hl=en
> .
>
>
On Dec 23, 12:08 am, David Casey <dave.ca...@gmail.com> wrote:
> Search through your gcode for lines starting with M104. I've seen
> multiple temperature change lines in the few objects I've tried.
>
> On Dec 23, 2009, at 12:58 AM, beverageexpert <beermake...@gmail.com>
It's a lot easier just to install a new table. That way you don't have
to try and correct the g code on every sketch.
--
J. E. 'jet' Townsend, IDSA
Design, Fabrication, Hacking
design: www.allartburns.org; hacking: www.flatline.net; HF: KG6ZVQ
PGP: 0xD0D8C2E8 AC9B 0A23 C61A 1B4A 27C5 F799 A681 3C11 D0D8 C2E8
I am in the same boat (Batch 8 Makerbot). I have gathered _a_ set of
firmware source files and I got them to compile last night, but I'm
still looking for a way to check what I built against the standard
download hex file to ensure I grabbed the right stuff in the first
place and built it correctly.
I also wouldn't mind experimenting with the I2C LCD display stuff I
saw - I have the displays already, and at least one of them (made by
Matrix Orbital) does have an I2C interface right there. Being able to
read real-time reports from the bot about temp and such looks very
interesting.
-ethan