We have received the DATA I/O UNISITE programmer. It is functional in 
the Hardware lab. It should program everything we need to program, 
even the TMS32010 family parts.

Data I/O just announced a trade-in value of $4000 for a 29A when 
purchasing a full featured unisite. (Last month the trade-in value 
was just $1000). Even though we have already placed our order and 
received the goods Data I/O will give us the $4000 trade-in. 

For $1000 trade_in value I wanted to keep the 29A. However, $4000 is 
too much to pass up, especially since there are two of them in the 
company. So, I propose to trade in the DIO 29A behind Cris Drobnys 
office to offset the $20,000 cost of the UNISITE. 

There is still a 29A in customer service if the need arises. (It used 
to belong to Manufacturing before they bought their DIO-2900.)

If you have a different view, speak now.
							Pat.

Regarding your intention to get rid of the Data I/O 29A:

1. Where will the Unisite be located?  Will it be moved to the location now 
   occupied by the 29A?

2. Will it program Bipolar PROMs?

3. Is it connected to the VAX?

4. Are there explicit written instructions for its use?

5. What is its projected usage? Presumably it was purchased in order to 
   program parts that could not be programmed on the 29A. What are these 
   parts and how much of the time do you expect the Unisite will be busy 
   programming these parts and therefore not available to program the parts 
   that would otherwise be programmed on the 29A?

6. The Unisite socket for PLCCs appears to be the same as that used on
   the 2900, which I evaluated. There is something you should know:

     	It doesn't work. 
   
   The first 2900 we had would not read a 320P15 no matter what. Data I/O 
   replaced it with a new unit that would sometimes read it if it was
   jiggled appropriately in its 'socket'. I would not trust it to program
   OTPs.

7. The 2900 had another problem with the 320P15 that may apply to ALL devices
   that you may want to secure. If you attempt to read the 320P15 after the
   Security Bit is set, the unit will refuse to read the device. It will
   inform you that the device is secured and cannot be read out.

   This is bogus. The security is in the device, not the Programmer.

   I have had a few 320P15s in which the Security Bit was set and verified
   but the part could still be read.

   I called Data I/O and informed them of this but they didn't understand why
   this is a problem.

   Does the Unisite do it this way, too?

 8. Rick has asked me to ask you to make sure the Unisite is working 
    completely before you get rid of the 29A.


Jed

> To: Mccarthy
> From: Margolin
> Subj:	Out-a-Site Programmer
> 
> Regarding your intention to get rid of the Data I/O 29A:
> 
> 1. Where will the Unisite be located?  Will it be moved to the location now 
>    occupied by the 29A?
In the Hardware lab, where it is now located. No, it will not be moved.

> 
> 2. Will it program Bipolar PROMs?
Yes. And PALs, GALs, FPLAs, FPGAs, EPLDs, EMICROs, EPROMs, ...

> 
> 3. Is it connected to the VAX?
Yes, via 9600 baud RS232. (Same as all the DATA I/O stuff here.)

> 
> 4. Are there explicit written instructions for its use?
Yes. I have posted them on the machine. They probably will not cover 
every situation. Only the current situations that I know about.

> 
> 5. What is its projected usage? Presumably it was purchased in order to 
>    program parts that could not be programmed on the 29A. What are these 
>    parts and how much of the time do you expect the Unisite will be busy 
>    programming these parts and therefore not available to program the parts 
>    that would otherwise be programmed on the 29A?
I don't know.

> 
> 6. The Unisite socket for PLCCs appears to be the same as that used on
>    the 2900, which I evaluated. There is something you should know:
> 
>      	It doesn't work. 
>    
>    The first 2900 we had would not read a 320P15 no matter what. Data I/O 
>    replaced it with a new unit that would sometimes read it if it was
>    jiggled appropriately in its 'socket'. I would not trust it to program
>    OTPs.
Duly noted.

> 
> 7. The 2900 had another problem with the 320P15 that may apply to ALL devices
>    that you may want to secure. If you attempt to read the 320P15 after the
>    Security Bit is set, the unit will refuse to read the device. It will
>    inform you that the device is secured and cannot be read out.
> 
>    This is bogus. The security is in the device, not the Programmer.
> 
>    I have had a few 320P15s in which the Security Bit was set and verified
>    but the part could still be read.
> 
>    I called Data I/O and informed them of this but they didn't understand why
>    this is a problem.
> 
>    Does the Unisite do it this way, too?
I don't know.

> 
>  8. Rick has asked me to ask you to make sure the Unisite is working 
>     completely before you get rid of the 29A.
> 
> Jed

The UNISITE is working to my satisfaction. It is in your own interest 
to check that devices you program are handled by the programmer. I 
will not do this since I do not know what devices you use. It should 
be able to program any currently manufactured part at least as well 
as the 29A can.