Sensor and Performance

The Abkoncore A660 is equipped with the PixArt PMW3325 sensor. According to specifications, the 3325 is capable of up to 5000 CPI, as well as a maximum tracking speed of 100 IPS, which equals 2.54 m/s. For the A660, Abkoncore doubled the CPI count to 10,000 via interpolation. Out of the box, four pre-defined CPI steps are available: 1000, 500, 1600, and 2000 (in that order).

CPI Accuracy

"CPI" (short for counts per inch) describes the number of counts registered by the mouse if it is moved exactly an inch. There are several factors (firmware, mounting height of the sensor not meeting specifications, mouse feet thickness, mousing surface, among others) which may contribute to actual CPI not matching nominal CPI. It is impossible to always achieve a perfect match, but ideally, nominal and actual CPI should differ as little as possible. In this test, I'm determining whether this is the case or not. However, please keep in mind that said variance will still vary from unit to unit, so your mileage may vary as well.


I've restricted my testing to the four most common CPI steps, which are 400, 800, 1600, and 3200. As you can see, deviation is not entirely consistent, but pretty low overall, which is a good result.

Motion Delay

"Motion delay" encompasses all kinds of sensor lag. Any further sources of input delay will not be recorded in this test. The main thing I'll be looking for in this test is sensor smoothing, which describes an averaging of motion data across several capture frames in order to reduce jitter at higher CPI values, increasing motion delay along with it. The goal here is to have as little smoothing as possible. As there is no way to accurately measure motion delay absolutely, it can only be done by comparison with a control subject that has been determined to have the lowest possible motion delay. In this case the control subject is a G403, whose 3366 has no visible smoothing across the entire CPI range.


First, I'm looking at two xCounts plots—generated at 1600 and 5000 CPI—to quickly gauge whether there is any smoothing, which would be indicated by any visible "kinks." As you can see, no such kinks can be observed at either 1600 CPI or 5000 CPI (although the 5000 CPI graph does show minor kinks, but that may be due to something else). Based on these findings, we can conclude that there is no visible smoothing across the entire CPI range. We can also see that SPI timing jitter levels are quite low.


Let us take a look at three additional xSum plots, generated at 1600, 5000, and 10,000 CPI, the latter of which is an interpolated step. The line further to the left denotes the sensor with less motion delay. I can measure a motion delay of roughly 3 ms across the entire CPI range, including the interpolated steps. Much like on the Abkoncore A530, this delay isn't caused by smoothing but something else.

Speed-Related Accuracy Variance (SRAV)

What people typically mean when they talk about "acceleration" is speed-related accuracy variance (or short SRAV). It's not about the mouse having a set amount of inherent positive or negative acceleration, but about the cursor not traveling the same distance if the mouse is moved the same physical distance at different speeds. The easiest way to test this is by comparison with a control subject that is known to have very low SRAV, which in this case is the G403. As you can see from the plot, no displacement between the two cursor paths can be observed, which confirms that SRAV is very low.

Perfect Control Speed

Perfect Control Speed (or PCS for short) is the maximum speed up to which the mouse and its sensor can be moved without the sensor malfunctioning in any way. Around 3.4 m/s, you can see the sensor malfunctioning. Although 3.4 m/s is above spec (~2.5 m/s), it's still pretty poor for today's standards.

Polling Rate Stability

All four available polling rates (125 Hz, 250 Hz, 500 Hz, and 1000 Hz) look nice and clean.

Paint Test

This test is used to indicate any potential issues with angle snapping (non-native straightening of linear motion) and jitter, along with any sensor lens rattle. As you can see, no issues with angle snapping can be observed. As expected from a sensor with no visible smoothing, jitter linearly increases with every CPI step. It's still reasonable all the way up to 5000 CPI, though. Steps beyond 5000 CPI are interpolated. Looking closely, one can see aliasing artifacts at the 10,000 CPI step, which are due to interpolation. Lastly, there is no sensor lens rattle.

Lift-off Distance

The A660 does not support adjusting LOD. The only available (default) setting is medium as the sensor does track at a height of 1 DVD, but not at a height of 2 DVDs (1.2 mm<x<2.4 mm). Keep in mind that LOD may vary slightly depending on the mousing surface (pad) it is being used on.

Click Latency

Since mechanical switches are being used for the buttons in most computer mice, debouncing is required in order to avoid unintended double clicks. Debouncing typically adds a delay (along with any potential processing delay), which shall be referred to as click latency. As there is no way to measure said delay directly, it has to be done by comparing it to a control subject, which in this case is the Logitech G100s. Click latency has been measured to be roughly +19.0 ms compared to the SteelSeries Ikari, which is considered as the baseline with 0 ms. Please keep in mind that the measured value is not the absolute click latency. Comparison data comes from this thread as well as my own testing, using qsxcv's program.