latest replicatorG/firmware not reading temp

[jet]

I'm working on finishing the heated build platform, and I'm stumbling
over an odd problem. I've built ReplicatorG (0011), and built/installed
the latest ArduinoSlaveExtruder and SanguinoMaster. I can control the
servos just fine, and the extruder motor responds, but I'm getting "0.0"
temperature readings on both the extruder and platform. If I switch to
the regular Cupcake mode, I still get a 0.0 temperature from the extruder.

When ReplicatorG launches, it reports Motherboard firmware v1.6 and
Extruder v1.7, that seems to match with what's in the source tree.

Any debugging tips? I found the code that lights DEBUG_PIN, it looks
like data *is* being received by the extruder controller, now just to
find out if the temp is being read/sent properly.

--
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

[anykey]

Hi,

there is a change your termistor is broken / not working. Check the
resistance at normal temperature on it, should be about 100k ohm
anything lower then 50 is for sure bad i believe.

[jet]

Yeah, just checked that on the off chance I was shorting it out. I also
need to see if it's using the right table -- I have the 1mm therms, not
the 3mm therms.

--jet

> --
>
> 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.

[jet]

Also, if I revert to the dist ArduinoSlaveExtruder, I get a temp reading
for the extruder. If I use a locally built version, I get 0.0 on both.

> --
>
> 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.
>
>
>

[jet]

Rebuilt with the table I made for the 1mm thermistor and now things
appear to be working. Will do some tests tonight, maybe Sandy Claws
will bring me a working configuration for the morning. :-)

--jet

> --
>
> 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.
>
>
>

[MakerBlock]

Hi Jet,

If you don't mind, could you post the table you used for the small
thermistor along with some info about how you updated the table? I'm
having the exact same problem with the extruder displaying a 0.0
temperature.

Thanks!

MakerBlock

On Dec 24, 5:59 pm, jet <allartbu...@gmail.com> wrote:
> Rebuilt with the table I made for the 1mm thermistor and now things
> appear to be working.  Will do some tests tonight, maybe Sandy Claws
> will bring me a working configuration for the morning. :-)
>
> --jet
>
>
>
> anykey wrote:
> > Hi,
>
> > there is a change your termistor is broken /notworking. Check the

> > resistance at normaltemperatureon it, should be about 100k ohm

> > anything lower then 50 is for sure bad i believe.
>
> > On Dec 24, 9:18 pm, jet <allartbu...@gmail.com> wrote:
> >> I'm working on finishing the heated build platform, and I'm stumbling
> >> over an odd problem.  I've built ReplicatorG (0011), and built/installed
> >> the latest ArduinoSlaveExtruder and SanguinoMaster.  I can control the
> >> servos just fine, and the extruder motor responds, but I'm getting "0.0"

> >>temperaturereadings on both the extruder and platform.   If I switch to
> >> the regular Cupcake mode, I still get a 0.0temperaturefrom the extruder.

>
> >> When ReplicatorG launches, it reports Motherboard firmware v1.6 and
> >> Extruder v1.7,  that seems to match with what's in the source tree.
>
> >> Any debugging tips?  I found the code that lights DEBUG_PIN, it looks
> >> like data *is* being received by the extruder controller, now just to
> >> find out if the temp is being read/sent properly.
>
> >> --
> >> 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
>
> > --
>
> > 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 athttp://groups.google.com/group/makerbot?hl=en.

[jet]

MakerBlock wrote:
> Hi Jet,
>
> If you don't mind, could you post the table you used for the small
> thermistor along with some info about how you updated the table? I'm
> having the exact same problem with the extruder displaying a 0.0
> temperature.

original post with sensor readings and content for ThermistorTable.cpp:

http://groups.google.com/group/makerbot/msg/8f1e8c0150cfadcd

You'll need to rebuild ArduinoSlaveExtruder and upload the new binary to
the extruder controller. If you haven't done that yet, or uploaded a
new motherboard controller, I suggest building both from source without
changes and uploading them just to make sure you have your Arduino
environment set up correctly. See "Upgrading Your Firmware" on the
main wiki page: <http://wiki.makerbot.com/cupcake>.

[Ethan]

On Dec 25 2009, 10:10 pm, MakerBlock <j...@makerblock.com> wrote:
> Hi Jet,
>
> If you don't mind, could you post the table you used for the small
> thermistor along with some info about how you updated the table? I'm
> having the exact same problem with the extruder displaying a 0.0temperature.

Hi, all,

Add me to the list of folks with 0.0 degree issues with the latest
version of the firmware.

I started with the distro 1.6 extruder firmware and have been using
that successfully for weeks. Without touching the hardware, I
uploaded a newer version of the firmware that I got from the 'tip'
with 'git clone' then patched with the recent updates for a heated
build platform. On my next run, I can see the build platform temp box
in ReplicatorG v0010 (updated) and I can turn all three MOSFET
channels on and off through the GUI (check box or a higher temp,
depending on the channel), but my extruder thermistor, which used to
report the temperature of the room right after I fired up the bot, now
reports 0. I'm sure there is no problem with thermistor wiring and
such. Something I'm doing with the firmware is not correct.

This is the first time I've tried to build the firmware from source.
I have not yet tweaked the thermistor table for my 1mm thermistor -
the table is identical to what's in the source repository. I have
previously checked the thermistor - it _is_ a 100K version that
fluctuates around 80K or so, and down to around 60K if I breathe
directly on it (~35C air).

Are there any obvious things I could be missing? I'm familiar with
the Arduino environment and how to build code from source. These are
not new to me. What I don't know is how I can confirm I've building
this package from the right source file beyond getting a payload size
from the Arduino framework.

Thanks,

-ethan

[jet]

Ethan wrote:
> Are there any obvious things I could be missing? I'm familiar with
> the Arduino environment and how to build code from source. These are
> not new to me. What I don't know is how I can confirm I've building
> this package from the right source file beyond getting a payload size
> from the Arduino framework.

I manually changed the version number to one higher than what I
downloaded from git -- that way I'd know for certain that my code was
getting installed and run.

[Ethan Dicks]

On 1/8/10, jet <allar...@gmail.com> wrote:
> Ethan wrote:
>> ... What I don't know is how I can confirm I've building

>> this package from the right source file beyond getting a payload size
>> from the Arduino framework.
>
> I manually changed the version number to one higher than what I
> downloaded from git -- that way I'd know for certain that my code was
> getting installed and run.

That will certainly tell me that I'm running what I've just built, but
since I can get all three MOSFET channels to respond to manual
manipulation through ReplicatorG, that isn't where I'm concerned - if
my firmware hadn't updated, then I wouldn't be able to get channel "A"
to respond.

What I really meant was in the absence of any sort of "release 1.x"
tags, how can I be sure that the source files I grabbed with 'git
clone' will build a working program in the first place. I wouldn't
presume to call 'tip' files a stable release.

-ethan