battery monitor, wifi SignalStrength
in [Compact Framework]
|
Prev: Changing File Attributes in CF
Next: System_SR_ES.CAB
From: Dani on 19 Feb 2010 04:50 hello, i need to read this information and i resolve this with opennetcf 2.3. I read battery life with batteryMonitor trigger and wifi SignalStrength with a timer tick event, but this is very slow and takes 2 seconds to return the value. Have another solutions ? Windows Mobile 6 classic or pro, C# language and CF 2.0 with VS 2005. Thanks. Dani.
From: "Paul G. Tobey [eMVP]" paultobey _AT_ earthlink _DOT_ on 22 Feb 2010 22:00 Well, no, not unless you can rewrite the WiFi driver! It's not like OpenNETCF is sitting around killing time. Trace the calls into the OpenNETCF source, if you have it and check which of the NDIS/WZC calls is taking most of the time and we might be able to suggest something to help a bit, but the interface was never designed to give real-time signal strength, so OpenNETCF can't make it do so. Paul T. "Dani" <nospam(a)tin.it> wrote in message news:4b7e5f01$0$1121$4fafbaef(a)reader3.news.tin.it... > hello, > i need to read this information and i resolve this with opennetcf 2.3. > I read battery life with batteryMonitor trigger and wifi SignalStrength > with a timer tick event, but this is very slow and takes 2 seconds to > return the value. Have another solutions ? > > Windows Mobile 6 classic or pro, C# language and CF 2.0 with VS 2005. > > Thanks. > > Dani.
From: Dani on 23 Feb 2010 02:53 Paul G. Tobey [eMVP] ha scritto: > Well, no, not unless you can rewrite the WiFi driver! It's not like > OpenNETCF is sitting around killing time. Trace the calls into the > OpenNETCF source, if you have it and check which of the NDIS/WZC calls is > taking most of the time and we might be able to suggest something to help a > bit, but the interface was never designed to give real-time signal strength, > so OpenNETCF can't make it do so. > Nooooooooooooooooooooooo.... This is very depressing ! The interface of the ipaq 214 is VZC compatible, if i try to use it directly have better chance to reduce time to give signal strength? Any other solution is appreciated. Dani.
From: Chris Tacke, MVP on 23 Feb 2010 13:32 I think I'm a bit confused as to why you would need that data faster than 2 seconds anyway. What could you possibly be doing that you need signal strength faser than that? I don't think there's any way to get it faster - we simply call into WZC, and we return the data when WZC gives it to us. We're not doing something like calling Thread.Sleep(2000) or anything. -- Chris Tacke, Embedded MVP OpenNETCF Consulting Giving back to the embedded community http://community.OpenNETCF.com "Dani" <nospam(a)tin.it> wrote in message news:4b838966$0$1121$4fafbaef(a)reader3.news.tin.it... > Paul G. Tobey [eMVP] ha scritto: >> Well, no, not unless you can rewrite the WiFi driver! It's not like >> OpenNETCF is sitting around killing time. Trace the calls into the >> OpenNETCF source, if you have it and check which of the NDIS/WZC calls is >> taking most of the time and we might be able to suggest something to help >> a bit, but the interface was never designed to give real-time signal >> strength, so OpenNETCF can't make it do so. >> > > Nooooooooooooooooooooooo.... This is very depressing ! The interface of > the ipaq 214 is VZC compatible, if i try to use it directly have better > chance to reduce time to give signal strength? > Any other solution is appreciated. > > Dani.
From: Paul G. Tobey [eMVP] paultobey _at_ earthlink _dot_ on 23 Feb 2010 14:21
If *that* is depressing, you'd better get on medication now -- you're going to need it! Try doing what you want to do in native C++. It's possible that some call or calls is being made by OpenNETCF that you could make once and not with every call into WZC. I don't have the OpenNETCF code in front of me, but something like that could be present. If not, the speed you're seeing is the speed of WZC and your network adapter driver and you'll never make it any faster. Generally, the adapter drivers only check those parameters every few seconds anyway; even if you could call in and get it every millisecond, it still wouldn't change every millisecond. We still need to know why you want this speed. Maybe you're completely off-track and we can point you in another direction... Paul T. "Dani" wrote: > Paul G. Tobey [eMVP] ha scritto: > > Well, no, not unless you can rewrite the WiFi driver! It's not like > > OpenNETCF is sitting around killing time. Trace the calls into the > > OpenNETCF source, if you have it and check which of the NDIS/WZC calls is > > taking most of the time and we might be able to suggest something to help a > > bit, but the interface was never designed to give real-time signal strength, > > so OpenNETCF can't make it do so. > > > > Nooooooooooooooooooooooo.... This is very depressing ! The interface of > the ipaq 214 is VZC compatible, if i try to use it directly have better > chance to reduce time to give signal strength? > Any other solution is appreciated. > > Dani. > . > |