The files are all generated with the correct footprint and file names.Unfortunately, development on Aligni Connector has been terminated. I then set the outjob variant to reference the component I'm keeping (to enable the corrct VariantName), and generate my outputs. For each output, I use the compile mask to mask out 2 of the 3 footprints, and recompile the project. I then covered each of the 3 components with Altium's "Compile Mask" feature. (In my outjob I use the VariantName parameter to create a subfolder and to label the files.) However, I put all three components on my schematic at once, with the same reference designator. I kept the 3 variants of the design to allow generation of unique output files. Even with "Allow variation of fabrication outputs" selected in the Edit Project Variant dialog box, I wasn't getting correct outputs. I needed to make 3 versions of a board with 3 different, overlapping footprints which would have interfered with each other. I just solved this problem myself, and I'm posting here in case anyone else happens to find this thread when searching as I did. If so, it again seems like a good way to generate confusing outputs (are these files, in the same folder and with the same file names, from variant A or B?). It's noteworthy that variants can be selected in the OutJob for fabrication outputs too, but I don't know if that's useful here or not. If neither of these is possible, and you really need two separate PCBs, then you're better off using two separate PCBs. By far the best is to use a single project, one common footprint (assuming they don't conflict), or two footprints (in different locations, again to avoid conflict). By using common schematics, you avoid the madness of having to sync two PCBs. Now you have two PCB projects, which means all the schematics that generate the PCB, and the PCB, and the project settings for them. Start two projects, each with all the common schematics, and one with the first schematic variant, and the other with the other. One way you could do this is to put everything that *doesn't* change into separate schematic(s), and the one thing that does change, into a separate schematic (one for each version). Sooner or later you'll forget what you did, and things get screwed up.
0 kommentar(er)
