This sounds like you want a bed-of-nails to get the values to work from.
Expect to pay $1000 for the unit + engineering to design it.  Not cheap.

The alternative is to have the device talk to you and accept changes, which
it stores in an EEPROM.  This is the method I have used several times and
it is MUCH preferable.


>3. Creates the proper code (would it have to COMPILE or just modify the
>right bits in a hex file?)

Just modify the hex file.  You need to be able to read the correct line,
adjust the value, and rewrite it.  The reason for this is that the HEX file
has a checksum on each line.

>4. Squirts the program into a PIC either in- circuit or just before
>insertion

Either method works.  I do the in-circuit deal on my stuff.

>It sounds really complex and capitol-intensive.

It can be, but for really high volume it's cost-effective.  For small runs,
you are better to add a couple cents to the circuit so you have pads which
can be rx/tx data when in "not completely programmed" mode (ie, the EEPROM
is empty).

>Has anybody worked with these before?  Is there commercial equipment that
>does this task automatically?

Every one is unique.  That's part of the engineering.

Andy
==================================================================
   Montana Design Tech Support - http://www.montanadesign.com
==================================================================