You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm playing with WireViz to see if I can use it to document an automotive wiring harness. This is a fairly complex beast, with several large-pin-count connectors - 26, 34, 38, 20, etc. plus a ton of smaller ones. I think trying to do them all, the whole harness, in a single image will just get too unwieldy. So perhaps doing sub-portions of the harness ?
For example, the in-cabin portion of the harness will have ECU_A (24pins), ECU_B (36 pins), II1 (38 pins), IJ1 (20 pins) connectors. There are about 20 wires that go between these 4, so do a run that just diagrams those connections and associated pins, hiding unused pins. Another would be between II1, IJ1, EA1, EA2, so another run for just those connections and the associated pins. I can see doing 5 or 6 sub-portions like that.
The problem is that each yml file will need to contain the same connectors, and keeping them in sync is an easily overlooked place for errors. It would be nice to define the connectors each in their own file, then include them in the connectors: section as needed for each sub-portion yml file.
This seems related to #220. Please try including your library of connector and cable templates as a YAML input file using the existing command line option--prepend-file. See also syntax and tutorial for using such templates. Does that solve your issue? If not, please describe use cases where more or different features are required, but please consider doing that by joining the discussion at #220 unless you feel that issue differs too much from your issue.
I'm playing with WireViz to see if I can use it to document an automotive wiring harness. This is a fairly complex beast, with several large-pin-count connectors - 26, 34, 38, 20, etc. plus a ton of smaller ones. I think trying to do them all, the whole harness, in a single image will just get too unwieldy. So perhaps doing sub-portions of the harness ?
For example, the in-cabin portion of the harness will have ECU_A (24pins), ECU_B (36 pins), II1 (38 pins), IJ1 (20 pins) connectors. There are about 20 wires that go between these 4, so do a run that just diagrams those connections and associated pins, hiding unused pins. Another would be between II1, IJ1, EA1, EA2, so another run for just those connections and the associated pins. I can see doing 5 or 6 sub-portions like that.
The problem is that each yml file will need to contain the same connectors, and keeping them in sync is an easily overlooked place for errors. It would be nice to define the connectors each in their own file, then include them in the
connectors:
section as needed for each sub-portion yml file.I know we can simulate this using a Makefile to assemble the sub-portion run yml files, but it would be cleaner this way I think.
The text was updated successfully, but these errors were encountered: