[qsxcv]

disclaimer: i received this mouse for free. not a review. just sharing info and pictures for those who are curious.<br><br>
the logitech g102 has a new optical sensor (i.e. led illuminated, image correlation) that is not made by avago/pixart<br><a class="H-lightbox-open" href="http://www.overclock.net/content/type/61/id/2906220/"><img alt="" class="lightbox-enabled" data-id="2906220" data-type="61" src="http://www.overclock.net/content/type/61/id/2906220/width/600/height/1000/flags/LL" style="; width: 600px; height: 450px"></a><br><a class="H-lightbox-open" href="http://www.overclock.net/content/type/61/id/2906218/"><img alt="" class="lightbox-enabled" data-id="2906218" data-type="61" src="http://www.overclock.net/content/type/61/id/2906218/width/600/height/1000/flags/LL" style="; width: 600px; height: 450px"></a><br><br>
the sensor is connected to the main pcb with some weird surface-mount soldering. not sure what it's called.<br><br>
illumination is external as you can see.<br><br>
the lens is sort of clipped onto the sensor block. there is a little bit of wiggle possible. i doubt anyone will complain about "lens rattle" like for some of the 3366 mice, but we'll see.<br><a class="H-lightbox-open" href="http://www.overclock.net/content/type/61/id/2906236/"><img alt="" class="lightbox-enabled" data-id="2906236" data-type="61" src="http://www.overclock.net/content/type/61/id/2906236/width/600/height/1000/flags/LL" style="; width: 600px; height: 450px"></a><br><br>
some quick probing around with a multimeter and an oscilloscope reveals most of the pins' functionalities:<br>
(1 is bottom right, closest to the mcu. numbers go counter clockwise)
<div class="bbcode_code">
<div class="bbcode_code_head">Code:</div>
<pre>
<code>1 ss
2 mosi
3 miso
4 sclk
5 vdd?
6 gnd
7 ??

8 ??
9 gnd
10 ??
11 gnd
12 ??
13 gnd

14 ??
15 gnd
16 led-
17 gnd
18 gnd
19 led+
20 gnd</code>
</pre></div>
<br><br>
anyway...<br>
mousetester looks unlike anything i've ever seen.
<div class="quote-container" data-huddler-embed="/t/1612080/logitech-g102-prodigy/500_100#post_25643945" data-huddler-embed-placeholder="false"><span>Quote:</span>
<div class="quote-block">Originally Posted by <strong>qsxcv</strong> <a href="/t/1612080/logitech-g102-prodigy/500_100#post_25643945"><img alt="View Post" class="inlineimg" src="/img/forum/go_quote.gif"></a><br><br><a class="H-lightbox-open" href="http://www.overclock.net/content/type/61/id/2905902/"><img alt="" class="lightbox-enabled" data-id="2905902" data-type="61" src="http://www.overclock.net/content/type/61/id/2905902/flags/LL" style="; width: 800px; height: 600px"></a><br>
at low speeds there are discrete steps. at high speeds eventually it gets to something above 10000fps. for now, i'm too lazy to figure out exactly<br><br>
i was quite confused by the discrete steps, but here's a plausible explanation<br>
it appears what is going on is that for moderate speeds, the framerate is continuously adjusted such that the amount of motion in a frame is nearly constant.<br><br>
i suspect this is a very low power sensor which will eventually be used in a wireless mouse</div>
</div>
<br>
well my hunch about the continuous framerate was sort of right. hooking up a wire to the led cathode gives a direct view of the timing of the frames:<br><a class="H-lightbox-open" href="http://www.overclock.net/content/type/61/id/2906238/"><img alt="" class="lightbox-enabled" data-id="2906238" data-type="61" src="http://www.overclock.net/content/type/61/id/2906238/width/600/height/1000/flags/LL" style="; width: 600px; height: 450px"></a><br>
when not in motion, the sensor runs at about 1000Hz.<br><a class="H-lightbox-open" href="http://www.overclock.net/content/type/61/id/2906247/"><img alt="" class="lightbox-enabled" data-id="2906247" data-type="61" src="http://www.overclock.net/content/type/61/id/2906247/flags/LL" style="; width: 800px; height: 480px"></a><br><br>
the sensor frames are not synchronized to the usb frames, which can be easily shown by taking a few snapshots:
<a class="spoiler-link H-spoiler-toggle" href="#"><strong>Warning: Spoiler!</strong> <span class="spoiler-help">(Click to show)</span></a><div class="spoiler-hidden">yellow trace is the led cathode. blue trace is USB D+.<br><a class="H-lightbox-open" href="http://www.overclock.net/content/type/61/id/2906241/"><img alt="" class="lightbox-enabled" data-id="2906241" data-type="61" src="http://www.overclock.net/content/type/61/id/2906241/flags/LL" style="; width: 800px; height: 480px"></a><br><a class="H-lightbox-open" href="http://www.overclock.net/content/type/61/id/2906242/"><img alt="" class="lightbox-enabled" data-id="2906242" data-type="61" src="http://www.overclock.net/content/type/61/id/2906242/flags/LL" style="; width: 800px; height: 480px"></a><br><a class="H-lightbox-open" href="http://www.overclock.net/content/type/61/id/2906243/"><img alt="" class="lightbox-enabled" data-id="2906243" data-type="61" src="http://www.overclock.net/content/type/61/id/2906243/flags/LL" style="; width: 800px; height: 480px"></a></div>
if you don't touch the sensor for about 100 seconds, it goes into a 50Hz rest mode. I'm not sure whether there are deeper rest modes though.<br><a class="H-lightbox-open" href="http://www.overclock.net/content/type/61/id/2906244/"><img alt="" class="lightbox-enabled" data-id="2906244" data-type="61" src="http://www.overclock.net/content/type/61/id/2906244/flags/LL" style="; width: 800px; height: 480px"></a><br>
k so what happens when you move it?<br><a class="H-lightbox-open" href="http://www.overclock.net/content/type/61/id/2906246/"><img alt="" class="lightbox-enabled" data-id="2906246" data-type="61" src="http://www.overclock.net/content/type/61/id/2906246/flags/LL" style="; width: 800px; height: 480px"></a><br>
the increasing intensity reflects increased density of the led's toggling. i.e. higher framerate<br><br>
zooming in:<br><a class="H-lightbox-open" href="http://www.overclock.net/content/type/61/id/2906249/"><img alt="" class="lightbox-enabled" data-id="2906249" data-type="61" src="http://www.overclock.net/content/type/61/id/2906249/flags/LL" style="; width: 800px; height: 480px"></a><br><a class="H-lightbox-open" href="http://www.overclock.net/content/type/61/id/2906250/"><img alt="" class="lightbox-enabled" data-id="2906250" data-type="61" src="http://www.overclock.net/content/type/61/id/2906250/flags/LL" style="; width: 800px; height: 480px"></a><br><br>
quite surprising how sporadic it is. not sure if this is a good or a bad thing. i would prefer to see either a constant framerate or at least one that always has periodic timings, but it's possible that this is intentional. i don't know.<br>
but anyway, unlike the 3310, 3360/3366, etc... the framerate isn't adjusted by entering different modes with predefined framerates. or so it appears at least<br><br>
the maximum framerate is something around 12kHz<br><a class="H-lightbox-open" href="http://www.overclock.net/content/type/61/id/2906271/"><img alt="" class="lightbox-enabled" data-id="2906271" data-type="61" src="http://www.overclock.net/content/type/61/id/2906271/width/500/height/1000/flags/LL" style="; width: 500px; height: 300px"></a><br><br>
anyway...<br>
some initial info about the spi:<br>
6 bytes of communication every 1ms.<br><a class="H-lightbox-open" href="http://www.overclock.net/content/type/61/id/2906255/"><img alt="" class="lightbox-enabled" data-id="2906255" data-type="61" src="http://www.overclock.net/content/type/61/id/2906255/flags/LL" style="; width: 800px; height: 480px"></a><br>
spi runs at 8MHz<br><a class="H-lightbox-open" href="http://www.overclock.net/content/type/61/id/2906256/"><img alt="" class="lightbox-enabled" data-id="2906256" data-type="61" src="http://www.overclock.net/content/type/61/id/2906256/flags/LL" style="; width: 800px; height: 480px"></a>

 

[vanir1337]

Thanks for another detailed info, you're our mouse hero for sure! This definitely looks interesting.

 

[dobragab]

Great, thanks for the info!<br><br>
Have you tested its perfect control speed or smoothing? <img alt="biggrin.gif" class="bbcode_smiley" src="http://files.overclock.net/images/smilies/biggrin.gif">

 

[munchzilla]

this looks really weird. is it weird?<br>
I don't really read sensor measurements all that often...

 

[wareya]

It's super weird. But it's weird in a good way, like that time someone handed you a controller with analog sticks on it for the first time.

 

[Alya]

<div class="quote-container" data-huddler-embed="/t/1615853/g102-mercury-sensor-info#post_25645304" data-huddler-embed-placeholder="false"><span>Quote:</span>
<div class="quote-block">Originally Posted by <strong>dobragab</strong> <a href="/t/1615853/g102-mercury-sensor-info#post_25645304"><img alt="View Post" class="inlineimg" src="/img/forum/go_quote.gif"></a><br><br>
Great, thanks for the info!<br><br>
Have you tested its perfect control speed or smoothing? <img alt="biggrin.gif" class="bbcode_smiley" src="http://files.overclock.net/images/smilies/biggrin.gif"></div>
</div>
<br>
woll3 said it has no smoothing at lower CPI and said that if it has smoothing at higher CPI it's not enough to counteract the jitter of higher CPI from what I understand, so I guess it has no or very little smoothing.<br><br>
so how's the SRAV? and the sensor being PCB mounted is...interesting, to say the least, weren't the MLT04 chips like that as well?

 

[chr1spe]

So the frames aren't separated by some multiple of the minimum interval between frames at all points or anything? Seeing those patterns I would think the gaps would all be 0.1ms, 0.2ms, 0.3ms or something, but I guess that doesn't look to be the case.

 

[JackCY]

Neat, as long as it works <img alt="biggrin.gif" class="bbcode_smiley" src="http://files.overclock.net/images/smilies/biggrin.gif">

 

[kd5151]

<img alt="specool.gif" class="bbcode_smiley" src="http://files.overclock.net/images/smilies/specool.gif">

 

[wareya]

<div class="quote-container" data-huddler-embed="/t/1615853/g102-mercury-sensor-info#post_25645328" data-huddler-embed-placeholder="false"><span>Quote:</span>
<div class="quote-block">Originally Posted by <strong>Alya</strong> <a href="/t/1615853/g102-mercury-sensor-info#post_25645328"><img alt="View Post" class="inlineimg" src="/img/forum/go_quote.gif"></a><br><br>
so how's the SRAV?</div>
</div>
I don't think qsxcv has tools to test that... if he does that would be cool though.<br><br>
My theory is that the weird granular dynamic framerate is to reduce one source of SRAV.<br><div class="quote-container" data-huddler-embed="/t/1615853/g102-mercury-sensor-info#post_25645338" data-huddler-embed-placeholder="false"><span>Quote:</span>
<div class="quote-block">Originally Posted by <strong>chr1spe</strong> <a href="/t/1615853/g102-mercury-sensor-info#post_25645338"><img alt="View Post" class="inlineimg" src="/img/forum/go_quote.gif"></a><br><br>
So the frames aren't separated by some multiple of the minimum interval between frames at all points or anything? Seeing those patterns I would think the gaps would all be 0.1ms, 0.2ms, 0.3ms or something, but I guess that doesn't look to be the case.</div>
</div>
<br>
If I'm right and the sensor is trying to get an integer amount of pixel motion in between each frame, it might be elongating every few frames because of its internal subpixel motion tracking falling ahead or behind. Also, if they wanted to get an integer-pixel-offset for each axis, they would have to capture two correlation frames for each reference frame (if possible for the given movement), which would be silly and cause a lot of DSP programming difficulties... would it?

 

[chr1spe]

<div class="quote-container" data-huddler-embed="/t/1615853/g102-mercury-sensor-info#post_25645379" data-huddler-embed-placeholder="false"><span>Quote:</span>
<div class="quote-block">Originally Posted by <strong>wareya</strong> <a href="/t/1615853/g102-mercury-sensor-info#post_25645379"><img alt="View Post" class="inlineimg" src="/img/forum/go_quote.gif"></a><br><br>
I don't think qsxcv has tools to test that... if he does that would be cool though.<br><br>
My theory is that the weird granular dynamic framerate is to reduce one source of SRAV.<br>
If I'm right and the sensor is trying to get an integer amount of pixel motion in between each frame, it might be elongating every few frames because of its internal subpixel motion tracking falling ahead or behind. Also, if they wanted to get an integer-pixel-offset for each axis, they would have to capture two correlation frames for each reference frame (if possible for the given movement), which would be silly and cause a lot of DSP programming difficulties... would it?</div>
</div>
<br>
Well, I'm just trying to figure out if that is the case. I'm having trouble telling with the first image, but the second one all of the gaps are actually 0.1ms or 0.2ms which would make me think that the others are too. Its difficult to read the other one for me though.

 

[qsxcv]

<div class="quote-container" data-huddler-embed="/t/1615853/g102-mercury-sensor-info/0_100#post_25645304" data-huddler-embed-placeholder="false"><span>Quote:</span>
<div class="quote-block">Originally Posted by <strong>dobragab</strong> <a href="/t/1615853/g102-mercury-sensor-info/0_100#post_25645304"><img alt="View Post" class="inlineimg" src="/img/forum/go_quote.gif"></a><br><br>
Have you tested its perfect control speed or smoothing? <img alt="biggrin.gif" class="bbcode_smiley" src="http://files.overclock.net/images/smilies/biggrin.gif"></div>
</div>
at least 6m/s. probably too high to measure. i didn't try very hard<br><a class="H-lightbox-open" href="http://www.overclock.net/content/type/61/id/2906298/"><img alt="" class="lightbox-enabled" data-id="2906298" data-type="61" src="http://www.overclock.net/content/type/61/id/2906298/width/350/height/700/flags/LL" style="; width: 350px; height: 263px"></a><br><br>
smoothing: don't know yet; assuming no.

 

[qsxcv]

<div class="quote-container" data-huddler-embed="/t/1615853/g102-mercury-sensor-info/0_100#post_25645379" data-huddler-embed-placeholder="false"><span>Quote:</span>
<div class="quote-block">Originally Posted by <strong>wareya</strong> <a href="/t/1615853/g102-mercury-sensor-info/0_100#post_25645379"><img alt="View Post" class="inlineimg" src="/img/forum/go_quote.gif"></a><br><br><div class="quote-container" data-huddler-embed="/t/1615853/g102-mercury-sensor-info#post_25645328" data-huddler-embed-placeholder="false"><span>Quote:</span>
<div class="quote-block">Originally Posted by <strong>Alya</strong> <a href="/t/1615853/g102-mercury-sensor-info#post_25645328"><img alt="View Post" class="inlineimg" src="/img/forum/go_quote.gif"></a><br><br>
so how's the SRAV?</div>
</div>
I don't think qsxcv has tools to test that... if he does that would be cool though</div>
</div>
i can only test with my hand. so not very accurate of course, but for the prototype i used it was as good as the other logitech mice. i assume this one is the same

 

[Klopfer]

wanna try it myself ....<br>
come on Logitech sell that damn **** in the rest of the World too ...<br>
only steps Im really interested in are ~400 - 1000 CPI ...( ~700-1000 for desktop and CIV , ~400 for fps )

 

[daniel0731ex]

Could someone enlighten me as to what is being referred to when you say "discrete steps at low speeds" I can't seem to make them out properly from the plot.<br><br>
EDIT: nvm I see it.

 

[wareya]

referring to the horizontal lines on the mousetester plot

 

[Jonagold]

How about click latency? I would buy g pro or this g102 but FM Scream One has less click delay atm and should be more or less equal in other aspects..

 

[v0rtex-SI]

<div class="quote-container" data-huddler-embed="/t/1615853/g102-mercury-sensor-info/10#post_25645467" data-huddler-embed-placeholder="false"><span>Quote:</span>
<div class="quote-block">Originally Posted by <strong>Klopfer</strong> <a href="/t/1615853/g102-mercury-sensor-info/10#post_25645467"><img alt="View Post" class="inlineimg" src="/img/forum/go_quote.gif"></a><br><br>
wanna try it myself ....<br>
come on Logitech sell that damn **** in the rest of the World too ...<br>
only steps Im really interested in are ~400 - 1000 CPI ...( ~700-1000 for desktop and CIV , ~400 for fps )</div>
</div>
Its on german ebay.. Just search for logitech g102 and buy it <img alt="biggrin.gif" class="bbcode_smiley" src="http://files.overclock.net/images/smilies/biggrin.gif">

 

[JackCY]

<div class="quote-container" data-huddler-embed="/t/1615853/g102-mercury-sensor-info/0_20#post_25645836" data-huddler-embed-placeholder="false"><span>Quote:</span>
<div class="quote-block">Originally Posted by <strong>v0rtex-SI</strong> <a href="/t/1615853/g102-mercury-sensor-info/0_20#post_25645836"><img alt="View Post" class="inlineimg" src="/img/forum/go_quote.gif"></a><br><br>
Its on german ebay.. Just search for logitech g102 and buy it <img alt="biggrin.gif" class="bbcode_smiley" src="http://files.overclock.net/images/smilies/biggrin.gif"></div>
</div>
Yeah but if the pricing is going to be similar in retail shops in our own countries it's better to buy it there considering the return rate on mice, monitors, etc. is staggering due to poor QC or bad design.<br>
eBay is sort of buy and keep, not buy and return if you don't like it or the one you got is faulty (such as inconsistent buttons or other stuff that doesn't make it DOA).<br><br>
At least that is why I wait, to have the option to return it if prices are very similar.

 

[v0rtex-SI]

<div class="quote-container" data-huddler-embed="/t/1615853/g102-mercury-sensor-info/10#post_25645912" data-huddler-embed-placeholder="false"><span>Quote:</span>
<div class="quote-block">Originally Posted by <strong>JackCY</strong> <a href="/t/1615853/g102-mercury-sensor-info/10#post_25645912"><img alt="View Post" class="inlineimg" src="/img/forum/go_quote.gif"></a><br><br>
Yeah but if the pricing is going to be similar in retail shops in our own countries it's better to buy it there considering the return rate on mice, monitors, etc. is staggering due to poor QC or bad design.<br>
eBay is sort of buy and keep, not buy and return if you don't like it or the one you got is faulty (such as inconsistent buttons or other stuff that doesn't make it DOA).<br><br>
At least that is why I wait, to have the option to return it if prices are very similar.</div>
</div>
You can always sell the mouse? Sure you lose an euro or two but theres no need to keep it if you dont like it.