Acknowledged
Default ECAD datums for ECAD PCBs need to be drastically enhanced
Please include detailed documentation such as screenshots, images or video.
1. What product and version are you running?
Creo Parametric 9.0.6.0
2. What is the problem?
Reference ticket: 17094872
We are trying to move beyond the IDF standard of ECAD MCAD collaboration to the IDX standard. However, we are seeing some major gaps that need to be resolved before we can fully use the module. The items below are specifically related to BOARD_DATUMS group.
- We need the ability to add more datums (we include an axis as part of our current ECAD datum setup for regular parts). The ability should allow a user to add/remove datums from this group as needed.
- The origin created should be using the name from ecad_board_csys_def_name config option.
- Allow the datums to be in the model tree without a PCB shape, so we can use it as a start part, with the correct names
- We need the ability to move the datums to the FOOTER. I've worked with ECAD collaboration for over 10 years and I believe this is critical. A PCB design, whether the shape of the board, the component placement, etc... should not be based on the origin. It should always be created using proper design intent. The origin is only used by the standards as a way to create a fixed point of reference to be used for collaboration. In many projects I have been involved in, the location of the origin is sometimes up for debate between the mechanical, electrical and PCB teams. The origin needs to be flexible enough to be moved at any point before collaboration begins. Many times this is a hole on the PCB. Currently, we can not change the reference to any feature below the first board shape The mechanical engineer could be weeks or months in development and shouldn't be editing the PCB outline to change the origin. Therefore, the origin needs to be able to be moved at any time and should always be at the bottom of the model tree (footer).
3. Are you using a workaround? If yes, please describe it.
We are currently not using this module as it has too many gaps.
4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.
Engineers would be able to manipulate the origin location and the datums much easier. The admins would be able to create a more effective start part.
5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)
Over 100 users affected. We are still using the EMN standard due to these limitations. We could easily be more effective by hundreds of hours a year if we were able to get the IDX standard moving.
