> What is the typical unit_count for applications you make?

It varies a lot.  I've got everything from two units for proof of concept
to lifetime volumes in the hundreds of thousands.  Even if volumes end up
being small, most costomers are optimistic and think everyone will
naturally want their little better moustrap.  There's also the issue of
cramming additional features into an existing design.  Sure, a 16F876
could easily take over from a crammed 16F628, but not without a board
redesign.

The point is that there are a lot of reasons beyond production volume for
chosing a PIC and the development environment.  If you use ONE environment
accross projects, then you end up knowing it very well and and justify
spending some time on customizing and maintaining it.  We've started with
MPASM and enhanced the environment significantly where we found it
lacking.  We've used it so much that we are very comfortable with it and
can whip out a new project quickly.  Also, there are now a lot of modules
and library routines that can be re-used, which is worth a lot.  The
statement often heard here that you can develop a project faster in a
higher level language versus assembler is just plain BS in my opinion.  It
has nothing to do with high or low level language, but how comfortable you
are with the development environment and how much re-usable code you have
sitting around.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.