Re: Low noise N-JFET ?

Pieter wrote:
On Fri, 02 Nov 2007 14:34:07 -0700, Joerg
<notthisjoergsch@xxxxxxxxxxxxxxxxxxxxx> wrote:

Pieter wrote:
On Fri, 02 Nov 2007 13:28:59 -0700, Joerg
<notthisjoergsch@xxxxxxxxxxxxxxxxxxxxx> wrote:

<snip-a-lot>
I will check the BF862 data***.
Got to go through Digikey because NXP's web site current can't find it
via the search box.
I never understood your rants about philips/nxp website. It's not that bad.
It is bad and I'm definitely not the only one saying that. Old saying here in the US: A product is only as good as potential customers think it is.
I had the same problem. Google helped and found it on the website.
Notice that the datahseet still says "Philips".

Just plug BF862 in the top right search box and it comes out immediately.
Well, today it does, maybe somebody reads these posts ;-)
Yesterday it clearly did not, and I've tried multiple times. So has Uwe Bonnes here in this thread. That NXP site isn't reliable IMHO.
So a temporary problem.

Things is, they've got a lot of those. And some not so temporary ones.

For example, right now when I go onto their homepage the whole center is blank. I cannot get into product categories anymore. Brand new Firefox browser, so that's not the issue. Not good.


My problem lies mostly in the 0-10Hz range, parts do get get specified
there.
Unfortunatley many parts such as the BF862 aren't spec'd for noise down
there.
You can have a grasp of what it does by looking at the BF861 fig. 14
Not the best for low frequency.
From the NF figure in the table the parts seemt o be much different though. But yes, the trend down there does not look good at all.

Hi,

It works over here. So I checked their code. I think it is a bad idea
to make code system dependent. This is a part of NXP system detection
(I changed formatting so I could read it), it checks for M$, opera,
mac:

var bCompatible = false;
if ( document.all
&& !navigator.userAgent.toLowerCase().match(/opera/)
&& !navigator.appVersion.match(/mac/i) )
{ try { bCompatible = true && new ActiveXObject('Microsoft.XMLHTTP');
} catch(e){}
}
else { bCompatible = window.controllers && (parseInt(navigator.productSub)>20031001) && new XMLHttpRequest();
}
if (!bCompatible) { location.href = "/indexnc.html"; //INDEX Non Compatible
}

I wonder what system the developer tests it on? Computersystems that
are protected may not give out enough browser information. Do you use
firewll, anonymizer, privacy protector etc?


Yes, a hardware firewall. And that's not going to come down just because the web designers at NXP lack competence. It wasn't much better in the Philips days. Back then they did not understand what a latency is. It's almost 200msec from Europe to the US, mostly it hung up when they did their stupid stock quote lookup. But with the change to NXP it became a whole lot worse. With older browsers the NXP site doesn't work at all, you get a blank screen all the time. And I can't possibly tell my clients "Oh, let's just install another browser...". We just move on to TI, National, ON, ST or other vendors.

Anyhow, I just pretty much quit using their parts. So have lots of others out here. There are enough competitors with more competence in the dissemination of info about their products.

--
Regards, Joerg

http://www.analogconsultants.com/
.

Quantcast