3-digit code for monitors in the script – manufacturer identification
3-digit code for monitors in the script – manufacturer identification
Hello everyone, I’m part of a non-profit initiative focused on refurbishing computers, often handling more than ten monitors simultaneously. To streamline our work, I developed a BASH script that checks certain features of connected displays. When it identifies compatible models, it generates a PDF containing key details such as manufacturer, model, serial number, maximum resolution, input options (if DDC support is available), and a barcode linked to the manufacturer’s ID. After creating the document, I print it and cut the sides for use in a scratchpad, then attach it to the monitor. The script is publicly available on GitHub at https://github.com/chaslinux/findmonitor.
We have a diverse collection of monitors from various brands, but not all manufacturers are represented. I reached out to several companies for more information, and one responded promptly with the needed details. Others haven’t replied yet. I’m seeking community assistance in identifying the three-digit manufacturer codes required for some monitors we need to verify or confirm their presence.
I’ve compiled a list of manufacturers whose web pages are accessible, including those not currently on my list. If you own a monitor from a company not listed here—such as BenQ, Arzoopa, Boifun Innoview, Koorui MSI, Pixio, Sansui, Sceptre, or Gigabyte—I’d appreciate any information you can share. You can email the code to me via the script’s address, or I’ll look into it myself.
I’m hopeful we’ll eventually acquire a Gigabyte or MSI monitor, as those are common in our setup. The Sceptre model is already included in the script, and its response was encouraging. The AUO came from someone mentioning an affordable MSI unit possibly made by another company. This situation applies to the 3M monitor we’re using.
Thank you for your support and any guidance you can offer.
Currently our setup uses Xorg with Xubuntu 20.04/22.04, but I plan to integrate Wayland equivalents. It's possible the upcoming non-LTS versions could adopt Wayland by April, so a transition might be faster than expected. We're not prepared to fully move all systems to Wayland just yet.