01
Start with the chip marking
Load a chip photo or use the phone camera, then inspect the visible marking. A clear image gives you something to compare against the reference. Before relying on a result, check that the code being read matches the characters you can see on the chip.
If part of a marking is obscured or difficult to distinguish, keep that uncertainty in view. A closer image or another angle may be more useful than accepting an unclear code.
02
Compare the reference, then review the result
BoardVision compares the marking with reference data and presents information such as storage, RAM and verification status. The useful question is whether the reference corresponds to the chip in front of you.
Review the code, the matching reference and the status together before placing the chip in a sorting group. A matching entry is information to inspect; it should not turn a doubtful marking into a certainty.
03
What identification does not establish
A reference match does not establish that a chip works. BoardVision is not an electrical or functional tester. It also does not determine the metal yield of a chip or circuit board.
Those questions require their own methods. Keeping identification separate from condition and material recovery makes the result easier to interpret and helps prevent a reference lookup from being used beyond its purpose.
04
An app shaped around a real task
BoardVision is in development for iOS and Android. A phone camera makes it easier to read a chip where it is. We test the workflow with an internal macOS prototype, and the interface shown here comes from that prototype; public availability, pricing and a release date are not announced here.
If you sort memory chips, tell us where reading markings or comparing references slows your work. Describe the input, the information you need and how you handle uncertain results. That context makes a product conversation useful.