Discussion:
IRIG B
Clive Green
2010-05-25 08:08:18 UTC
Permalink
Can anyone help with a modern IRIG B chipset manufacturer

Many thanks

Clive Green



Quartzlock

+ Gothic, Plymouth Road, Totnes, Devon. TQ9 5LH England

(: +44 (0) 1803 862 062 7: +44 (0) 1803 867 962

š: <mailto:nlaw-***@public.gmane.org> cgreen-***@public.gmane.org ü:
<http://www.quartzlock.com> www.quartzlock.com

Skype: clive.green.skype Messenger: cgreen-***@public.gmane.org

Registered office: Gothic, Plymouth Road, Totnes, Devon. TQ9 5LH England
Registered in England



_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Rob Kimberley
2010-05-25 08:25:21 UTC
Permalink
Hello Clive.

I believe that Meinberg may have something. Take a look at the link below:-

http://www.pcidatabase.com/vendor_details.php?id=1623

Hope all going well.

Rob Kimberley

-----Original Message-----
From: time-nuts-bounces-***@public.gmane.org [mailto:time-nuts-bounces-***@public.gmane.org] On
Behalf Of Clive Green
Sent: 25 May 2010 9:08 AM
To: time-nuts-***@public.gmane.org
Subject: [time-nuts] IRIG B

Can anyone help with a modern IRIG B chipset manufacturer

Many thanks

Clive Green



Quartzlock

+ Gothic, Plymouth Road, Totnes, Devon. TQ9 5LH England

(: +44 (0) 1803 862 062 7: +44 (0) 1803 867 962

š: <mailto:nlaw-***@public.gmane.org> cgreen-***@public.gmane.org ü:
<http://www.quartzlock.com> www.quartzlock.com

Skype: clive.green.skype Messenger: cgreen-***@public.gmane.org

Registered office: Gothic, Plymouth Road, Totnes, Devon. TQ9 5LH England
Registered in England



_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.



_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Hal Murray
2010-05-25 08:49:59 UTC
Permalink
> Can anyone help with a modern IRIG B chipset manufacturer

Send or receive?

The ntp package has software for both sides using PC audio cards.

--
These are my opinions, not necessarily my employer's. I hate spam.




_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
jimlux
2010-05-25 13:06:43 UTC
Permalink
Hal Murray wrote:
>> Can anyone help with a modern IRIG B chipset manufacturer
>
> Send or receive?
>
> The ntp package has software for both sides using PC audio cards.
>

I've been looking for an open-source IRIG B or E reader for FPGA use.

_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Stanley Reynolds
2010-05-25 13:13:18 UTC
Permalink
Example of IRIG-B generator and decoder implemented in LabVIEW FPGA:

http://zone.ni.com/devzone/cda/epd/p/id/3396

Stanley

_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
jimlux
2010-05-25 15:09:22 UTC
Permalink
Stanley Reynolds wrote:
>
> Example of IRIG-B generator and decoder implemented in LabVIEW FPGA:
>
> http://zone.ni.com/devzone/cda/epd/p/id/3396
>
>

Thanks,
I was looking for something in VHDL or Verilog... I'm not sure how well
the Labview RIO, etc. stuff ports to non-Labview environments, but I'll
ask some Labview gurus about this one.

Thanks again
Jim

_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Bob Camp
2010-05-25 11:38:34 UTC
Permalink
Hi

For full send / receive in hardware it looks like a "grab a FPGA and codec" sort of thing. Might be able to do it with a micro depending on the performance level.

Bob

On May 25, 2010, at 4:08 AM, Clive Green wrote:

> Can anyone help with a modern IRIG B chipset manufacturer
>
> Many thanks
>
> Clive Green
>
>
>
> Quartzlock
>
> + Gothic, Plymouth Road, Totnes, Devon. TQ9 5LH England
>
> (: +44 (0) 1803 862 062 7: +44 (0) 1803 867 962
>
> š: <mailto:nlaw-***@public.gmane.org> cgreen-***@public.gmane.org ü:
> <http://www.quartzlock.com> www.quartzlock.com
>
> Skype: clive.green.skype Messenger: cgreen-***@public.gmane.org
>
> Registered office: Gothic, Plymouth Road, Totnes, Devon. TQ9 5LH England
> Registered in England
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>


_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
jimlux
2010-05-25 13:03:29 UTC
Permalink
Clive Green wrote:
> Can anyone help with a modern IRIG B chipset manufacturer
>

I didn't know that there was such a thing, even in ancient times, much
less modern. All I've seen are designs made of discretes or programmed
in a microcontroller or FPGA.

Are you looking for a IRIG generator or receiver. DC or modulated on audio?

_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Dean Weiten
2010-05-25 13:05:19 UTC
Permalink
Date: Tue, 25 May 2010 09:08:18 +0100
From: "Clive Green" <cgreen-***@public.gmane.org>
Subject: [time-nuts] IRIG B
To: <time-nuts-***@public.gmane.org>
Message-ID: <000d01cafbe1$6f6788b0$4e369a10$@com>
Content-Type: text/plain; charset="iso-8859-2"

Can anyone help with a modern IRIG B chipset manufacturer

Many thanks

Clive Green

----------------------

Hi Clive and the group.

I can't give you a lead on an ready-made chipset, but I've implemented an IRIG-B decoder in a 68HC11 and in an 68HCS12. I found the difficult part to be the analog section, as it can introduce significant uncertainties in the timing stream, especially in a modulated signal. We got ours down to around 10 uSec which we considered quite good. Of course the 5 volt logic levels of the unmodulated signal makes it easier to get better accuracy.

The IRIG-B decoder work I did was implemented on power systems relays & disturbance recorders several years ago, then I left the company and in the meantime, they changed over to an FPGA implementation and skipped the processor altogether. Now I'm back with that same company (although ownership has changed), but I haven't yet had a chat with the new FPGA designer to find out how he did it :-)

I've also tweaked and "upgraded" (well in my opinion) the TG program of the NTP package, which generates WWV(H) and IRIG-B audio signals in *NIX operating systems. It was targeted for the Sun Sparc and I moved it to OSS audio which was what I was using on X86 GNU/LINUX at the time. I think I submitted it for inclusion in the NTP package but I don't think it ever got in there; I used to claim that it was rejected, but then again it's also possible that I didn't submit it correctly. I can give this to you if you would like.

If you would advise on your application and parametric requirements, perhaps I (or someone else on the mailing list) could make further suggestion or help directly.

--

Dean Weiten


_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Bob Camp
2010-05-25 16:05:08 UTC
Permalink
Hi

Audio codecs (especially monophonic ones) are pretty cheap these days.
Depending on volume they can get to the sub $1 range. Even in small quantity
they are below $4. That makes them a pretty tempting "front end" for a send
/ receive box.

Bob

-----Original Message-----
From: time-nuts-bounces-***@public.gmane.org [mailto:time-nuts-bounces-***@public.gmane.org] On
Behalf Of Dean Weiten
Sent: Tuesday, May 25, 2010 9:05 AM
To: cgreen-***@public.gmane.org
Cc: time-nuts-***@public.gmane.org
Subject: Re: [time-nuts] IRIG B

Date: Tue, 25 May 2010 09:08:18 +0100
From: "Clive Green" <cgreen-***@public.gmane.org>
Subject: [time-nuts] IRIG B
To: <time-nuts-***@public.gmane.org>
Message-ID: <000d01cafbe1$6f6788b0$4e369a10$@com>
Content-Type: text/plain; charset="iso-8859-2"

Can anyone help with a modern IRIG B chipset manufacturer

Many thanks

Clive Green

----------------------

Hi Clive and the group.

I can't give you a lead on an ready-made chipset, but I've implemented an
IRIG-B decoder in a 68HC11 and in an 68HCS12. I found the difficult part to
be the analog section, as it can introduce significant uncertainties in the
timing stream, especially in a modulated signal. We got ours down to around
10 uSec which we considered quite good. Of course the 5 volt logic levels
of the unmodulated signal makes it easier to get better accuracy.

The IRIG-B decoder work I did was implemented on power systems relays &
disturbance recorders several years ago, then I left the company and in the
meantime, they changed over to an FPGA implementation and skipped the
processor altogether. Now I'm back with that same company (although
ownership has changed), but I haven't yet had a chat with the new FPGA
designer to find out how he did it :-)

I've also tweaked and "upgraded" (well in my opinion) the TG program of the
NTP package, which generates WWV(H) and IRIG-B audio signals in *NIX
operating systems. It was targeted for the Sun Sparc and I moved it to OSS
audio which was what I was using on X86 GNU/LINUX at the time. I think I
submitted it for inclusion in the NTP package but I don't think it ever got
in there; I used to claim that it was rejected, but then again it's also
possible that I didn't submit it correctly. I can give this to you if you
would like.

If you would advise on your application and parametric requirements, perhaps
I (or someone else on the mailing list) could make further suggestion or
help directly.

--

Dean Weiten


_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.




_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Don Latham
2010-05-25 17:20:09 UTC
Permalink
16 bit audio interfaces with USB adapters (cheap sound cards) are
available made in the old country for less than ten inflated rasbuckniks
on epray...
Don

Bob Camp
> Hi
>
> Audio codecs (especially monophonic ones) are pretty cheap these days.
> Depending on volume they can get to the sub $1 range. Even in small
> quantity
> they are below $4. That makes them a pretty tempting "front end" for a
> send
> / receive box.
>
> Bob
>
> -----Original Message-----
> From: time-nuts-bounces-***@public.gmane.org [mailto:time-nuts-bounces-***@public.gmane.org] On
> Behalf Of Dean Weiten
> Sent: Tuesday, May 25, 2010 9:05 AM
> To: cgreen-***@public.gmane.org
> Cc: time-nuts-***@public.gmane.org
> Subject: Re: [time-nuts] IRIG B
>
> Date: Tue, 25 May 2010 09:08:18 +0100
> From: "Clive Green" <cgreen-***@public.gmane.org>
> Subject: [time-nuts] IRIG B
> To: <time-nuts-***@public.gmane.org>
> Message-ID: <000d01cafbe1$6f6788b0$4e369a10$@com>
> Content-Type: text/plain; charset="iso-8859-2"
>
> Can anyone help with a modern IRIG B chipset manufacturer
>
> Many thanks
>
> Clive Green
>
> ----------------------
>
> Hi Clive and the group.
>
> I can't give you a lead on an ready-made chipset, but I've implemented an
> IRIG-B decoder in a 68HC11 and in an 68HCS12. I found the difficult part
> to
> be the analog section, as it can introduce significant uncertainties in
> the
> timing stream, especially in a modulated signal. We got ours down to
> around
> 10 uSec which we considered quite good. Of course the 5 volt logic levels
> of the unmodulated signal makes it easier to get better accuracy.
>
> The IRIG-B decoder work I did was implemented on power systems relays &
> disturbance recorders several years ago, then I left the company and in
> the
> meantime, they changed over to an FPGA implementation and skipped the
> processor altogether. Now I'm back with that same company (although
> ownership has changed), but I haven't yet had a chat with the new FPGA
> designer to find out how he did it :-)
>
> I've also tweaked and "upgraded" (well in my opinion) the TG program of
> the
> NTP package, which generates WWV(H) and IRIG-B audio signals in *NIX
> operating systems. It was targeted for the Sun Sparc and I moved it to
> OSS
> audio which was what I was using on X86 GNU/LINUX at the time. I think I
> submitted it for inclusion in the NTP package but I don't think it ever
> got
> in there; I used to claim that it was rejected, but then again it's also
> possible that I didn't submit it correctly. I can give this to you if you
> would like.
>
> If you would advise on your application and parametric requirements,
> perhaps
> I (or someone else on the mailing list) could make further suggestion or
> help directly.
>
> --
>
> Dean Weiten
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>


--
"Neither the voice of authority nor the weight of reason and argument are
as significant as experiment, for thence comes quiet to the mind."
R. Bacon


Dr. Don Latham AJ7LL
Six Mile Systems LLP
17850 Six Mile Road
POB 134
Huson, MT, 59846
VOX 406-626-4304
www.lightningforensics.com
www.sixmilesystems.com


_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Bob Camp
2010-05-25 21:12:47 UTC
Permalink
Hi

I *think* Clive is looking for a chip set to put on a pc board in a product.

Bob

-----Original Message-----
From: time-nuts-bounces-***@public.gmane.org [mailto:time-nuts-bounces-***@public.gmane.org] On
Behalf Of Don Latham
Sent: Tuesday, May 25, 2010 1:20 PM
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] IRIG B

16 bit audio interfaces with USB adapters (cheap sound cards) are
available made in the old country for less than ten inflated rasbuckniks
on epray...
Don

Bob Camp
> Hi
>
> Audio codecs (especially monophonic ones) are pretty cheap these days.
> Depending on volume they can get to the sub $1 range. Even in small
> quantity
> they are below $4. That makes them a pretty tempting "front end" for a
> send
> / receive box.
>
> Bob
>
> -----Original Message-----
> From: time-nuts-bounces-***@public.gmane.org [mailto:time-nuts-bounces-***@public.gmane.org] On
> Behalf Of Dean Weiten
> Sent: Tuesday, May 25, 2010 9:05 AM
> To: cgreen-***@public.gmane.org
> Cc: time-nuts-***@public.gmane.org
> Subject: Re: [time-nuts] IRIG B
>
> Date: Tue, 25 May 2010 09:08:18 +0100
> From: "Clive Green" <cgreen-***@public.gmane.org>
> Subject: [time-nuts] IRIG B
> To: <time-nuts-***@public.gmane.org>
> Message-ID: <000d01cafbe1$6f6788b0$4e369a10$@com>
> Content-Type: text/plain; charset="iso-8859-2"
>
> Can anyone help with a modern IRIG B chipset manufacturer
>
> Many thanks
>
> Clive Green
>
> ----------------------
>
> Hi Clive and the group.
>
> I can't give you a lead on an ready-made chipset, but I've implemented an
> IRIG-B decoder in a 68HC11 and in an 68HCS12. I found the difficult part
> to
> be the analog section, as it can introduce significant uncertainties in
> the
> timing stream, especially in a modulated signal. We got ours down to
> around
> 10 uSec which we considered quite good. Of course the 5 volt logic levels
> of the unmodulated signal makes it easier to get better accuracy.
>
> The IRIG-B decoder work I did was implemented on power systems relays &
> disturbance recorders several years ago, then I left the company and in
> the
> meantime, they changed over to an FPGA implementation and skipped the
> processor altogether. Now I'm back with that same company (although
> ownership has changed), but I haven't yet had a chat with the new FPGA
> designer to find out how he did it :-)
>
> I've also tweaked and "upgraded" (well in my opinion) the TG program of
> the
> NTP package, which generates WWV(H) and IRIG-B audio signals in *NIX
> operating systems. It was targeted for the Sun Sparc and I moved it to
> OSS
> audio which was what I was using on X86 GNU/LINUX at the time. I think I
> submitted it for inclusion in the NTP package but I don't think it ever
> got
> in there; I used to claim that it was rejected, but then again it's also
> possible that I didn't submit it correctly. I can give this to you if you
> would like.
>
> If you would advise on your application and parametric requirements,
> perhaps
> I (or someone else on the mailing list) could make further suggestion or
> help directly.
>
> --
>
> Dean Weiten
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>


--
"Neither the voice of authority nor the weight of reason and argument are
as significant as experiment, for thence comes quiet to the mind."
R. Bacon


Dr. Don Latham AJ7LL
Six Mile Systems LLP
17850 Six Mile Road
POB 134
Huson, MT, 59846
VOX 406-626-4304
www.lightningforensics.com
www.sixmilesystems.com


_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.




_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Magnus Danielson
2010-05-25 22:30:59 UTC
Permalink
On 05/25/2010 11:12 PM, Bob Camp wrote:
> Hi
>
> I *think* Clive is looking for a chip set to put on a pc board in a product.

Me too, but I think the reality is that I don't think there is such a
thing except maybe in some early ASICs. Today FPGAs rule that world. The
benefit is naturally that functional updates can come cheaply if
provision is made for remove firmware updates.:)

The closest I can come up with is maybe WWV receiver chips. But that is
IRIG-H and not IRIG-B.

The only reasons for heading down the audio ADC/DAC route over 8-bit is
dynamic range and cost. It makes sense for IRIG-B102 signals.

Cheers,
Magnus

_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Bob Camp
2010-05-25 23:09:35 UTC
Permalink
Hi

Like all the rest of us I'm making assumptions. I *assume* that we're talking about an implementation that will handle IRIG over audio over a fairly wide dynamic range.

Bob


On May 25, 2010, at 6:30 PM, Magnus Danielson wrote:

> On 05/25/2010 11:12 PM, Bob Camp wrote:
>> Hi
>>
>> I *think* Clive is looking for a chip set to put on a pc board in a product.
>
> Me too, but I think the reality is that I don't think there is such a thing except maybe in some early ASICs. Today FPGAs rule that world. The benefit is naturally that functional updates can come cheaply if provision is made for remove firmware updates.:)
>
> The closest I can come up with is maybe WWV receiver chips. But that is IRIG-H and not IRIG-B.
>
> The only reasons for heading down the audio ADC/DAC route over 8-bit is dynamic range and cost. It makes sense for IRIG-B102 signals.
>
> Cheers,
> Magnus
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>


_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Magnus Danielson
2010-05-25 23:23:37 UTC
Permalink
On 05/26/2010 01:09 AM, Bob Camp wrote:
> Hi
>
> Like all the rest of us I'm making assumptions. I *assume* that we're talking about an implementation that will handle IRIG over audio over a fairly wide dynamic range.

Well, like most cases, I'd assume it is over "sufficient" dynamic range.
The signal itself doesn't require very high dynamics, 8 bit should work
well, 12 bits should allow for less care in level settings, 24 bits is
excessive but cheap and only real care is high amplitude/clipping.

Cheers,
Magnus

_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Bob Camp
2010-05-25 23:32:11 UTC
Permalink
Hi

Most of the cheap codecs are 24 bits "as advertised" and maybe 16 bits "as measured".

That puts them in a nice comfort zone a bit past the 10 or 12 bits you get from a micro.

Bob


On May 25, 2010, at 7:23 PM, Magnus Danielson wrote:

> On 05/26/2010 01:09 AM, Bob Camp wrote:
>> Hi
>>
>> Like all the rest of us I'm making assumptions. I *assume* that we're talking about an implementation that will handle IRIG over audio over a fairly wide dynamic range.
>
> Well, like most cases, I'd assume it is over "sufficient" dynamic range. The signal itself doesn't require very high dynamics, 8 bit should work well, 12 bits should allow for less care in level settings, 24 bits is excessive but cheap and only real care is high amplitude/clipping.
>
> Cheers,
> Magnus
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>


_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
jimlux
2010-05-26 03:50:22 UTC
Permalink
Magnus Danielson wrote:
> On 05/26/2010 01:09 AM, Bob Camp wrote:
>> Hi
>>
>> Like all the rest of us I'm making assumptions. I *assume* that we're
>> talking about an implementation that will handle IRIG over audio over
>> a fairly wide dynamic range.
>
> Well, like most cases, I'd assume it is over "sufficient" dynamic range.
> The signal itself doesn't require very high dynamics, 8 bit should work
> well, 12 bits should allow for less care in level settings, 24 bits is
> excessive but cheap and only real care is high amplitude/clipping.
>
>

if you've got a low speed ADC, (perhaps on the chip) that's one way to
go. You can also do stuff like use a output pin from the micro and some
resistor/capacitor stuff to do a CVSD encoder, which you can pretty
easily turn into the level data you need to decode the IRIG.

At some point, though, the Rs and Cs cost enough (in board space and
installation cost, if nothing else) that you might as well get a ADC (or
a bigger uC that has one on chip)..

_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Bob Camp
2010-05-26 11:02:35 UTC
Permalink
Hi

Strange as it seems, *stocking* the R's and C's can be an issue. There's also placement cost. Based on some of the numbers you see, the cross over point (IC to odd value R's and C's) is amazingly low. I'm not saying any of that's right, just that it's the way a lot of companies roll up the costs.

Bob


On May 25, 2010, at 11:50 PM, jimlux wrote:

> Magnus Danielson wrote:
>> On 05/26/2010 01:09 AM, Bob Camp wrote:
>>> Hi
>>>
>>> Like all the rest of us I'm making assumptions. I *assume* that we're talking about an implementation that will handle IRIG over audio over a fairly wide dynamic range.
>> Well, like most cases, I'd assume it is over "sufficient" dynamic range. The signal itself doesn't require very high dynamics, 8 bit should work well, 12 bits should allow for less care in level settings, 24 bits is excessive but cheap and only real care is high amplitude/clipping.
>>
>
> if you've got a low speed ADC, (perhaps on the chip) that's one way to go. You can also do stuff like use a output pin from the micro and some resistor/capacitor stuff to do a CVSD encoder, which you can pretty easily turn into the level data you need to decode the IRIG.
>
> At some point, though, the Rs and Cs cost enough (in board space and installation cost, if nothing else) that you might as well get a ADC (or a bigger uC that has one on chip)..
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>


_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
jimlux
2010-05-26 13:16:49 UTC
Permalink
Bob Camp wrote:
> Hi
>
> Strange as it seems, *stocking* the R's and C's can be an issue. There's also placement cost. Based on some of the numbers you see, the cross over point (IC to odd value R's and C's) is amazingly low. I'm not saying any of that's right, just that it's the way a lot of companies roll up the costs.
>
> Bob
>
>
Not surprising.. the cost to stock, pick, place, solder is probably the
same for a small IC and a R or C. So, the only possible saving would be
if the IC is a LOT more expensive than a single or two Rs or Cs.

There might be a power dissipation difference, or a temperature range
difference that would push you one way or another.

_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Robert Atkinson
2010-05-26 20:17:02 UTC
Permalink
A good example is the good old 555 timer. A cmos 55 is 41 cents and needs a timing cap and resistor. A pic10f200 is 31 cents and needs no support components. You can also do fancy timing with the pic. I hate to say it but there is really no contest once you have the tools (free complier and a programmer for <$50). Just a shame it's killing analog skills.
 
Robert G8RPI. 

--- On Wed, 26/5/10, jimlux <jimlux-***@public.gmane.org> wrote:


From: jimlux <jimlux-***@public.gmane.org>
Subject: Re: [time-nuts] IRIG B
To: "Discussion of precise time and frequency measurement" <time-***@febo.com>
Date: Wednesday, 26 May, 2010, 14:16


Bob Camp wrote:
> Hi
>
> Strange as it seems, *stocking* the R's and C's can be an issue. There's also placement cost. Based on some of the numbers you see, the cross over point (IC to odd value R's and C's) is amazingly low. I'm not saying any of that's right, just that it's the way a lot of companies roll up the costs.
> Bob
>
>
Not surprising.. the cost to stock, pick, place, solder is probably the same for a small IC and a R or C.  So, the only possible saving would be  if the IC is a LOT more expensive than a single or two Rs or Cs.

There might be a power dissipation difference, or a temperature range difference that would push you one way or another.

_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.




_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
jimlux
2010-05-26 03:36:16 UTC
Permalink
Bob Camp wrote:
> Hi
>
> Audio codecs (especially monophonic ones) are pretty cheap these days.
> Depending on volume they can get to the sub $1 range. Even in small quantity
> they are below $4. That makes them a pretty tempting "front end" for a send
> / receive box.
>
> Bob
>


i would think, given that the audio carrier is 1kHz-ish, that almost any
of the small microcontrollers would work, using a single bit in/out with
some RC signal conditioning. Maybe a bit of a challenge for the
receive.. you'd need two inputs with different resistors.

_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Don Latham
2010-05-26 06:25:42 UTC
Permalink
Could probably do it all with a Propeller.
Don

----- Original Message -----
From: "jimlux" <jimlux-***@public.gmane.org>
To: "Discussion of precise time and frequency measurement"
<time-nuts-***@public.gmane.org>
Sent: Tuesday, May 25, 2010 9:36 PM
Subject: Re: [time-nuts] IRIG B


> Bob Camp wrote:
>> Hi
>>
>> Audio codecs (especially monophonic ones) are pretty cheap these days.
>> Depending on volume they can get to the sub $1 range. Even in small
>> quantity
>> they are below $4. That makes them a pretty tempting "front end" for a
>> send
>> / receive box.
>>
>> Bob
>>
>
>
> i would think, given that the audio carrier is 1kHz-ish, that almost any
> of the small microcontrollers would work, using a single bit in/out with
> some RC signal conditioning. Maybe a bit of a challenge for the receive..
> you'd need two inputs with different resistors.
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.


_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Hal Murray
2010-05-25 18:49:54 UTC
Permalink
> The IRIG-B decoder work I did was implemented on power systems relays &
> disturbance recorders several years ago, then I left the company and in the
> meantime, they changed over to an FPGA implementation and skipped the
> processor altogether. Now I'm back with that same company (although
> ownership has changed), but I haven't yet had a chat with the new FPGA
> designer to find out how he did it :-)

Interesting. I'd like to know why they switched to FPGA.

I thought the consensus in the FPGA world was that if you could do it in
software that was probably the better way to go. The main idea is that it's
easier to hire programmers than FPGA designers.

I'd expect silicon costs to be roughly equal. In a FPGA you are "wasting" a
lot of silicon for routing. In a CPU, you are wasting it on instruction
decoding. Both are high volume parts riding the crest of Moore's Law. Of
course, algorithm details may push you one way or the other.


> I've also tweaked and "upgraded" (well in my opinion) the TG program of the
> NTP package, which generates WWV(H) and IRIG-B audio signals in *NIX
> operating systems. It was targeted for the Sun Sparc and I moved it to OSS
> audio which was what I was using on X86 GNU/LINUX at the time. I think I
> submitted it for inclusion in the NTP package but I don't think it ever got
> in there; I used to claim that it was rejected, but then again it's also
> possible that I didn't submit it correctly. I can give this to you if you
> would like.

It's in there. Thanks. I called it tg2 because I couldn't test it in the
Sun world and I wanted to make sure I didn't break anything.

The recipe for getting fixes into the NTP package is pretty simple: find an
insider who likes your changes. Mechanically, their bugzilla is at
https://support.ntp.org/bugs/index.cgi
That tracks enhancements/wishes as well as bugs. You can upload diffs and
such.

--
These are my opinions, not necessarily my employer's. I hate spam.




_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Bob Camp
2010-05-25 21:14:59 UTC
Permalink
Hi

A lot of the codec's talk I2S. That's not a real popular item in the
embedded processor world. If you are already running a FPGA, the IRIG might
fit in the "empty" part of the chip. You often have to bump up 1.5 or 2:1
when you run out of this or that.

Bob

-----Original Message-----
From: time-nuts-bounces-***@public.gmane.org [mailto:time-nuts-bounces-***@public.gmane.org] On
Behalf Of Hal Murray
Sent: Tuesday, May 25, 2010 2:50 PM
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] IRIG B


> The IRIG-B decoder work I did was implemented on power systems relays &
> disturbance recorders several years ago, then I left the company and in
the
> meantime, they changed over to an FPGA implementation and skipped the
> processor altogether. Now I'm back with that same company (although
> ownership has changed), but I haven't yet had a chat with the new FPGA
> designer to find out how he did it :-)

Interesting. I'd like to know why they switched to FPGA.

I thought the consensus in the FPGA world was that if you could do it in
software that was probably the better way to go. The main idea is that it's

easier to hire programmers than FPGA designers.

I'd expect silicon costs to be roughly equal. In a FPGA you are "wasting" a

lot of silicon for routing. In a CPU, you are wasting it on instruction
decoding. Both are high volume parts riding the crest of Moore's Law. Of
course, algorithm details may push you one way or the other.


> I've also tweaked and "upgraded" (well in my opinion) the TG program of
the
> NTP package, which generates WWV(H) and IRIG-B audio signals in *NIX
> operating systems. It was targeted for the Sun Sparc and I moved it to
OSS
> audio which was what I was using on X86 GNU/LINUX at the time. I think I
> submitted it for inclusion in the NTP package but I don't think it ever
got
> in there; I used to claim that it was rejected, but then again it's also
> possible that I didn't submit it correctly. I can give this to you if you
> would like.

It's in there. Thanks. I called it tg2 because I couldn't test it in the
Sun world and I wanted to make sure I didn't break anything.

The recipe for getting fixes into the NTP package is pretty simple: find an
insider who likes your changes. Mechanically, their bugzilla is at
https://support.ntp.org/bugs/index.cgi
That tracks enhancements/wishes as well as bugs. You can upload diffs and
such.

--
These are my opinions, not necessarily my employer's. I hate spam.




_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.




_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
jimlux
2010-05-26 03:43:43 UTC
Permalink
Hal Murray wrote:
>> The IRIG-B decoder work I did was implemented on power systems relays &
>> disturbance recorders several years ago, then I left the company and in the
>> meantime, they changed over to an FPGA implementation and skipped the
>> processor altogether. Now I'm back with that same company (although
>> ownership has changed), but I haven't yet had a chat with the new FPGA
>> designer to find out how he did it :-)
>
> Interesting. I'd like to know why they switched to FPGA.
>
> I thought the consensus in the FPGA world was that if you could do it in
> software that was probably the better way to go. The main idea is that it's
> easier to hire programmers than FPGA designers.
>
> I'd expect silicon costs to be roughly equal. In a FPGA you are "wasting" a
> lot of silicon for routing. In a CPU, you are wasting it on instruction
> decoding. Both are high volume parts riding the crest of Moore's Law. Of
> course, algorithm details may push you one way or the other.
>
>

Maybe you have an all FPGA design otherwise, and just want to add IRIG
to it?

Maybe you've got both FPGA and CPU resources in the box, and the CPU is
used for non-real-time-critical stuff, and you want to do timing in
hardware (that's my situation).

Not all applications are high volume.. even a mid volume app might need
enough glue that one FPGA is a better choice than a uC and a FPGA.


_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Hal Murray
2010-05-25 19:00:07 UTC
Permalink
> For full send / receive in hardware it looks like a "grab a FPGA and codec"
> sort of thing. Might be able to do it with a micro depending on the
> performance level.

It doesn't take a lot of CPU.

I have a 433 MHz AMD Geode (i386 clone) running ntpd's IRIG decoder. Top
says the CPU usage bounces around a lot. Typical large samples are 2.3%.
Round that up and we are talking 20 MHz. It would be fun to get it running
an an ARM and see how slow it could go. (Or pick your favorite embedded CPU.)

--
These are my opinions, not necessarily my employer's. I hate spam.




_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Hal Murray
2010-05-25 19:21:19 UTC
Permalink
> Audio codecs (especially monophonic ones) are pretty cheap these days.
> Depending on volume they can get to the sub $1 range. Even in small quantity
> they are below $4. That makes them a pretty tempting "front end" for a send /
> receive box.

I got an interesting education in silicon economics 5-8 years ago.

We were looking for a low cost audio A/D. A guy from TI suggested using a
codec and ignoring the other half. (The idea of throwing away half of a chip
had never occurred to me.)


--
These are my opinions, not necessarily my employer's. I hate spam.




_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Hal Murray
2010-05-26 08:34:31 UTC
Permalink
> Could probably do it all with a Propeller.

That sounds like an invitation for a contest.

What would be the output to indicate success?
PPS?
Disciplined 10 MHz?
Time in ASCII, LEDs, LCD, ...?

How would you score things?
Cost?
Say list price for key parts at qty 1000
Ignore power, PCB, connectors, debugging stuff...
Multiply or adder for RMS error or area under an ADEV plot from A to B?




--
These are my opinions, not necessarily my employer's. I hate spam.




_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Morris Odell
2010-05-26 11:26:01 UTC
Permalink
I have done this with an AVR microcontroller and it turned out to be very
easy. Just program one output to generate a 1 KHz carrier and another to
modulate the amplitude using a resistive divider. A simple LPF will knock
the edges off the carrier and not affect the timing accuracy too much.

Receive is easy too if you have a micro with a comparator which can tell the
difference between the two amplitude levels. I would extract the carrier
first and feed it to another input of the micro to provide a phase reference
and then do the decoding all in firmware.

Morris

>
>
> i would think, given that the audio carrier is 1kHz-ish, that almost
> any
> of the small microcontrollers would work, using a single bit in/out
> with
> some RC signal conditioning. Maybe a bit of a challenge for the
> receive.. you'd need two inputs with different resistors.
>


_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Hal Murray
2010-06-28 23:45:15 UTC
Permalink
> The one I'm building up is a ADS1278
> http://focus.ti.com/lit/ds/symlink/ads1278.pdf
> There are others in the series with fewer inputs. As with a lot of
> converters, there isn't a whole lot of data on them.

What are you looking for?

There is a section of DC parameters on page 3.

No missing codes: 24 bits
INL: 0.0003% (typical), 0.0012% (max)
Offset drift: 0.8 microvolts/C (typical)
Gain drift: 1.3 ppm/C (typical)



--
These are my opinions, not necessarily my employer's. I hate spam.
Bob Camp
2010-06-28 23:48:34 UTC
Permalink
Hi

Noise spectra down into the 1/f region (< 10 Hz) would be nice.

Bob


On Jun 28, 2010, at 7:45 PM, Hal Murray wrote:

>
>> The one I'm building up is a ADS1278
>> http://focus.ti.com/lit/ds/symlink/ads1278.pdf
>> There are others in the series with fewer inputs. As with a lot of
>> converters, there isn't a whole lot of data on them.
>
> What are you looking for?
>
> There is a section of DC parameters on page 3.
>
> No missing codes: 24 bits
> INL: 0.0003% (typical), 0.0012% (max)
> Offset drift: 0.8 microvolts/C (typical)
> Gain drift: 1.3 ppm/C (typical)
>
>
>
> --
> These are my opinions, not necessarily my employer's. I hate spam.
>
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
Magnus Danielson
2010-06-28 23:59:38 UTC
Permalink
On 06/29/2010 01:45 AM, Hal Murray wrote:
>
>> The one I'm building up is a ADS1278
>> http://focus.ti.com/lit/ds/symlink/ads1278.pdf
>> There are others in the series with fewer inputs. As with a lot of
>> converters, there isn't a whole lot of data on them.
>
> What are you looking for?
>
> There is a section of DC parameters on page 3.
>
> No missing codes: 24 bits
> INL: 0.0003% (typical), 0.0012% (max)
> Offset drift: 0.8 microvolts/C (typical)
> Gain drift: 1.3 ppm/C (typical)

There are also some useful plots relating to temperature dependence
among other things, things relating in particular to long term aspects.

Choosing the right Vref value can be among the things to do to get the
performance.

Also, TI claims it to address both the DC precision and audio
properties. Looks like a good choice to me. Naturally, things must be
tested and tried.

Cheers,
Magnus
Hal Murray
2010-06-29 00:39:38 UTC
Permalink
> Noise spectra down into the 1/f region (< 10 Hz) would be nice.

Usually that stuff scales with the master clock frequency.

There are a couple of shorted-input graphs on page 11. They go down to 1 Hz.
Figure 15 on the next page goes down to 0.2 Hz.


For EFC type uses, I'd expect the drift over temperature to be the major problem, or maybe the temperature drift of the reference voltage.

I suppose you could put them in an oven.


--
These are my opinions, not necessarily my employer's. I hate spam.
Hal Murray
2010-08-14 17:17:32 UTC
Permalink
> Line got moved to other side of big ocean. Process got " tweaked" beta is
> now 4x what it was.

I'm pretty sure that military grade parts have paperwork and processes to
cover that case. I expect it costs a lot.

I think the same sort of service is available to high volume customers at a
less than military price.

Or, as Javier said:
> I periodically receive PCNs (product change notifications) from EBV
> Elektronik, which is a quite big european semiconductor distributor,

So maybe it doesn't take a high volume, you just have to get plugged into the
right paperwork flow and then read all the fine print to see if the change is
interesting.



--
These are my opinions, not necessarily my employer's. I hate spam.
Javier Herrero
2010-08-14 17:38:39 UTC
Permalink
El 14/08/2010 19:17, Hal Murray escribió:
>
> So maybe it doesn't take a high volume, you just have to get plugged into the
> right paperwork flow and then read all the fine print to see if the change is
> interesting.
>
>
Yes. I'm not a high volume customer, only mid-to-low :) But I receive
the PCNs even for components that I've only purchased one 50pcs bar for
a special project. But I'm not sure if all manufacturers are the same.
This example from NXP is very very detailed, in other cases there is
only a note that production has changed from one factory to another.

Regards,

Javier

--
------------------------------------------------------------------------
Javier Herrero EMAIL: jherrero-vPjxGBZQJSB9uiUsa/***@public.gmane.org
HV Sistemas S.L. PHONE: +34 949 336 806
Los Charcones, 17 FAX: +34 949 336 792
19170 El Casar - Guadalajara - Spain WEB: http://www.hvsistemas.com
Bob Camp
2010-08-14 17:49:22 UTC
Permalink
Hi

I seem to get weekly notices about a resin changing or a new date code format. Silicon changes don't seem to be on the same "system". That's still better than it was 30 years back.

Bob



On Aug 14, 2010, at 1:38 PM, Javier Herrero <***@hvsistemas.es> wrote:

> El 14/08/2010 19:17, Hal Murray escribió:
>>
>> So maybe it doesn't take a high volume, you just have to get plugged into the
>> right paperwork flow and then read all the fine print to see if the change is
>> interesting.
>>
>>
> Yes. I'm not a high volume customer, only mid-to-low :) But I receive the PCNs even for components that I've only purchased one 50pcs bar for a special project. But I'm not sure if all manufacturers are the same. This example from NXP is very very detailed, in other cases there is only a note that production has changed from one factory to another.
>
> Regards,
>
> Javier
>
> --
> ------------------------------------------------------------------------
> Javier Herrero EMAIL: ***@hvsistemas.com
> HV Sistemas S.L. PHONE: +34 949 336 806
> Los Charcones, 17 FAX: +34 949 336 792
> 19170 El Casar - Guadalajara - Spain WEB: http://www.hvsistemas.com
>
>
> _______________________________________________
> time-nuts mailing list -- time-***@febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>

_______________________________________________
time-nuts mailing list -- time-***@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinf
Javier Herrero
2010-08-14 17:52:21 UTC
Permalink
I sometimes get some PCNs about process changes on silicon (new process
or new masks). I suppose that depends on manufacturers :)

Regards,

Javier

El 14/08/2010 19:49, Bob Camp escribió:
> Hi
>
> I seem to get weekly notices about a resin changing or a new date code format. Silicon changes don't seem to be on the same "system". That's still better than it was 30 years back.
>
> Bob
>
>
>
> On Aug 14, 2010, at 1:38 PM, Javier Herrero<***@hvsistemas.es> wrote:
>
>> El 14/08/2010 19:17, Hal Murray escribió:
>>>
>>> So maybe it doesn't take a high volume, you just have to get plugged into the
>>> right paperwork flow and then read all the fine print to see if the change is
>>> interesting.
>>>
>>>
>> Yes. I'm not a high volume customer, only mid-to-low :) But I receive the PCNs even for components that I've only purchased one 50pcs bar for a special project. But I'm not sure if all manufacturers are the same. This example from NXP is very very detailed, in other cases there is only a note that production has changed from one factory to another.
>>
>> Regards,
>>
>> Javier
>>
>> --
>> ------------------------------------------------------------------------
>> Javier Herrero EMAIL: ***@hvsistemas.com
>> HV Sistemas S.L. PHONE: +34 949 336 806
>> Los Charcones, 17 FAX: +34 949 336 792
>> 19170 El Casar - Guadalajara - Spain WEB: http://www.hvsistemas.com
>>
>>
>> _______________________________________________
>> time-nuts mailing list -- time-***@febo.com
>> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
>>
>
> _______________________________________________
> time-nuts mailing list -- time-***@febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.

--
------------------------------------------------------------------------
Javier Herrero EMAIL: ***@hvsistemas.com
HV Sistemas S.L. PHONE: +34 949 336 806
Los Charcones, 17 FAX: +34 949 336 792
19170 El Casar - Guadalajara - Spain WEB: http://www.hvsistemas.com


_______________________________________________
time-nuts mailing list -- time-***@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailma
Bob Camp
2010-08-14 17:45:58 UTC
Permalink
Hi

Not so much.

Mil grade just makes sure they qualify a change.

At the time we had the issues the volume on the transistors was quite high. The cost os screening was still prohibitive. They write the specs with very few limits for a reason....

Bob



On Aug 14, 2010, at 1:17 PM, Hal Murray <hmurray-8cQiHa/C+6Go9G/***@public.gmane.org> wrote:

>
>> Line got moved to other side of big ocean. Process got " tweaked" beta is
>> now 4x what it was.
>
> I'm pretty sure that military grade parts have paperwork and processes to
> cover that case. I expect it costs a lot.
>
> I think the same sort of service is available to high volume customers at a
> less than military price.
>
> Or, as Javier said:
>> I periodically receive PCNs (product change notifications) from EBV
>> Elektronik, which is a quite big european semiconductor distributor,
>
> So maybe it doesn't take a high volume, you just have to get plugged into the
> right paperwork flow and then read all the fine print to see if the change is
> interesting.
>
>
>
> --
> These are my opinions, not necessarily my employer's. I hate spam.
>
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
Didier Juges
2010-08-14 18:12:14 UTC
Permalink
Mil specs cover a number of things that are not always in the commercial specs, but not always, and mil spec parts are going the way of the dodo. Nobody wants to make them, except the local garage shop which does not mind selling you $0.02 parts for $60 (quite common) and the worst is that these parts are often made in very small runs from the old masks, or they are custom packaged dies bought from commercial sources and screened to meet the requirements and end up having very poor reliability because the small runs do not allow the quality of commercial parts made in the gazillion.

Quite a paradox!!!

In my 30 years experience designing military and space hardware, I now believe the commercial grade plastic parts you get from Digikey are quite a bit better than the expensive mil spec ones in the hermetic packages, even when rated 0-70C and when used in a humid environment.

Of course, if you have to have hermetic parts to satisfy an explicit customer requirement, that's another story, even though I have been fairly successful at obtaining waivers from customers in that regard.

Didier

------------------------
Sent from my BlackBerry Wireless thingy while I do other things...

-----Original Message-----
From: Hal Murray <hmurray-8cQiHa/C+6Go9G/***@public.gmane.org>
Sender: time-nuts-bounces-***@public.gmane.org
Date: Sat, 14 Aug 2010 10:17:32
To: Discussion of precise time and frequency measurement<time-nuts-***@public.gmane.org>
Reply-To: Discussion of precise time and frequency measurement
<time-nuts-***@public.gmane.org>
Subject: Re: [time-nuts] Simulation


> Line got moved to other side of big ocean. Process got " tweaked" beta is
> now 4x what it was.

I'm pretty sure that military grade parts have paperwork and processes to
cover that case. I expect it costs a lot.

I think the same sort of service is available to high volume customers at a
less than military price.

Or, as Javier said:
> I periodically receive PCNs (product change notifications) from EBV
> Elektronik, which is a quite big european semiconductor distributor,

So maybe it doesn't take a high volume, you just have to get plugged into the
right paperwork flow and then read all the fine print to see if the change is
interesting.



--
These are my opinions, not necessarily my employer's. I hate spam.




_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
J. Forster
2010-08-14 18:18:37 UTC
Permalink
When I was building spacecraft payloads for the USAF, there was a lot of
resistance to using commercial parts. If something failed, you had to
right back to square one with the acceptance tests, and that took months.
Often we just used stuff from the Apollo QPL.

-John

=============

> Mil specs cover a number of things that are not always in the commercial
> specs, but not always, and mil spec parts are going the way of the dodo.
> Nobody wants to make them, except the local garage shop which does not
> mind selling you $0.02 parts for $60 (quite common) and the worst is that
> these parts are often made in very small runs from the old masks, or they
> are custom packaged dies bought from commercial sources and screened to
> meet the requirements and end up having very poor reliability because the
> small runs do not allow the quality of commercial parts made in the
> gazillion.
>
> Quite a paradox!!!
>
> In my 30 years experience designing military and space hardware, I now
> believe the commercial grade plastic parts you get from Digikey are quite
> a bit better than the expensive mil spec ones in the hermetic packages,
> even when rated 0-70C and when used in a humid environment.
>
> Of course, if you have to have hermetic parts to satisfy an explicit
> customer requirement, that's another story, even though I have been fairly
> successful at obtaining waivers from customers in that regard.
>
> Didier
>
> ------------------------
> Sent from my BlackBerry Wireless thingy while I do other things...
>
> -----Original Message-----
> From: Hal Murray <hmurray-8cQiHa/C+6Go9G/***@public.gmane.org>
> Sender: time-nuts-bounces-***@public.gmane.org
> Date: Sat, 14 Aug 2010 10:17:32
> To: Discussion of precise time and frequency
> measurement<time-nuts-***@public.gmane.org>
> Reply-To: Discussion of precise time and frequency measurement
> <time-nuts-***@public.gmane.org>
> Subject: Re: [time-nuts] Simulation
>
>
>> Line got moved to other side of big ocean. Process got " tweaked" beta
>> is
>> now 4x what it was.
>
> I'm pretty sure that military grade parts have paperwork and processes to
> cover that case. I expect it costs a lot.
>
> I think the same sort of service is available to high volume customers at
> a
> less than military price.
>
> Or, as Javier said:
>> I periodically receive PCNs (product change notifications) from EBV
>> Elektronik, which is a quite big european semiconductor distributor,
>
> So maybe it doesn't take a high volume, you just have to get plugged into
> the
> right paperwork flow and then read all the fine print to see if the change
> is
> interesting.
>
>
>
> --
> These are my opinions, not necessarily my employer's. I hate spam.
>
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>
jimlux
2010-08-14 21:42:39 UTC
Permalink
Hal Murray wrote:
>> Line got moved to other side of big ocean. Process got " tweaked" beta is
>> now 4x what it was.
>
> I'm pretty sure that military grade parts have paperwork and processes to
> cover that case. I expect it costs a lot.
>
> I think the same sort of service is available to high volume customers at a
> less than military price.

just so..

In the space business, we call it "traceability to sand"... you haven't
lived til someone has a failed 2n2222, somwhere on some piece of
critical hardware, and they issue a GIDEP alert, and then the mission
assurance folks call you up and ask, "you don't by any chance have
2N2222's in your flight hardware do you?".. then there's the whole
manufacturer and date code hunt.. Looking through the build
documentation to find out. (or worse yet, if you had decided for some
reason to use the prototype, which you didn't keep such good records on,
but which you have photos of, and trying to read the date codes off the
assembled item with a magnifying glass)
J. Forster
2010-08-14 21:49:29 UTC
Permalink
On Apollo they had file cabinets full of drawers for IBM punch cards,
except each had a microfilm insert.

They could trace a single #6-32 screw back to the mine the iron ore came
from.

-John

=============


> Hal Murray wrote:
>>> Line got moved to other side of big ocean. Process got " tweaked" beta
>>> is
>>> now 4x what it was.
>>
>> I'm pretty sure that military grade parts have paperwork and processes
>> to
>> cover that case. I expect it costs a lot.
>>
>> I think the same sort of service is available to high volume customers
>> at a
>> less than military price.
>
> just so..
>
> In the space business, we call it "traceability to sand"... you haven't
> lived til someone has a failed 2n2222, somwhere on some piece of
> critical hardware, and they issue a GIDEP alert, and then the mission
> assurance folks call you up and ask, "you don't by any chance have
> 2N2222's in your flight hardware do you?".. then there's the whole
> manufacturer and date code hunt.. Looking through the build
> documentation to find out. (or worse yet, if you had decided for some
> reason to use the prototype, which you didn't keep such good records on,
> but which you have photos of, and trying to read the date codes off the
> assembled item with a magnifying glass)
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>
Didier Juges
2010-08-14 22:18:15 UTC
Permalink
Once I had a batch of JANTX 2N2222A (with all the paperwork) that were PNPs. They actually were marked JANTX 2N2222A. This was for a mil job in the 80's. We did not fool around with the mil specs back then.

I was a young engineer then and not all that involved in the process, so I was kept somewhat out of the process that followed. I wish I has seen QA and purchasing explain that one :)

Didier


------------------------
Sent from my BlackBerry Wireless thingy while I do other things...

-----Original Message-----
From: jimlux <jimlux-***@public.gmane.org>
Sender: time-nuts-bounces-***@public.gmane.org
Date: Sat, 14 Aug 2010 14:42:39
To: Discussion of precise time and frequency measurement<time-nuts-***@public.gmane.org>
Reply-To: Discussion of precise time and frequency measurement
<time-nuts-***@public.gmane.org>
Subject: Re: [time-nuts] Simulation

Hal Murray wrote:
>> Line got moved to other side of big ocean. Process got " tweaked" beta is
>> now 4x what it was.
>
> I'm pretty sure that military grade parts have paperwork and processes to
> cover that case. I expect it costs a lot.
>
> I think the same sort of service is available to high volume customers at a
> less than military price.

just so..

In the space business, we call it "traceability to sand"... you haven't
lived til someone has a failed 2n2222, somwhere on some piece of
critical hardware, and they issue a GIDEP alert, and then the mission
assurance folks call you up and ask, "you don't by any chance have
2N2222's in your flight hardware do you?".. then there's the whole
manufacturer and date code hunt.. Looking through the build
documentation to find out. (or worse yet, if you had decided for some
reason to use the prototype, which you didn't keep such good records on,
but which you have photos of, and trying to read the date codes off the
assembled item with a magnifying glass)


_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Mike Feher
2010-08-14 22:38:38 UTC
Permalink
Not that it really matters for this thread, but, the 2N2222A was one of the
most common NPNs and not PNPs. As I recall, the 2N2907A was its PNP
complement. - regards - Mike

Mike B. Feher, N4FS
89 Arnold Blvd.
Howell, NJ, 07731
732-886-5960



-----Original Message-----
From: time-nuts-bounces-***@public.gmane.org [mailto:time-nuts-bounces-***@public.gmane.org] On
Behalf Of Didier Juges
Sent: Saturday, August 14, 2010 6:18 PM
To: Time-Nuts
Subject: Re: [time-nuts] Simulation

Once I had a batch of JANTX 2N2222A (with all the paperwork) that were PNPs.
They actually were marked JANTX 2N2222A. This was for a mil job in the 80's.
We did not fool around with the mil specs back then.

I was a young engineer then and not all that involved in the process, so I
was kept somewhat out of the process that followed. I wish I has seen QA and
purchasing explain that one :)

Didier
Alan Melia
2010-08-14 23:47:46 UTC
Permalink
Surely all this is a case of an engineer being able to
read......specifications :-))
Manufactures specify to sell parts, most of the important parameter are
minimum values, and the range is as wide as it can be. If you want a
parameter "bracketed" then you must specify that when buying and pay the
premium or take the expense of testing incomming batches for sensitive
parameters. I used to give lectures to new engineers on reading
specifications .....and what "Absolute maximum" actually means. Clever
engineers also love using operations that rely on unspecified parameters.
For example using a stock switching diode as a spike quencher in a relay
driver. The usually work (but not always!) but are generally not specified
for that service.

Spice parameters are probably a few "typical" samples of even "the one I
happened to choose to measure"!!

I had a case of some +/-12v transistor logic which made it was into a big
telecoms project. the prototypes worked fine. By the time of bulk
manufacture the supplier of the the main transistor had had several cost
improvement stages. The result was the kit was unreliable. The problem was
that first the base junction were swung to -12v by the "0" logic state and
second from a transistor with a fairly simple round dot geometry emitter,
the device had been replaced by an interdigital high ft chip (it still met
the basic "greater than" specs.)

The interdigital device suffered severe loss of gain after a period of
avalanching at several millamps (I think it also suffered electromigration)
much more than the circular geometry transistors. I think this was due to
the increased emitter periphery length. It was solved by placing a simple
diode in the emitter leg, or a clamp on the base. The engineer had not read,
or not understood the meaning of the Vebmax = 5v parameter, and his
prototype had worked. The production side were not very happy but eventually
were forced to junk thousands of 8inch square pcbs and do a re-layout. This
was in the days before computer simulation !! It might have helped!

Alan G3NYK


----- Original Message -----
From: "jimlux" <jimlux-***@public.gmane.org>
To: "Discussion of precise time and frequency measurement"
<time-nuts-***@public.gmane.org>
Sent: Saturday, August 14, 2010 10:42 PM
Subject: Re: [time-nuts] Simulation


> Hal Murray wrote:
> >> Line got moved to other side of big ocean. Process got " tweaked" beta
is
> >> now 4x what it was.
> >
> > I'm pretty sure that military grade parts have paperwork and processes
to
> > cover that case. I expect it costs a lot.
> >
> > I think the same sort of service is available to high volume customers
at a
> > less than military price.
>
> just so..
>
> In the space business, we call it "traceability to sand"... you haven't
> lived til someone has a failed 2n2222, somwhere on some piece of
> critical hardware, and they issue a GIDEP alert, and then the mission
> assurance folks call you up and ask, "you don't by any chance have
> 2N2222's in your flight hardware do you?".. then there's the whole
> manufacturer and date code hunt.. Looking through the build
> documentation to find out. (or worse yet, if you had decided for some
> reason to use the prototype, which you didn't keep such good records on,
> but which you have photos of, and trying to read the date codes off the
> assembled item with a magnifying glass)
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
Bob Camp
2010-08-15 00:33:12 UTC
Permalink
Hi

Simulation might or might not have helped.

1) Was Vbe breakdown even included in the Spice model
2) If so did it ring bells (rare) or did it just clip without error ( common )
3) Would the same designer who didn't understand it in the first place have seen it clipping at -5 and concluded "looks to be in spec at -5"
4) Would any of it be reviewed in light of the new transistor or was the guy on another project by then

My favorite in the absolute max Vbe category is the typical class C RF amp. Look at the spec, check a few thousand working boards. Scratch head and move on. Lots of reverse bias on the base and they run forever.

Bob



On Aug 14, 2010, at 7:47 PM, "Alan Melia" <alan.melia-***@public.gmane.org> wrote:

> Surely all this is a case of an engineer being able to
> read......specifications :-))
> Manufactures specify to sell parts, most of the important parameter are
> minimum values, and the range is as wide as it can be. If you want a
> parameter "bracketed" then you must specify that when buying and pay the
> premium or take the expense of testing incomming batches for sensitive
> parameters. I used to give lectures to new engineers on reading
> specifications .....and what "Absolute maximum" actually means. Clever
> engineers also love using operations that rely on unspecified parameters.
> For example using a stock switching diode as a spike quencher in a relay
> driver. The usually work (but not always!) but are generally not specified
> for that service.
>
> Spice parameters are probably a few "typical" samples of even "the one I
> happened to choose to measure"!!
>
> I had a case of some +/-12v transistor logic which made it was into a big
> telecoms project. the prototypes worked fine. By the time of bulk
> manufacture the supplier of the the main transistor had had several cost
> improvement stages. The result was the kit was unreliable. The problem was
> that first the base junction were swung to -12v by the "0" logic state and
> second from a transistor with a fairly simple round dot geometry emitter,
> the device had been replaced by an interdigital high ft chip (it still met
> the basic "greater than" specs.)
>
> The interdigital device suffered severe loss of gain after a period of
> avalanching at several millamps (I think it also suffered electromigration)
> much more than the circular geometry transistors. I think this was due to
> the increased emitter periphery length. It was solved by placing a simple
> diode in the emitter leg, or a clamp on the base. The engineer had not read,
> or not understood the meaning of the Vebmax = 5v parameter, and his
> prototype had worked. The production side were not very happy but eventually
> were forced to junk thousands of 8inch square pcbs and do a re-layout. This
> was in the days before computer simulation !! It might have helped!
>
> Alan G3NYK
>
>
> ----- Original Message -----
> From: "jimlux" <jimlux-***@public.gmane.org>
> To: "Discussion of precise time and frequency measurement"
> <time-nuts-***@public.gmane.org>
> Sent: Saturday, August 14, 2010 10:42 PM
> Subject: Re: [time-nuts] Simulation
>
>
>> Hal Murray wrote:
>>>> Line got moved to other side of big ocean. Process got " tweaked" beta
> is
>>>> now 4x what it was.
>>>
>>> I'm pretty sure that military grade parts have paperwork and processes
> to
>>> cover that case. I expect it costs a lot.
>>>
>>> I think the same sort of service is available to high volume customers
> at a
>>> less than military price.
>>
>> just so..
>>
>> In the space business, we call it "traceability to sand"... you haven't
>> lived til someone has a failed 2n2222, somwhere on some piece of
>> critical hardware, and they issue a GIDEP alert, and then the mission
>> assurance folks call you up and ask, "you don't by any chance have
>> 2N2222's in your flight hardware do you?".. then there's the whole
>> manufacturer and date code hunt.. Looking through the build
>> documentation to find out. (or worse yet, if you had decided for some
>> reason to use the prototype, which you didn't keep such good records on,
>> but which you have photos of, and trying to read the date codes off the
>> assembled item with a magnifying glass)
>>
>>
>> _______________________________________________
>> time-nuts mailing list -- time-nuts-***@public.gmane.org
>> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
Alan Melia
2010-08-15 10:36:48 UTC
Permalink
Hi Bob yes that was a point raised by Prof Nat Sokal after I published some
data, or rather he pointed out it happened in RF amps. I guess if you take
an used PA transistor out of service and measure it you might find the base
emitter junction very leaky, but does few mA of leakage matter so much in a
low impedance high drive power circuit.
Reliability asks "does it do the job it was designed for" not "is it as good
as new now"

Alan
G3NYK
----- Original Message -----
From: "Bob Camp" <lists-***@public.gmane.org>
To: "Discussion of precise time and frequency measurement"
<time-nuts-***@public.gmane.org>
Sent: Sunday, August 15, 2010 1:33 AM
Subject: Re: [time-nuts] Simulation


> Hi
>
> Simulation might or might not have helped.
>
> 1) Was Vbe breakdown even included in the Spice model
> 2) If so did it ring bells (rare) or did it just clip without error (
common )
> 3) Would the same designer who didn't understand it in the first place
have seen it clipping at -5 and concluded "looks to be in spec at -5"
> 4) Would any of it be reviewed in light of the new transistor or was the
guy on another project by then
>
> My favorite in the absolute max Vbe category is the typical class C RF
amp. Look at the spec, check a few thousand working boards. Scratch head and
move on. Lots of reverse bias on the base and they run forever.
>
> Bob
J. Forster
2010-08-15 22:17:04 UTC
Permalink
It depends on whether the leakage continues to rise or stabilizes after a
"burn in" period.

-John

============


> Hi Bob yes that was a point raised by Prof Nat Sokal after I published
> some
> data, or rather he pointed out it happened in RF amps. I guess if you take
> an used PA transistor out of service and measure it you might find the
> base
> emitter junction very leaky, but does few mA of leakage matter so much in
> a
> low impedance high drive power circuit.
> Reliability asks "does it do the job it was designed for" not "is it as
> good
> as new now"
>
> Alan
> G3NYK
> ----- Original Message -----
> From: "Bob Camp" <lists-***@public.gmane.org>
> To: "Discussion of precise time and frequency measurement"
> <time-nuts-***@public.gmane.org>
> Sent: Sunday, August 15, 2010 1:33 AM
> Subject: Re: [time-nuts] Simulation
>
>
>> Hi
>>
>> Simulation might or might not have helped.
>>
>> 1) Was Vbe breakdown even included in the Spice model
>> 2) If so did it ring bells (rare) or did it just clip without error (
> common )
>> 3) Would the same designer who didn't understand it in the first place
> have seen it clipping at -5 and concluded "looks to be in spec at -5"
>> 4) Would any of it be reviewed in light of the new transistor or was the
> guy on another project by then
>>
>> My favorite in the absolute max Vbe category is the typical class C RF
> amp. Look at the spec, check a few thousand working boards. Scratch head
> and
> move on. Lots of reverse bias on the base and they run forever.
>>
>> Bob
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>
jimlux
2010-08-16 00:16:18 UTC
Permalink
J. Forster wrote:
> It depends on whether the leakage continues to rise or stabilizes after a
> "burn in" period.
>
> -John
>
> ============
>
>
>> Hi Bob yes that was a point raised by Prof Nat Sokal after I published
>> some
>> data, or rather he pointed out it happened in RF amps. I guess if you take
>> an used PA transistor out of service and measure it you might find the
>> base
>> emitter junction very leaky, but does few mA of leakage matter so much in
>> a
>> low impedance high drive power circuit.
>> Reliability asks "does it do the job it was designed for" not "is it as
>> good
>> as new now"
>>
>> Alan
>
We get into the argument about "still works ok in the circuit" vs
"doesn't meet databook specs" all the time at work. To some folks, "not
meet datasheet" = "failure", while if you have a circuit that needs a
gain of 10, and the part has a gain of 1000, and degrades to 500, it's
hardly failed.

And rarely, do you have the budget or time to do a real "life test" to
prove it experimentally.


In radiation environments, it's more of a continuous aging effect.. more
dose, more leakage. And what drives the conflict between designer and
reliability guys is that the effect isn't particularly predictable,
particularly between lots (because it's not something controlled in the
process)

(which makes life testing all that much more fun)
Magnus Danielson
2010-08-16 00:43:54 UTC
Permalink
On 08/16/2010 02:16 AM, jimlux wrote:
> We get into the argument about "still works ok in the circuit" vs
> "doesn't meet databook specs" all the time at work. To some folks, "not
> meet datasheet" = "failure", while if you have a circuit that needs a
> gain of 10, and the part has a gain of 1000, and degrades to 500, it's
> hardly failed.
>
> And rarely, do you have the budget or time to do a real "life test" to
> prove it experimentally.
>
>
> In radiation environments, it's more of a continuous aging effect.. more
> dose, more leakage. And what drives the conflict between designer and
> reliability guys is that the effect isn't particularly predictable,
> particularly between lots (because it's not something controlled in the
> process)
>
> (which makes life testing all that much more fun)

But armed with the knowledge of what parameters do degrade, you may do
simulations of various grades of degradation and show that with the
current knowledge of degradation and assumptions on its effects and
degrees, it is reasonable to expect functionality.

Right?

Simulation can be off assistance, if used wisely...
(or a tool of self deception if not used wisely)

Cheers,
Magnus
G***@public.gmane.org
2010-08-14 22:51:57 UTC
Permalink
In a message dated 14/08/2010 23:39:20 GMT Daylight Time, mfeher-Tjqmpovjv17QT0dZR+***@public.gmane.org
writes:

Not that it really matters for this thread, but, the 2N2222A was one of the
most common NPNs and not PNPs. As I recall, the 2N2907A was its PNP
complement. - regards - Mike


------------------
Wasn't that exactly the point that was being made?:-)

regards

Nigel
GM8PZR
Mike Feher
2010-08-15 00:45:06 UTC
Permalink
Yes, I guess it was. I have been in the military business since 1967, and,
certainly seen my share. Besides all of the screw ups, there was one that
really took the cake. I once worked for a company that had to build a radio
that was strictly build-to-print. The original drawing had a mil-spec yellow
band resistor of value X in the front end. Well, with that resistor the NF
could not be met. They could meet it with a value Y. Pleading with the
government reps made no difference. Finally, the head of the company QA
department wrote a letter to AB and actually asked them to provide resistors
with value Y, but, color code them with the value X. Everyone signed off on
it, and, everything was fine. I still have a copy of the letter someplace. I
just got back from Fort Bragg where I was involved in certifying a system at
Ka band. The antenna is a 30 footer and had only a 10 degree elevation look
angle to see the bird needed. Well, guess what? There are three 30 foot
dishes in the system, the other two being Ku, and this antenna was between
them looking right through one of the Ku antennas. Really messed with the
patterns. Now, based on my input they are changing the feed assembly and all
of the RF between the two antennas to prevent the blockage. It will take a
month. I am sure I will be there again. A few simple examples of hundreds.
- Regards - Mike

Mike B. Feher, N4FS
89 Arnold Blvd.
Howell, NJ, 07731
732-886-5960




-----Original Message-----
From: time-nuts-bounces-***@public.gmane.org [mailto:time-nuts-bounces-***@public.gmane.org] On
Behalf Of GandalfG8-***@public.gmane.org
Sent: Saturday, August 14, 2010 6:52 PM
To: time-nuts-***@public.gmane.org
Subject: Re: [time-nuts] Simulation


In a message dated 14/08/2010 23:39:20 GMT Daylight Time, mfeher-Tjqmpovjv17QT0dZR+***@public.gmane.org
writes:

Not that it really matters for this thread, but, the 2N2222A was one of the
most common NPNs and not PNPs. As I recall, the 2N2907A was its PNP
complement. - regards - Mike


------------------
Wasn't that exactly the point that was being made?:-)

regards

Nigel
GM8PZR
_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
J. Forster
2010-08-15 01:42:48 UTC
Permalink
?? The yellow banded R means established reliability. I see no reason why
the NF should be any different then one w/o the yellow band. They are the
same part, only one is tested more.

Not white band perchance?

-John

===========


> Yes, I guess it was. I have been in the military business since 1967, and,
> certainly seen my share. Besides all of the screw ups, there was one that
> really took the cake. I once worked for a company that had to build a
> radio
> that was strictly build-to-print. The original drawing had a mil-spec
> yellow
> band resistor of value X in the front end. Well, with that resistor the NF
> could not be met. They could meet it with a value Y. Pleading with the
> government reps made no difference. Finally, the head of the company QA
> department wrote a letter to AB and actually asked them to provide
> resistors
> with value Y, but, color code them with the value X. Everyone signed off
> on
> it, and, everything was fine. I still have a copy of the letter someplace.
> I
> just got back from Fort Bragg where I was involved in certifying a system
> at
> Ka band. The antenna is a 30 footer and had only a 10 degree elevation
> look
> angle to see the bird needed. Well, guess what? There are three 30 foot
> dishes in the system, the other two being Ku, and this antenna was between
> them looking right through one of the Ku antennas. Really messed with the
> patterns. Now, based on my input they are changing the feed assembly and
> all
> of the RF between the two antennas to prevent the blockage. It will take a
> month. I am sure I will be there again. A few simple examples of hundreds.
> - Regards - Mike
>
> Mike B. Feher, N4FS
> 89 Arnold Blvd.
> Howell, NJ, 07731
> 732-886-5960
>
>
>
>
> -----Original Message-----
> From: time-nuts-bounces-***@public.gmane.org [mailto:time-nuts-bounces-***@public.gmane.org] On
> Behalf Of GandalfG8-***@public.gmane.org
> Sent: Saturday, August 14, 2010 6:52 PM
> To: time-nuts-***@public.gmane.org
> Subject: Re: [time-nuts] Simulation
>
>
> In a message dated 14/08/2010 23:39:20 GMT Daylight Time,
> mfeher-Tjqmpovjv17QT0dZR+***@public.gmane.org
> writes:
>
> Not that it really matters for this thread, but, the 2N2222A was one of
> the
> most common NPNs and not PNPs. As I recall, the 2N2907A was its PNP
> complement. - regards - Mike
>
>
> ------------------
> Wasn't that exactly the point that was being made?:-)
>
> regards
>
> Nigel
> GM8PZR
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>
Mike Feher
2010-08-15 01:50:59 UTC
Permalink
I only mentioned the yellow band because of reliability. Seems like the
original resistor was 220 ohms and the one that actually met the required NF
was 330 (or the other way around). So, it was not the yellow band that had
to be changed. - Mike

Mike B. Feher, N4FS
89 Arnold Blvd.
Howell, NJ, 07731
732-886-5960




-----Original Message-----
From: time-nuts-bounces-***@public.gmane.org [mailto:time-nuts-bounces-***@public.gmane.org] On
Behalf Of J. Forster
Sent: Saturday, August 14, 2010 9:43 PM
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] Simulation

?? The yellow banded R means established reliability. I see no reason why
the NF should be any different then one w/o the yellow band. They are the
same part, only one is tested more.

Not white band perchance?

-John

===========


> Yes, I guess it was. I have been in the military business since 1967, and,
> certainly seen my share. Besides all of the screw ups, there was one that
> really took the cake. I once worked for a company that had to build a
> radio
> that was strictly build-to-print. The original drawing had a mil-spec
> yellow
> band resistor of value X in the front end. Well, with that resistor the NF
> could not be met. They could meet it with a value Y. Pleading with the
> government reps made no difference. Finally, the head of the company QA
> department wrote a letter to AB and actually asked them to provide
> resistors
> with value Y, but, color code them with the value X. Everyone signed off
> on
> it, and, everything was fine. I still have a copy of the letter someplace.
> I
> just got back from Fort Bragg where I was involved in certifying a system
> at
> Ka band. The antenna is a 30 footer and had only a 10 degree elevation
> look
> angle to see the bird needed. Well, guess what? There are three 30 foot
> dishes in the system, the other two being Ku, and this antenna was between
> them looking right through one of the Ku antennas. Really messed with the
> patterns. Now, based on my input they are changing the feed assembly and
> all
> of the RF between the two antennas to prevent the blockage. It will take a
> month. I am sure I will be there again. A few simple examples of hundreds.
> - Regards - Mike
>
> Mike B. Feher, N4FS
> 89 Arnold Blvd.
> Howell, NJ, 07731
> 732-886-5960
>
>
>
>
> -----Original Message-----
> From: time-nuts-bounces-***@public.gmane.org [mailto:time-nuts-bounces-***@public.gmane.org] On
> Behalf Of GandalfG8-***@public.gmane.org
> Sent: Saturday, August 14, 2010 6:52 PM
> To: time-nuts-***@public.gmane.org
> Subject: Re: [time-nuts] Simulation
>
>
> In a message dated 14/08/2010 23:39:20 GMT Daylight Time,
> mfeher-Tjqmpovjv17QT0dZR+***@public.gmane.org
> writes:
>
> Not that it really matters for this thread, but, the 2N2222A was one of
> the
> most common NPNs and not PNPs. As I recall, the 2N2907A was its PNP
> complement. - regards - Mike
>
>
> ------------------
> Wasn't that exactly the point that was being made?:-)
>
> regards
>
> Nigel
> GM8PZR
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>



_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
J. Forster
2010-08-15 02:01:36 UTC
Permalink
Somebody read the resistor code backwards then? Easy enough if you don't
know what you're doing w/ Established Reliability parts.

-John

=============


> I only mentioned the yellow band because of reliability. Seems like the
> original resistor was 220 ohms and the one that actually met the required
> NF
> was 330 (or the other way around). So, it was not the yellow band that had
> to be changed. - Mike
>
> Mike B. Feher, N4FS
> 89 Arnold Blvd.
> Howell, NJ, 07731
> 732-886-5960
>
>
>
>
> -----Original Message-----
> From: time-nuts-bounces-***@public.gmane.org [mailto:time-nuts-bounces-***@public.gmane.org] On
> Behalf Of J. Forster
> Sent: Saturday, August 14, 2010 9:43 PM
> To: Discussion of precise time and frequency measurement
> Subject: Re: [time-nuts] Simulation
>
> ?? The yellow banded R means established reliability. I see no reason why
> the NF should be any different then one w/o the yellow band. They are the
> same part, only one is tested more.
>
> Not white band perchance?
>
> -John
>
> ===========
>
>
>> Yes, I guess it was. I have been in the military business since 1967,
>> and,
>> certainly seen my share. Besides all of the screw ups, there was one
>> that
>> really took the cake. I once worked for a company that had to build a
>> radio
>> that was strictly build-to-print. The original drawing had a mil-spec
>> yellow
>> band resistor of value X in the front end. Well, with that resistor the
>> NF
>> could not be met. They could meet it with a value Y. Pleading with the
>> government reps made no difference. Finally, the head of the company QA
>> department wrote a letter to AB and actually asked them to provide
>> resistors
>> with value Y, but, color code them with the value X. Everyone signed off
>> on
>> it, and, everything was fine. I still have a copy of the letter
>> someplace.
>> I
>> just got back from Fort Bragg where I was involved in certifying a
>> system
>> at
>> Ka band. The antenna is a 30 footer and had only a 10 degree elevation
>> look
>> angle to see the bird needed. Well, guess what? There are three 30 foot
>> dishes in the system, the other two being Ku, and this antenna was
>> between
>> them looking right through one of the Ku antennas. Really messed with
>> the
>> patterns. Now, based on my input they are changing the feed assembly and
>> all
>> of the RF between the two antennas to prevent the blockage. It will take
>> a
>> month. I am sure I will be there again. A few simple examples of
>> hundreds.
>> - Regards - Mike
>>
>> Mike B. Feher, N4FS
>> 89 Arnold Blvd.
>> Howell, NJ, 07731
>> 732-886-5960
>>
>>
>>
>>
>> -----Original Message-----
>> From: time-nuts-bounces-***@public.gmane.org [mailto:time-nuts-bounces-***@public.gmane.org] On
>> Behalf Of GandalfG8-***@public.gmane.org
>> Sent: Saturday, August 14, 2010 6:52 PM
>> To: time-nuts-***@public.gmane.org
>> Subject: Re: [time-nuts] Simulation
>>
>>
>> In a message dated 14/08/2010 23:39:20 GMT Daylight Time,
>> mfeher-Tjqmpovjv17QT0dZR+***@public.gmane.org
>> writes:
>>
>> Not that it really matters for this thread, but, the 2N2222A was one of
>> the
>> most common NPNs and not PNPs. As I recall, the 2N2907A was its PNP
>> complement. - regards - Mike
>>
>>
>> ------------------
>> Wasn't that exactly the point that was being made?:-)
>>
>> regards
>>
>> Nigel
>> GM8PZR
>> _______________________________________________
>> time-nuts mailing list -- time-nuts-***@public.gmane.org
>> To unsubscribe, go to
>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
>>
>>
>> _______________________________________________
>> time-nuts mailing list -- time-nuts-***@public.gmane.org
>> To unsubscribe, go to
>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
>>
>>
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>
Bob Camp
2010-08-15 01:55:40 UTC
Permalink
Hi

I think it was the value that changed. Somebody typo'd 10k at 10 ohms ....

Bob




On Aug 14, 2010, at 9:42 PM, "J. Forster" <jfor-***@public.gmane.org> wrote:

> ?? The yellow banded R means established reliability. I see no reason why
> the NF should be any different then one w/o the yellow band. They are the
> same part, only one is tested more.
>
> Not white band perchance?
>
> -John
>
> ===========
>
>
>> Yes, I guess it was. I have been in the military business since 1967, and,
>> certainly seen my share. Besides all of the screw ups, there was one that
>> really took the cake. I once worked for a company that had to build a
>> radio
>> that was strictly build-to-print. The original drawing had a mil-spec
>> yellow
>> band resistor of value X in the front end. Well, with that resistor the NF
>> could not be met. They could meet it with a value Y. Pleading with the
>> government reps made no difference. Finally, the head of the company QA
>> department wrote a letter to AB and actually asked them to provide
>> resistors
>> with value Y, but, color code them with the value X. Everyone signed off
>> on
>> it, and, everything was fine. I still have a copy of the letter someplace.
>> I
>> just got back from Fort Bragg where I was involved in certifying a system
>> at
>> Ka band. The antenna is a 30 footer and had only a 10 degree elevation
>> look
>> angle to see the bird needed. Well, guess what? There are three 30 foot
>> dishes in the system, the other two being Ku, and this antenna was between
>> them looking right through one of the Ku antennas. Really messed with the
>> patterns. Now, based on my input they are changing the feed assembly and
>> all
>> of the RF between the two antennas to prevent the blockage. It will take a
>> month. I am sure I will be there again. A few simple examples of hundreds.
>> - Regards - Mike
>>
>> Mike B. Feher, N4FS
>> 89 Arnold Blvd.
>> Howell, NJ, 07731
>> 732-886-5960
>>
>>
>>
>>
>> -----Original Message-----
>> From: time-nuts-bounces-***@public.gmane.org [mailto:time-nuts-bounces-***@public.gmane.org] On
>> Behalf Of GandalfG8-***@public.gmane.org
>> Sent: Saturday, August 14, 2010 6:52 PM
>> To: time-nuts-***@public.gmane.org
>> Subject: Re: [time-nuts] Simulation
>>
>>
>> In a message dated 14/08/2010 23:39:20 GMT Daylight Time,
>> mfeher-Tjqmpovjv17QT0dZR+***@public.gmane.org
>> writes:
>>
>> Not that it really matters for this thread, but, the 2N2222A was one of
>> the
>> most common NPNs and not PNPs. As I recall, the 2N2907A was its PNP
>> complement. - regards - Mike
>>
>>
>> ------------------
>> Wasn't that exactly the point that was being made?:-)
>>
>> regards
>>
>> Nigel
>> GM8PZR
>> _______________________________________________
>> time-nuts mailing list -- time-nuts-***@public.gmane.org
>> To unsubscribe, go to
>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
>>
>>
>> _______________________________________________
>> time-nuts mailing list -- time-nuts-***@public.gmane.org
>> To unsubscribe, go to
>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
>>
>>
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
Hal Murray
2010-09-28 02:20:21 UTC
Permalink
> Bottom line appears to be - fine for day to day checks. I would not trust
> any of these chips to be long term stable to sub 10 mK levels.

I think the temperature correction is only used in holdover.

What's the time constant on learning the temperature profile of the OCXO? As
long as the aging in the temperature sensor is slow relative to that its
(long term) stability shouldn't matter much.



--
These are my opinions, not necessarily my employer's. I hate spam.
Bob Camp
2010-09-28 02:37:54 UTC
Permalink
Hi

Based only on the fact that they never fixed the problem with the chip - I don't think they do a lot of fine grain temperature correction. They certainly went on shipping the units as spec compliant.

Bob



On Sep 27, 2010, at 10:20 PM, Hal Murray <hmurray-8cQiHa/C+6Go9G/***@public.gmane.org> wrote:

>
>> Bottom line appears to be - fine for day to day checks. I would not trust
>> any of these chips to be long term stable to sub 10 mK levels.
>
> I think the temperature correction is only used in holdover.
>
> What's the time constant on learning the temperature profile of the OCXO? As
> long as the aging in the temperature sensor is slow relative to that its
> (long term) stability shouldn't matter much.
>
>
>
> --
> These are my opinions, not necessarily my employer's. I hate spam.
>
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
Mark Sims
2010-09-28 03:39:30 UTC
Permalink
Long term stability is pretty much totally irrelevant for Tbolts.  What is important is resolution of the temperature readings.  The Tbolt responds much more to changes in temperature,  not absolute temperature.  

----------------------------------------
Since few of us have an oil bath to check the thermometer chips with, it's tough to really know what the long term stability is
Mark J. Blair
2010-09-28 05:23:24 UTC
Permalink
What is the purpose of the temperature sensor chip on the PCB, anyway? Isn't the temperature inside the OCXO much more important?

--
Mark J. Blair, NF6X <nf6x-/***@public.gmane.org>
Web page: http://www.nf6x.net/
GnuPG public key available from my web page.
b***@public.gmane.org
2010-09-28 05:32:11 UTC
Permalink
Instead of reacting to a change in the OCXO, the control software can be
proactive wrt a change that is heading towards the inside of the oven.

--

Björn

> What is the purpose of the temperature sensor chip on the PCB, anyway?
> Isn't the temperature inside the OCXO much more important?
>
> --
> Mark J. Blair, NF6X <nf6x-/***@public.gmane.org>
> Web page: http://www.nf6x.net/
> GnuPG public key available from my web page.
>
>
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
russell
2010-09-28 05:46:08 UTC
Permalink
Isn't the temperature inside the OCXO oven held at a set point (greater than
ambient) with it own independent thermostat? The DS1620 thermometer only
reads ambient temperature. In this case amibent means inside the Tbolt
enclosure.

If so, what does the Lady Heather "t t" command do? It prompts you to
"enter desired operating temperature". What could it control?

Russell (newbie)


----- Original Message -----
From: <bg-***@public.gmane.org>
To: "Discussion of precise time and frequency measurement"
<time-nuts-***@public.gmane.org>
Sent: Tuesday, September 28, 2010 12:32 AM
Subject: Re: [time-nuts] antennas


Instead of reacting to a change in the OCXO, the control software can be
proactive wrt a change that is heading towards the inside of the oven.

--

Björn

> What is the purpose of the temperature sensor chip on the PCB, anyway?
> Isn't the temperature inside the OCXO much more important?
>
> --
> Mark J. Blair, NF6X <nf6x-/***@public.gmane.org>
> Web page: http://www.nf6x.net/
> GnuPG public key available from my web page.
>
>
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>



_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Bob Camp
2010-09-28 10:58:23 UTC
Permalink
Hi

The TBolt firmware does not interact with the ocxo's temperature controller.

Bob



On Sep 28, 2010, at 1:46 AM, "russell" <***@austin.rr.com> wrote:

> Isn't the temperature inside the OCXO oven held at a set point (greater than ambient) with it own independent thermostat? The DS1620 thermometer only reads ambient temperature. In this case amibent means inside the Tbolt enclosure.
>
> If so, what does the Lady Heather "t t" command do? It prompts you to "enter desired operating temperature". What could it control?
>
> Russell (newbie)
>
>
> ----- Original Message ----- From: <***@lysator.liu.se>
> To: "Discussion of precise time and frequency measurement" <time-***@febo.com>
> Sent: Tuesday, September 28, 2010 12:32 AM
> Subject: Re: [time-nuts] antennas
>
>
> Instead of reacting to a change in the OCXO, the control software can be
> proactive wrt a change that is heading towards the inside of the oven.
>
> --
>
> Björn
>
>> What is the purpose of the temperature sensor chip on the PCB, anyway?
>> Isn't the temperature inside the OCXO much more important?
>>
>> --
>> Mark J. Blair, NF6X <***@nf6x.net>
>> Web page: http://www.nf6x.net/
>> GnuPG public key available from my web page.
>>
>>
>>
>>
>>
>> _______________________________________________
>> time-nuts mailing list -- time-***@febo.com
>> To unsubscribe, go to
>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
>>
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-***@febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-***@febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>

_______________________________________________
time-nuts mailing list -- time-***@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and fol
Hal Murray
2010-10-23 04:44:45 UTC
Permalink
> Then you hope that there's at least one floppy drive in the universe that
> will load what you *hope* is the right software for the programmer.

If anybody ever needs a working floppy drive, I have several that that I'm
not using. They came in refurbished PCs. I expect they work, but I haven't
tested them.


> I'm having a tough enough time finding a working example of a PIC programmer
> (with socket) running around the basement here. I have found two so far that
> I believe died a long time ago ....

There are two interesting areas with PROM programmers. One is the hardware
side. Old chips used strange voltage levels and/or finicky timings. The
other is the software to drive them. Another possible/likely problem is
finding documentation for the programming recipe. (Old was before pdf, so
even if the manufacturer gave out the info it probably isn't on the web.)

Most modern chips are much easier to program. You talk to them with TTL
level signals. (It might take a high voltage on one pin at reset time to
kick them into programming mode.) The timing is internal and the programming
software is told about it at the protocol level. So I expect a future hacker
could program a way-old PIC as long as they can find the data sheet.
(Admittedly, the programming recipe may be hidden off in a separate document.)

I haven't done it, but a friend/co-worker has written code to program Atmel
AVRs and ARMs. I'm pretty sure I could write similar code. I'm not sure how
long that would take. Admittedly, he is a lot smarter than I am. Perhaps my
confidence level is unwarranted. If so, I expect there is a good chance that
somebody on this list could/would do it.



--
These are my opinions, not necessarily my employer's. I hate spam.
bownes
2010-10-23 15:09:15 UTC
Permalink
Precicesly why I have a basement shelf or two dedicated to old datebooks. :)



On Oct 23, 2010, at 12:44 AM, Hal Murray <hmurray-8cQiHa/C+6Go9G/***@public.gmane.org> wrote:

>
Mark Sims
2010-10-23 15:19:25 UTC
Permalink
I make backup images of all my EPROMs and even bipolar devices.  I even built a device for reverse engineering secured PALs.  I have a fully configured Data I/O Unisite for programming.  This machine with all the device adapters, etc cost somebody well over $100,000

The Unisite is probably the most capable, robust, and expensive programmer ever built (and quite a boat anchor, itself).  It's a real shame they stopped adding new devices last year.  The 2900 and 3900's are smaller but don't do a few parts (mostly odd bipolar proms).  External interface is a standard RS232 terminal.  They do boot off of floppies (720kbfor the Unisite, 1.44Mb for the others).  There are also units with internal hard drives.  The floppy images can be burned from a CD  (all my computers still have floppy drives,  some 5 1/4",  one has 8 inch).  The last software release spans 9 diskettes.

I have accumulated a few spare machines when I bought some units just to get some oddball package adapter that I did not have.  Email me if interested...
Ziggy
2010-10-23 19:05:22 UTC
Permalink
I don't know if embedded images will make it through to the list, but
can someone explain the behavior indicated in this graph? This is from
an auction and it doesn't look at all like other graphs that I've seen.
It's only for a 12 min span, but others with a short span aren't similar.



If the included graph doesn't make it to the list, please take a look at
the auction (150508234942). I'd like to understand more of what I am am
seeing there.

Thanks!
Ziggy

Please wait
Image not available
Magnus Danielson
2010-10-23 19:28:39 UTC
Permalink
Hi Ziggy,

On 10/23/2010 09:05 PM, Ziggy wrote:
> I don't know if embedded images will make it through to the list, but
> can someone explain the behavior indicated in this graph? This is from
> an auction and it doesn't look at all like other graphs that I've seen.
> It's only for a 12 min span, but others with a short span aren't similar.
>
> If the included graph doesn't make it to the list, please take a look at
> the auction (150508234942). I'd like to understand more of what I am am
> seeing there.

I assume you refer to the yellow curve...

Isn't that the average from the temp-sensor, being the modern
coarse-stepped variant as things heats up it looks like the
step-response of a one pole low-pass filter.

Cheers,
Magnus
Bob Camp
2010-10-23 19:31:35 UTC
Permalink
Hi

If you look at the fine print on the yellow graph, it's running right at the limit of the "bad" temp sensor. What you are seeing is normal stepping / averaging on the low resolution sensor.

Bob


On Oct 23, 2010, at 3:28 PM, Magnus Danielson wrote:

> Hi Ziggy,
>
> On 10/23/2010 09:05 PM, Ziggy wrote:
>> I don't know if embedded images will make it through to the list, but
>> can someone explain the behavior indicated in this graph? This is from
>> an auction and it doesn't look at all like other graphs that I've seen.
>> It's only for a 12 min span, but others with a short span aren't similar.
>>
>> If the included graph doesn't make it to the list, please take a look at
>> the auction (150508234942). I'd like to understand more of what I am am
>> seeing there.
>
> I assume you refer to the yellow curve...
>
> Isn't that the average from the temp-sensor, being the modern coarse-stepped variant as things heats up it looks like the step-response of a one pole low-pass filter.
>
> Cheers,
> Magnus
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
Ziggy
2010-10-23 21:59:46 UTC
Permalink
I did note that it was the temp sensor, but the behavior was clearly
different. I guess my earlier search terms weren't good enough to reveal
this info about the sensor differences in the T'bolts. I've done some
further digging and now have the scoop on these DS1620 changes, etc.
Other than pretty graphs, it looks like the difference between units
using one vs. the other is a (relatively) minor difference in pps
jitter. Also that for those interested enough, there have been plenty of
folks that have swapped the sensor. Thanks!

Ziggy

On 10/23/2010 3:31 PM, Bob Camp wrote:
> Hi
>
> If you look at the fine print on the yellow graph, it's running right at the limit of the "bad" temp sensor. What you are seeing is normal stepping / averaging on the low resolution sensor.
>
> Bob
>
>
> On Oct 23, 2010, at 3:28 PM, Magnus Danielson wrote:
>
>> Hi Ziggy,
>>
>> On 10/23/2010 09:05 PM, Ziggy wrote:
>>> I don't know if embedded images will make it through to the list, but
>>> can someone explain the behavior indicated in this graph? This is from
>>> an auction and it doesn't look at all like other graphs that I've seen.
>>> It's only for a 12 min span, but others with a short span aren't similar.
>>>
>>> If the included graph doesn't make it to the list, please take a look at
>>> the auction (150508234942). I'd like to understand more of what I am am
>>> seeing there.
>> I assume you refer to the yellow curve...
>>
>> Isn't that the average from the temp-sensor, being the modern coarse-stepped variant as things heats up it looks like the step-response of a one pole low-pass filter.
>>
>> Cheers,
>> Magnus
>>
>> _______________________________________________
>> time-nuts mailing list -- time-nuts-***@public.gmane.org
>> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
Heathkid
2010-10-23 20:30:17 UTC
Permalink
Backup images are fine... but has anyone considered or tried to contact the
original programmers to get the actual code used? I'm sure there wouldn't
be any reason someone would still consider 30+ year old code a "trade
secret" and if one had the original code... could reasonably replicate an
old programmed chip with a newer one. Just a thought.

----- Original Message -----
From: "Mark Sims" <holrum-***@public.gmane.org>
To: <time-nuts-***@public.gmane.org>
Sent: Saturday, October 23, 2010 11:19 AM
Subject: [time-nuts] Maintaining boatanchors (was Capacitor Failures)



I make backup images of all my EPROMs and even bipolar devices. I even built
a device for reverse engineering secured PALs. I have a fully configured
Data I/O Unisite for programming. This machine with all the device adapters,
etc cost somebody well over $100,000

The Unisite is probably the most capable, robust, and expensive programmer
ever built (and quite a boat anchor, itself). It's a real shame they stopped
adding new devices last year. The 2900 and 3900's are smaller but don't do a
few parts (mostly odd bipolar proms). External interface is a standard RS232
terminal. They do boot off of floppies (720kbfor the Unisite, 1.44Mb for the
others). There are also units with internal hard drives. The floppy images
can be burned from a CD (all my computers still have floppy drives, some 5
1/4", one has 8 inch). The last software release spans 9 diskettes.

I have accumulated a few spare machines when I bought some units just to get
some oddball package adapter that I did not have. Email me if interested...



_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Bob Camp
2010-10-23 20:58:49 UTC
Permalink
Hi

I've been down that road a couple of times. You get to a point where everyone involved does indeed agree that "it's not a secret" anymore. Going the final step and actually getting permission to hand out the code is often impossible. You get into a "nobody has the authority to approve that" hassle.

Bob

On Oct 23, 2010, at 4:30 PM, Heathkid wrote:

> Backup images are fine... but has anyone considered or tried to contact the original programmers to get the actual code used? I'm sure there wouldn't be any reason someone would still consider 30+ year old code a "trade secret" and if one had the original code... could reasonably replicate an old programmed chip with a newer one. Just a thought.
>
> ----- Original Message ----- From: "Mark Sims" <holrum-***@public.gmane.org>
> To: <time-nuts-***@public.gmane.org>
> Sent: Saturday, October 23, 2010 11:19 AM
> Subject: [time-nuts] Maintaining boatanchors (was Capacitor Failures)
>
>
>
> I make backup images of all my EPROMs and even bipolar devices. I even built a device for reverse engineering secured PALs. I have a fully configured Data I/O Unisite for programming. This machine with all the device adapters, etc cost somebody well over $100,000
>
> The Unisite is probably the most capable, robust, and expensive programmer ever built (and quite a boat anchor, itself). It's a real shame they stopped adding new devices last year. The 2900 and 3900's are smaller but don't do a few parts (mostly odd bipolar proms). External interface is a standard RS232 terminal. They do boot off of floppies (720kbfor the Unisite, 1.44Mb for the others). There are also units with internal hard drives. The floppy images can be burned from a CD (all my computers still have floppy drives, some 5 1/4", one has 8 inch). The last software release spans 9 diskettes.
>
> I have accumulated a few spare machines when I bought some units just to get some oddball package adapter that I did not have. Email me if interested...
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
Charles P. Steinmetz
2010-10-23 21:29:07 UTC
Permalink
Bob wrote:

>I've been down that road a couple of times. You get to a point where
>everyone involved does indeed agree that "it's not a secret"
>anymore. Going the final step and actually getting permission to
>hand out the code is often impossible. You get into a "nobody has
>the authority to approve that" hassle.

Approve it? I bet most manufacturers can't even FIND the code for
equipment designed more than 25 years ago. Note that HP has had to
rely on the kindness of strangers for copies of its older manuals.

Best regards,

Charles
J. Forster
2010-10-23 21:44:51 UTC
Permalink
Very true, except it's more like 5-10 years.

-John

==============


> Bob wrote:
>
>>I've been down that road a couple of times. You get to a point where
>>everyone involved does indeed agree that "it's not a secret"
>>anymore. Going the final step and actually getting permission to
>>hand out the code is often impossible. You get into a "nobody has
>>the authority to approve that" hassle.
>
> Approve it? I bet most manufacturers can't even FIND the code for
> equipment designed more than 25 years ago. Note that HP has had to
> rely on the kindness of strangers for copies of its older manuals.
>
> Best regards,
>
> Charles
>
>
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>
David I. Emery
2010-10-24 03:21:33 UTC
Permalink
On Sat, Oct 23, 2010 at 02:44:51PM -0700, J. Forster wrote:
> Very true, except it's more like 5-10 years.

These days John is absolutely right... likely none of the
developers, none of the equipment, perhaps not even the corporate
shell of the division or department that designed the product and
wrote the software survives. Probably the source code was thrown
out with the old servers that were sold for scrap... or just carted off
to be shredded with all the other paper and electronic records...

Horror stories abound about organizations that need to make some
minor patch or change to source code of a popular product for some
important customer even just a few years after its release and nobody
can find the right source code or the right build environment
(compilers, libraries, OS etc and the hardware they ran on) or if they
can be found it takes many many hours of expensive time and talent to
reconstruct the right stuff to actually make a code image that matches
what is shipping.


--
Dave Emery N1PRE/AE, die-NI3WtVA4WvYg9ELcbhaJlAC/***@public.gmane.org DIE Consulting, Weston, Mass 02493
"An empty zombie mind with a forlorn barely readable weatherbeaten
'For Rent' sign still vainly flapping outside on the weed encrusted pole - in
celebration of what could have been, but wasn't and is not to be now either."
David C. Partridge
2010-10-24 11:10:58 UTC
Permalink
Oh how true - an organisation I worked for some years back had the source code matching a custom package that was running at a certain customer, but not the build environment (that machine with that precise operating system patch level, compiler patch level etc.).

When the customer said thay'd pay for the source to look after if themselves, rather than continue to pay maintenance, they insisted that a new build be run to prove that exact byte for byte identical binaries to what they were running could be re-created - a wise move indeed - it took 8 man months to re-create that build environment (and that was only possible because I insisted we archive all the patches to the system, compilers and libraries).

Regards,
David Partridge


-----Original Message-----
From: time-nuts-bounces-***@public.gmane.org [mailto:time-nuts-bounces-***@public.gmane.org] On Behalf Of David I. Emery
Sent: 24 October 2010 04:22
To: jfor-***@public.gmane.org; Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] Maintaining boatanchors

Horror stories abound about organizations that need to make some minor patch or change to source code of a popular product for some important customer even just a few years after its release and nobody can find the right source code or the right build environment (compilers, libraries, OS etc and the hardware they ran on) or if they can be found it takes many many hours of expensive time and talent to reconstruct the right stuff to actually make a code image that matches what is shipping.


--
Dave Emery N1PRE/AE, die-NI3WtVA4WvYg9ELcbhaJlAC/***@public.gmane.org DIE Consulting, Weston, Mass 02493 "An empty zombie mind with a forlorn barely readable weatherbeaten 'For Rent' sign still vainly flapping outside on the weed encrusted pole - in celebration of what could have been, but wasn't and is not to be now either."


_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
Magnus Danielson
2010-10-24 11:30:48 UTC
Permalink
On 10/24/2010 05:21 AM, David I. Emery wrote:
> On Sat, Oct 23, 2010 at 02:44:51PM -0700, J. Forster wrote:
>> Very true, exncept it's more like 5-10 years.
>
> These days John is absolutely right... likely none of the
> developers, none of the equipment, perhaps not even the corporate
> shell of the division or department that designed the product and
> wrote the software survives. Probably the source code was thrown
> out with the old servers that were sold for scrap... or just carted off
> to be shredded with all the other paper and electronic records...
>
> Horror stories abound about organizations that need to make some
> minor patch or change to source code of a popular product for some
> important customer even just a few years after its release and nobody
> can find the right source code or the right build environment
> (compilers, libraries, OS etc and the hardware they ran on) or if they
> can be found it takes many many hours of expensive time and talent to
> reconstruct the right stuff to actually make a code image that matches
> what is shipping.
>
>

Even if you have the source code, you need to keep the compiling
environment in a runable state. This may be problematic since things
like licensees may have gone out (nobody payed for them and you can't
get a new one), the machines setup for running it has dropped out of
service. Maybe some manual work was never automated so some of the magic
is in the hands of someone that doesn't work there anymore... or recall it.

Keeping the source is one thing, being able to actually use it is another.

The RTOS manuals and support files may have been tossed for instance...

With all this... I still want the source thought. Alongside with other
internal documentation. I have never seen any of that surfaced for
boatanchors of any kind.

Cheers,
Magnus
Rick Karlquist
2010-10-24 12:04:11 UTC
Permalink
It is even worse than you think. When I was developing
the HP 5334B counter, the plan was to use the firmware
from the 5334A counter (currently in production) and use
the same legacy microprocessors. However, we wanted to
replace the expensive HP made divide by 10 prescaler with
an off the shelf divide by 64 (or some power of two, I
don't remember). At that point in time, we had already,
while still building the 5334A, reached the point described
below. No source code, and no development system. Also,
the whole thing had been shoehorned into 2k of memory, with
little or no extra space.

Fortunately, the original software engineer still worked
for the company and I talked him into tweaking the machine
code to change the prescale modulus. Miraculously, he
was able to pull it off, and the rest is history.

Speaking of important customers, the military wanted some
feature called "MATE" which meant something like Military
Automatic Test Equipment. It involved translating commands
from HP-IB. What they had to do to add this was add a board
with its own microprocessor that did the translation and wire
it between the HP-IB hardware and the measurement controller,
because they could not modify the measurement controller for
the reasons given below, and other reasons.

Rick Karlquist N6RK


Magnus Danielson wrote:
> On 10/24/2010 05:21 AM, David I. Emery wrote:
>> On Sat, Oct 23, 2010 at 02:44:51PM -0700, J. Forster wrote:
>>> Very true, exncept it's more like 5-10 years.
>>
>> These days John is absolutely right... likely none of the
>> developers, none of the equipment, perhaps not even the corporate
>> shell of the division or department that designed the product and
>> wrote the software survives. Probably the source code was thrown
>> out with the old servers that were sold for scrap... or just carted off
>> to be shredded with all the other paper and electronic records...
>>
>> Horror stories abound about organizations that need to make some
>> minor patch or change to source code of a popular product for some
>> important customer even just a few years after its release and nobody
>> can find the right source code or the right build environment
>> (compilers, libraries, OS etc and the hardware they ran on) or if they
>> can be found it takes many many hours of expensive time and talent to
>> reconstruct the right stuff to actually make a code image that matches
>> what is shipping.
>>
>>
>
> Even if you have the source code, you need to keep the compiling
> environment in a runable state. This may be problematic since things
> like licensees may have gone out (nobody payed for them and you can't
> get a new one), the machines setup for running it has dropped out of
> service. Maybe some manual work was never automated so some of the magic
> is in the hands of someone that doesn't work there anymore... or recall
> it.
>
> Keeping the source is one thing, being able to actually use it is another.
>
> The RTOS manuals and support files may have been tossed for instance...
>
> With all this... I still want the source thought. Alongside with other
> internal documentation. I have never seen any of that surfaced for
> boatanchors of any kind.
>
> Cheers,
> Magnus
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>
J. Forster
2010-10-24 16:02:01 UTC
Permalink
I buy a lot of 10-20 year old test and other gear. When I try to get info
on some things the reaction is usually, "Oh, we havn't made that thing for
AGES now. It turns out "ages" is anything over about 3 months. "We now
have the xxxx model which is SOO much better than that old POS, and it's
only $25,000 more w/o options".

At that point I ask to speak to the oldest engineer or srevice tech.

SIGH!!!

BTW, I have started and joined a number of Yahoo Groups because sharing
and pooling info is now easy electronically, and in many cases is the only
source of information, other than suppliers of scanned or copied manuals,
like Artek Media.

FWIW,

-John

================

> On Sat, Oct 23, 2010 at 02:44:51PM -0700, J. Forster wrote:
>> Very true, except it's more like 5-10 years.
>
> These days John is absolutely right... likely none of the
> developers, none of the equipment, perhaps not even the corporate
> shell of the division or department that designed the product and
> wrote the software survives. Probably the source code was thrown
> out with the old servers that were sold for scrap... or just carted off
> to be shredded with all the other paper and electronic records...
>
> Horror stories abound about organizations that need to make some
> minor patch or change to source code of a popular product for some
> important customer even just a few years after its release and nobody
> can find the right source code or the right build environment
> (compilers, libraries, OS etc and the hardware they ran on) or if they
> can be found it takes many many hours of expensive time and talent to
> reconstruct the right stuff to actually make a code image that matches
> what is shipping.
>
>
> --
> Dave Emery N1PRE/AE, die-NI3WtVA4WvYg9ELcbhaJlAC/***@public.gmane.org DIE Consulting, Weston, Mass
> 02493
> "An empty zombie mind with a forlorn barely readable weatherbeaten
> 'For Rent' sign still vainly flapping outside on the weed encrusted pole -
> in
> celebration of what could have been, but wasn't and is not to be now
> either."
>
>
Magnus Danielson
2010-10-24 16:19:51 UTC
Permalink
On 10/24/2010 06:02 PM, J. Forster wrote:
> I buy a lot of 10-20 year old test and other gear. When I try to get info
> on some things the reaction is usually, "Oh, we havn't made that thing for
> AGES now. It turns out "ages" is anything over about 3 months. "We now
> have the xxxx model which is SOO much better than that old POS, and it's
> only $25,000 more w/o options".
>
> At that point I ask to speak to the oldest engineer or srevice tech.
>
> SIGH!!!

There is an issue of fatigue that adds to the situation. Now that they
*FINALY* have done away with that old box somebody comes and ask for it,
and for meager motivation in money...

Cheers,
Magnus
J. Forster
2010-10-24 16:51:38 UTC
Permalink
Actually, I've found that some old timers are delighted to chat about
older gear with somebody who still appreciates it.

The newbies are usually far less than helpful.

-John

===============


> On 10/24/2010 06:02 PM, J. Forster wrote:
>> I buy a lot of 10-20 year old test and other gear. When I try to get
>> info
>> on some things the reaction is usually, "Oh, we havn't made that thing
>> for
>> AGES now. It turns out "ages" is anything over about 3 months. "We now
>> have the xxxx model which is SOO much better than that old POS, and it's
>> only $25,000 more w/o options".
>>
>> At that point I ask to speak to the oldest engineer or srevice tech.
>>
>> SIGH!!!
>
> There is an issue of fatigue that adds to the situation. Now that they
> *FINALY* have done away with that old box somebody comes and ask for it,
> and for meager motivation in money...
>
> Cheers,
> Magnus
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>
Bob Camp
2010-10-24 17:03:54 UTC
Permalink
Hi

At least for us the process goes like:

1) Customer wants more than what's in the card file on in the electronic record system
2) Decision is made about how bad they want it
3) Engineer (not a tech) is assigned to dig the paper data up
4) A *guess* is made about which of many thousands of boxes *might* have the info in it
5) A request is put in to retrieve the most likely dozen boxes from off site storage
6) The boxes are gone through looking for the information
7) loop through steps 4,5,6 how ever many times needed
8) The data is re-formated so it's readable and rational
9) Out it goes

The whole process runs 1 to 4 weeks depending ...

Bob


On Oct 24, 2010, at 12:02 PM, J. Forster wrote:

> I buy a lot of 10-20 year old test and other gear. When I try to get info
> on some things the reaction is usually, "Oh, we havn't made that thing for
> AGES now. It turns out "ages" is anything over about 3 months. "We now
> have the xxxx model which is SOO much better than that old POS, and it's
> only $25,000 more w/o options".
>
> At that point I ask to speak to the oldest engineer or srevice tech.
>
> SIGH!!!
>
> BTW, I have started and joined a number of Yahoo Groups because sharing
> and pooling info is now easy electronically, and in many cases is the only
> source of information, other than suppliers of scanned or copied manuals,
> like Artek Media.
>
> FWIW,
>
> -John
>
> ================
>
>> On Sat, Oct 23, 2010 at 02:44:51PM -0700, J. Forster wrote:
>>> Very true, except it's more like 5-10 years.
>>
>> These days John is absolutely right... likely none of the
>> developers, none of the equipment, perhaps not even the corporate
>> shell of the division or department that designed the product and
>> wrote the software survives. Probably the source code was thrown
>> out with the old servers that were sold for scrap... or just carted off
>> to be shredded with all the other paper and electronic records...
>>
>> Horror stories abound about organizations that need to make some
>> minor patch or change to source code of a popular product for some
>> important customer even just a few years after its release and nobody
>> can find the right source code or the right build environment
>> (compilers, libraries, OS etc and the hardware they ran on) or if they
>> can be found it takes many many hours of expensive time and talent to
>> reconstruct the right stuff to actually make a code image that matches
>> what is shipping.
>>
>>
>> --
>> Dave Emery N1PRE/AE, die-NI3WtVA4WvYg9ELcbhaJlAC/***@public.gmane.org DIE Consulting, Weston, Mass
>> 02493
>> "An empty zombie mind with a forlorn barely readable weatherbeaten
>> 'For Rent' sign still vainly flapping outside on the weed encrusted pole -
>> in
>> celebration of what could have been, but wasn't and is not to be now
>> either."
>>
>>
>
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
J. Forster
2010-10-24 17:21:32 UTC
Permalink
I've found engineers tend to be squirrels. A number of times they've said
to me "I'll look in my files". They will often either scan it for me or
let me borrow the original informally so I can Xerox it locally.

IMO, going through Sales or making an "official" request costs a bunch and
ir rarely successful. It's also worth asking "do you remember any major
customers of this unit?>"

-John

===============


> Hi
>
> At least for us the process goes like:
>
> 1) Customer wants more than what's in the card file on in the electronic
> record system
> 2) Decision is made about how bad they want it
> 3) Engineer (not a tech) is assigned to dig the paper data up
> 4) A *guess* is made about which of many thousands of boxes *might* have
> the info in it
> 5) A request is put in to retrieve the most likely dozen boxes from off
> site storage
> 6) The boxes are gone through looking for the information
> 7) loop through steps 4,5,6 how ever many times needed
> 8) The data is re-formated so it's readable and rational
> 9) Out it goes
>
> The whole process runs 1 to 4 weeks depending ...
>
> Bob
>
>
> On Oct 24, 2010, at 12:02 PM, J. Forster wrote:
>
>> I buy a lot of 10-20 year old test and other gear. When I try to get
>> info
>> on some things the reaction is usually, "Oh, we havn't made that thing
>> for
>> AGES now. It turns out "ages" is anything over about 3 months. "We now
>> have the xxxx model which is SOO much better than that old POS, and it's
>> only $25,000 more w/o options".
>>
>> At that point I ask to speak to the oldest engineer or srevice tech.
>>
>> SIGH!!!
>>
>> BTW, I have started and joined a number of Yahoo Groups because sharing
>> and pooling info is now easy electronically, and in many cases is the
>> only
>> source of information, other than suppliers of scanned or copied
>> manuals,
>> like Artek Media.
>>
>> FWIW,
>>
>> -John
>>
>> ================
>>
>>> On Sat, Oct 23, 2010 at 02:44:51PM -0700, J. Forster wrote:
>>>> Very true, except it's more like 5-10 years.
>>>
>>> These days John is absolutely right... likely none of the
>>> developers, none of the equipment, perhaps not even the corporate
>>> shell of the division or department that designed the product and
>>> wrote the software survives. Probably the source code was thrown
>>> out with the old servers that were sold for scrap... or just carted off
>>> to be shredded with all the other paper and electronic records...
>>>
>>> Horror stories abound about organizations that need to make some
>>> minor patch or change to source code of a popular product for some
>>> important customer even just a few years after its release and nobody
>>> can find the right source code or the right build environment
>>> (compilers, libraries, OS etc and the hardware they ran on) or if they
>>> can be found it takes many many hours of expensive time and talent to
>>> reconstruct the right stuff to actually make a code image that matches
>>> what is shipping.
>>>
>>>
>>> --
>>> Dave Emery N1PRE/AE, die-NI3WtVA4WvYg9ELcbhaJlAC/***@public.gmane.org DIE Consulting, Weston,
>>> Mass
>>> 02493
>>> "An empty zombie mind with a forlorn barely readable weatherbeaten
>>> 'For Rent' sign still vainly flapping outside on the weed encrusted
>>> pole -
>>> in
>>> celebration of what could have been, but wasn't and is not to be now
>>> either."
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> time-nuts mailing list -- time-nuts-***@public.gmane.org
>> To unsubscribe, go to
>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>
bownes
2010-10-24 17:38:22 UTC
Permalink
This makes me re-think arguing with my wife about tossing the 15 linear feet of three ring binders full of systems documentation sitting in the basement.

But not for long. I'll keep what I don't have electronically I guess, but the SunOS 2.2 manual set can totally go in the trash.

The field engineering manuals on the other hand, all stay. I actually used one from the early 80's a few weeks ago to build a discrete stepper motor controller rather than order the newfangled ic.


On Oct 24, 2010, at 1:03 PM, Bob Camp <lists-***@public.gmane.org> wrote:

>> ask to speak to the oldest engineer or srevice tech.
>>
Rick Karlquist
2010-10-24 15:13:14 UTC
Permalink
Charles P. Steinmetz wrote:

> Approve it? I bet most manufacturers can't even FIND the code for
> equipment designed more than 25 years ago. Note that HP has had to
> rely on the kindness of strangers for copies of its older manuals.

In the old days, the manuals were typeset by some outside service,
and they maintained the manual. There was nothing maintained at
HP, so when the product was discontinued, the outside service no
longer received orders for manuals, and they threw away their
stuff. The only documentation at HP itself were actual copies of
manuals, that had to be purchased from the outside service. It
was no one's job to save obsolete manuals, even at the division
that wrote them. Some HP libraries collected whatever manuals
were donated and tried to archive them. But there was no guarantee
any particular manual would get donated. And then the libraries
ran low on space and had to purge. Etc.

Rick Karlquist N6RK
J. Forster
2010-10-24 16:48:34 UTC
Permalink
It was my impression that many HP (and Tek, PAR and others) Field Offices
had full manual sets for everythng they supported. I got a hardware fiche
manual for an HP total station from the Boston office.

Best,

-John

==============

> Charles P. Steinmetz wrote:
>
>> Approve it? I bet most manufacturers can't even FIND the code for
>> equipment designed more than 25 years ago. Note that HP has had to
>> rely on the kindness of strangers for copies of its older manuals.
>
> In the old days, the manuals were typeset by some outside service,
> and they maintained the manual. There was nothing maintained at
> HP, so when the product was discontinued, the outside service no
> longer received orders for manuals, and they threw away their
> stuff. The only documentation at HP itself were actual copies of
> manuals, that had to be purchased from the outside service. It
> was no one's job to save obsolete manuals, even at the division
> that wrote them. Some HP libraries collected whatever manuals
> were donated and tried to archive them. But there was no guarantee
> any particular manual would get donated. And then the libraries
> ran low on space and had to purge. Etc.
>
> Rick Karlquist N6RK
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>
Charles P. Steinmetz
2010-10-25 01:48:05 UTC
Permalink
I've encountered an HP5345A (prefix 2040A) that was apparently
originally part of an HP5390A frequency stability analyzer (prefix
2036A). It has a factory label (No. 05345-80023) indicating that it
has a "modified front end." I have not seen anything in the 5345A or
5390A documentation to suggest what might have been changed in the
front end. Does anyone here know?

So far, the 5345A appears to work normally, but I have not
characterized its sensitivity or triggering performance. The 10811
oscillator does seem to be a cut above the others I have in terms of
stability -- I don't know if this was intentional or accidental.

Thank you,

Charles
David C. Partridge
2010-10-24 10:56:40 UTC
Permalink
Or it's just been lost between the cracks in reality ...


Regards,
David Partridge


-----Original Message-----
From: time-nuts-bounces-***@public.gmane.org [mailto:time-nuts-bounces-***@public.gmane.org] On Behalf Of Bob Camp
Sent: 23 October 2010 21:59
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] Maintaining boatanchors (was Capacitor Failures)

Hi

I've been down that road a couple of times. You get to a point where everyone involved does indeed agree that "it's not a secret" anymore. Going the final step and actually getting permission to hand out the code is often impossible. You get into a "nobody has the authority to approve that" hassle.

Bob
jimlux
2010-10-23 21:32:14 UTC
Permalink
Heathkid wrote:
> Backup images are fine... but has anyone considered or tried to contact
> the original programmers to get the actual code used? I'm sure there
> wouldn't be any reason someone would still consider 30+ year old code a
> "trade secret" and if one had the original code... could reasonably
> replicate an old programmed chip with a newer one. Just a thought.
>
>
more likely, nobody still working there knows what the original code is,
and they threw it away 10 years ago.

I work in the spacecraft electronics business, and we're positively
compulsive about documentation, but there's plenty of stuff that just
gets lost. "Oh yeah, we were cleaning out Dave's office after he died,
and we just pitched all those printouts and databooks with the notes on
the pages. Everything is online now, right?"

Or, it's somewhere in the archives, in one of several hundred boxes
labeled "miscellaneous documentation from 1981-1985" and it would cost
literally hundreds of dollars to retrieve the boxes and have someone
hunt through it for something that might or might not be there.

Or, in a cost cutting thing "We have all these boxes of stuff from 1980
that we're paying for storage on. Do you have a charge number for the
storage fees? No? Ok, into the trash it goes"
J. Forster
2010-10-23 21:47:33 UTC
Permalink
True.

I've been in warehouses with hundreds of rows of shelves of Bankers Boxes
filled with records. I doubt the stuff is even indexed.

-John

==============


> Heathkid wrote:
>> Backup images are fine... but has anyone considered or tried to contact
>> the original programmers to get the actual code used? I'm sure there
>> wouldn't be any reason someone would still consider 30+ year old code a
>> "trade secret" and if one had the original code... could reasonably
>> replicate an old programmed chip with a newer one. Just a thought.
>>
>>
> more likely, nobody still working there knows what the original code is,
> and they threw it away 10 years ago.
>
> I work in the spacecraft electronics business, and we're positively
> compulsive about documentation, but there's plenty of stuff that just
> gets lost. "Oh yeah, we were cleaning out Dave's office after he died,
> and we just pitched all those printouts and databooks with the notes on
> the pages. Everything is online now, right?"
>
> Or, it's somewhere in the archives, in one of several hundred boxes
> labeled "miscellaneous documentation from 1981-1985" and it would cost
> literally hundreds of dollars to retrieve the boxes and have someone
> hunt through it for something that might or might not be there.
>
> Or, in a cost cutting thing "We have all these boxes of stuff from 1980
> that we're paying for storage on. Do you have a charge number for the
> storage fees? No? Ok, into the trash it goes"
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>
jimlux
2010-10-23 22:04:26 UTC
Permalink
J. Forster wrote:
> True.
>
> I've been in warehouses with hundreds of rows of shelves of Bankers Boxes
> filled with records. I doubt the stuff is even indexed.
>

Yep.. You get to the end of your phase of the project. You've got file
cabinets and shelves full of stuff, most junk, but some useful, as do
your co-workers. The managers are anxious to "get those people off the
charge number" and besides YOU want to get working on the next project.
So, into the boxes it goes, "Miscellaneous documentation, Box 1 of
50", "Miscellaneous documentation, Box 2 of 50".

If something goes wrong, and you need to do it, you ask for a big
conference room and have them bring back all 50 boxes, and THEN go
hunting through it for the stuff you need.

We all start out saying, "This time, we're going to archive things in an
orderly way, and do it as we go along, and it's going to be a exemplary
situation" and pretty soon, as schedules get tight and budgets tighter,
that good intention goes by the wayside.

(And besides, nobody ever gets an award or merit pay increase for "good
filing".. you get it for "delivering the product on time", or worse yet
"for finding that nugget in the 100 boxes of documentation")
s***@public.gmane.org
2010-10-24 01:21:37 UTC
Permalink
They are required to keep it by law, and they will get paid to look for stuff, if anyone (most likely the government of a court) wants them to, so I am not sure why they should spend their own money to make that task easy...

Didier

Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: "J. Forster" <jfor-***@public.gmane.org>
Sender: time-nuts-bounces-***@public.gmane.org
Date: Sat, 23 Oct 2010 14:47:33
To: Discussion of precise time and frequency measurement<time-nuts-***@public.gmane.org>
Reply-To: jfor-***@public.gmane.org, Discussion of precise time and frequency measurement
<time-nuts-***@public.gmane.org>
Subject: Re: [time-nuts] Maintaining boatanchors (was Capacitor Failures)

True.

I've been in warehouses with hundreds of rows of shelves of Bankers Boxes
filled with records. I doubt the stuff is even indexed.

-John

==============


> Heathkid wrote:
>> Backup images are fine... but has anyone considered or tried to contact
>> the original programmers to get the actual code used? I'm sure there
>> wouldn't be any reason someone would still consider 30+ year old code a
>> "trade secret" and if one had the original code... could reasonably
>> replicate an old programmed chip with a newer one. Just a thought.
>>
>>
> more likely, nobody still working there knows what the original code is,
> and they threw it away 10 years ago.
>
> I work in the spacecraft electronics business, and we're positively
> compulsive about documentation, but there's plenty of stuff that just
> gets lost. "Oh yeah, we were cleaning out Dave's office after he died,
> and we just pitched all those printouts and databooks with the notes on
> the pages. Everything is online now, right?"
>
> Or, it's somewhere in the archives, in one of several hundred boxes
> labeled "miscellaneous documentation from 1981-1985" and it would cost
> literally hundreds of dollars to retrieve the boxes and have someone
> hunt through it for something that might or might not be there.
>
> Or, in a cost cutting thing "We have all these boxes of stuff from 1980
> that we're paying for storage on. Do you have a charge number for the
> storage fees? No? Ok, into the trash it goes"
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>



_______________________________________________
time-nuts mailing list -- time-nuts-***@public.gmane.org
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
jimlux
2010-10-24 02:34:06 UTC
Permalink
shalimr9-***@public.gmane.org wrote:
> They are required to keep it by law, and they will get paid to look for stuff, if anyone (most likely the government of a court) wants them to, so I am not sure why they should spend their own money to make that task easy...
>
> Didier
>

Bankers Box is a brand name for a cardboard file storage box.
Of late, banks and businesses store most records electronically. Except
in cases like a home mortgage, where there are legal requirements to
keep the originals on file.

Most businesses these days are pretty vigorous on document retention
policies, not saving anything they don't have to, particularly if it
might *ever* come up as discovery in a lawsuit. Remember the Enron VP's
comment to her staff "Make sure you're following the retention and
disposal policy"..


I've seen some very nifty machines that will take a box full of paper
documents and with almost no human intervention, take the documents out
of the folders, scan both sides, etc. at amazingly high speeds.

But that doesn't mean that there aren't warehouses full of boxes and
crates of miscellanea out there, ready to be studied by "top men,
top..." should the need arise.


> Sent from my Verizon Wireless BlackBerry
>
> -----Original Message-----
> From: "J. Forster" <jfor-***@public.gmane.org>
> Sender: time-nuts-bounces-***@public.gmane.org
> Date: Sat, 23 Oct 2010 14:47:33
> To: Discussion of precise time and frequency measurement<time-nuts-***@public.gmane.org>
> Reply-To: jfor-***@public.gmane.org, Discussion of precise time and frequency measurement
> <time-nuts-***@public.gmane.org>
> Subject: Re: [time-nuts] Maintaining boatanchors (was Capacitor Failures)
>
> True.
>
> I've been in warehouses with hundreds of rows of shelves of Bankers Boxes
> filled with records. I doubt the stuff is even indexed.
>
> -John
>
Mark Sims
2010-10-24 00:57:41 UTC
Permalink
The "bad" temperature sensors can have a rather dramatic effect on the tbolt output,  particularly if you are even remotely time-nutty.  Their disciplining algorithm seems to use it as a rather important number.  
And the "bad" sensor is rather useless if you are trying to use Lady Heather to stabilize the temperature of the unit.  The "good" sensor allows temperature control to a few millidegrees absolute,  with longer term averages in the low tens of microdegrees using just a cardboard box and fan.  

With nutty level attention to all the details and potential sources of disturbance (temperature, power, signal, location, disciplining, moon phase, gerbil alignment, etc) you can coax E-13 level stability out of these things.  Not too shabby for a $100 box originally meant for microsecond level timing.
Mark Sims
2010-10-24 11:47:22 UTC
Permalink
HP had a program called NOMAS (Not Manufacturer Supported) where they did release the source code to some of their calculator products (mainly the HP41 family) and possibly others.  There are many great HP41 (and other calculators) emulations out there because of it.

I really wish they'd do it for the HP16500 logic analyzers... 

----------------------------------------
>With all this... I still want the source thought. Alongside with other >internal documentation. I have never seen any of that surfaced for >boatanchors of any kind.
Magnus Danielson
2010-10-24 11:56:09 UTC
Permalink
On 10/24/2010 01:47 PM, Mark Sims wrote:
>
> HP had a program called NOMAS (Not Manufacturer Supported) where they did release the source code to some of their calculator products (mainly the HP41 family) and possibly others. There are many great HP41 (and other calculators) emulations out there because of it.
>
> I really wish they'd do it for the HP16500 logic analyzers...

I would not mind having the HP5372A software, as there is room for
improvements in it.

When doing long measurements it would nice to see some form of
indication of time left or so. For similar measurements it would be nice
with an incremental display, which is feasable for some configs as not
all data is needed unless you need to calculate a frequency estimate.

Cheers,
Magnus
Jason Rabel
2010-10-25 18:00:59 UTC
Permalink
This is slightly off on a tangent, but has to do with licenses...

I had some old Alteon equipment which I needed a firmware update for. Nortel bought Alteon, but they continued the products and
updates (for a while).

Most the products were EOL (including the one I had), we're talking past updates, past support, past everything. HOWEVER, Nortel
still had files on their website for download. You could download documents and such no problems... But firmware files you needed an
account with certain support level to download.

So I try to contact Nortel, they tell me I need a service contract so that I can download the firmware files. Okay, I ask them to
for that department. The service department tells me I can't get a contract because the products are EOL. So I ask them how am I
supposed to download the files if I need a service contract, but he's telling me I can't get a contract? *sigh*

After constant pestering, I guess someone there finally felt sorry for me and changed my account so that I could *finally* download
the files... But man, what a freaking zoo...

> Even if you have the source code, you need to keep the compiling
> environment in a runable state. This may be problematic since things
> like licensees may have gone out (nobody payed for them and you can't
> get a new one), the machines setup for running it has dropped out of
> service. Maybe some manual work was never automated so some of the magic
> is in the hands of someone that doesn't work there anymore... or recall it.
J. Forster
2010-10-25 18:12:10 UTC
Permalink
Actually, you are very lucky Nortel is even still answering the phone. The
stockholders were a lot less fortunate.

-John

================


> This is slightly off on a tangent, but has to do with licenses...
>
> I had some old Alteon equipment which I needed a firmware update for.
> Nortel bought Alteon, but they continued the products and
> updates (for a while).
>
> Most the products were EOL (including the one I had), we're talking past
> updates, past support, past everything. HOWEVER, Nortel
> still had files on their website for download. You could download
> documents and such no problems... But firmware files you needed an
> account with certain support level to download.
>
> So I try to contact Nortel, they tell me I need a service contract so that
> I can download the firmware files. Okay, I ask them to
> for that department. The service department tells me I can't get a
> contract because the products are EOL. So I ask them how am I
> supposed to download the files if I need a service contract, but he's
> telling me I can't get a contract? *sigh*
>
> After constant pestering, I guess someone there finally felt sorry for me
> and changed my account so that I could *finally* download
> the files... But man, what a freaking zoo...
>
>> Even if you have the source code, you need to keep the compiling
>> environment in a runable state. This may be problematic since things
>> like licensees may have gone out (nobody payed for them and you can't
>> get a new one), the machines setup for running it has dropped out of
>> service. Maybe some manual work was never automated so some of the magic
>> is in the hands of someone that doesn't work there anymore... or recall
>> it.
>
>
> _______________________________________________
> time-nuts mailing list -- time-nuts-***@public.gmane.org
> To unsubscribe, go to
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
>
>
Jason Rabel
2010-10-25 18:06:10 UTC
Permalink
I wish Symmetricom would release source to the old TrueTime / Datum products... But I'm sure most of that source code has been lost
/ thrown away.

For instance, the older network time servers are much cooler to me than the new models. The old stuff was custom designed and
specifically written / tweaked by hand. The newer time servers are just off-the-shelf single board computers, a GPS module, and then
*maybe* a custom oscillator module.... Then they just run on a *nix OS with some small custom scripts to do the timing and automate
setup... Just not the same...

> HP had a program called NOMAS (Not Manufacturer Supported) where
> they did release the source code to some of their calculator products
Poul-Henning Kamp
2010-10-25 18:13:57 UTC
Permalink
In message <***@Inspiron>, "Jason Rabel" writes:

>I wish Symmetricom would release source to the old TrueTime / Datum
>products... But I'm sure most of that source code has been lost

Once I become supreme ruler, to sell any product costing more than
a months work on minimum salary, you would have to file full product
documentation, including source code, with a escrow-agency. This
information would be released to the public, once the company is
unable or unwilling to help owners with their repair enquiries.

I would also mandate a 10 year warranty on the same products while
I was at it: It is a pointless waste of resources to design things
to cease functioning after 2 years, when we can build it to last
10 years for less than 25% additional cost in materials.

Poul-Henning

--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk-***@public.gmane.org | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
Loading...