MG Expedition ликбез ... Опции

[3.14]

Как перетащить компонент с частью разведенных дорожек?
А то в режиме разводки корпус не "зацепляется" и наоборот.
Еще, что то автоматическая переразводка при перетаскивании компонента работает так криво, что приходится сначала отрубать кончики линий у компонента а потом перетаскивать и доводить линии, может что посоветуете, ну или хотя бы как эту "дрянь" выключить?

[3.14]

Спасибо.
Еще, потерял ссылку на "инструктаж" перевода PCAD <-> WG, не подскажите?
Экспериментировал с трансляцией с год назад, из воспоминаний только то что безсмысленно конвертировать PCAD-овские файлы в WG (слишком много руками править) да и к тому же конвертировала только определенная версия CAMCAD PCBtranslator, как сейчас обстоят дела, может появился "нормальный" конвертер?

[fill]

Спасибо.
Еще, потерял ссылку на "инструктаж" перевода PCAD <-> WG, не подскажите?
Экспериментировал с трансляцией с год назад, из воспоминаний только то что безсмысленно конвертировать PCAD-овские файлы в WG (слишком много руками править) да и к тому же конвертировала только определенная версия CAMCAD PCBtranslator, как сейчас обстоят дела, может появился "нормальный" конвертер?

PCAD(схема)--->DxDesigner
PCAD(плата)--->PADS_Layout--->ExpeditionPCB
все родное от ментора

Еще,
объединил шину в группу и указал максимальный разбег в длинне 5мм , развел, тыкаю кнопку tune, а он вместо выравнивания просто сокращает пути (разрешил все возможные типы выравнивания). Хотя в ReviewHazards появляется ошибка на разбег в длинах на эти цепи.

Symptoms
Trouble getting nets to tune

Tuning does not work

Nets fail to tune
Causes
Most likely, either there is an incorrect spelling or syntax in the tuning parameters, or more likely the tolerances and/or tuning constraints and/or space available in which to tune prevent the algorithm from being able to tune to said tolerances, restraints and parameters. Or, not all the nets involved in the tuning "equation" are fully routed (in which case, the algorithm will not even attempt a tuning).
Solutions
The following is a checklist for the more common causes of tuning failure or poor tuning results:

1 - ALL nets involved in a tuning "equation" (that is, both nets of a diff pair, all nets of a match set, all nets interrelated by Delay Formulas equations you've set up, ...) MUST be 100% routed before ANY of them will tune. Please check that the nets you are trying to tune, plus any nets to which or to equations involving which you are trying to tune them, are fully routed.

2 - Fixed or locked trace segments cannot be modified. Therefore, to ensure tunability, please ensure as far as is feasible that all segments of all nets to be tuned are unfixed and unlocked.

3 - Tolerances. In the Net Properties dialog (or the equivalent area in CES), there are tolerance values for diff pair tuning, match sets, and delay formulas. If these tolerances are so tight that the tuning algorithm cannot adhere to them, it will often abandon the attempt. You need to ensure that these tolerances are realistic, taking into account the other restrictions (below) - in other words, for example, if all number of tuning patterns are allowed and there's stacks of board space available around the traces of the net to be tuned, a fine tolerance will probably still work... While experimenting with getting tuning to work, and seeking to eliminate any other possible reason preventing successful tuning, I would suggest slackening these tolerances considerably, even if only to tighten them again once you've established that tuning will work on the design. And please also check that the _type_ of units in the tolerances corresponds to that in the values - i.e. time with time, or length with length.

4 - Editor Control Tuning Tab. As above, if the restrictions are so tight that the tuning algorithm cannot tune within the specified tolerances, it will likely not tune at all. Again, for experimentation I would initially allow all patterns, and reduce minimum values to 0 and maximum values to an inproportionately large value. These can be tightened to reasonable design requirements once it is established that the tuning algorithm is working successfully (please note use of Online DRC for verifying tuning results), although again, one must be realistic in the restrictions one imposes, they must of course satisfy board design requirements, but must also satisfy feasibility for the algorithm!

5 - Space is required to tune! Ensure as far as possible that there is plenty of routable free space on the board in which to tune the appropriate signals. NB the tuning algorithm does NOT reroute, change layers, et al. for the purposes of completing the most effective tuning result possible. The design must prepare a realistic layout for tuning. Very often, bringing a signal out into open space will make all the difference, and enable the tuning algoithm to complete an effective tuning result. Effective use of space AND LAYERS by the designer is critical as an input to the tuning. If all else fails, try experimenting by bringing the signals to be tuned out into open board space, and retry.

6 - This relates also to #4 above. It is usually adviseable to route and tune the most critical signals first, and work down from there towards the least critical nets. This will ensure (see #4 above) maximum space and therefore maximum tuning capability and best results for the most critical nets.

7 - Are one or more of the nets in question DIFF PAIR nets? If ANY diff pair nets are involved, then ALL Online DRC Diff Pair violations for them MUST be cleared before the tuning algorithm with ATTEMPT to tune.

8 - If all else fails, double-check the Net Properties settings to ensure that the tuning parameters are correctly defined, there are no typos, and in particular that the syntax of t.he Delay Formulas definitions, if applicable, if correct throughout. If needs be, start with a simple test involving one or two cells in the table, and work up from there.