Hello,

I wanted to import some eagle files using the Eagle_to_DipTrace_SCH/Eagle_to_DipTrace_PCB ulp's. Therefore I first played a little bit around with the singlesided.sch/brd demofiles from eagle 5.11. Running the ulp from eagle goes fine. Import the schematic file (the asc) in diptrace 2.1.9.3 Beta seems at first everything went well. But when I highlight GND in Design Manager, I found that there are some GND Pins did not highlight, they are not part oft the GND net?! I have to Net Name them on my own to the correct GND net.

Then when I'm calling convert to pcb, I mention a strange behavior. I cannot route traces manually?! Nothing happens when I click on Route Manual and click on the pads!

Autorouter did work (route the board). However when I right click on a routed trace, the context menue is totally missing?! So I cannot change the traces for example.

Design roule check found no errors.

I also tried to import the converted eagle pcb file (singlesided.pcb converted with ulp) in diptrace pcb. This seems not to work at all, because there are no parts, no ratsnests, nothing but some strange lines??!

I don't know if this is because of the diptrace beta version. I'currently running diptrace on Windows 7

Regards,
Udo

Hi Udo,
I see the problem. It seems because new features of the beta version (net classes). We will fix it in the next release.

Hello Alex,

in PCB Layout ( DipTrace 2.1.9.4 beta (54.1 Mb, build July 1, 2011)) Diptrace ASCII Import from eagle PCB is still not working.

Of course, there is a workaround in using the old stable v2.1.07 for PCB Board import and then change to the new beta to keep on working.

But it's a pity that the bug is still present.

Regards,
Udo

Hello Udo,

We haven't fixed the issue with importing ASCII files from Eagle yet. We will do it in the next build. Thanks for the remainder about the problem.

There is another serious bug in the conversion process (last beta 5). Please try one of the eagle examples (doesn't matter which one you use; try singlesided.sch/brd). After ulp-conversion and import in diptrace when I do a Renew Design from Schematic by Components (don't touch the schematic before to show the effect) then I got a totally hang-on in harddisk activity and I have to kill the task with the task manager on Win7-32 bit). This is reproducible, but there are situations where things differently run (no freeze) but then diptrace move some of the parts out of their position and a lot of the routing wires gone wild. I tried many hours to clear the thing out, but I did not succeed. However, Renew Design from Schematic and Back Annotate did work for me on regular diptrace files, but not from eagle converted files (even not on my own eagle files). I'm somehow surprised and disappointed about that.

Regards,
Udo

PS: I deleted my old posting ("now in v2.1.9.5 beta July 5. ASCII Import for running eagle board layout files did work.") because the Forum Soft always want to append my new posting. Don't know why this foolish's happen.

After importing files from Eagle, renew design from schematic/ by RefDes should be used because all components and nets have different IDs. Renewing by components will mess up all traces , but it shouldn't hang up machine.

Let's leave the hang ups for a moment aside and concentrate on the eagle example files to discuss the situation (is the easiest way to narrow down the problem).

For example import singlesided.brd/sch from eagle using the ulp
importing the files to diptrace works, but a dialog appears saying

"Components "GND, GND1, GND2, GND3, GND4, GND5, GND6, GND7, GND8, GND9, GND10, P+1, P+2, P+3, P+4, P+5, P+6" don't have patterns. The schematic can be converted to the board incorrectly!"

It seems that there are problems with some supply symbols. Then I do a Renew Design by RefDes which seems to work but some of the components had moved (a few ten mil)??? They are not all on their place as one would expect. This is a very simple layout so it doesn't matter at all, but suggest the layout is complex and routed?! I think this would be not nice.

Another example. I imported hexapod from eagle. When I try Renew Design by RefDes a dialog pops up displaying 'Different Net Width', asking 'Use PCB Layout Settings' oder 'Schematic Layout Settings'. ..
Same Problem, diptrace move some of the components out of their position??

Third example. Imported demo2 from eagle . Again the dialog 'Different Net Width' appeard. Also after proceeding the dialog diptrace move some of the components out of their position??

Why not keep diptrace the pads on their exact location as everyone would expect?

But one thing goes EXTREMLY worse. Try the following

Please open the Eagle Testversion v5.11 and load example singlesided board. There is a 18 pin DIP IC. Right click on the center of IC1 (in eagle) and mirror the IC1. Then go to Autorouter and let the board route (it's simple, it only take seconds). Use the Diptrace conversion ulp on it and import the board.asc into Diptrace 2.1.9.5 Beta. Now look on the position on IC1 in Diptrace. It' FALSE!!! On the left side is shown Pin 1 of IC1 instead of Pin 9! Look on the eagle board to compare them.

When you now make a Renew Design by RefDes then diptrace mirrored the IC1 and the chaos is perfect (all routings are destroyed).

Please investigate the matter. I've already spent hours on it.

Thanks for the report. I will check the issues with importing Eagle files.