Re: [time-nuts] Motorola UT+ Oncore GPS Timing Receiver 1pps R5122U1154

2012-05-07 Thread Magnus Danielson
On 05/08/2012 01:19 AM, Art Sepin wrote: Ken, You can find the UT+ Engineering Notes and the complete UT+/GT+ User's Guide here: http://www.synergy-gps.com/index.php?option=com_content&task=view&id=35&; Itemid=60 We should have the legacy UT+ and M12+ firmware history and Firmware Application

[time-nuts] measure zero beat

2012-05-07 Thread Lee Mushel
David, I haven't been following this thread so I suppose it has already been answered, but how are you measuring "zero beat?" Lee Mushel - Original Message - From: "David I. Emery" To: ; "Discussion of precise time and frequency measurement" Sent: Monday, May 07, 2012 5:37 PM Subj

Re: [time-nuts] Oh dear

2012-05-07 Thread Had
May we PLEASE go back the the intended purpose of this list. Hadley K7MLR A fine is a tax for doing wrong. A tax is a fine for doing well. Peter Cooper, of Fermi Lab, says, "Every experimentalist knows that the apparatus, or at least your understanding of it, is always at fault until

Re: [time-nuts] Motorola UT+ Oncore GPS Timing Receiver 1ppsR5122U1154

2012-05-07 Thread Art Sepin
Motorola offered an 8 channel GPS chipset and also a 12 channel chipset based on the MC2003. A separate "RF Oncore" GPS receiver front end (PWA Board) was also sold in the late nineties. These products were only available to volume users (50 K pieces and up). I'll review what we have stored in th

[time-nuts] frequency (absolute) accuracy in sound recording/playback

2012-05-07 Thread Jim Lux
One area where accuracy is important is not because of pitch (nobody can hear 1ppm differences), but because of the need to synchronize sound from different sources, particularly with video or motion picture frames. 1000 seconds (20 minutes, give or take) with the sampler off by 1ppm will be

Re: [time-nuts] frequency (absolute) accuracy in sound recording/playback

2012-05-07 Thread J. Forster
A movie may be 7000 seconds, and you may need a fairly stable timebase, but every movie I've watched is made up of short (<300 second) scenes that are placed sequentially on the framework. You are not meshing together a pair or multiplicity of 7000 second event sequences. E#very time you edit in a

Re: [time-nuts] Motorola UT+ Oncore GPS Timing Receiver 1ppsR5122U1154

2012-05-07 Thread ken johnson
If it's of any use to you, here is a link to the layout and parts placement for a board I designed when I was playing with the oncore for APRS some years ago. The board is designed so the motorola oncore plugs in to the top of my board and is secured by 10mm high stand-offs. My board supplies a reg

Re: [time-nuts] Faster than light of a different type

2012-05-07 Thread Tom Knox
Yea NIST and JILA keep pushing pseudo science, and they keep on recieveing the Noble Prize in Physics for these ideas. Thomas Knox > From: alan.me...@btinternet.com > To: jwsm...@jwsss.com; time-nuts@febo.com > Date: Tue, 8 May 2012 00:13:44 +0100 > Subject: Re: [time-nuts] Faster than light

Re: [time-nuts] frequency (absolute) accuracy in sound recording/playback

2012-05-07 Thread David I. Emery
On Mon, May 07, 2012 at 06:13:56PM -0700, J. Forster wrote: > A movie may be 7000 seconds, and you may need a fairly stable timebase, > but every movie I've watched is made up of short (<300 second) scenes that > are placed sequentially on the framework. 5-10 seconds a cut is quite common,

Re: [time-nuts] frequency (absolute) accuracy in sound recording/playback

2012-05-07 Thread Peter Gottlieb
We had time code to sync a number of separate A/V recorders so that during editing you can cut from one to another seamlessly. I didn't calculate or look at how tight the sync had to be. The mobile cams could be out there for a while, maybe an hour or more, starting and stopping to

Re: [time-nuts] DPLL for 10MHz

2012-05-07 Thread Tom Knox
I do not know if this is the type of solution you were looking for but Wenzel builds a fantastic LNPLL. Thomas Knox > Date: Mon, 7 May 2012 16:11:13 -0500 > From: docdai...@gmail.com > To: time-nuts@febo.com > Subject: Re: [time-nuts] DPLL for 10MHz > > Regarding my abilities.. regarding ele

Re: [time-nuts] frequency (absolute) accuracy in sound recording/playback

2012-05-07 Thread J. Forster
When I was doing some video production, we would first "Black Burst" the tape. This was done from end-to-end as the lattice. Then we assembled the segments onto the that tape. The inserted segments were always an integral number of frames. The source deck for the playback was slaved to the prerec

Re: [time-nuts] frequency (absolute) accuracy in sound recording/playback

2012-05-07 Thread Peter Gottlieb
Yes, the nice thing about that is it is so easy (if you prepare ahead of time). Here is what we used: http://en.wikipedia.org/wiki/SMPTE_timecode Both have their uses. On 05/07/12, J. Forster wrote: When I was doing some video production, we would first "Black Burst" the

Re: [time-nuts] frequency (absolute) accuracy in sound recording/playback

2012-05-07 Thread J. Forster
The SMPTE Time Code was on one line in first 20 odd of the Verticle Blanking Interval (VBI), along with the Color Bars, Multiburst, Closed Captrion data and some other things. It was not accurate to microseconds. It had a format of HH:MM:SS:FR (Hours, Minutes, Seconds, Frame) ... the frame was a

Re: [time-nuts] frequency (absolute) accuracy in sound recording/playback

2012-05-07 Thread Jim Lux
On 5/7/12 6:13 PM, J. Forster wrote: A movie may be 7000 seconds, and you may need a fairly stable timebase, but every movie I've watched is made up of short (<300 second) scenes that are placed sequentially on the framework. You are not meshing together a pair or multiplicity of 7000 second eve

Re: [time-nuts] Faster than light of a different type

2012-05-07 Thread Hal Murray
c...@employees.org said: > one more thing, people need to learn to hit the "delete" key if they don't > like a particular email. get over it. I don't think that's a reasonable approach. Yes, of course, we should all be more tolerant. But that's only half the story. There is an interesting

Re: [time-nuts] Faster than light of a different type

2012-05-07 Thread Jim Lux
On 5/7/12 8:45 PM, Hal Murray wrote: One thing that might help is if everybody would get in the habit of scanning all their mail before responding to anything. The idea is that if a discussion explodes while you are sleeping (or away from your mail for whatever reason), you will learn that a to

Re: [time-nuts] Faster than light of a different type

2012-05-07 Thread Mike S
On 5/7/2012 7:22 PM, Cliff Sojourner wrote: one more thing, people need to learn to hit the "delete" key if they don't like a particular email. I prefer to simply subscribe to low noise sources, where I'm not required to get manually intervene. get over it. Don't tell me what to do. Get o

Re: [time-nuts] Faster than light of a different type

2012-05-07 Thread Hal Murray
jim...@earthlink.net said: > I wonder if the nature of email and how it gets read has any effect on > usenet lists. > Think back to expensive dialup days.. you'd dial up, download the batch, > and then hangup. So you'd go through all the mail (almost like a digest) > before responding. I think

Re: [time-nuts] Faster than light of a different type

2012-05-07 Thread jim s
Observed phenomena which verify or demonstrate this impact some theories related to how the quantum effects govern areas around black holes. Since they are only observable from their effects, and the theories about the causes of these effects are used to explain these observations, anything th

Re: [time-nuts] Faster than light of a different type

2012-05-07 Thread Hal Murray
j...@jwsss.com said: > At least let someone claim that this affects climate change before you > condemn it or make a comment like this. > On 5/7/2012 6:38 PM, Tom Knox wrote: >> Yea NIST and JILA keep pushing pseudo science, and they keep on recieveing >> the Noble Prize in Physics for these id

Re: [time-nuts] frequency (absolute) accuracy in sound recording/playback

2012-05-07 Thread Magnus Danielson
On 05/08/2012 04:25 AM, J. Forster wrote: The SMPTE Time Code was on one line in first 20 odd of the Verticle Blanking Interval (VBI), along with the Color Bars, Multiburst, Closed Captrion data and some other things. It was not accurate to microseconds. It had a format of HH:MM:SS:FR (Hours, M

<    1   2