Now, that gets compiled in to the OBData.txt file and shows up as ĪBC123 NET_BIGPOWER 0.5 12.0 40 If Voltage below 11V, dead CPU NET_BIGPOWER 0.5 12.0 40 If Voltage below 11V, dead CPU desktops/asus/abc123.txt, in it will contain a line Now, someone writes the expected values for the nets for the ASUS ABC123, and one of the nets is NET_BIGPOWER, its values are 0.5V diode, 12V running, and 40R resistance OpenBoardData will have a file perhaps called.
Say you have boardview program XYZ, it loads up an ASUS FZ file for some motherboard ABC123, that's fine, you can see the pins/nets/parts, but there's no data for the readings to expect on those. OpenBoardView will have the ability to read it in soon too, it's just on FlexBV right now because I'm developing it initially on that platform since it's the one that I control of course, but OpenBoardData itself is open/free to all and doesn't have any API/tie-ins or anything at all to do with specific file formats or existing boardview programs. It's just a collection of data that can be used to overlay/enhance existing boardviews. It has nothing to do with the boardview file format. I think you're still overthinking it perhaps, not sure if we're talking past each other?
0 kommentar(er)
