Comments for ATtiny13 and some hacking...

Comment on Programming ATtiny13 with USBtinyISP by Programming ATtiny13 with USBtinyISP – Ubuntu « ATtiny13 and some hacking…

Tue, 27 Apr 2010 20:09:50 +0000

[...] made a tutorial on how to program your ATtiny13 (or other ATtiny) on windows with USBtinyISP, here. This post will be a quick tutorial on how to do it on Ubuntu (9.10). For me it was a lot of work, [...]

Comment on VMLAB with ATtiny13 by admin

admin — Thu, 15 Apr 2010 21:46:18 +0000

Thanks for reply. I took that code from the other website/tutorial and someone says this:
=================
# scienceprog Says:
September 4th, 2006 at 2:26 pm

Diodes can be connected only to VDD. this means that anode has to be connected to VDD like D1 VDD PD1
==================

For double check you could try the vmlab forum.

Comment on VMLAB with ATtiny13 by DerKnipser

DerKnipser — Fri, 09 Apr 2010 09:37:53 +0000

Hi,
good Tut for beginners (as I am).

But as I understand it, there is a little mistake in your connection diagram.
With the command:

D1 VDD D1_NODE

R1 D1_NODE PB3 0.62K

I think a Diode is connected to VDD (5V, not GND) with its anode and with its cathode to the resistor R1, whose other pin is connected to Port B3. So this is how I would wire it in reality. I rebuilt this in VMLab and the diode turns ON whenever Port B3 is 0. This suggests my belief, too.
Or am I wrong with this? I’m a little confused.

Comment on Nikon D40 infrared remote DIY by Jack Tanner

Jack Tanner — Mon, 15 Mar 2010 06:00:16 +0000

Or you can run a lirc client (e.g., irreco), which has an ML-L3 definition. The Nokia N900 makes for a great IR remote this way.

Comment on VMLAB with ATtiny13 by admin

admin — Thu, 11 Feb 2010 13:38:03 +0000

Thanks.
Good point about the clock (Mhz). I will leave your message here so people can read it.

Comment on VMLAB with ATtiny13 by Brian Lowery

Brian Lowery — Wed, 10 Feb 2010 20:46:50 +0000

Lars,
This is an excellent beginners tutorial on VMLAB. I followed your instructions and only had one minor problem. I forget initially to change the default clock frequency of 1.0 Mhz to 1.2 Mhz.

Comment on Basics Programming ATtiny13 by gruby poland

gruby poland — Wed, 10 Feb 2010 09:18:40 +0000

Great post! Make another one

Comment on Basics Programming ATtiny13 by admin

admin — Sat, 23 Jan 2010 17:48:12 +0000

Did you try the avrfreaks forums?

http://www.avrfreaks.net/index.php?name=PNphpBB2&file=index

Comment on Basics Programming ATtiny13 by Bill

Bill — Fri, 22 Jan 2010 22:37:27 +0000

Nice.. helps somewhat.. but im still a long way from being able to write the code I want. I know how to change some of the data sets in an exisiting prg I use, but want to write code to have my ATTINY 2313 do something similar but different than what it does now. I am currently running the SLM (brain Machine) from Mitch Altman(got from makezine.com).
Lots of fun and pretty cool. But what I need now is to change out the (tables?) with different data. I want to be able to set up specific led flash frequencies.. I dont know If this will all fit on one chip so may have to span the tables across several controllers and select the output”ranges” via a selector switch which would select differrent controllers for different ranges of flash rates.
I need to get my leds to flash at rates from 1hz – 600hz.
Probably would have one 2313 programmed with tables for say frequencies from 1-25hz or whatever fits and second chip from 26-50hz and so on. building and fabricating everything for me is rather a simple matter since at present I only need to flash two large leds. And adding a multipole selector switch to switch between controllers is easy too… Where I fall flat is in knowing how to program the chip /’s to do what I want..
if I can see the actual programming and where the data tables go etc for the first controller I might be able to manage subsequent controllers on my own.. Can anyone help me with this?

Thanks

Comment on Basics Programming ATtiny13 by admin

admin — Mon, 11 Jan 2010 15:33:16 +0000

Thanks for the reply.

I tried putting the delay under the main label and that did not work, so that is why I put it above it. Theoretically it shouldn’t bother where you put it, I guess.