We use Mydata PNP equipment, and are quite happy with it's speed and accuracy, especially with the latest version of the Mydata Tpsys software which includes a prototype version of their emergent auto-teach function for package sizes that can handle BGAs quite nicely in the real world.
Unfortunately, I have recently assumed complete programming responsibilities for our Mydatas, and have found that no previous backups of our Packages database exists except for the standard Mydata defaults, and the previous programmer did not follow a consistant naming or programming standard for making Packages. As a contract manufacturer we have many different customers, and each customers component packages have been programmed from scratch and given unique names to link them with the customer.
This works fine in production, except for the time wasted programming new packages when there is assuredly a similar or identical package already in the system somewhere, under a strange name.
I have cleaned out a lot of the redundant packages that were under different names using Mydata's web interface and database search functions, but there are several thousand defined Packages in our system. Verifying each package as to accuracy will be a time consuming process, to say the least.
If any kind soul out there has already built a proper Mydata database of defined Packages using proper industry naming conventions, and is willing to help share their wisdom, please please please contact me at jpatricelli@analog-tech.com
reply »