View ADNS-5700-H5MD_8757702.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

adns-5700 optical mouse sensor data sheet description the adns-5700- xxxx is a c ompact, one chip usb optical mouse sensor for implementing a non-mechanical track- ing engine for computer mice. it is based on optical navigation technology that measures changes in position by optically acquiring sequential surface images (frames) and mathematically determining the direction and magnitude of movement. the sensor is in a 18 -pin optical package that is designed to be used with the adns-5100-001 trim lens the adns- 5200 clip and the hlmp-eg3e-xxxxx led. these parts provide a complete and compact mouse sensor. there are no moving parts, and precision optical alignment is not required, facilitating high volume assembly. the output format is usb. this device meets hid revision 1.11 specifi cation and is compatible with usb revision 2.0 specifi cation. frame rate is varied internally to the sensor to achieve tracking and speed performance, eliminating the need for the use of many registers. default resolution is specifi ed as 1000 counts per inch, with rates of motion up to 30 inches per second. buttons and tilt wheel features are also available. a complete mouse can be built with the addition of a pc board, switches and mechanical z-wheel, plastic case and cable. theory of operation the adns-5700- xxxx is based on optical navigation technology. it contains an image acquisition system (ias), a digital signal processor (dsp) and usb stream output. the ias acquires microscopic surface images via the lens and illumination system provided by the adns-5100- 001 trim lens, adns-5200 clip and hlmp-eg3e-xxxxx led. these images are processed by the dsp to determine the direction and distance of motion. the dsp generates the x and y relative displacement values which are converted to usb motion data. features ? optical navigation technology ? default resolution 1000cpi, selectable resolution 800cpi or 1200cpi through diff erent part number ? high speed motion detection up to 30 inches per second (ips) and acceleration of 8g ? accurate navigation over a wide variety of surfaces ? no precision optical alignment needed ? wave solderable ? single 5.0 volt power supply ? meets usb revision 2.0 specifi cation ? meets hid revision 1.11 ? tilt wheel function ? optical or mechanical z-wheel function ? 12bits motion reporting ? 2 axis sensor rotation : 0 or 270 applications ? mice for desktop pcs, workstations, and portable pcs ? trackballs ? integrated input devices
2 pinout 18pin pdip adns-5700-xxxx pin number 3 button 5 button h3mb, h3nb h4mb, h4nb h5md, h5nd 1 d + d + d + 2 d - d - d - 3za za za 4zb zb zb 5 led_gnd led_gnd led_gnd 6 xy_led xy_led xy_led 7v dd5 v dd5 v dd5 8 gnd gnd gnd 9 reg0 reg0 reg0 10 v dd3 v dd3 v dd3 11 nc tl b4 12 nc tr osc_in 13 gnd gnd gnd 14 osc_in osc_in osc_out 15 osc_out osc_out b3 16 b3 b3 b2 17 b2 b2 b1 18 b1 b1 b5 pin description table pin name description d + usb d+ line d - usb d- line za za optical wheel quadrature input zb zb optical wheel quadrature input led_gnd led ground xy_led xy_led input v dd5 5 volt power (usb vbus) gnd system ground zled z-wheel led input reg0 / v dd3 3 volt power v dd3 nc no connect osc_in ceramic resonator input osc_out ceramic resonator output b5 fifth button b4 fourth button b3 middle button input b2 right button input b1 left button input figure 1a. package pinout note : see table for part number marking 7 4 3 12 18 17 16 15 14 13 11 10 9 8 6 5 2 1 product number date code lot code item marking remarks product number a5700 date code xyywwz x = subcon code yyww = date code z = sensor die source lot code vvv numeric disclaimer: all designers and manufacturers of this design must assure that they have all necessary intellectual property right s.
3 strap (jumper) table the pid/string strap matrix is the following: part number description resolution (cpi) buttons tilt wheel z-wheel sensor position vid pid mfg string product string adns-5700-h3mb standard 3 buttons 1000 3 no mechanical 0 0x192f 0x0416 null usb optical mouse adns-5700-h4mb standard 3 buttons 1000 3 tw mechanical 0 0x192f 0x0416 null usb optical mouse ADNS-5700-H5MD standard 5 buttons 1000 5 no mechanical 0 0x192f 0x0616 null usb optical mouse adns-5700-h3nb standard 3 buttons 1000 3 no mechanical 270 0x192f 0x0416 null usb optical mouse adns-5700-h4nb standard 3 buttons 1000 3 tw mechanical 270 0x192f 0x0416 null usb optical mouse adns-5700-h5nd standard 5 buttons 1000 5 no mechanical 270 0x192f 0x0616 null usb optical mouse disclaimer: all designers and manufacturers of this design must assure that they have all necessary intellectual property rights. the xy motion reporting direction when is lens is attached to the sensor is shown in fig 1b for 0 and fig 1c for 270 sensor orientation. figure 1b. package pinout at 0 figure 1c. package pinout at 270 rb lb top xray view of mouse positive x p o s i t i v e y 7 4 3 12 18 17 16 15 14 13 11 10 9 8 6 5 2 1 rb lb top xray view of mouse positive x p o s i t i v e y 7 4 3 12 18 17 16 15 14 13 11 10 9 8 6 5 2 1
4 figure 2. package outline drawing caution: it is advised that normal static precautions be taken in handling and assembly of this component to prevent damage and/or degradation which may be induced by esd. detail1 scale 10:1 0.25 0.010 50 q see detail1 0.40 lead width 0.016 1.00 lead offset 0.039 20.30 0.799 feature for illustration only pin 1 aa pin 1 clear optical path protective kapton tape 6.19 0.244 2.00 lead pitch 0.079 11.46 0.451 (1.00) 0.039 7.28 0.03 0.287 0.001 4.55 0.179 section a-a 5.60 0.03 (at base) 0.220 0.001 (0.46) 0.018 (3.40) 0.134 (2.54) 0.100 (1 q ) 12.85 0.54 (at lead tip) 0.506 0.021 4.30 0.169 1.00 0.039 0.25 0.010 12.85 (at shoulder) 0.506 9.10 0.358 5.15 0.203 1.09 0.03 0.043 0.001 (6.43) 0.253 2x 90 3 q notes: 1. dimensions in milimeter / inches. 2. dimensional tolerance: 0.1mm. 3. coplanarity of leads: 0.1mm. 4. lead pitch tolerance: 0.15mm. 5. non-cumulative pitch tolerance: 0.15mm. 6. angular tolerance: 3 q 7. maximum flash: 0.2mm. 8. brackets () indicate reference dimension. 9. document number: led_soc_18a_pkg_001
5 figure 3. recommended pcb mechanical cutouts and spacing (top view) avago technologies provides an iges fi le drawing describing the base plate molding features for lens and pcb align- ment. stand-off of the base plate shall not be larger than 5mm. note: the recommended pin hole dimension of the sensor is 0.7 mm. shown with adns-5100-001 trim lens, adns-5200 clip and hlmp-eg3e-xxxxx. clear zone pin #1 hole notes: 1. dimensions in milimeter / inches and for reference only. 1.00 0.039 26.50 1.043 40.59 1.598 0.35 0.014 12.95 0.510 2.25 0.089 10.35 0.408 7.57 0.298 5.03 0.198 2.00 0.079 12.61 0.496 10.60 0.417 2.00 0.079 38.52 1.516 28.09 1.106 2.65 0.104 2x ? 3.05 0.120 recommended 18x 0.80 0.031 recommended 2x 1.00 0.039 recommended 0 0 ? ?
6 figure 4. 2d assembly drawing of adns-5700-xxxx notes: 1. all dimensions in millimeters/inches. 2. all tolerance 0.1 mm. top of sensor to surface top of pcb to surface lens reference plane to tracking surface (z) pcb sensor lens led clip section b-b 10.59 0.417 7.45 0.293 2.40 0.094 13.89 top of clip 0.547 bb pcb surface 13.10 0.516 42.16 1.660
7 figure 5. exploded view drawing the components interlock as they are mounted onto defi ned features on the base plate. the adns-5700 sensor is designed for mounting on a through hole pcb, looking down. the aperture stop and features on the package align it to the lens (see fi gure 3). the adns-5100-001 trim lens provides optics for the imaging of the surface as well as illumination of the surface at the optimum angle. lens features align it to the sensor, base plate, and clip with the led. the adns-5200 clip holds the led in relation to the lens. the led must be inserted into the clip and the leds leads formed prior to loading on the pcb. the clip interlocks the sensor to the lens, and through the lens to the alignment features on the base plate. the hlmp-eg3e-xxxxx led is recommended for illumination. customer supplied base plate with recommended features per iges 3d model lens (full flange shown) pcb sensor led led clip
8 block diagram zb za image processor z wheel power on reset lgnd xy_led led drive oscillator oscillator led osc_in osc_out voltage reference d d + usb port 5 volt power vdd3 gnd vdd5 gnd buttons control and i/o processor gnd tl/b4 b3 b2 b1 tr/b5 zled v o l t a g e r e g u l a t o r figure 6. block diagram pcb assembly considerations 1. insert the sensor and all other electrical components into pcb. 2. bend the led leads 90 degrees and then insert the led into the assembly clip until the snap feature locks the led base. 3. insert the led/clip assembly into pcb. 4. this sensor package is only qualifi ed for wave-solder process. 5. wave solder the entire assembly in a no-wash solder process utilizing solder fi xture. the solder fi xture is needed to protect the sensor during the solder process. it also sets the correct sensor to pcb distance, as the lead shoulders do not normally rest on the pcb surface. the fi xture should be designed to expose the sensor leads to solder while shielding the optical aperture from direct solder contact. a solder fi xture must be used to set the correct sensor to pcb distance. 6. place the lens onto the base plate. 7. remove the protective kapton tape from optical aperture of the sensor. care must be taken to keep contaminants from entering the aperture. recommend not placing the pcb facing up during the entire mouse assembly process. recommend to hold the pcb fi rst vertically for the kapton removal process. 8. insert pcb assembly over the lens onto base plate aligning post to retain pcb assembly. the sensor aperture ring should self-align to the lens. 9. the optical position reference for the pcb is set by the base plate and lens. note that the pcb motion due to button presses must be minimized to maintain optical alignment. 10. install mouse top case. there must be feature in the top case to press down onto the clip to ensure all components are interlocked to correct vertical height
9 design considerations for improving esd performance the table below shows typical values assuming base plate construction per the avago technologies supplied iges fi le and adns-5100-001 trim lens. stand-off of the base plate shall not be larger than 5mm. typical distance adns-5100-001 creepage 17.9mm clearance 9.2mm note that the lens material is polycarbonate or polysty- rene hh30, therefore, cyanoacrylate based adhesives should not be used as they will cause lens material defor- mation lens/light pipe pcb base plate surface sensor clip led figure 7. typical application
10 figure 8a. application circuit with adns-5700-hxxb with optical z-wheel +3.3 v vdd 5 v c2 c4 c5 c3 8 13 10 7 vdd 3 vdd 5 gnd gnd d - d + zled za zb zled vdd qa qb z - encoder 27 k 27 k usb d - usb d + 100 pf 100 pf 2 1 9 3 4 +3.3 v 1.5k led_gnd xy_led osc in osc out b1 b2 b3 5 6 14 15 18 17 16 nav led vdd 5 v guard gnd 33 ? c6 c7 33 ? 11 12 see pinout table r1 c2, c3 = 1 nf c4 = 4.7 uf c5 = 3.3 uf disclaimer: all designers and manufacturers of this design must assure that they have all necessary intellectual property rights. notes: ? all caps (except c4) must be as close to the sensor pins as possible. ? c3 and c5 connected to pin 10 must be terminated at pin 13. ? caps should be ceramic. ? caps should have less than 5 nh of self inductance. ? caps connected to v dd3 must have less than 0.2 ? esr. ? 1.5k resistor should be 1% tolerance. surface mount parts are recommended. r1 value (ohm) led bin 59.0 k 59.0 l 59.0 m 59.0 n 59.0 to 66.5 p 59.0 to 78.7 q 59.0 to 93.1 r 59.0 to 110 s 59.0 to 143 t
11 figure 8b. application circuit with adns-5700-hxxb with mechanical z-wheel r1 value (ohm) led bin 59.0 k 59.0 l 59.0 m 59.0 n 59.0 to 66.5 p 59.0 to 78.7 q 59.0 to 93.1 r 59.0 to 110 s 59.0 to 143 t +3.3 v vdd 5 v c2 c4 c5 c3 8 10 7 vdd 3 vdd 5 gnd d - d + za zb vdd 5 v usb d - usb d + 2 1 3 4 +3.3 v 1.5 k led_gnd xy_led osc in osc out b1 b2 b3 5 6 14 15 18 17 16 nav led vdd 5 v mechanical zwheel guard gnd c1 c6 13 9 reg 0 gnd 100 pf 100 pf c7 c8 11 12 see pinout table 33 ? 33 ? r1 c2, c3 = 1 nf c4 = 4.7 uf c5 = 3.3 uf disclaimer: all designers and manufacturers of this design must assure that they have all necessary intellectual property rights. notes: ? all caps (except c4) must be as close to the sensor pins as possible. ? c1 and c6 connected to pin 10 must be terminated at pin 13. ? c3 and c5 connected to pin 9 must be terminated at pin 8. ? caps should be ceramic. ? caps should have less than 5 nh of self inductance. ? caps connected to v dd3 must have less than 0.2 ? esr. ? 1.5k resistor should be 1% tolerance. surface mount parts are recommended.
12 figure 8c. application circuit with ADNS-5700-H5MD and adns-5700-h5nd with 5 button and mechanical z-wheel r1 value (ohm) led bin 59.0 k 59.0 l 59.0 m 59.0 n 59.0 to 66.5 p 59.0 to 78.7 q 59.0 to 93.1 r 59.0 to 110 s 59.0 to 143 t c1, c2, c3 = 1 nf c4 = 4.7 uf c5, c6 = 3.3 uf +3.3 v vdd 5 v c2 c4 c5 c3 8 10 7 vdd 3 vdd 5 gnd d - d + za zb vdd usb d - usb d + 2 1 3 4 +3.3 v 1.5 k led_gnd xy_led osc in osc out b5 b4 b3 b2 b1 5 6 12 14 18 11 15 16 17 nav led vdd 5 v mechanical zwheel guard gnd c1 c6 13 9 reg 0 gnd 100 pf 100 pf 33 ? 33 ? c8 c7 r1 disclaimer: all designers and manufacturers of this design must assure that they have all necessary intellectual property rights. notes: ? all caps (except c4) must be as close to the sensor pins as possible. ? c1 and c6 connected to pin 10 must be terminated at pin 13. ? c3 and c5 connected to pin 9 must be terminated at pin 8. ? caps should be ceramic. ? caps should have less than 5 nh of self inductance. ? caps connected to v dd3 must have less than 0.2 ? esr. ? 1.5k resistor should be 1% tolerance.
13 regulatory requirements ? passes fcc b and worldwide analogous emission limits when assembled into a mouse with shielded cable and following avago technologies recommendations. ? passes en61000-4-4/iec801-4 eft tests when assembled into a mouse with shielded cable and following avago technologies recommendations. ? ul fl ammability level ul94 v-0. ? provides suffi cient esd creepage/clearance distance to withstand discharge up to 15kv when assembled into a mouse with lens according to usage instructions above. absolute maximum ratings parameter symbol minimum maximum units notes storage temperature t s -40 85 c operating temperature t a -15 55 c lead solder temp 260 c for 7 seconds, 1.6mm below seating plane. supply voltage v dd -0.5 5.5 v esd 2 kv all pins, jesd22-a114 input voltage v in -0.5 v dd +0.5 v all i/o pins except osc_in and osc_out, d+, d- input voltage v in -1.0 4.6 v d+, d-, ac waveform, see usb specifi cation (7.1.1) input voltage v in -0.5 3.6 v osc_in and osc_out input short circuit voltage v sc 0v dd v d+, d-, see usb specifi cation (7.1.1) recommended operating conditions parameter symbol minimum typical maximum units notes operating temperature t a 040c power supply voltage v dd 4.25 5.0 5.25 volts for accurate navigation and proper usb operation power supply voltage v ddm 4 5.0 5.25 volts maintains communication to usb host and internal register contents. power supply rise time v rt 0.003 100 ms supply noise v n 100 mv peak to peak within 0-80 mhz bandwidth velocity vel 30 ips acceleration acc 8 g 0.5g from rest clock frequency f clk 23.64 24 24.36 mhz due to usb timing constraints resonator impedance x res 55 ? distance from lens reference plane to surface z 2.3 2.4 2.5 mm see figure 9 frame rate 4000 fps internally adjusted by sensor
14 figure 9. distance from lens reference plane to object surface ac electrical specifi cations electrical characteristics over recommended operating conditions. typical values at 25c, v dd =5.0 v parameter symbol min. typical max. units notes wakeup delay from rest mode due to motion. t wupp 2ms power up delay t pup 50 ms debounce delay on button inputs t dbb 5 10 17 ms maximum specifi ed at 8ms polling rate. scroll wheel sampling period t sw 150 200 300 s za pin for optical scroll wheel 1.9 2.0 2.8 ms za pin for mechanical scroll wheel transient supply current i ddt 60 ma max. supply current during a v dd ramp from 0 to 5.0 v with > 500 ? s rise time. does not include charging currents for bypass capacitors. input capacitance (osc pins) c osc_in 50 pf ocs_in, osc_out to gnd usb electrical specifi cations electrical characteristics over recommended operating conditions. parameter symbol min. max. units notes output signal crossover voltage v crs 1.5 2.0 v c l = 200 to 600 pf (see figure 10) input signal crossover voltage v icrs 1.2 2.1 v c l = 200 to 600 pf (see figure 10) output high v oh 2.8 3.6 v with 15 kohm to ground and 7.5 k ? to vbus on d- (see figure 11) output low v ol 0.0 0.3 v with 15 kohm to ground and 7.5 k ? to vbus on d- (see figure 11) single ended input v sei 0.8 v input high (driven) v ih 2.0 v input high (floating) v ihz 2.7 3.6 v input low v il 0.8 v 7.5k ? to v dd5 diff erential input sensitivity v di 0.2 v |(d+)-(d-)| see figure 12 diff erential input common mode range v cm 0.8 2.5 v includes v di , see figure 12 single ended receiver threshold v se 0.8 2.0 v transceiver input capacitance c in 12 pf d+ to v bus , d- to v bus z sensor lens object surface
15 usb timing specifi cations timing specifi cations over recommended operating conditions. parameter symbol min. max. units notes d+/d- transition rise time t lr 75 ns c l = 200 pf (10% to 90%), see figure 10 d+/d- transition rise time t lr 300 ns c l = 600 pf (10% to 90%), see figure 10 d+/d- transition fall time t lf 75 ns c l = 200 pf (90% to 10%), see figure 10 d+/d- transition fall time t lf 300 ns c l = 600 pf (90% to 10%), see figure 10 rise and fall time matching t lrfm 80 125 % t r /t f ; c l = 200 pf; excluding the fi rst transi- tion from the idle state wakeup delay from usb suspend mode due to buttons push t wupb 17 ms delay from button push to usb operation only required if remote wakeup enabled wakeup delay from usb suspend mode due to buttons push until accurate navigation t wupn 50 ms delay from button push to navigation operation only required if remote wakeup enabled usb reset time t reset 18.7 ? s data rate t ldrate 1.4775 1.5225 mb/s average bit rate, 1.5 mb/s +/- 1.5% receiver jitter tolerance t djr1 -75 75 ns to next transition, see figure 13 receiver jitter tolerance t djr2 -45 45 ns for paired transitions, see figure 13 diff erential to eop transition skew t ldeop -40 100 ns see figure 14 eop width at receiver t leopr 670 ns accepts eop, see figure 14 source eop width t leopt 1.25 1.50 ? s width of se0 interval during diff erential transition t lst 210 ns see figure 11 diff erential output jitter t udj1 -95 95 ns to next transition, see figure 15 diff erential output jitter t udj2 -150 150 for paired transitions, see figure 15 figure 10. data signal rise and fall times v crs 10% 10% 90% 90% t lr rise time t lf fall time v ol v oh d + d -
16 figure 12. diff erential receiver input sensitivity vs. common mode input range figure 13. receiver jitter tolerance figure 11. data signal voltage levels v oh (min) v ol (max) one bit time (1.5 mb/s) gnd v oh (min) v il (max) minimal re?ectance and ringing t lst -1.0 0.0 0.2 0.4 0.6 0.8 1.0 1.2 1.4 1.6 1.8 2.0 2.2 2.4 2.6 2.8 3.0 3.2 4.6 di?erential input voltage range di?erential output crossover voltage range input voltage range (volts) t djr1 t djr2 t djr t period consecutive transitions n * t period + t djr1 paired transitions n * t period + t djr2
17 figure 15. diff erential output jitter figure 14. diff erential to eop transition skew and eop width t period di?erential data lines di?erential data to se0 skew n * t period + t ldeop crossover point crossover point extended source eop width: t leopt receiver eop width: t leopr consecutive transitions n * t period + t udj1 paired transitions n * t period + t udj2 t period di?erential data lines
18 dc electrical specifi cations electrical characteristics over recommended operating conditions. typical values at 25c, v dd =5.0 v. parameter symbol minimum typical maximum units notes system current, mouse moving i dd5 100 ma includes xy_led current system current, mouse not moving i dd5n 100 ma includes xy_led current system current, usb suspend mode, remote wakeup enabled i dd5s 500 ? a includes xy_led current and d- pullup resistor. supply current (sensor only), mouse moving i dds 12 15 ma no load on b1-b5, xy-led, za, zb, d+, d- supply current (sensor only), mouse not moving i ddsn 11 14 ma no load on b1-b5, xy-led, za, zb, d+, d- sensor supply current, usb suspend mode i ddss 260 ? a no load on b1-b5, xy-led, za, zb, d+,d- xy_led current i led 40 49 ma typical at rbin 59ohm with binp led. maximum dc current allowed through xy_led pin and led. xy_led output low voltage v ol 1.1 v refer to figure 16 input low voltage v il 0.5 v pins: za, zb, b1-b5, v il max of 0.5v dc is at v dd min of 4v dc , with a typical of 0.8v dc at v dd of 5v dc input high voltage v ih 0.6*v dd v pins: za, zb, b1-b5 input hysteresis v hyst 285 mv pins: b1-b5, opt 0, opt 1 button pull up current b iout 125 275 500 ? a pins: b1-b5, opt 0, opt 1 buttons the minimum time between button presses is tdbb. buttons b1 through b5 are connected to a schmidt trigger input with 100 ua current sources pulling up to +3 volts during normal, sleep and usb suspend modes. debounce algorithm ? button inputs b1, b2, b3, b4, b5 are sampled every 2ms. ? three consecutive low create a button press event. ? three consecutive high create a button release event.
19 the following graphs are the typical performance of the adns-5700 sensor, assembled as shown in the 2d assembly drawing with the adns-5100-001 trim lens/prism, the adns-5200 clip, and the hlmp-eg3e-xxxxx led. figure 16. typical resolution vs. z height figure 17. wavelength responsivity. [1] (comparative surfaces) note: 1. the adns-5700 is designed for optimal performance when used with the hlmp-eg3e-xxxxx (red led 639nm). 2. z = distance from lens reference plane to surface. 3. dof = depth of field typical performance characteristics performance characteristics over recommended operating conditions. typical values at 25 c, v dd =5.0 v, 24mhz parameter symbol minimum typical maximum units notes path error (deviation) p error 0.5 % average path error as percent of total 2.5 travel on various standard surfaces resolution vs z-height on standard surfaces (adns-5700-xxxx) 0 200 400 600 800 1000 1200 1.6 1.8 2 2.2 2.4 2.6 2.8 3 3.2 z-height (mm) resolution(cpi) white paper manila spruce wood black formica relative wavelength response 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1 400 500 600 700 800 900 1000 wavelength in nm normalised response
20 confi guration after power up (data values) signal function state from figure 9-1 of usb spec: powered or default address or confi gured state from figure 9-1 of usb spec: suspended from any other state b1 b2 b3 b4 b5 v dd3 or gnd if used as vid/pid jumper else pullup active for button use v dd3 or gnd if used as vid/pid jumper v dd3 or gnd if used as vid/pid jumper v dd3 or gnd if used as vid/pid jumper else pullup active for button use v dd3 or gnd if used as vid/pid jumper else pullup active for button use v dd3 or gnd if used as vid/pid jumper else pullup active for button use v dd3 or gnd if used as vid/pid jumper v dd3 or gnd if used as vid/pid jumper v dd3 or gnd if used as vid/pid jumper else pullup active for button use v dd3 or gnd if used as vid/pid jumper else pullup active for button use d- usb i/o hi-z input d+ usb i/o hi-z input osc_in 24mhz logic 1 osc_out 24mhz logic 1 xy_led always on / pulsing pulled high (off ) zb hi-z input hi-z input za hi-z if za tied to gnd hi-z input z_led hi-z input hi-z input
21 usb commands mnemonic command notes usb_reset d+/d- low > 18.7us device resets; address=0 usb_suspend idle state > 3ms device enters usb low-power mode usb_resume non-idle state device exits usb low-power mode get_status_device 80 00 00 00 00 00 02 00 normally returns 00 00, self powered 00 00, remote wakeup 02 00 get_status_interface 81 00 00 00 00 00 02 00 normally returns 00 00 get_status_endpt0 82 00 00 00 xx 00 02 00 out: xx=00, in: xx=80 normally returns 00 00 get_status_endpt1 82 00 00 00 81 00 02 00 normally returns 00 00, halt 00 01 get_confi guration 80 08 00 00 00 00 01 00 return: 00=not confi g., 01=confi gured get_interface 81 0a 00 00 00 00 01 00 normally returns 00 get_protocol a1 03 00 00 00 00 01 00 normally returns 01, boot protocol 00 get_desc_device 80 06 00 01 00 00 nn 00 see usb command details get_desc_confi g 80 06 00 02 00 00 nn 00 see usb command details get_desc_string 80 06 xx 03 00 00 nn 00 see usb command details get_desc_hid 81 06 00 21 00 00 09 00 see usb command details get_desc_hid_report 81 06 00 22 00 00 nn 00 see usb command details get_hid_input a1 01 00 01 00 00 nn 00 return depends on motion & confi g get_idle a1 02 00 00 00 00 01 00 returns rate in multiples of 4ms get_vendor_test c0 01 00 00 xx 00 01 00 read register xx set_address 00 05 xx 00 00 00 00 00 xx = address set_confi guration 00 09 xx 00 00 00 00 00 not confi gured: xx=00 confi gured: xx=01 set_interface 01 0b 00 00 00 00 00 00 only one interface supported set_protocol 21 0b xx 00 00 00 00 00 boot: xx=00, report: xx=01 set_feature_device 00 03 01 00 00 00 00 00 enable remote wakeup set_feature_endpt0 02 03 00 00 xx 00 00 00 halt. out: xx=00, in: xx=80 set_feature_endpt1 02 03 00 00 81 00 00 00 halt clear_feature_device 00 01 01 00 00 00 00 00 disable remote wakeup clear_feature_endpt0 02 01 00 00 xx 00 00 00 clear halt; out: xx=00, in: xx=80 clear_feature_endpt1 02 01 00 00 81 00 00 00 clear halt set_idle 21 0a 00 rr 00 00 00 00 rr = report rate in multiples of 4ms set_vendor_test 40 01 00 00 xx yy 00 00 write yy to address xx poll_endpt1 read buttons, motion, & z-wheel note: the last two bytes in a command shown as nn 00 specify the 16-bit data size in the order of lowbyte highbyte. for example a two-byte data size would be specifed as 02 00. adns-5700- xxxx will not provide more bytes than the number requested in the command, but it will only supply up to a maximum of 8 bytes at a time. the adns-5700- xxxx will re-send the last packet if the transfer is not acknowledged properly.
22 usb command details usb_reset d+/d- low for an extended period usb spec: a device may reset after seeing an se0 for more than 18.7 us, and defi nitely after 10ms. notes: after power up and prior to reset, the device will not respond to any usb commands. after the device has been given a usb reset, the devices address will be reset to zero and the device will be in the default state. the chip will default to report protocol and any pending output will be fl ushed. all registers will be reset to a state that matches power-on-reset with the following exceptions: usb state register will be default instead of attached. usb_suspend idle state for an extended period usb spec: a device may suspend after seeing an idle for more than 3ms, and defi nitely after 10ms. notes: the chip will take a minimum of 5ms to start suspend, though will defi nitely start after 6ms. the chip may fi nish the current frame if necessary before stopping the clock. thus, an additional frame time may be used to reach suspend mode. usb_resume non-idle state usb spec: remote resume signalling from a device must be between 1ms and 15ms. the host is required to send resume signaling for 20ms plus 10ms of resume recovery time in which it does not access any devices. this allows devices enough time to wake back up. notes: the chip can cause a resume if remote wakeup is enabled and a button has been pressed. remote resume signalling from the chip will last 11.45ms to 12.45ms. get_status_device 80 00 00 00 00 00 02 00 returns: xx yy xx[0] = self powered xx[1] = remote wakeup xx[7:2] = 0 yy = 00 (reserved) default: accept (undefi ned in usb spec) addressed: accept confi gured: accept notes: use set_feature_device/clear_feature_device to set/clear remote wakeup. get_status_interface 81 00 00 00 00 00 02 00 returns: 00 00 default: stall (undefi ned in usb spec) addressed: stall confi gured: accept notes: both return bytes are reserved and currently 00.
23 get_status_endpt0 82 00 00 00 xx 00 02 00 82 00 00 00 00 00 02 00 82 00 00 00 80 00 02 00 xx = 00 = endpt0 out xx = 80 = endpt0 in returns: xx yy xx[0] = halt xx[7:1] = 0 yy = 00 (reserved) default: accept (undefi ned in usb spec) addressed: accept confi gured: accept notes: use set_feature_endpt0/clear_feature_endpt0 to (try to) set/clear halt bit. according to usb, it is neither required or recommended that the halt feature be implemented for the default control pipe. since a new setup command will clear any endpt0 halt bit, it is impossible to tell if there really is a halt bit. get_status_endpt1 82 00 00 00 81 00 02 00 returns: xx yy xx[0] = halt xx[7:1] = 0 yy = 00 (reserved) default: stall (undefi ned in usb spec) addressed: stall confi gured: accept notes: use set_feature_endpt1/clear_feature_endpt1 to set/clear halt bit. get_confi guration 80 08 00 00 00 00 01 00 returns: xx xx = confi g value default: accept (undefi ned in usb spec) C returns 00 addressed: accept C returns 00 confi gured: accept C returns 01 notes: use set_confi guration to change. get_interface 81 0a 00 00 00 00 01 00 returns: 00 default: stall (undefi ned in usb spec) addressed: stall confi gured: accept C returns 00 notes: command has no alternate interfaces, so only valid value is 00
24 get_protocol a1 03 00 00 00 00 01 00 returns: xx xx = 00 = boot protocol xx = 01 = report protocol default: accept addressed: accept confi gured: accept notes: defaults to report protocol after usb reset. use set_protocol to change. get_desc_device 80 06 00 01 00 00 nn 00 80 06 00 01 00 00 12 00 returns: 12 01 00 02 00 00 00 08 vv vv pp pp dd dd mm pp ss 01 vv vv = vendor id pp pp = product id (vendor specifi ed) dd dd = device id (vendor specifi ed) (bcd rev_id byte) mm = imanufacturer pp = iproduct ss = iserialnumber (00 - no string) default: accept addressed: accept confi gured: accept get_desc_string will return stall if manufac turer string is queried when imanufacturer = 0x00.
25 get_desc_confi g 80 06 00 02 00 00 nn 00 80 06 00 02 00 00 22 00 returns: 09 02 22 00 01 01 00 a0 32 09 04 00 00 01 03 01 02 00 09 21 11 01 00 01 22 rr 00 07 05 81 03 05 00 0a rr = hid report descriptor length 47 = 12 bit motion reporting with z-wheel: 09 02 22 00 01 01 00 a0 32 09 04 00 00 01 03 01 02 00 09 21 11 01 00 01 22 3d 00 07 05 81 03 04 00 0a // confi g descriptor | 09 // blength | 02 // bdescriptortype | 22 // wtotallength (34 decimal) | 00 // high byte of wtotallength | 01 // bnuminterfaces | 01 // bconfi gurationvalue | 00 // iconfi guration | a0 // bmattributes (bus powered/remote wakeup) | 32 // maxpower (in 100ma in 2ma units) // interface descriptor | 09 // blength | 04 // bdescriptortype | 00 // binterfacenumber | 00 // balternatesetting | 01 // bnumendpoints | 03 // binterfaceclass (hid class) | 01 // binterfacesubclass | 02 // binterfaceprotocol | 00 // iinterface // hid descriptor | 09 // blength | 21 // bdescriptortype | 11 // bcdhid ( hid release ##.##; hid 1.11 compliant ) | 01 // | 00 // bcountry | 01 // bavailable | 22 // btype | 34 // wlength (length of hid report below) | 00 // // endpoint descriptor | 07 // blength | 05 // bdescriptortype | 81 // bendpointaddress (in & #=1) | 03 // bmattributes (interrupt) | 05 // wmaxpacketsize | 00 // 12bit 0x06 | 0a // binterval (10ms)
26 default: accept addressed: accept confi gured: accept notes: this is the concatenation of 4 descriptors: confi guration interface hid endpt get_desc_string 80 06 xx 03 00 00 nn 00 xx= 00 language string 01 manufacturer string 02 product string returns: ss 03 ?unicode string ss = string descriptor length these values are determined by jumper confi guration on page xx: for xx=00: 04 03 09 04 // language id for xx=01: return stall if manufacturer string is queried when imanufacturer = 0x00. see get_desc_device section for xx=02: 24 03 55 00 53 00 42 00 // usb 20 00 4f 00 70 00 74 00 // opt 69 00 63 00 61 00 6c 00 // ical 20 00 4d 00 6f 00 75 00 // mou 73 00 65 00 // se default: accept addressed: accept confi gured: accept notes: a request for any other string will stall. get_desc_hid 81 06 00 21 00 00 09 00 returns: 09 21 11 01 00 01 22 rr 00 rr = hid report descriptor length 47 = 12 bit motion default: accept addressed: accept confi gured: accept
27 get_desc_hid_report 81 06 00 22 00 00 nn 00 returns: this returns a report descriptor that describes how many buttons and x, y, z data. these values are determined by jumper confi guration see table on page 4: with tilt wheel and 12bit reporting: 05 01 09 02 a1 01 09 01 a1 00 05 09 19 01 29 05 15 00 25 01 75 01 95 05 81 02 75 03 95 01 81 01 05 01 09 30 09 31 16 01 f8 26 ff 07 75 0c 95 02 81 06 09 38 15 81 25 7f 75 08 95 01 81 06 05 0c 0a 38 02 81 06 c0 c0 // hid report | 05 01 // usage_page (generic desktop) | 09 02 // usage (mouse) | a1 01 // collection (application) | 09 01 // usage (pointer) | a1 00 // collection (physical) | 05 09 // usage_page (button) | 19 01 // usage_minimum (button 1) | 29 05 // usage_maximum (button #) | 15 00 // logical_minimum (0) | 25 01 // logical_maximum (1) | 75 01 // report_size (1) | 95 05 // report_count (button #) | 81 02 // input (data,var,abs) | 75 03 // report_size (8 - button #) | 95 01 // report_count (1) | 81 01 // input (cnst,ary,abs) | 05 01 // usage_page (generic desktop) | 09 30 // usage (x) | 09 31 // usage (y) | 16 01 f8 // logical_minimum (-127) | 26 ff 07 // logical_ maximum (127) | 75 0c // report_size (8) | 95 01 // report_count (3) | 81 06 // input (data,var,rel) | 09 38 // usage (zwheel) | 15 81 // logical_minimum (-127) | 25 7f // logical_ maximum (127) | 75 08 // report_size (8) | 95 01 // report_count (1) | 81 06 // input (data,var,rel) | 05 0c // usage_page (consumer) | 0a 38 02 // usage (ac pan) | 81 06 // input (data,var,rel) | c0 // end_collection | c0 // end_collection
28 with without tilt wheel and 12bit reporting: 05 01 09 02 a1 01 09 01 a1 00 05 09 19 01 29 05 15 00 25 01 75 01 95 05 81 02 75 03 95 01 81 01 05 01 09 30 09 31 16 01 f8 26 ff 07 75 0c 95 02 81 06 09 38 15 81 25 7f 75 08 95 01 81 06 c0 c0 // hid report | 05 01 // usage_page (generic desktop) | 09 02 // usage (mouse) | a1 01 // collection (application) | 09 01 // usage (pointer) | a1 00 // collection (physical) | 05 09 // usage_page (button) | 19 01 // usage_minimum (button 1) | 29 05 // usage_maximum (button #) | 15 00 // logical_minimum (0) | 25 01 // logical_maximum (1) | 75 01 // report_size (1) | 95 05 // report_count (button #) | 81 02 // input (data,var,abs) | 75 03 // report_size (8 - button #) | 95 01 // report_count (1) | 81 01 // input (cnst,ary,abs) | 05 01 // usage_page (generic desktop) | 09 30 // usage (x) | 09 31 // usage (y) | 16 01 f8 // logical_minimum (-127) | 26 ff 07 // logical_ maximum (127) | 75 0c // report_size (8) | 95 01 // report_count (3) | 81 06 // input (data,var,rel) | 09 38 // usage (zwheel) | 15 81 // logical_minimum (-127) | 25 7f // logical_ maximum (127) | 75 08 // report_size (8) | 95 01 // report_count (1) | 81 06 // input (data,var,rel) | c0 // end_collection | c0 // end_collection default: accept addressed: accept confi gured: accept notes: the length of this report is needed in the hid descriptor.
29 get_hid_input a1 01 00 01 00 00 nn 00 nn = 06 (with tilt wheel and 12 bit motion reporting) nn = 05 (without tilt wheel and 12 bit reporting) returns: bb xx yy zz tw (tilt wheel) or bb xx yy zz (z-wheel) or bb xx yy (if no z-wheel present) bb = button byte xx = x motion byte yy = y motion byte zz = z motion byte tw = tilt wheel byte default: stall addressed: stall confi gured: accept notes: if the device is confi gured, it will always respond with a report for this command, even if no motion or button changes have occurred. in this case, it would report 00 for motion and simply report the current button state. if a report is pending on endpt1, the data there will be reported and the report on endpt1 cleared. the mouse will only create new button/motion packets when it is in the confi gured state see usb byte format end of this section for more detail get_idle a1 02 xx 00 00 00 01 00 xx = 00 all reports xx = 01 first report returns: rr rr = rate in multiples of 4ms default: accept addressed: accept confi gured: accept notes: the third byte of the command is to select the report id. there is only one for the mouse -- so, using 00 or 01 will work. see also set_idle. get_vendor_test c0 01 00 00 xx 00 01 00 ii = ignore xx = address of register to read returns: rr (depends on register read) default: accept addressed: accept confi gured: accept notes: address range (xx) is datasheet register range
30 set_address 00 05 xx 00 00 00 00 00 xx = new device address, from 00 to 7f default: accept addressed: accept confi gured: accept (undefi ned in usb spec) chip gets new address, but stays in confi gured mode. notes: if device is not confi gured, the device will be given the new address and put in the addressed state (or default if new address=00). if the device is already confi gured, the device will be given the new address state and remain confi gured. set_confi guration 00 09 xx 00 00 00 00 00 xx = 00 = not confi gured xx = 01 = confi gured default: accept (undefi ned in usb spec) addressed: accept confi gured: accept notes: invalid confi g values will cause stall. chip will stall invalid value in confi gured mode, and leave device in old (confi gured) mode. set_interface 01 0b 00 00 00 00 00 00 default: stall (undefi ned in usb spec) addressed: stall confi gured: accept notes: mouse has only one valid interface (00) and alternate setting (00). invalid values will cause stall. chip retains previous (valid) interface state after executing this command in confi gured mode even if invalid values are given and command was stalled. set_protocol 21 0b xx 00 00 00 00 00 xx = 00 = boot protocol xx = 01 = report protocol default: accept (not in usb spec) addressed: accept (not in usb spec) confi gured: accept notes: 3 byte data packets will be reported in boot mode. these bytes are button, xx data, and yy data. tilt wheel botton 7,8 will not be reported set_feature_device 00 03 01 00 00 00 00 00 default: accept (undefi ned in usb spec) addressed: accept confi gured: accept notes: this sets the remote wakeup bit.
31 set_feature_endpt0 02 03 00 00 xx 00 00 00 02 03 00 00 00 00 00 00 02 03 00 00 80 00 00 00 xx = 00 = endpt0 out xx = 80 = endpt0 in default: stall (undefi ned in usb spec) addressed: stall confi gured: stall notes: this (tries to) sets the halt bit. the chip always stalls the status stage for this command. the chip never reports the halt bit set for endpt0 with the get_status_endpt0 command, as any new setup command will clear endpt0 stall. set_feature_endpt1 02 03 00 00 81 00 00 00 default: stall (undefi ned in usb spec) addressed: stall confi gured: accept notes: sets the halt bit for endpt1. clear_feature_device 00 01 01 00 00 00 00 00 default: accept (undefi ned in usb spec) addressed: accept confi gured: accept notes: this clears the remote wakeup bit. clear_feature_endpt0 02 01 00 00 xx 00 00 00 02 01 00 00 00 00 00 00 02 01 00 00 80 00 00 00 xx = 00 = endpt0 out xx = 80 = endpt0 in default: accept (undefi ned in usb spec) addressed: accept confi gured: accept notes: the chip does not stall like it does for set_feature_endpt0. clear_feature_endpt1 02 01 00 00 81 00 00 00 default: stall (undefi ned in usb spec) addressed: stall confi gured: accept notes: see set_feature_endpt1.
32 set_idle 21 0a xx rr 00 00 00 00 xx = 00 all reports xx = 01 first report rr = rate in multiples of 4ms default: accept addressed: accept confi gured: accept notes: the third byte of the command is to select the report id. there is only one for the mouse C so, using either 00 or 01 will work. the fourth byte of the command sets the rate in multiples of 4ms. the initial value for mice will be x00 which means infi nite C that is packets only come out when there is a change in data. data will only be allowed to come out when the device is confi gured. however, the chip will accept the command in default or addressed mode and use that value when the device is later confi gured. set_vendor_test 40 01 00 00 xx yy 00 00 xx = address yy = data default: accept addressed: accept confi gured: accept notes: address range for xx should be 0x00 to 0x3f. addresses above this are reserved for possible future use. see also get_vendor_test.
33 poll_endpt1 returns: bb xx yy zz tw bb = button byte xx = x motion byte yy = y motion byte zz = z motion byte (if z-wheel) tw = tilt wheel byte default: ignore request addressed: ignore request confi gured: accept (nak if no data; send packet if available) notes: see also get_hid_input. endpt will only stall if halt bit is set by set_feature_endpt1. details of data packet are below endpt1 should be polled at least every 10 frames (ms). it is typically polled every 8 frames on windows machines. for internal testing, endpt1 can be continuously polled if desired. the chip will not generate any report packets unless in the confi gured state. if endpt1 is currently empty, any motion or button change will be loaded into the endpt1 buff ers. once the endpt1 buff ers are full, any further motion events will get accumulated. when the endpt1 buff ers are later polled and emptied, the current accumulated x/y/z values will be loaded into the endpt1 buff ers. after transferring their data, the accumula- tion registers are reset so they are ready to start accumulating new motion events. button information is handled a bit diff erently. if the endpt1 buff ers are empty, and a button change event occurs, the new button state is put into the endpt1 buff ers. at the same time, the button state that is put in endpt1 is copied for later use. while endpt1 is full, changes in button state are essentially ignored. when endpt1 is emptied, if the current button state is diff erent than that which was last loaded into endpt1, then the new state will be loaded and a new copy saved. basically, the button state that is loaded into endpt1 is always the current button state at that point in time. it should also be noted that there is hardware on the chip to help de-bounce the buttons. special note on wlength: the wlength paramater in commands specifi es the maximum number of bytes a device should send back. the commands listed below are not able to handle a wlength of 0 cor- rectly. get_status_device get_status_interface get_status_endpt0 get_status_endpt1 get_confi guration get_interface this chip will send one byte of data rather than none when wlength=0 is requested for the above commands.
34 usb data packet format of mouse with tilt wheel bit76543210 byte 100000 b3(mb) b2(rb) b1(lb) byte 2x7x6x5x4x3x2x1x0 byte 3 y3 y2 y1 y0 x11 x10 x9 x8 byte 4 y11 y10 y9 y8 y7 y6 y5 y4 byte 5z7z6z5z4z3z2z1z0 byte 6 tw7 tw6 tw5 tw4 tw3 tw2 tw1 tw0 usb data packet format of mouse without tilt wheel bit76543210 byte 100000 b3(mb) b2(rb) b1(lb) byte 2x7x6x5x4x3x2x1x0 byte 3 y3 y2 y1 y0 x11 x10 x9 x8 byte 4 y11 y10 y9 y8 y7 y6 y5 y4 byte 5z7z6z5z4z3z2z1z0 byte 600000000 usb data packet format of 5 button mouse bit76543210 byte 1000b5b4 b3(mb) b2(rb) b1(lb) byte 2x7x6x5x4x3x2x1x0 byte 3 y3 y2 y1 y0 x11 x10 x9 x8 byte 4 y11 y10 y9 y8 y7 y6 y5 y4 byte 5z7z6z5z4z3z2z1z0 byte 600000000
35 registers the sensor can be programmed through registers, via the usb port, and confi guration and motion data can be read from these registers. certain registers must be enabled after power up but before fi rst read or write to that reg- ister. the registers will be disabled by vdd going low or sending a usb reset command. address register 0x00 product_id 0x01 revision_id 0x02 mousestat 0x03 delta_x_l 0x04 delta_y_l 0x05 delta_xy_h 0x06 squal 0x07 shut_hi address register 0x08 shut_low 0x09 pix_max 0x0a pix_accum 0x0b pix_min 0x0c pix_grabber 0x0d dz 0x0e-3f reserved 0x40 invrevid product_id address: 0x00 access: read reset value: 0x27 bit 7 6 5 4 3 2 1 0 field pid 7 pid 6 pid 5 pid 4 pid 3 pid 2 pid 1 pid 0 data type: eight bit number with the product identifi er. usage: the value in this register does not change; it can be used to verify that the sensor communications link is ok. revision_id address: 0x01 access: read reset value: 0x01 bit 7 6 5 4 3 2 1 0 field rid 7 rid 6 rid 5 rid 4 rid 3 rid 2 rid 1 rid 0 data type: eight bit number with current revision of the ic. usage: this register contains the ic revision. it is subject to change when new ic versions are released.
36 mousestat address: 0x02 access: read reset value: undefi ned bit 7 6 5 4 3 2 1 0 field mot reserved reserved but 5 but 4 but 3 but 2 but 1 data type: bit fi eld usage: a 1 in the motion bit indicates that the usb endpoint has valid data. this regist er is included for test purposes only. for navigation use, use the usb hid defi ned commands. the button status bits reported are for the de- bounce signals. field name description mot for internal test purposes only reserved reserved but 5 reports the status of b5 0 = pin at logic 1 (vdd3) 1 = pin at logic 0 (gnd) but 4 reports the status of b4 0 = pin at logic 1 (vdd3) 1 = pin at logic 0 (gnd) but 3 reports the status of b3 0 = pin at logic 1 (vdd3) 1 = pin at logic 0 (gnd) but 2 reports the status of b2 0 = pin at logic 1 (vdd3) 1 = pin at logic 0 (gnd) but 1 reports the status of b1 0 = pin at logic 1 (vdd3) 1 = pin at logic 0 (gnd)
37 delta_x_l address: 0x03 access: read reset value: 0x00 bit 7 6 5 4 3 2 1 0 field x 7 x 6 x 5 x 4 x 3 x 2 x 1 x 0 data type: bit fi eld usage: the value in this register refl ects the last usb delta x (lower 8 bits) data output or data queued for output. this register is included for test purposes only. for navigation use, use the hid defi ned commands. data is 2s complement. absolute value is determined by the currently set resolution. register 0x03 must be read before register 0x04 (delta_y_l) and 0x05 (delta_xy_h) delta_y_l address: 0x04 access: read reset value: 0x00 bit 7 6 5 4 3 2 1 0 field y 7 y 6 y 5 y 4 y 3 y 2 y 1 y 0 data type: bit fi eld usage: the value in this register refl ects the last usb delta y (lower 8 bits) data output or data queued for output. this register is included for test purposes only. register 0x03 should be read before register 0x04 (delta_y_l) and 0x05 (delta_xy_h), else delta_y_l will return 0. for navigation use, use the hid defi ned commands. data is 2s complement. absolute value is determined by the currently set resolution. delta_xy_h address: 0x05 access: read reset value: 0x00 bit 7 6 5 4 3 2 1 0 field x 11 x 10 x 9 x 8 y 11 y 10 y 9 y 8 data type: bit fi eld usage: the value in this register refl ects the last usb delta x and y (upper 4 bits) data output or data queued for output. this register is included for test purposes only. register 0x03 should be read before register 0x04 (delta_y_l) and 0x05 (delta_xy_h), else delta_xy_h will return 0. for navigation use, use the hid defi ned commands. data is 2s complement. absolute value is determined by the currently set resolution.
38 squal address: 0x06 access: read reset value: 0x00 bit 7 6 5 4 3 2 1 0 field sq 7 sq 6 sq 5 sq 4 sq 3 sq 2 sq 1 sq 0 data type: eight bit number. usage: squal is a measure of the number of features visible by the sensor in the current frame. the maximum value is 128. since small changes in the current frame can result in changes in squal, slight variations in squal on one surface is expected. shut_hi address: 0x07 access: read reset value: 0x00 bit 7 6 5 4 3 2 1 0 field s 15 s 14 s 13 s 12 s 11 s 10 s 19 s 18 data type: eight bit number. usage: the combination of shut_hi and shut_low is a 16-bit number. this is the number of clocks the shutter was open for the last image taken. the units are in main clocks ticks (nominally 24mhz). to avoid split read issues, read shut_hi fi rst. shut_low address: 0x08 access: read reset value: 0x64 bit 7 6 5 4 3 2 1 0 field s 7 s 6 s 5 s 4 s 3 s 2 s 1 s 0 data type: eight bit number. usage: the combination of shut_hi and shut_low is a 16-bit number. this is the number of clocks the shutter was open for the last image taken. the units are in main clocks ticks (nominally 24mhz). to avoid split read issues, read shut_hi fi rst (0x06).
39 pix_accum address: 0x0a access: read reset value: 0x00 bit 7 6 5 4 3 2 1 0 field ac 7 ac 6 ac 5 ac 4 ac 3 ac 2 ac 1 ac 0 data type: eight bit number. usage: this is the accumulated pixel value from the last image taken. for the 19x19 raw image only the 8 most interest- ing bits are reported ([15:8]). to get the true average pixel value, divide this register value by 1.41. pix_max address: 0x09 access: read reset value: 0x00 bit 7 6 5 4 3 2 1 0 field 0 mx 6 mx 5 mx 4 mx 3 mx 2 mx 1 mx 0 data type: eight bit number. usage: this is the maximum pixel value from the last image taken. pix_min address: 0x0b access: read reset value: 0x7f bit 7 6 5 4 3 2 1 0 field 0 mn 6 mn 5 mn 4 mn 3 mn 2 mn 1 mn 0 data type: eight bit number. usage: this is the minimum pixel value from the last image taken. pix_grab address: 0x0c access: read reset value: 0x00 bit 7 6 5 4 3 2 1 0 field valid pg 6 pg 5 pg 4 pg 3 pg 2 pg 1 pg 0 data type: eight bit number. usage: the pixel grabber captures 1 pixel per frame. if ther e is a valid pixel in the grabber when this is read, the msb will be set, an internal counter will incremented to captured the next pixel and the grabber will be armed to capture the next pixel. it will take 361 reads to upload the completed image. any write to this register will reset and arm the grabber to grab pixel 0 on the next image. see pixel array num- bering in figure 19.
40 rb l b t op x ra y v iew of mo u se pos itive x p o s i t i v e y 7 4 3 1 2 1 8 1 7 1 6 1 5 1 4 1 3 11 1 0 9 8 6 5 2 1 pixel address map (looking through the sensor at the surface) 0 19 38 57 76 95 114 133 152 171 190 209 228 247 266 285 304 323 342 1 20 39 58 77 96 115 134 153 172 191 210 229 248 267 286 305 324 343 2 21 40 59 78 97 116 135 154 173 192 211 230 249 268 287 306 325 344 3 22 41 60 79 98 117 136 155 174 193 212 231 250 269 288 307 326 345 4 23 42 61 80 99 118 137 156 175 194 213 232 251 270 289 308 327 346 5 24 43 62 81 100 119 138 157 176 195 214 233 252 271 290 309 328 347 6 25 44 63 82 101 120 139 158 177 196 215 234 253 272 291 310 329 348 7 26 45 64 83 102 121 140 159 178 197 216 235 254 273 292 311 330 349 8 27 46 65 84 103 122 141 160 179 198 217 236 255 274 293 312 331 350 9 28 47 66 85 104 123 142 161 180 199 218 237 256 275 294 313 332 351 10 29 48 67 86 105 124 143 162 181 200 219 238 257 276 295 314 333 352 11 30 49 68 87 106 125 144 163 182 201 220 239 258 277 296 315 334 353 12 31 50 69 88 107 126 145 164 183 202 221 240 259 278 297 316 335 354 13 32 51 70 89 108 127 146 165 184 203 222 241 260 279 298 317 336 355 14 33 52 71 90 109 128 147 166 185 204 223 242 261 280 299 318 337 356 15 34 53 72 91 110 129 148 167 186 205 224 243 262 281 300 319 338 357 16 35 54 73 92 111 130 149 168 187 206 225 244 263 282 301 320 339 358 17 36 55 74 93 112 131 150 169 188 207 226 245 264 283 302 321 340 359 18 37 56 75 94 113 132 151 170 189 208 227 246 265 284 303 322 341 360 figure 19. pixel map the fi gure above shows the readout order of the array. rows are read top to bottom and columns are from right to left. dz address: 0x0d access: read reset value: 0x00 bit 7 6 5 4 3 2 1 0 field z 7 z 6 z 5 z 4 z 3 z 2 z 1 z 0 data type: bit fi eld usage: if mouse is confi gured to contain a z-wheel, this register contains the z-wheel count. range is from C127 to 127 decimal. reserved address: 0x0e C 0x3f
ic register state after reset (power up) address register default value meaning 0x00 product_id 0x27 product id = 27 (fixed value) 0x01 revision_id 0x01 revision of ic (fixed value). (for each device design revision). 0x02 mousestat C 0x03 delta_x_l 0x00 0x04 delta_y_l 0x00 0x05 delta_xy_h 0x00 0x06 squal 0x00 0x07 shut_hi 0x00 0x08 shut_low 0x64 0x09 pix_max 0x00 0x0a pix_accum 0x00 0x0b pix_min 0x00 0x0c pix_grabber 0x00 0x0d dz 0x00 0x0e-3f reserved C 0x40 inverserevesion id 0xfe invrevid address: 0x040 access: read reset value: 0xfe bit 7 6 5 4 3 2 1 0 field rrid 7 rrid 6 rrid 5 rrid 4 rrid 3 rrid 2 rrid 1 rrid 0 data type: eight bit number with current revision of the ic. usage: contains the inverse of the revision id which is located in register 0x01. for product information and a complete list of distributors, please go to our web site: www.avagotech.com avago, avago technologies, and the a logo are trademarks of avago technologies in the united states and other countries. data subject to change. copyright ? 2005-2011 avago technologies. all rights reserved. av02-1655en - november 1, 2011

▲Up To Search▲

Price & Availability of ADNS-5700-H5MD

	To Download ADNS-5700-H5MD Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .