Feed on
Posts
Comments

Just a quick post to let you all know that the Standalone Temperature Logger has now been updated to v1.1. This update is for the re-design of the PCB board, it’s now been adjusted so that there are components close to the battery solder joints thus making it easier to solder the battery.

Visit the Standalone Temperature Logger project page to view/download the update.

10 Responses to “Standalone Temperature Logger updated to v1.1”

  1. sergey says:

    hi! Good work! how are you going to use it? are you going to make lots of loggers and collect lots of data from lots of objects? (diy ecology monitoring…)??

    • Alex says:

      Thanks, I thought I would just put it in a little box and keep it outside for a few weeks and see how the temperature changed over that time, it’s convenient because you can just set it up then forget about it until you need to check the temps.

      There’s so many things you could do with it, like test your fridge/freezer, check a room’s temperature over a few weeks, put it in a car to see how hot it gets when outside in the sun, maybe even make a waterproof case then put it underwater in a lake, that would be fun!

      I was thinking about buying some PCBs and possibly turning this into a kit of some sort if there is interest. Only downside is that people will need an Arduino to program it or to extract the data (unless I make a small reader for it to connect via USB but that would probably take me a long time).

      • ptichki_pichuzhki says:

        whoa! USB interface! how long will it take to add such a functionality?
        or may be it’s possible to connect this board to a mac using FTDI data cable? I hate the idea of buying Arduino just for the purpose of data transfer…

        • Alex says:

          Hard to say, I’m working on the write up of another simple project which I should have up in a few days then after that I’ll probably look into the AVR-USB thing.

          But just for you to note that you will have to program the ATtiny85 using a programmer, do you have a device to do so? (I used the Arduino as you probably already know). Or were you expecting to buy a kit? (This would be interesting to do)

          I feel I should just mention that this temperature logger is very basic and designed to be small and cheap, thus it doesn’t log the time or have a crystal so the time delay specified can vary up to 10%.

          • ptichki_pichuzhki says:

            Well, I have an ISP programmer which I use for my tiny2313, and it seems to be perfectly enough for me – that’s why I don’t want buying an Arduino. All in all I do not see any sense in Arduino and I can’t understand all this ado about it – it seems an overkill in most cases, and it still does not allow in-system debugging (As I am on a mac, so, no avr studio is available for this platform, and debugging features of Arduino software could be a plus, but it has no such features… )

            As for your device – of course it would be much better if it could keep the full log (with date and time), but this version is also OK. And I really appreciate your scientific and weighted approach when designing the firmware.

  2. sergey says:

    Good idea about “small reader” – but it will be better – portable, with LCD and some connector…. to read logger at just “plug&read&save” to SD card! for field adventures, nature monitoring … i’ll think more about it!!! i have attiny45, will it be enought memory?

    • Alex says:

      That sounds good. The SRAM size is like under 50 bytes so barely nothing. At the moment the flash size I use for my program is 4220 bytes, you will need to get under 4K bytes for the ATtiny45 which you could do if you removed some code that isn’t needed from my program, for example, remove the part about configuring the delay time or communication with Arduino, it’s up to you.

      If you are connecting up to an LCD, etc you need to take care with the voltage difference between than and the ATtiny45 (if you run the ATtiny45 like I did with a 3V battery).

      Good luck!

      Edit: Also the EEPROM on the ATtiny45 (256 bytes) is half the size of the ATtiny85 (512 bytes).

      • ptichki_pichuzhki says:

        4220 is the size of a .hex file? cause it’s twice as more than the actual size of machine code.

        • Alex says:

          The properties of the .hex file from windows reads as 11.6 KB (11,885 bytes) however if you use avr-size to the .hex file it reads as below.
          text data bss dec hex
          0 4220 0 4220 107c
          It confirms the 4220 bytes given by the Arduino software [Binary sketch size: 4220 bytes (of a 8192 byte maximum)].

          I opened the .hex file and it looks like:
          :1000000047C061C094C05FC05EC01AC45CC05BC022
          :100010005AC059C058C057C080C055C054C008000D
          ….
          :1010600090959B01AC01BD01CF010895F894FFCF8D
          :0C10700001000400010003000100FFFF6C
          :00000001FF

          By looking at that I figured out that the first lot of numbers is rising “:10001000” so this must be the address of where the rest of the data in that line is to go to. If we do 4220 bytes in hex it’s 107C, the 2nd last line says “0C107000” so I’m thinking that’s how avr-size gets the “real” size for the program that will go on the chip from.

Leave a Reply