Ну при большом желании можно все что угодно

Как создается Reusable Block в DxD-Expedition PCB? Или работать с Reusable Blocks возможно при DC/DV-Expedition?

В EXP2005 SP1 + OCUR11, DxD-Expedition flow, редактор символов, вызываемый из Library Manager, позволяет выставлять метрическую сетку, и, соответственно, рисовать в миллиметрах. Возникает вопрос, не будет ли проблем с использованием таких символов в DxDesigner? Будут ли выводы такого метрического символа попадать в узлы сетки?

Вопрос по поводу видеокарты, на работе комп P4-1.2ГГц 256М, дома Р4-2.8ГГц 512М, на обоих машинах испытваю неприятное подтормаживание на 4-х слойке (почти одинаковое), это может быть связано с видеокартой (на обоих машинах отстойныйе видеокарточки)?

Будут. Редактор символов в Library Manager сам то работает некорректно с единицами. Попробуйте задать длину вывода 2 мм. Сохраните символ и откройте его. Посмотрите на длину. Она стала 2.032!!!. Соответственно такие же видоизменения произойдут и в Dx. Несовершенство интеграции Dx и Library Manager....


В DxD поддерживается только хранение схемотехнической части многократно используемого блока. К сожалению топологию (в отличие от маршрута DC/DV-Expedition) пока сохранить нельзя.

Пока только в DC/DV-Expedition



Попадать будут всегда, но в единичную (при открытии в DxD, при не попадании произойдет смещение в ближайший узел единичной сетки, как пинов так и графики)



Может.

Сообщение отредактировал fill - May 16 2007, 07:17

http://forums.mugweb.org/showflat.php?Cat=...page=0#Post2792

- Most people are having OK success with dual monitors - it's still not perfect yet. Graphics will be rewritten in OPEN GL, starting 2008. Be prepared to have top of the line video cards with lots of ram when this happens.

Копите деньги на хорошие карточки.

- CES in 2007 database is merged into one database instead of the distributed database as it is now. After 2007 there will no longer be net classes and net clearness dialogs. CES will be the only tool.

Т.е. начинайте готовится к переходу на CES

там еще есть вроде приятные задумки:

- 2007 planes processor will go away. Planes updates happen automatically, dynamic area fills has been updated. Is there a way to short different planes of different potentials some automatic way. Not at this time, can use buried res, drawing elements etc the same way we are doing it today.

кстати, MG изменил дизайн supportnet, и теперь даже анонс выходов новых релизов засекречен...

про новые карточки понятно. А поддерка двухядерных процессоров планируется?

- has anyone noticed a difference between core 2 duo machines - seems to be running a lot better and smoother

ну это то понятно, кому-то кажется, что вроде бы, несколько лучше и глаже. Это понятно, что если в системе запущена ресурсоемкая задача (ну например перерисовка экрана с оширной графикой), то даже если эта задача не использует второе ядро, то в двуядерной ситеме она должна работать лучше, хотя бы потому, что захваченное ей ядро не будет отвлекаться операционной системой на нужды ОС.
я то имел в виду, что не планируется ли в критичных с точки быстродействия местах задействовать оба ядра на эту одну задачу. Как например общеизвестно, что wirar поддерживает двуядерные процессоры и соответственно скорость упаковки\распаковки в двуядерной системе почти в 2 раза выше.

Ресурсоемкие задачи уже распараллеливаются - например автотрассировка в Xtreme
Проблема в том, что очень немногие задачи поддаются распараллеливанию. Второй вопрос это ... лицензирование второго параллельного процесса (вопрос тонкий - ибо денежный ).
А вообще конечно думают.

Кстати по поводу релизов\обновлений, после выхода 2005_Sp1 выпущено 19 обновлений
#

Problems Fixed in OCUR19 - Expedition PCB:

* DR/ER: 00407615 - Expedition PCB - Interactive Route: Manipulation of diff pair separation hazard crashes Expedition.

Problems Fixed in OCUR19 - Design Capture:

* DR/ER: 00405875 - EDIF Import crashes with no hint of why.

#

Problems Fixed in OCUR18 - Expedition PCB:

* DR/ER: 00381935 - Output DXF of Assembly Outline Top crashes the DXF routine I/O Designer
* DR/ER: 00327890 - should be able to set clock capable pins as clock type.
* DR/ER: 00327891 - LC pins can be used as LVDS output.

Problems Fixed in OCUR18 - DxDesigner:

* DR/ER: 00397649 - archive.ini file is missing from OCUR15, which causes Reuse Block Wizard to fail during the Publish step.

#

Problems Fixed in OCUR17 - Quiet Expert:

* DR/ER: 00357509 - QE crashes while running qe_PathMinPin2Pin.
* DR/ER: 00340236 - qe_NetAreaInPolygon: Cannot obtain the area.
* DR/ER: 00340243 - qe_PathMinPin2Pin the returned shortest path differs between when part_pin1 to part_pin2 is specified, and when part_pin2 to part_pin1 is specified.
* DR/ER: 00340250 - qe_PathMinWidthPin2Pin the list of sections is not in order from part_pin1 (start pin) to part_pin2 (end pin).
* DR/ER: 00340252 - qe_PathRouteInfo path sections are not detected.
* DR/ER: 00340503 - qe_PartInfo returned pin group contains pins that belong to another group.
* DR/ER: 00340504 - qe_PartInfo returned pin group is missing pins that belong to the group.
* DR/ER: 00340510 - qe_ViasInPolygon API returns a via although the via hole is not included nor intersects with the specified area.

#

Problems Fixed in OCUR16 - Design Capture:

* DR/ER 00358955 - Print Design does not work with File name over 32 characters.

Note: This OCUR is for Windows only.
#

Problems Fixed in OCUR15 - Xtreme PCB and Variant Manager:

* DR/ER: 00378764 - Extra pieces of trace appear in Xtreme at default width when trace has been routed at minimum width.
* DR/ER: 00382961 - Multiple Reference Designators are appearing in Variant Manager, this was supposed to be fixed in 2005.1 (DR/ER: 00336364)

#

Problems Fixed in OCUR14 - DMS DDD, DMS Librarian, and DxDesigner:

* DR/ER: 00346945 - DDD will not allow dashboard to re-open with a DMS user that has a password.
* DR/ER: 00352363 - update_cache_wg.sh will update all parts in the library if a part number in the production library does not have a CAD part associated to it.
* DR/ER: 00371356 - The root cause to be special characters in the part number field (e.g. | (pipe))
* DR/ER: 00311847 - crash during add many files to repository from popup.
* DR/ER: 00311784 - "The parameter is incorrect" - hang - up dashboard during project synchronization.

#

Problems Fixed in OCUR13 - DxSim:

* DR/ER: 00356501 - Need VHDL/Verilog Port to symbol pin Mapping capability.
* DR/ER: 00356502 - Need to be able to compile VHDL models for ADMS with the -ms option.
* DR/ER: 00356505 - When starting simulation, there is a long delay in reading pins/ports/order list.
* DR/ER: 00356506 - Need Support for multiple boundary elements for specific pins.
* DR/ER: 00365926 - DxSim cannot launch 2006.1 Eldo nor 2006.1 EzWave.

Problems Fixed in OCUR13 - DxDatabook:

* DR/ER: 0100244162 - DxDatabook is not finding symbols in Oracle Database.

#

Problems Fixed in OCUR12 - NC Drill:

* DR/ER: 00366837 - Holes with dia 1um are not output in NCDrill output.
This fix is for contour hole restrictions for NC Drill output. If a contour is created with a hole name "No Tool Contour" and the hole size is less than 3 um or 3 th depending on the design units, then the NC drill engine does not output this contour. 2 EXP2005 SPac1 OCUR12 Release Notes December, 2006.
Note: This fix is only for NC Drill in this OCUR. However, Manufacturing Output Validation (MOV) fails if validation is done for generated NC Drill having contours with holes less that 3Th or 3um. MOV reports the following error message in that case: “THIS PACKAGE CONSIDERED INVALID FOR MANUFACTURING PURPOSES.“

#

Problems Fixed in OCUR11 - Expedition PCB:

* DR/ER: 00356640 - Reimport of the ndd file from DFL mode results in deletion of all testpoints and testpoint vias in Allegro.
* DR/ER: 00369523 - Using OCUR8, vias are not included in the join if they are placed at the reserved area boundary.
* DR/ER: 00369423 - PinPkgLengths are not used for Xtreme session.
* DR/ER: 00359838 - Deleting Net0 hangers results in crash.

# Problems Fixed in OCUR10 - Expedition PCB:

* DR/ER: 00359735 - ODB++ output does not contain customer defined attributes.
* DR/ER: 00364343 - all component and via pads have .test_point attribute.
* DR/ER: 00365301 - extra not expected characters appended to partname attribute.

#

Problems Fixed in OCUR9 - DxDesigner:

* DR/ER: 00324237 - Script that worked in 2004 does not work now in 2005.
* DR/ER: 00353839 - DxDesigner Archive.exe does not archive PCB folder. EXP2005 SPac1 OCUR12 Release Notes 3 December, 2006

# Problems Fixed in OCUR8 - CES:

* DR/ER: 00361950 - Two passes of compile, package CDB, & Forward Annotating changes to schematic -> pin pairs & Constraints lost in CES.
* DR/ER: 00362539 - Back annotate after changes in both CES and Expedition, cms_sync discards/loses pin pairs and constraints.
* DR/ER: 00351591 - Crash when opening CES.
* DR/ER: 00354824 - "Invalid via span Via usage hazards that appear to be valid via spans".

Problems Fixed in OCUR8 - Expedition PCB:

* DR/ER: 00356367 - Expedition PCB crashes during forward annotation.
* DR/ER: 00349986 - Design rule check for same-net via to via is giving erroneous results when using teardrops.
* DR/ER: 00307407 - TeamPCB - Users allowed to perform move and delete operations on vias that sit on the reserved area boundary.
* DR/ER: 00350460 - Multiplow does not push/shove as good as plowing a single trace.
* DR/ER: 00356637 - Design hangs when attempting to open DFL mode design.

#

Problems Fixed in OCUR7 - Expedition PCB:

* DR/ER: 00356903 - Import IDF should understand cutouts defined in Obstruct/keepout.
Note: The Fix is available for Placement Obstructs only and not Route Obstructs.
* DR/ER: 00356911 - Import IDF should assume UNOWED owner type on all IDF entities if owner type is not specified 4 EXP2005 SPac1 OCUR12 Release Notes December, 2006.

#

Problems Fixed in OCUR6 - DxDesigner:

* DR/ER: 00346224 – Need MySQL support for Linux and UNIX in DxDatabase.

#

Problems Fixed in OCUR5 - DMS Librarian:

* DR/ER: 00350931 - Update cache is downloading pad stacks every time.
* DR/ER: 00352396 - Update cache is downloading Components two times when both the mapping and component change.
* DR/ER: 00353663 - Update_cache and UPLW need the ability to export length type characteristics in multiple units.
* DR/ER: 00361843 - The partprops_utils.tcl script does not recognize commas as decimal characters.

#

Problems Fixed in OCUR4 - Expedition PCB and Fablink XE:

* DR/ER: 00348822 - Direct ODB++ output is excluding slotted drill features from certain layers.
* General performance improvement in ODB++.
* Linux only fix: DR/ER: 00349912 - ODB++ uses a lot of memory and the machine runs out of memory and disk quota.
Note: When running ODB++ on Solaris, set the environmental variable "MWNO_FILE_LOCKING" to "1". Otherwise the following error displays during ODB++ generation and the process stops: "Problem opening input file ../solaris/2005EXP/SDD_HOME/standard/config/pcb/sysAttr.att". EXP2005 SPac1 OCUR12 Release Notes 5 December, 2006.

#

Problems Fixed in OCUR3 - CES:

* DR/ER: 00352114 - Start CES from DxDesigner – CES database grows bigger – 20% larger, exit and start again, .db shrinks 70%, discrete maps grow geometrically.

#

Problems Fixed in OCUR2 - Expedition PCB:

* DR/ER: 00350260 - The MGC_ENABLE_PINCASE environmental variable is no longer working.
* DR/ER: 00347901 - When generated with raster polygon fill, getting shorts in GerbTool and CAM350.
* DR/ER: 00350755 - Symbols with inverted pins do not import into the Part Editor correctly.
* DR/ER: 00351223 - NSE is no longer saving the timestamp in the NSE symbol file. This was working in EXP2005.
* DR/ER: 00336489 - XAR client crash during last route pass.
* DR/ER: 00346426 - Export to ICX (IS Interface) crashes when at least one spare part is placed on the board.
* DR/ER: 00344451 - Activate dynamic area fill --> crash.

#

Problems Fixed in OCUR1 - Expedition PCB:

* DR/ER: 00344678 - Breakouts/Teardrops are removed when they shouldn't with push/shove in Local Gloss mode.
* DR/ER: 00344721 (DR/ER: 00336067) - Caused by Odd/Even change that is creating small segments of traces after dynamove.

Не подскажете, а где можно взять OCUR11 ???

OCUR старшего номера включает в себе все предыдущие - задача найти старший

Хорошо, уточню вопрос: а где можно найти OCUR19 ??? (он ведь последний, верно?)