\chapter{Results}
The project did succeed in producing a design for a device, which accurately performs frame rate measurements using the multi-state color marker. The time frame from the beginning of the project to the final hardware design was 7 months, and to the first official release of the software 9 months. All design work was done by the author, while the product manager, sales team and hardware team provided highly useful feedback.

The 5-month schedule set at the beginning of the project was exceeded slightly, and the amount of features implemented during the thesis work had to be significantly reduced. Most significantly, it was initially planned to develop a high-speed camera extension board for the device, but this would have been an excessive amount of work.

When considering the schedule in retrospect, it becomes clear that the target product should have been defined more clearly in the beginning. Even though the hardware choices were made early, there were little discussions about at which point the device should be fit for sale as a product. This didn't affect the actual work much, as it smoothly transitioned from initial design to productization. However, it did cause confusion in communicating about the project status, which could have been avoided if the goals were set more accurately.

Product development in small companies poses a few unique challenges. Due to the difficult to predict future market success, relatively small amount of resources can be allocated to a single project. The most important thing is to be able to prove the concept and probe the market potential with a small investment, and then continue development if the product sells well. In this case, the single person development team and extensible hardware were good choices for keeping costs low. However, having only a single developer involved in the initial design caused trouble when transferring the further development work to other groups. Having wider involvement through design and code reviews during the development could have paid back by making further development easier.

Overall, bringing a new product from the first designs to a sellable pilot product in only 9 months and 3 hardware revisions is a good achievement for the project. The rest of this Chapter evaluates the product as a device, i.e. whether the instrument that has been designed fulfills its purpose well.

\section{Compared to previous version}
The measurement accuracy of the previous version, Frame Rate Meter, has never been completely characterized. The general feel is that both the Frame Rate Meter and the Video Multimeter have a similar accuracy, down to the millisecond level. However, the Video Multimeter does not require manual adjustments of the brightness limits, and also handles dropped frames better.

The market potential of the Video Multimeter is much larger than that of the Frame Rate Meter. Because many new measurement functions can be implemented in software, the company can provide custom solutions for individual customers. The co-operation with customers also provides new use cases, some of which have wider demand on the market.

The hardware costs of the two versions are similar. In both cases, the cost of assembly dominates the price. The number of manual steps in the assembly has been reduced compared to the previous version, and the amount of electrical components on the PCB is also smaller. The 3D-printed enclosure is also quick to assemble.

Characterization has shown that the Video Multimeter can measure up to 150~FPS with 1~ms resolution. This improves over the 120~FPS limit of the Frame Rate Meter. The resolution of the Frame Rate Meter was 0.1~ms, which was possible due to the simpler signal processing requirements. However, 1~ms is a sufficient measurement resolution for the displays expected in the near future, and very likely exceeds the limits of human perception. Specialized measurement tasks could also use a simpler signal processing pipeline in order to measure at higher resolution.

\section{Achieving of goals}
The primary goal was to implement frame detection in a way that could solve the problems with dropped frames that had arisen in the previous revision. This was achieved by means of a multi-state color marker and a sensor capable of reading it.

Secondary goals were to expand the device to new kinds of measurement tasks. The extensibility designed into the hardware makes this possible. This has been demonstrated by implementing a few additional measurements, such as camera latency, and more can be added through software and new sensors.

Tertiary goal was to simplify the use of the device by automatically compensating for different display types, backlight brightnesses and other factors, without manual configuration. This has been achieved through a careful design of signal processing algorithms. The difficulty of this task was greatly underestimated in the beginning of the project, and about a month of the schedule slip is entirely due to problems in making the signal processing cope with display variations. However, in the end a single algorithm that accepts any display type allows a much better result than having a separate algorithm for every situation.

There were also other secondary goals that were related to the planned camera extension board. However, these had to be dropped midway through the project, when the schedule began to slip. The hardware does allow the implementation of the camera extension later on, so these goals can be considered to be postponed for now.

\section{Sales and customer feedback}
Generally, the customers have been interested in the possibilities of the new model. Some example measurement reports have been prepared for customer's own devices, and these have been considered very useful. A few customers have also provided us with completely new use cases, which will highly benefit from the extensibility built into the device.

The sales department has been pleased about the easier demonstrability of the new device, compared to the previous models. As the device is self-contained and portable, the demonstration is easy to set up. Also the new measurement tasks, such as camera latency measurement, have allowed more interesting demonstrations and they also give the potential customers an idea about the flexibility of the device.

Early pilot customers had concerns about the accuracy of the results. These have been addressed both by fixing of several software problems, and by performing a full characterization of the repeatability of the measurement results. The characterization results have proven the high repeatability and accuracy of the measurements across several display types.

Some negative feedback has been received about the look and feel of the enclosure. This is definitely something that could be improved now that the main hardware development is complete. A custom milled aluminum case could be more fitting for the price range of these instruments.

The basic design choice of making a portable instrument with its own touchscreen has also been questioned. However, the explanation that the portability allows mobile measurements in e.g. moving vehicle, has been generally accepted. It is true that a PC-based user interface can in some cases provide a better usability. Nevertheless, even that becomes feasible, as an API to control the device through USB has been planned.

Finally, the feature of camera latency measurements has drawn interest inside the company itself. OptoFidelity Oy develops many kinds of camera systems and the latency of video transfer is important in many of them. The portability and design of the Video Multimeter have been ideal for these measurements, as setting up the measurement takes only seconds. Usually it requires just the turning on of the device and positioning the fiber on the screen.
