The fourth argument, should be the net, not the net name. Just change that one line to this:
Set My_Tp = My_Board.PutTestPoint(TP_Cell, False, x, y, 0, Curr_net, , , 1, , , 0)
and it should work.
Thanks for you quick answer. I will check it soon.
I just wrote an update for AATK Testpoints. It allows the user to specify the number of testpoints per net in CES and then sync Expedition with this number. It also allows for some checking in CES on the number of Testpoints. Is this of use to you?
Here is the new DFT stuff, unzip this and replace the corresponding files in your AATK directory.
One note, you will not see the new CES menus on existing designs. When you start a new design it reads the user.cns out of your WDIR path and will build an ICDB with the new columns in it.
user.zip 9.8 KB
Thanks for you answer and code.
My intention was solving a bug of mine, in order to place Testpoints manuali , outside board, all of then, at once.
We use a file to feed the system with required testpoints.
Maybe, yous code gives a more sophisticated way to enter them.
But I have to check it first.
one question I have regarding your AATK extension for testabillity.
Is the number of engineering required Testpoints the user can add in CES also written to Expedition
nets property RequiredNumberOftestpoints ?
Also, it seems you have some experience with the user.cns file.
We tried to start using it, but in our evironment we have seen, that constraints added by one user were not visible for other ones.
How do you manage this with yoour AATK?
Yes I have code that takes the values in the first column and pushes that into Expedition as the required number of testpoints, the second column. I track these separately because there is two places to change this number I wanted the user to know how many were required from the front end verses the backend. The last column is just a status of how many were actually placed in the design.
For the user.cns file in AATK, if everbody has AATK in their WDIR path then there should be no problem between users since all are pointing to the same user.cns file.
thank you for the reply.
Now I can investigate in the AATK how it works in detail.
Unfortunately we can not use the AATK , because it has too much inside we do not need.
But many of them we have made by our own before in a slightly different way. It also is a great ressource
for additional tools.
A great job you are doing there. Thank you.
AATK was never intended as something on every desk. It is a set of example scripts and how to create menus so each company can pull out what is useful to them and create their own menus. You find a problem look and see if AATK has a solution, pull it out test it on your designs and put it in your menu.
I would like to know about TEST POINTS, can anybody give some Detailed idea about TEST POINTS.
* What is Test Points..?
* Why we need it..?
* To whom it is really useful ( Layout Designer, PCB Fabricator, Production fellows or in Board level testing and Debugging)..?
* what are all the constrains to be followed to use Test Points.
Kindly Help me,
Thanks in advance,
You may also find this link useful: http://www.testelectronics.com/dft.html. I also did a presentation at U2U in 2007 that may be of use: http://supportnet.mentor.com/member/u2u/2007/presentations/Heidel_LSILogic_pres.pdf
Thank you. it given me basic idea about my questions.
Very good persentation from Mentor regarding the DFT test ,It helps me a lot..
Thanks and Regards
I am not bale to place the testpoints using
Document.PutTestPoint(ByVal sCellname As String ,
ByVal bFromCentralLib As Boolean ,
ByVal dX As Double ,
ByVal dY As Double ,
ByVal dRotation As Double ,
ByVal pNet As IMGCPCBNet ,
[ByVal sRefDes As String] ,
[ByVal sPartName As String] ,
[ByVal eSide As EPcbSide = epcbSideTop] ,
[ByVal eFixType As EPcbAnchorType = epcbAnchorNone] ,
[ByVal eUnit As EPcbUnit = epcbUnitCurrent] , [
ByVal eAngleUnit As
EPcbAngleUnit = epcbAngleUnitDegrees]) As
Showing a type mismatch error