Yahoo Groups archive

AVR-Chat

Index last updated: 2026-04-28 22:41 UTC

Message

[OT] Re: [AVR-Chat] ATtiny84/85 suppliers - NZ/elsewhere?

2007-03-02 by Ivan Vernot

Hi David,
Welcome.
Sorry I can't help you directly (I don't use the Time84/85)
I am writing as your have the same name as a former colleague and I am 
curious as to how small the world can be ;-)

Have you ever done software development in Oz?

Specifically, working for a small company with a digit and a letter in the 
name? ;-)

In Toongabbie/Girraween NSW  - working from 'wood panelled area' erected 
inside a factory unit with desks arranged  in two rows like at school.
Working on  a project that was already late even before the team was hired!

Ahhh those where the days (NOT!)  .... Around the late 80's/early 90's?

Cheers,
Ivan Vernot


----- Original Message ----- 
From: "David McNab" <rebirth@orcon.net.nz>
To: <AVR-Chat@yahoogroups.com>
Sent: Wednesday, February 28, 2007 12:01 AM
Subject: [AVR-Chat] ATtiny84/85 suppliers - NZ/elsewhere?


> Hi,
>
> I'm an AVR newbie (converting from PIC), looking to get hold of some
> ATtiny84/85 devices.
>
> One problem is that here in NZ, none of the usual retailers (Sicom,
> Jaycar, RS, Farnell etc) seem to carry them.
>
> The other problem is that DigiKey adds NZ$60 to small NZ orders, in the
> form of 'international fee' and inflated shipping costs. I don't want to
> deal with DigiKey unless I'm buying >$200 worth of parts, which won't be
> for quite a while yet.
>
> Does anyone know of an NZ (or even Australia) based supplier who carries
> these devices, and can accept payments by credit card or paypal?
>
> Alternately, is there anyone here who deals regularly with DigiKey and
> wouldn't mind buying some on my behalf? I could pay you the parts
> prices, postage and a bit extra for your trouble.
>
> Cheers
> David
>
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.