[Diy_efi] help with Eagle PCB software

[Torbjörn Forsman]

Although not just Eagle related, it can happen in any PCB cad system 
that a schematic design gets corrupted.

My specific experiences relate to old DOS versions of Cadstar, in case a 
schematic has got corrupted there is a chance to salvage it by exporting 
it as an "ascii dump", then restart the schematic editor and import the 
ascii dump. At my former job, we called that process "washing" a 
schematic. I think most of those corruption problems were related to DOS 
- too little environment space, problems with TSR programs, network 
drivers etc. Cadstar seems not to be very tolerant to such problems.

In really nasty cases, one can check out the ascii dump with a text 
editor to see what nodes really are connected to which nets and maybe 
have luck with manual editing.

Best regards

Torbj?rn Forsman

Steve Ravet wrote:
> sorry, forgot to mention that when I use the show command and click on the VIGN net, the VBATT net is also highlighted.  So somehow these 2 symbols are still connected to each other logically, even though they are not connected via a wire.
>  
> thanks,
> --steve
>  
> 
> ________________________________
> 
> From: diy_efi-bounces at diy-efi.org on behalf of Bernd Felsche
> Sent: Thu 3/2/2006 8:27 AM
> To: diy_efi at diy-efi.org
> Subject: Re: [Diy_efi] help with Eagle PCB software
> 
> 
> 
> On Thursday 02 March 2006 13:02, Steve Ravet wrote:
> 
>>I'm putting together a schematic and PCB using Eagle for the first
>>time and I'm having problems, mostly with ERCs on the power pins.
>>Is anyone here familiar with Eagle and willing to lend a hand?
>>This is an EFI related project...
> 
> 
> If it fails an Electrical Rule Check, then double-check the
> connections on the power pins, including those on devices with
> designated power supply.
> 
> If you've used standard pads for connectors and not run traces
> between them, then it's usually a matter of not connecting to a
> signal on the schematic, or using an inappropriate name.
> 
> Select the "show" mode for the pointer on the schematic and
> double-click on the power traces. The "pins" on the connected
> devices and the corresponding net will be highlighted. If the ones
> you expect to be highlighted aren't, they're not really connected.
> 
> The online help for ERC explains what it checks to some greater
> detail. The error report isn't quite as helpful as it could be.
> 
> --
> /"\ Bernd Felsche - Innovative Reckoning, Perth, Western Australia
> \ /  ASCII ribbon campaign | "Laws do not persuade just because
>  X   against HTML mail     |  they threaten."
> / \  and postings          | Lucius Annaeus Seneca, c. 4BC - 65AD.
> 
> 
> _______________________________________________
> Diy_efi mailing list
> Diy_efi at diy-efi.org
> http://lists.diy-efi.org/mailman/listinfo/diy_efi
> 
> 
> 
> -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.
> 
> _______________________________________________
> Diy_efi mailing list
> Diy_efi at diy-efi.org
> http://lists.diy-efi.org/mailman/listinfo/diy_efi
>