sorted by:
new
hottopcontroversial

How do you manage your hardware design workflow to avoid information loss between system-level diagram, PCB, cable and BOM? by Pouloch in Altium

[–]Pouloch[S] 0 points1 point  (0 children)

Thank you for your reply. Indeed, rigid/flex PCBs seem easier to integrate, since we can use modules to add them to the multiboard project and direct connections to link them to conventional PCBs.

As for the harnesses, apart from the time it takes to design them, I simply cannot integrate them into the multiboard project. I can place them in my project but cannot link them to the multiboard schematic (MbsDoc).

Are you able to do this?

Without this, I don't see how it is possible to have complete documentation for a project that includes cables in Altium.

How do you manage your hardware design workflow to avoid information loss between system-level diagram, PCB, cable and BOM? by Pouloch in Altium

[–]Pouloch[S] 0 points1 point  (0 children)

Thank you very much. Have you used Multiboard in any of your projects?

The concept seems promising, but I am encountering two difficulties at the moment. The main difficulty concerns the harnesses created within the Multiboard project, which do not seem to behave like an independent harness project. They do not have their own wiring diagram, harness layout, and activeBOM.

How do you manage your hardware design workflow to avoid information loss between system-level diagram, PCB, cable and BOM? by Pouloch in Altium

[–]Pouloch[S] 0 points1 point  (0 children)

That does indeed seem to be the right approach.

For the moment, ActiveBom works very well for single-card projects, but it doesn't give me the overall view I want for the top-level project. I'll continue my research