I spoke with Yipeng about the functionality of the "Net Mapping" software. "Nets" are patches of bare copper that are at the same voltage - each new net listed on the relevant mapping documents is a different patch of copper. Most of the nets are distinguished from each other by components, like resistors and capacitors, that for our purposes need to be labeled as part of the same net. (In the physical sense, they're on the same current path.)
Yipeng's program can, on a single document, record and list out the nets associated with arbitrary component types. The "output" of the mapping functions return the nets and the associated connections. These functions do not need to be changed at all for new boards; they should work on anything.
The issue in "porting" over the code to the new boards is the final part, which is associating the mapped nets on each document with the mapped nets on other documents. Nets end up being connected to other boards - signified by amendment like J1 or J2 - and the function to connect the finished net outputs with each other by this process needs to be "manually" reconstructed.
At the moment, Yipeng would like to take direct control of the development, as he feels time is running short. But I should understand the relevant composition of the code now, in the sense of what components need to be redeveloped to fit into arbitrary situations as they arise in the future.
I spoke with Yipeng about the functionality of the "Net Mapping" software. "Nets" are patches of bare copper that are at the same voltage - each new net listed on the relevant mapping documents is a different patch of copper. Most of the nets are distinguished from each other by components, like resistors and capacitors, that for our purposes need to be labeled as part of the same net. (In the physical sense, they're on the same current path.)
Yipeng's program can, on a single document, record and list out the nets associated with arbitrary component types. The "output" of the mapping functions return the nets and the associated connections. These functions do not need to be changed at all for new boards; they should work on anything.
The issue in "porting" over the code to the new boards is the final part, which is associating the mapped nets on each document with the mapped nets on other documents. Nets end up being connected to other boards - signified by amendment like J1 or J2 - and the function to connect the finished net outputs with each other by this process needs to be "manually" reconstructed.
At the moment, Yipeng would like to take direct control of the development, as he feels time is running short. But I should understand the relevant composition of the code now, in the sense of what components need to be redeveloped to fit into arbitrary situations as they arise in the future.
@wcparker