Create Software/GUI for SFP Optical Transceivers

Our company is provider of third-party OEM compatible optical transceivers (GBICs/SFPs) and Direct-Attach Cables (DAC). Our company is looking for an individual or company that can create a software GUI to be used in conjunction with a coding box/board that connects via USB. The coding box is used to read and write coding on SFP optical transceivers. We want to use a software version that we already have and improve upon it. We can provide the source code for the current software which is written in C++ to create an enhanced, more custom version. The ideal candidate or company will have optical transceiver programming and software development experience to improve upon our current custom programing software and GUI that will allow us to read, write, generate, load, and save .bin and .hex files (ASCII and Hex codes files) that follow the MSA standards for optical transceivers in the various form factors. We would like to build off this and improve it, perhaps make a website to interface with customers and provide remote coding. Ideally we would like to work with someone that has connections to electrical engineers with experience with manufacturing so we can proceed with working in conjunction with both to create a total solution of software GUI and coding box. The software would need to perform the following functions: • The ability to generate codes (.bin/.hex files) across specific banks utilizing a unique algorithm based on predetermined templates that contain changeable fields • Create different templates and algorithms based on specific coding parameters dependent on the OEM it is intended for, including banks in vendor specific, part number, vendor name, serial number, date code, and other A2H and TABLE 2 banks. • Ability to generate a single code or create a serial number range to generate sequentially serialized bulk codes based on the predetermined template. • Ability to create our own templates and save for future and more automated use. • Simple to read GUI/Interface for ease of use • Ability to input a starting serial number and the quantity of codes and have them created automatically in sequential order • Ability for codes to be saved automatically as they are generated • Field to include password Below are the specific Pages or Tables and specific Banks of code that we will need to be able to read and write. SFP/SFP+/SFP28: Need to be able to read/write code to the following: Page A0, Banks 0-127 Page A0H, Banks 128-255 Page A2H, Banks 128-255 XFP: Need to be able to read/write code to the following: TABLE 00 TABLE 02 QSFP+/QSFP28: Need to be able to read/write code to the following: TABLE 00 TABLE 02 QSFP-DD: Need to be able to read/write code to the following: TABLE 00 TABLE 02 Each of the above listed form factors have a specific MSA document stating/describing the locations that are listed above and being able to read/write code to the modules. Listed below are links to each of the MSA documents for reference. MSA Document Links: (link removed) When coding the different module types there are a few specific areas within each code that we commonly modify that we will require to be part of the templating creation. VENDOR NAME PART NUMBER SERIAL NUMBER DATE CODE VENDOR SPECIFIC A2H page and/or TABLE 02 (depending on the form factor)