infobot has quit [Remote host closed the connection]
infobot has joined #neo900
houkime has quit [Ping timeout: 260 seconds]
_Chris_ has quit [Remote host closed the connection]
infobot has quit [Ping timeout: 248 seconds]
andi- has quit [Remote host closed the connection]
andi- has joined #neo900
infobot has joined #neo900
preview has quit [Quit: preview]
preview has joined #neo900
pagurus` has quit [Ping timeout: 246 seconds]
pagurus has joined #neo900
preview_ has joined #neo900
preview has quit [Read error: No route to host]
preview_ has quit [Client Quit]
preview has joined #neo900
preview has quit [Ping timeout: 264 seconds]
him-cesjf has joined #neo900
himcesjf_ has quit [Ping timeout: 268 seconds]
_whitelogger has joined #neo900
_whitelogger has joined #neo900
Pali has joined #neo900
Pali has quit [Ping timeout: 268 seconds]
Kabouik has joined #neo900
preview has joined #neo900
_Chris_ has joined #neo900
houkime has joined #neo900
<houkime>
Joerg-Neo900, I couldn't find any details on proximity sensor for stylus detection in whitepapers.
<houkime>
Joerg-Neo900, and in stuff also for that matter
<houkime>
Joerg-Neo900, what i want to know is allowed wavelength range, power consumption and calculations for aperture diameter in LOWER.
<houkime>
the position of the stylus bay i can calculate from the wpwrak's scans myself.
<houkime>
Joerg-Neo900, i have little idea now about bay wall reflection spectrum.
<DocScrutinizer51>
houkime: I'm sorry for missing details in whitepaper. Wavelength is irrelevant, Appertures (plural) size depends on sensor design, the idea I tried to
<houkime>
can't one have only one aperture (via hanging sensor from the lower side of the UPPER?)
<DocScrutinizer51>
sketch yesterday is: sensor sends throuch one apperture and receives through a second. Both appertures get "shu" by stylus
<DocScrutinizer51>
shut
<houkime>
ok, so two apertures are for led and detector itself. got it
<DocScrutinizer51>
purpose of proto_v2 is (among other) to verify functionality of this design
<houkime>
so what we are looking for here is very narrow angle for emitting LED, almost a laser-like thing, Otherwise it will illuminate LOWER and the integrated reflection power from LOWER will be much greater than from a tiny aperture.
<houkime>
or rather, one should look at detection and LED emission cones, make sure that they intersect well at the depth of the bay
<houkime>
and then make an artistic orifice based on these cones in LOWER
Pali has joined #neo900
<houkime>
which might turn out to be either 2 separate orifices or one merged.
wpwrak has quit [Ping timeout: 272 seconds]
Pali has quit [Ping timeout: 268 seconds]
_Chris_ has quit [Ping timeout: 246 seconds]
yanu has quit [Ping timeout: 268 seconds]
<houkime>
TMD49033 looks nice. It is multi-wavelength and can detect color. Same footprint as other TMDs which we already have. 1.8v all across.
<houkime>
but it doesn't have a datasheet. though knowing ams it is probably included in TMD49031 datasheet or sth
<houkime>
checking
<Joerg-Neo900>
houkime: the sensor was planned to get mounted onto S2 looking *down*ward through apperture un PCB S1-S2
<Joerg-Neo900>
the idea is to have receiver optically separated from LED when some object sits on surface S1
<houkime>
Joerg-Neo900, separation is not necessary since this kind of sensors can measure yield and compare it with reference
<houkime>
basically it measures distance by comparing integrated reflection
<Joerg-Neo900>
go ahead as you think works best
<Joerg-Neo900>
just keep in mind this sensor is always-on and thus will have massive impact on battery standby time
<Joerg-Neo900>
it should have active supply current <1mA
<Joerg-Neo900>
ideally <<1mA
<Joerg-Neo900>
average
<Joerg-Neo900>
if it doesn't "out of the box", you might need to define a sort of "polling" scheme driven by CPU that enables sensor every 5s for 0.01s or whatever
<houkime>
Joerg-Neo900, the number of pulses per measuring act is programmable and less pulses are needed for smaller distances
<houkime>
Joerg-Neo900, they don't need polling because they have a configurable interrupt pin
<houkime>
Joerg-Neo900, though to configure it one probably needs to calibrate it and then write needed values into i2c registers
<Joerg-Neo900>
as I said: >>if it doesn't "out of the box", you might need ...<
<houkime>
Joerg-Neo900, well, it technically doesn't work out of the box)) it needs calibration ad experiments.
<Joerg-Neo900>
initializing is "OOTB"
<houkime>
ok
<Joerg-Neo900>
just needs to run autonomously after that, with a supply current average <<1mA
<Joerg-Neo900>
funny little detail that even works for N900: insering a lamba/4 antenna into stylus bay will massively improve FM TX ;-) the antenna is parallel to stylus and would get coupled to such l/4
<Joerg-Neo900>
re stylus sensor, I also pondered mechanical switch (EEEWW!) and even capacitive "touch" sensor directly to a GPIO pin that senses statical charge movement in stylus plastic and change in capacitor value of the sensor pad to verify status inserted/removed
_Chris_ has joined #neo900
<houkime>
alas. In stock on Digikey but no datasheet on the ams website after all. Such a mess.
<houkime>
going to next candidate.
<DocScrutinizer51>
bydy, its a PITA
atk has quit [Ping timeout: 250 seconds]
<DocScrutinizer51>
btdt even
atk has joined #neo900
enyc has quit [Ping timeout: 250 seconds]
enyc has joined #neo900
preview has quit [Ping timeout: 264 seconds]
preview has joined #neo900
<houkime>
datasheet is present though on alldatasheet.com
<houkime>
need to check remaining other candidates regardless
<houkime>
though all these sensors are so expensive... 5-6 dollars for a proximity thing. oh man...
<Joerg-Neo900>
prohibitive pricing
<houkime>
it might be even better idea to have led and sensor separate at this point and sensor just have a programmable interrupt on too much/too little light.
yanu has joined #neo900
<Joerg-Neo900>
rule of thumb: sourcing * 3, so almost 20$ for stylus sensor isn't a selling point
<Joerg-Neo900>
those reflexive lightbar sensors were always a PITA
<Joerg-Neo900>
prolly there are more sensor concepts where LED is separate component
<Joerg-Neo900>
I see soap dispensers with lightbar, sold for like 8 bucks
<houkime>
due to small distance needed in neo900 led could be so weak that it can be just always on wherever phone is on.
<houkime>
so no flashing circuitry or whatever.
<DocScrutinizer51>
duh, that would cause at least 0.5 to 1mA
<DocScrutinizer51>
and sensing unmodulated light level is a nogo regarding noise rejection and reliability
<Joerg-Neo900>
if you really wanna go that route, you need a LED controlled by a CPU GPIO to pulse it with a duty cycle of <0.001% and detect the pulses on a A/D converted photodiode. Nasty but feasible
clapont has joined #neo900
clapont has quit [Client Quit]
<Joerg-Neo900>
even I would opt against that stylus detection feature based on this concept. But in the end it's your design now
clapont has joined #neo900
<Joerg-Neo900>
"even I" since I'm notorious for my featuritis
<clapont>
hi everyone
<Joerg-Neo900>
hi
Pali has joined #neo900
wpwrak has joined #neo900
<houkime>
SI1151-AB00-GM looks kinda nice compared to ams stuff.
<houkime>
1.8 bucks
<houkime>
no integrated LED but LED driver instead
<houkime>
interrupt pin, all things programmable
<houkime>
1.8v all across (excluding LED which has separate power) possible
<houkime>
and the LED can be basically just any LED under 5.5v
<houkime>
both visible and IR
<houkime>
maximum sensitivity in blue area
<houkime>
so it is bring_your_own_LED proximity sensor thing