[time-nuts] Symmetricom TS2100 Faults and Forgetfulness
On 12/06/18 12:23, time-nuts-requ...@lists.febo.com wrote: Esa Heikkinen I think IP address or display settings cannot be stored to that EEPROM, it contains oscillator steering parameters etc. That is because this EEPROM is write protected by jumper JP4, so any user settings cannot be there. You only need to edit the EEPROM content if you change to different oscillator. To do any changes there JP4 must be shorted to enable writing. From my TS2100 I have stored two EEPROM dumps: With original TXCO: 0e 5b 45 4b 00 00 00 46 31 30 34 30 38 30 37 39 00 00 00 00 00 00 00 00 00 a0 6e 04 1f d3 56 43 58 4f 00 00 00 00 00 00 00 00 00 00 00 00 ff ff ff eb 00 00 00 02 3f 73 33 33 00 04 00 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 After upgrading MTI OCXO: a5 73 9b 52 00 00 00 46 31 30 34 30 38 30 37 39 00 00 00 00 00 00 00 00 00 a0 6e 04 1f d3 56 43 58 4f 00 00 00 00 00 00 00 00 00 00 00 00 ff ff ff eb ff ff ff ec 3f 7f df 3b 00 04 00 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 So there must be some other place to store the user data. I would look if there's more EEPROMs on the board and does they have write protect jumpers also. Erratic jumper setting there could prevent storing any changes. It may also be faulty eeprom. -- 73s! Esa OH4KJU Here's mine again: fe 55 73 7c 00 00 00 46 33 30 30 30 30 30 32 31 00 00 00 00 00 00 00 00 00 a0 6e 04 14 4a 56 43 58 4f 00 00 00 00 00 00 00 00 00 00 00 00 ff ff ff ed 00 00 00 14 3f 7f df 03 00 04 00 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Already replaced the oscillator a while back. Comparing the output to a gps 10Mhz, the original was jittering all over the place and not very nice on an sa either. Didn't have the exact fit, but did have a small ovenised vcxo which had the right vcc and control range. Epoxied that the the board, but had to add a squarer (a single transistor) as it had a sine wave op. So, it's been hacked around a bit already. One thing I did notice in the eeprom, 4th line down, first six bytes, is the ether mac address, but haven't edited any parameters as yet. Right now, it's running on a ups, along with a couple of other what I call, "essential loads" :-). As for user setups, from memory, there are two eeproms on the board, so may swap the other item to see if it fixes the fault... Regards, Chris ___ time-nuts mailing list -- time-nuts@lists.febo.com To unsubscribe, go to http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com and follow the instructions there.
[time-nuts] NDK Oscillator 30F8297 40MHz
I am looking for any information on an NDK 40MHz 4 pin canned oscillator part number 30F8297, the body is 10mm square and the flange at the base 12mm square, height excluding pins is 5mm and pins are at the corners of an 8mm square. I thought at first that 8297 might just be a date code but several online obsolete parts dealers do show 30F8297 as a 40MHz oscillator so perhaps not. NDK no longer lists these and I have found nothing online apart from the above dealer listings. I would appreciate any information on these specific oscillators or perhaps any other NDK data for similarly numbered obsolete parts.Links to any old NDK catalogues would also be appreciated. Nigel, GM8PZR ___ time-nuts mailing list -- time-nuts@lists.febo.com To unsubscribe, go to http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com and follow the instructions there.
Re: [time-nuts] VLF time station, cheap sdrs
Jim mentioned the teensy earlier. This led to a couple of interesting links : This thread describes using the internal trim adjustment to lock the cpu clock frequency onto a VLF transmission https://forum.pjrc.com/threads/35397-Teensy3-1-as-a-precision-Frequency-Standard Two SDR implementations on teensy 3 https://hackaday.com/2014/04/25/building-a-software-defined-radio-with-a-teensy/ https://forum.pjrc.com/printthread.php?t=40590&pp=25 and, not teensy but another sdr for MSF https://www.armms.org/media/uploads/s_day_implementation_of_a_software_defined_radio_for_the_60khz_msf_time_signal.pdf On Wed, Dec 5, 2018 at 11:05 PM Dana Whitlow wrote: > Here is my capture of a few minutes of WWVB amplitude and phase from last > fall. > It's somewhat larger of a file than I had remembered, more like 3.5MB, and > it has > lots of fine detail. So be prepared for it to take half a minute or so > (maybe more, > depending) before it starts to plot. > > The data was recorded with an SDR-14 SDR, using a DXE broadband loop > antenna. I had to wait until the wee hours to get a decent-looking signal > in > my high-line-noise area (Kerrville, TX). > > The demodulation was done after the capture was complete, in 'C' SW that > I've written to make this kind of signal analysis fairly easy and regular. > Basically > I examine the spectrum of the raw signal using an FFT, and manually pick > the > band limits within which I want to work. Then I shift that band to roughly > zero- > center frequency, and take an IFFT to return to time domain. At this point > the > frequency is invariably a bit off, and I have an interactive graphical > means of > correcting the frequency error pretty accurately. Hence, my "Costas loop" > is > really a manual process to de-tilt the phase versus time plot. > > Normally I quit there, but realized that I needed a better way to plot such > a > long record, so I developed a little program to plot the data in spiral > form to > an EasyCAD file, to which I manually added explanatory text. > > Thanks to TVB for converting my oversize pdf plot to something reasonable. > > Enjoy, > > Dana > > > On Wed, Dec 5, 2018 at 4:29 PM Dana Whitlow wrote: > > > Here is my capture of a few minutes of WWVB amplitude and phase from last > > fall. > > It's somewhat larger of a file than I had remembered, more like 3.5MB, > and > > it has > > lots of fine detail. So be prepared for it to take half a minute or so > > (maybe more, > > depending) before it starts to plot. > > > > The data was recorded with an SDR-14 SDR, using a DXE broadband loop > > antenna. I had to wait until the wee hours to get a decent-looking > signal > > in > > my high-line-noise area (Kerrville, TX). > > > > The demodulation was done after the capture was complete, in 'C' SW that > > I've written to make this kind of signal analysis fairly easy and > > regular. Basically > > I examine the spectrum of the raw signal using an FFT, and manually pick > > the > > band limits within which I want to work. Then I shift that band to > > roughly zero- > > center frequency, and take an IFFT to return to time domain. At this > > point the > > frequency is invariably a bit off, and I have an interactive graphical > > means of > > correcting the frequency error pretty accurately. Hence, my "Costas > loop" > > is > > really a manual process to de-tilt the phase versus time plot. > > > > Normally I quit there, but realized that I needed a better way to plot > > such a > > long record, so I developed a little program to plot the data in spiral > > form to > > an EasyCAD file, to which I manually added explanatory text. > > > > Enjoy, > > > > Dana > > > > > > On Wed, Dec 5, 2018 at 8:56 AM jimlux wrote: > > > >> https://www.rtl-sdr.com/tag/vlf/ > >> > >> a fair number of examples - > >> > >> As I speculated, the 8 bit RTL-SDR has a problem with strong broadcast > >> band AM, so you need some sort of LPF. > >> > >> There are some examples of "amplified whip into sound card into Rpi" > >> implementations. > >> > >> I didn't see anybody actually decoding or measuring the phase though - > >> lots of waterfall plots showing the existence of a signal. > >> > >> > >> ___ > >> time-nuts mailing list -- time-nuts@lists.febo.com > >> To unsubscribe, go to > >> http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com > >> and follow the instructions there. > >> > > > ___ > time-nuts mailing list -- time-nuts@lists.febo.com > To unsubscribe, go to > http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com > and follow the instructions there. > ___ time-nuts mailing list -- time-nuts@lists.febo.com To unsubscribe, go to http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com and follow the instructions there.
Re: [time-nuts] Symmetricom TS2100 Faults and Forgetfulness
Chris Quayle kirjoitti 6.12.2018 klo 2:13: Eeprom dump included. If another member has one of these, do these values look sane ?. No idea of function though... I think IP address or display settings cannot be stored to that EEPROM, it contains oscillator steering parameters etc. That is because this EEPROM is write protected by jumper JP4, so any user settings cannot be there. You only need to edit the EEPROM content if you change to different oscillator. To do any changes there JP4 must be shorted to enable writing. From my TS2100 I have stored two EEPROM dumps: With original TXCO: 0e 5b 45 4b 00 00 00 46 31 30 34 30 38 30 37 39 00 00 00 00 00 00 00 00 00 a0 6e 04 1f d3 56 43 58 4f 00 00 00 00 00 00 00 00 00 00 00 00 ff ff ff eb 00 00 00 02 3f 73 33 33 00 04 00 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 After upgrading MTI OCXO: a5 73 9b 52 00 00 00 46 31 30 34 30 38 30 37 39 00 00 00 00 00 00 00 00 00 a0 6e 04 1f d3 56 43 58 4f 00 00 00 00 00 00 00 00 00 00 00 00 ff ff ff eb ff ff ff ec 3f 7f df 3b 00 04 00 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 So there must be some other place to store the user data. I would look if there's more EEPROMs on the board and does they have write protect jumpers also. Erratic jumper setting there could prevent storing any changes. It may also be faulty eeprom. -- 73s! Esa OH4KJU ___ time-nuts mailing list -- time-nuts@lists.febo.com To unsubscribe, go to http://lists.febo.com/mailman/listinfo/time-nuts_lists.febo.com and follow the instructions there.
