EEVblog Electronics Community Forum

Products => Test Equipment => Topic started by: PetrosA on March 18, 2013, 02:40:53 am

Title: Agilent case study
Post by: PetrosA on March 18, 2013, 02:40:53 am
Yep, I'm tooting my own horn :) I don't get to very often, and almost never as an electrician, so when I found out some of the field testing I had done for Agilent was being used in a case study, and that it mentions me and my company by name, I was shocked!

Anyway, I owe a lot to Dave and this forum for educating me to a lot of things about test gear that I wouldn't have know otherwise and I wanted to send out a shout of thanks to Dave and everyone here and share the case study for anyone who's interested. It deals with their U1177A Bluetooth module and how I used it on a troubleshooting call.

http://cp.literature.agilent.com/litweb/pdf/5991-2084EN.pdf (http://cp.literature.agilent.com/litweb/pdf/5991-2084EN.pdf)
Title: Re: Agilent case study
Post by: EEVblog on March 18, 2013, 02:50:29 am
Agilent need to show you some hardware love I think  ;)
:-+

Dave.
Title: Re: Agilent case study
Post by: larry42 on March 18, 2013, 11:48:29 am
Hei, congrats and nice story. How long does the U1177A batteries last in practice (and at which logging rate) - I've been thinking of getting this myself to monitor AC line voltage, which dips a lot in my lab...

Title: Re: Agilent case study
Post by: PetrosA on March 20, 2013, 03:38:53 am
In my work, I haven't left the datalogging on long enough to kill the batteries - usually an hour or two at the most gives me what I need. The most common way I kill the batteries is by not noticing that the module turned back on when I put the meters back in the case... I keep lots of spare AAAs on my truck now ;)