--- In [email protected], "jean-pierre.char...@..." <jean-pierre.char...@...> wrote: > > lynchaj a écrit : > > > > > > > > Hi! Thanks! I am using EEschema version build 2010-04-19 23xx-unstable > > > > I recently upgraded EEschema to try to fix this problem but it remains. > > > > I am using WinXP home 32 bit. > > > Are you sure the ALPACA.sch file was created from the scratch. > It sounds like a copy outside Eschema of a file used in a complex > hierarchy, and never reannotated. > (There is a lot of garbage relative to successive annotations inside a > complex hierarchy in this file). > > You can easily fix annotation issues (at least if you do not have > already created a board) by clearing annotion and reannotate (Annotation > dialog) > > -- > Jean-Pierre CHARRAS > > Maître de conférences > Directeur d'études 2ieme année. > Génie Electrique et Informatique Industrielle 2 > Institut Universitaire de Technologie 1 de Grenoble > BP 67, 38402 St Martin d'Heres Cedex > > Recherche : > GIPSA-LAB - INPG > Rue de la Houille Blanche > 38400 Saint Martin d'Heres >
Hi! Yes, I entered the ALPACA schematic completely by hand, from scratch, in EEschema. I reannotated it once for the top half (Z80 SBC, CTC, SIO/0, IDE, etc) and assigned footprints with CVPCB to the components. Later on, I entered the bottom half (uPD7220) circuit in EEschema the same way and that's where the problems started. I was able to fix the schematic by manually editting the file to replace the U?'s with the appropriate Uxx values. There seems to be something funny going on with devices keeping their annotations in EEschema although I have no idea what. If I am the only person seeing this anomaly then maybe it is something I am doing? I pick and place each component separately without using cut and paste. I hope this helps! Thanks and have a nice day! Andrew Lynch
