Actions
Forum Thread Details
  • Replies 4 replies
  • Subscribers 189 subscribers
  • Views 438 views
  • Users 0 members are here
Related

Version 6.0 crash

e14 Contributor

Four times now, I have had the new Eagle version crash when I try to save a schematic under a new name after a (long) routing or partial routing has been done. Not sure if that is the exact reason for the crash, but crash happens right when I try to save with new name.

 

TC

Parents

  • Also discovered another problem with the program. Not sure if this problem is in versions of Eagle before v6.0 or not, but it is in v6.0

    After running the autorouter for a while, I clicked "Stop" to pause the routing process. Then I did a "Save As" with a new filename. When I returned to try to continue the routing process, there was no option to continue. I checked the directory and Eagle did not save the .job file (routing status and memory buffer) along with the new filename. I made a copy of the most recent .job file under the old filename, and then renamed the copy to the new filename that I used for "Save As". This solved the problem and when I opened the new file again, it allowed me to resume the routing from where it left off, but I would suggest the .job file should be saved under the new filename when using "save as".

Reply

  • Also discovered another problem with the program. Not sure if this problem is in versions of Eagle before v6.0 or not, but it is in v6.0

    After running the autorouter for a while, I clicked "Stop" to pause the routing process. Then I did a "Save As" with a new filename. When I returned to try to continue the routing process, there was no option to continue. I checked the directory and Eagle did not save the .job file (routing status and memory buffer) along with the new filename. I made a copy of the most recent .job file under the old filename, and then renamed the copy to the new filename that I used for "Save As". This solved the problem and when I opened the new file again, it allowed me to resume the routing from where it left off, but I would suggest the .job file should be saved under the new filename when using "save as".

Children
  • in reply to e14 Contributor

    There is yet another problem with the router that is still in Eagle v6.1.0 I had mentioned this to George at cadsoftusa and he said it was being adressed but the problem is still there.

     

    When I try to hand route a wire that should end at a pad or wire on the same layer, the router does not snap to the end point or complete the routing until I select it again and route the tiny little airwire that results from it not having snapped to the end point where routing should have completed at the previous step. The workaround of reselcting and routing it the second time obviously works, but it is still a bug that needs to be addressed. V5.11 (and others before) never had this problem.