parts: torq x5l shell, top part of torq x5l pcb, d2f-f-3-7's, pmw3366 board from a g502, adafruit fpc stick, nrf24l01+ mini module, teensy2.0, adafruit 150mah lipo battery and switch, lots of wire and kapton tape, superglue and sugru in various places
small protoboard from fry's, teensy2.0, nrf24l01+ module
i removed all side buttons and also other various parts of the shell.button latency:
wireless vs my modded g100s (wired):
g100s_teensy_r_vs_x5l_teensy_l.txt 4k .txt file
avg: 0.342ms slower
wireless vs g303:
g303_r_vs_x5l_teensy_l.txt 4k .txt file
avg 4.98ms fastermotion latency:
well i don't have logitech's rig, and mousecomparator/tester is only precise/repeatable to around 1ms or so. but i can directly measure the timing between the sensor communications and the usb stuff on the oscilloscope.
my wireless thing:
g303:synchronization to usb frames:
Originally Posted by CPate
It's theoretically possible make a nicer-looking plot by doing things differently, but this has the consequence of a drastic decrease in battery life. So that's not what we did.
Originally Posted by CPate
can't you just have the wireless receiver send a packet every 50 usb frames or so to keep the main loop of the mouse firmware in sync? something like a phase-locked loop
i don't see how that affects battery life significantly
well idk if logitech has tried this yet, but i did and got it within ~1us
here, the oscilloscope is triggered by sensor communication in the main loop. the yellow trace is the usb D+ line from the receiver. i can explain in greater detail how it works but it's not very interesting.
and of course it's perfectly stable in mousetesterbattery life:
unknown right now. probably around 3-4hrs. i haven't optimized for power consumption yet. after doing that i'd expect the current draw to be ~25mA when the sensor is tracking, so around 6 hours of continuous use with the 150mAh battery. adding in idle modes should make it good enough that i would only need to charge it overnight.
once i do that and clean things up a bit more, i'll post the firmware (pm me if you want what i currently have)wireless performance:
well... i can't really test it but
1. in usual circumstances where the receiver is only a few feet away, it never drops packets. (or at least i don't see any from a 30s interval plot in mousetester)
2. the mouse sends absolute coordinates to the receiver, so even a packet is dropped, there is no drift. if you were to do logitech's circular motion test on this with lots of background 2.4ghz stuff going on, the only issue would be that the circles might show some flat sides due to the dropped packets, but it won't show jumps like the mamba 2015 (http://www.pcper.com/news/General-Tech/Just-Delivered-Logitech-G900-Chaos-Spectrum-Wireless-Ambidextrous-Mouse
3. the channel it uses is hard-coded, whereas i'd expect the g900 to be more robust and automatically select the best channel or something.