I bought the very Last Symmetricom SA.22C in the shop!

[Johnny B Good]

 @wa4whl

 Did you have any luck getting hold of information on your Symmetricom SA.22C ? Im hoping you clicked the notification button when you made this post just over nine years ago! 

 I recently bought a later (2006) 15MHz square wave output version after downloading data sheets and user guides which suggested that it might be possible to program it to produce a 10MHz sine wave via the customer interface using the serial port connectivity feature. At the very least, I could always phase lock one of my many 10MHz sine output OXCO spares to the 15MHz square wave output if the worst came to the worst (excluding of course, the even worse case of receiving a non functioning unit (the very last one available via any on line shopping sites).

 As it happens, it does appear to be a fully functional 15 MHz unit as advertised and, after making up an 18 pin dual row 2 to 2.54 mm pitch adaptor and a test break out board plus connecting up an FTD-232 usb to serial adaptor, was finally able to access the serial interface and experiment with the customer run commands two days after taking delivery.

I was able to change the frequency to 10MHz using the o command) (but still square wave) and fine tune the initial +5.5mHz offset out using the f command. Unfortunately, these settings revert to defaults when next powered up and the 't' save tuning settings command is not clearly explained by the example given in the user guide. I'm hoping you managed to at least figure out the various user commands and how to interpret the 'health' data (w command). Basically, I need an "Idiot's Guide to control and configuration of an SA22C".

 I'm planning on disciplining to the 1PPS of an M8T gps receiver module so, apart from the need to reset it back to 10MHz using a nano3 mcu on every power up, I might not need to worry any further about reprogramming it. I'm going to attach one of my spare M8Ts and experiment with this built in GPSDRO feature.

[EDIT] Finally figured out why my attempt to reply was being aborted by eevblog's cackamaimee posting system - it was the now smaller 4000kB limit error with its carefully hidden error message which was the cause of my grief 

[Johnny B Good]

 I see my attached images raised some interest so it seems the subject of DIY rubidium atomic frequency standards isn't totally dead (just rather moribund  ).

 I did finally get round to sending my reply to our newbie friend, wa4whl but, with only 2 posts to his credit in over nine years, I doubt I'll ever get a reply.

 I only jumped on that post out of desperation since I couldn't track down other discussions on the SA22C anywhere on the 'net, just that one reference. I ticked the notification button just in case before closing that tab to post more on my 'new toy' here in this now renamed topic thread.

 I've been busy testing it out against my home brewed gpsdo (basically a revamp of the G3RUH design with an M8T replacing the Jupiter T, phase locking the ocxo at 100KHz with a 1200 seconds TC filter) and was finally persuaded to reorganise the bench to accommodate my LPR101 based RFS and give my SDS2502X+ something useful to do for its 46 second boot up time and its 54W consumption (versus the 16 seconds/22W of the SDS1202X-E that usually suffices as a graphic TIC).

 The reason for the reorganisation to show both rubidium oscillators against the GPS reference simultaneously being the reappearance of a curious symptom of instability I'd seen with the LPRO a few weeks ago (the impetus for blowing another 290 quid in total on acquiring the SA22C).

 Initially I'd assumed the rapid 10 to 20 ns transient backward phase shifts to be a very peculiar intermittent fault being developed by my now 25+ yo lpro but I am now starting to suspect the GPS system may be suffering fall out from the war in Ukraine due to electronic countermeasures by either the Russians or possibly even by the Americans as part of a strategy to wrong foot the Russians who may be using GPS as a sanity check/backup to their GLONAS systems 

 Yesterday I started seeing similar symptoms with the SA22C which had me dialling in offset corrections via its serial interface to try and keep it syntonised to the GPS reference which raised my suspicions once more about the stability of the GPS system as a high(ish) precision reference source. That was the moment I decided to make room for my LPRO RFS in order to confirm or lay my suspicions to rest. Of course, this 'weirdness' only occurs once every few days or so and the setup now seems to back to its normal state of precision (ionospheric disturbances aside).

 Unfortunately, the SA22C is only at the bench testing stage and subject to the variations of ambient temperature (just like the LPRO did when I was first checking it out almost 2 years ago now) which makes the task of pinning down 'the guilty party' just a little more tricky than I like. Still, I only need to witness another such 'event' to determine which, between the LPRO RFS and the GPS reference. is the true cause of these phase jumps.

 In the meantime, I'm trying to make sense of the information in the Symmetricom / Microsemi user guides and data sheet specifications. Of more immediate interest to me, is how to interpret the health data which is simply listed in hexadecimal form as per the w command output shown below:-

r>w

AData:
  SCont: 6012
  SerNum: A12
  PwrHrs: 5F18
  PwrTicks: 1282841
  LHHrs: 5ECF
  LHTicks: 10F5542
  RHHrs: 5ECF
  RHTicks: 1063C65
  dMP17: 4159F035.
  dMP5: 3D4E9CE6.
  dHtrVolt: 4172E210.
  PLmp: 3F93465F.
  PRes: 3FC3C440.
  dLVthermC: B8520000.
  dRVthermC: B99CD000.
  dLVolt: 3F8F52C5.
  dMVoutC: C9D122BB.
  dTempLo: 41000000.
  dTempHi: 42B10000.
  dVoltLo: 4156B1A8.
  dVoltHi: 4173473E.
  iFpgaCtl: 204C
  dCurTemp: 425A0000.
  dLVoutC: 3E0508D5.
  dRVoutC: 3DF08B1B.
  dMV2demAvg: 3F0C7C1A.

  Does anyone know how to interpret this data. Unless the  PwrHrs: (5F18) counter has wrapped around a 16 bit limit, it looks like it's clocked up just a tad over 1014  24344 hours, a mere 2.7771 years worth of run time, which if true, is just 27% of its design life.

 The i command displays this:

r>i


SA22C by Symmetricom, Inc., Copyright 2006
   SA22 Version 6.02C of 7/2006; Loader Version 3
   Mode CN41  Flag 0004

Unit serial code is 1211EC3234-h, current tuning state is 6
Crystal: 3938700hz, ACMOS: E4E1C0.00000000hz, Sine: 989680.00000000hz
Ctl Reg: 004C, Res temp off: BFC53F7D., Lamp temp off: BFF9418E.
FC: enabled, Srvc: low

 The final line just indicates the sense of the service output pin when it asserts a service required warning. The service pin reads 4.9 volts so no warning of imminent failure within the next few months at least. Worthy of note is the firmware version which predates the later version 6.05C which offers customer access to the 1PPS configuration, along with being able to enable sine wave output.

 The user guide suggested that the early version would normally default to 10MHz sine wave and enable the PPS feature  by default, the implication being that the end user wouldn't be able to tune the PPS control algorithm with the earlier firmware version. To test this, I added an SMA-F socket to my breakout board and connected an M8T to it. Sad to say, there was absolutely no indication that the PPS input option was enabled so it seems I'm out of luck regarding a quick solution to creating a GPSDRO by simply adding nothing more than a suitable GPS receiver module into the mix. I wasn't too surprised at this after reading this note in the user guide:
================================================================================
Setting the 1PPS Synchronization
The following are the steps for setting 1PPS signal synchronization (SA.22c with 1PPS enabled customer
version of firmware at revision 6.05c or higher installed.)
================================================================================

 I did a search to try and track down a firmware update but came up completely dry. I guess such an update has now long since become yet another item of "Unobtainium", so it's looking like I'll just have to create a 10MHz sine wave output GPSDRO the old fashioned way. I rather think I'm on my own in this endeavour but if anyone knows anything useful about these SA22C units, I'd really appreciate the help.

 I've attached four photos of the current bench setup.

[Johnny B Good]

Notes regarding the photos attached to the previous post (plus a set of ten screenshots taken earlier this evening)

The SDS2000X+ series conveniently display the date and time in the bottom right hand corner of their displays. The time is UTC and running about 1 1/2 minutes behind.

 The first image shows the SA22C with the heatsink plate temporarily removed in the left hand side of the foreground with the LPRO based RFS to its right (that big 12 by 10 by 8 inch WxDxH aluminium enclosure sized to accommodate a 25mm polystyrene foam lining and an LPRO wrapped in another 25mm thick polystyrene foam overcoat covering all sides other than the fan cooled heat spreader bolted to its base plate).

 The oled display is showing (top to bottom respectively) ambient temperature, base plate temperature and barometric pressure. The lockable ten turn counter drives a ten turn 5K helipot used to trim the frequency. The LED to the LHS of the oled display is a bi-colour red/green LED which shows red for powered up awaiting atomic lock and green to indicate lock. Power is courtesy of a 19v laptop charging brick. Its 10MHz sine wave output exits via an SMA-F connector mounted on the rear panel which I have connected to CH3 on the SDS2504X+ in the background. CH1 is the GPSDO reference from which the timebase is triggered whilst CH2 is the SA22C's square wave output. I have infinite persistence enabled to record the relative shift between the GPS reference (the source of the 5ns pk-pk wobbles on the LPRO trace). The larger drift of the SA22C obliges me to clear the persistence every half hour or so to keep track of its behaviour otherwise I'd only need to clear the persistence once every 6 to 24 hours or so for the LPRO on its own

 The second image includes the SDM3065X displaying the LPRO's lamp voltage. The second image is a more encompassing view to include the cheap 'n' cheerful Owon XDM1041 displaying the GPSDO's EFC voltage. The final image is just a slightly different angle to reduce the glare on the SDS's display.

 I've attached ten screen shots taken over a 2 hour and 20 minute time period to demonstrate the difference between a temperature stabilised rubidium oscillator (the LPRO) and one attached to a heatsink simply to prevent it overheating (typical hobbyist usage case going by the various youtube videos I've watched on the subject of setting up a home lab with an atomic frequency standard).

 Enjoy!

P.S. I almost forgot: I ran some temperature excursion tests on the SA22C using a small USB powered desk fan to chill it down and I was able to ascertain that it has a negative frequency tempco for what that's worth. My particular LPRO for example, has a positive frequency tempco but a sample of 19, according to the user guide showed a scattering of both positive and negative tempcos so that information is not a hard fact regarding the tempco of other SA22Cs, more a point of mild interest.

[Johnny B Good]

 Since there's some interest being shown in the SA22C, I thought I'd pop the lid off and take a few teardown photos for those either too shy to ask or daring enough to break the warranty sticker on theirs.

 It's not as if it's still in warranty and it does appear to be functioning ok after clocking up some 24,344 hours of service life out of a design life of better than 88,000 hours. It's obviously survived the 'infant mortality' phase of the MTBF bathtub curve and a long way off hitting the old age mortality end of said curve. IOW, it's just nicely matured That's assuming of course, that I've correctly interpreted the PwrHrs: data -fingers crossed that I have.

 I've attached the 1st 5 images of the teardown sequence and there'll be several more posts to follow with the later high detail images.

[Johnny B Good]

More images

[Johnny B Good]

Yet more photos

[Johnny B Good]

Another two pictures!

[Johnny B Good]

And, yet another two!

[Johnny B Good]

Almost there!

[Johnny B Good]

 And, finally, the last two

 These, along with the 2nd of the previous posting's attachments, are more detailed views of my breakout board, adapting the 2mm pitch socket to a 2.54mm pitch perf-board.

[Johnny B Good]

I got fed up seeing the SA22C spoiling the SDO screenshot sequences yesterday so decided to remove its presence (I'd needed to disconnect it anyway in order to take those teardown pictures) and create a sequence with only the LPRO and GPS traces in view.

 I've attached a 5 hour 11 minute sequence captured this afternoon, just ten images.

For the benefit of anyone who hasn't already seen my other contributions to rubidium oscillator related threads regarding my current temperature stabilised and barometrically compensated RFS project, here's a list of links which provide more detail on the contents of that BFO 12 by 10 by 8 inch aluminium enclosure housing the LPRO 101.

https://www.eevblog.com/forum/metrology/gnss-rb-(chinese)/msg4173502/#msg4173502

https://www.eevblog.com/forum/metrology/i-just-bought-an-efratom-100318/msg4176703/#msg4176703

https://www.eevblog.com/forum/blog/eevblog-235-rubidium-frequency-standard/msg3652885/#msg3652885

https://www.eevblog.com/forum/repair/efratom-lpro-repair-attempt/msg4277602/#msg4277602

[Johnny B Good]

 It's been some ten months since I made my last contribution to this "echo chamber" but since I've just received a request via a PM asking for help in establishing a serial link to the SA.22C, I thought it best to post what documentation I'd managed to obtain at that time rather than try tracking down the original links to send in a reply PM.

 I'd assumed that anyone interested enough to have bought one of these units would already have tracked down all such documentation (and more). However, since it took some search effort to gather these files and there's now a possibility that some may no longer be available, I've picked three of the most relevant files I have to hand.

[romal76]

Thanks for information.
I was able to connect to my SA22c by FTDI interface.
It is possible to change from 15MHz to 10MHz by typing

o
3<cr>

and save to memory for next startup by

t
5987717<cr>

it may not showing typing but after that you will have message that changes saved
Alsough I was able to change 1PPS output and the sine output through Lady Heather from this topic

https://www.eevblog.com/forum/metrology/lady-heather-v6-beta-for-windows-exe/msg1434005/#msg1434005

[Johnny B Good]

Thank you very much, romal76.

 Is yours running a later firmware version than mine?

SA22C by Symmetricom, Inc., Copyright 2006
   SA22 Version 6.02C of 7/2006; Loader Version 3
   Mode CN41  Flag 0004

 I was able to set it to 10MHz square wave output only but the 't' command didn't seem to work. I'd assumed the 5987717 was just an example parameter rather than some sort of key code required to validate the save command and hadn't wanted to risk saving an irreversible change.

 I'll set it back up again to test those commands and see if I can make the 10MHz square option 'stick' this time. Adding an LPF to convert it to a sine wave is a trivial exercise but even if I have to work with the default 15MHz square wave output, all is not lost since I can simply use a divide by three circuit as shown in the attached pdf, followed by an NB3N502 clock multiplier to get round that issue.

 Alternatively, since I'll be using an Arduino nano to regulate the base plate temperature and compensate for barometric pressure changes as per the current LPRO 101 based RFS project, I can use it to reprogram the output to 10MHz each time it's powered up.

 Also, thanks for the link to texaspyro's LadyHeather topic thread. I noticed my user name in the 'thank you' list to his OP so I've obviously read some of that thread way back then. I'll reaquaint myself with the rest of the thread in the hope that the latest version of LH will reveal more of the hidden features of my particular 15MHz SA.22C.

 Right now, after spending the past 5 months upgrading my Desktop PC, I'm only now resuming further development on the LPRO based RFS which has been on hold for lack of time and workbench space during what turned out to be a rather more protracted PC upgrading exercise than I'd anticipated.

 I'll post a report on any further progress with the SA.22C in this thread after I've had a chance to retest it with your suggestions and tried the latest version of LH.

[romal76]

 Is yours running a later firmware version than mine?

I have the same 6.02C

[Johnny B Good]

 Is yours running a later firmware version than mine?

I have the same 6.02C

 Thanks! That's encouraging. It looks like I may be able to reprogram it after all.

 However, reading the user guide suggests the possibility that despite having identical firmware versions, we may still have different degrees of success due to individual customer feature requests. I'll do some tests later on and compare our findings.

[Johnny B Good]

 I reran my original tests and can happily report that using the t command with 5987717 successfully saved the 10MHz setting which does away with the divide by three and doubler circuit, leaving only the matter of adding an LPF to generate a 10MHz sine wave.

 My understanding from reading the manuals is that the sinewave option is a factory default option chosen by the customer. I've not had any success in enabling this so from what you said about using LH to enable the sine wave (and PPS) options, maybe I'll be able to eliminate the LPF and perhaps even turn it into a gpsdro simply by connecting one of my spare NEO M8T modules to it (the PPS is currently disabled). Could you perhaps elaborate on how you used LH to do this?

[romal76]

From LH you can set to use SA22c by

/rxSA

then set COM port, for example 3

/3

after that you can view more information about your SA22c

if you see that than you can for example switch ACMOS off or set SINE 40% by pressing

p

you will see another menu at the bottom

pressing s and 40 you can set SINE 40%
pressing a and 0 you can disable ACMOS

and so on

[mmemBD]

hello, can you upload datasheet or describe scheme of your own adapter board? i have the sa.22c, but failed to find any information about official adapter test board
i'd really appreciate it

[Johnny B Good]

 I've already posted all the documentation I could gather together. The user/designer's guides mention a test adapter kit which is now "Unobtanium".

 When it came to making my own adapter, I looked through my collection of "Scrapped parts that might be of use someday". For the pcb I'd removed from an external 2.5 inch IDE HDD usb housing a decade or so earlier, its time to 'be of use' had finally arrived.

 The pin spacing on these drives is the required 2mm pitch making the pcb mounted socket the ideal carrier to push the 20mm long pins (extracted from a length or two of single row header strips I'd acquired some 35 years ago) through an 18 hole section I'd cut off the 44pin socket after trimming away the no longer needed solder tags.

 Making sure I had the pins protruding the required amount to fully engage the SA.22C's socket, I soldered the pins to the remains of the socket contacts to secure them in place and then carefully splayed them out to match the 2.54mm pitch on the perf board I was using.

 The obvious alternative to all that McGuivering is to get a PCB made up to directly take a 2mm pitch 18 pin dual row header but I was in a hurry to test the seller's description (especially the bit about it being in full working order) and didn't want to invest in a pcb with only the minimal amount of functionality required at this stage.

 It would have cost no more to make a complete adapter with the dc-dc converters required to power it from a 19v laptop charging brick and the sma sockets and header connectors for led and serial interface and so on, so I was rather loathe to double up my costs in the most unlikely event that I were to decide to have an adapter board made up for this one off 'special'.

 Anyway, that's two options for you to consider. Either McGuiver it like I did or else purchase a 2mm pitch 18 pin dual row header (or three) and get a PCB made up. One remaining alternative (which I didn't fancy much) is to push solid core wires into the SA.22C's socket and croc clip onto them for power and output and serial interface and leds. Ok for a quick 'n' dirty test bench lash up for basic testing purposes but not a serious contender for a more permanent setup.

[mmemBD]

Thank you very much, i will try to make adapter by your instructions! 

[edpalmer42]

FYI, back in 2015 I saw some anonymous circuit boards on ebay that I recognized as the Adapter Test Boards that are discussed in the Symmetricom 'Designer's Reference & User Guide'.  I picked up a couple to go with the two SA-22C units that I had.  I've attached the auction pictures.  If it would help, I can take higher resolution pictures.

Ed

[Xtremexp]

FYI, back in 2015 I saw some anonymous circuit boards on ebay that I recognized as the Adapter Test Boards that are discussed in the Symmetricom 'Designer's Reference & User Guide'.  I picked up a couple to go with the two SA-22C units that I had.  I've attached the auction pictures.  If it would help, I can take higher resolution pictures.

Ed

Are you selling it? I am looking for one, can you provide me details on cost, location etc.

[edpalmer42]

FYI, back in 2015 I saw some anonymous circuit boards on ebay that I recognized as the Adapter Test Boards that are discussed in the Symmetricom 'Designer's Reference & User Guide'.  I picked up a couple to go with the two SA-22C units that I had.  I've attached the auction pictures.  If it would help, I can take higher resolution pictures.

Ed

Are you selling it? I am looking for one, can you provide me details on cost, location etc.

No, I'm not selling it.  I thought that high resolution pictures might be of value to those of you who are trying to reverse-engineer it.

Ed

[Name00]

Hello, long time lurker on the forum but first time poster.   

I recent purchased one of these after getting everything up and wired.  It runs but failing to get a Rubidium Lock.  I do get an output but it swings wildly.    I've checked the input voltage it is 15V and checked the ground to ensure it's properly grounded, and follwoed that was itneh troubleshooting section and all was fine, I also doubled check the temperature and humidity and they are within "normal"

Does any one have any suggestions on what to check if I were to take it a part?

[Johnny B Good]

 Did you also verify the 5v rail (pin 6)?

[Name00]

Yes, the 5V rail is good, all voltages look fine measure at point of connections (the pins), I've also verified the GPS pulse and tracked it's output.   I'm able to talk to the interfaces using Lady Heather which I presume also means the unit is fully functional.  Lady heather reports the same thing I'm seeing no Rubidium Lock, the Lock pin also stays high, the manual indicates a +/- 21ppm cyclying for lock without verifying the exact ppm sweep, I see it cycle back and forth on a scope.

I'm waiting for confirmation from the seller it's okay to take it all apart.

[Johnny B Good]

 If the warranty sticker is still intact, I'd be more inclined to request a return with a full refund on the basis of it being "Not fit for purpose" by reason of it being DoA.

 I'm assuming from the fact you've asked the seller for permission to open it up that it had been described as a fully functioning item in the seller's description. The seller will most likely demand some video evidence demonstrating the issue.

 BTW, if you're going to video the scope display and voltage readings, place the camera on a tripod or other suitable support. This will maximise the benefit of processing the video into a more compact format using a video conversion/ compression app (I use Handbrake for this).

 Although the SA.22C is a modernised and more compact version of the venerable LPRO - 101 (same single board smd construction - no pesky electrolytics to spoil your day), unlike the LPRO, no one AFAIAA, has produced / published a comprehensive fault finding guide that could help you repair the more common and fixable faults. Unless you're prepared to do some reverse engineering, the best you can hope for is visually spotting a dry joint or a damaged component (a cracked mlcc, maybe?).

 If the seller gives you permission to open it up, then by all means do so. You never know, contrary to (my) expectations, you just might spot a suspicious looking component / bad solder joint or a broken wire which might allow you to effect a repair. Also, of course, you may be able to detect the glow of the rubidium vapour lamp which will tell you that the lamp itself is still intact.

 If no glow is visible that can also indicate a failure of the excitation oscillator circuit which energises the lamp. If you haven't already done so, it'll be worth downloading the latest LPRO repair guide simply to get some useful hints on how to do some basic tests (temperatures, frequency emissions from the lamp exciter oscillator, voltages and so on).

 Anyway, that's the best I can offer for now.  However, it might be worth posting the results of the health data (w command) for comparison against my own health data (reply #1).

[Name00]

I've opened the unit it all looks clean.  Nothing obvious.  I think the dMP17 value is low looking at yours it seems to translate to around 13.x volts, mine is measuring around 11.x.   According to the life, it's been up for 92.6K hours, ~10.5 years

Mine:
  dMP17: 41306B00.

Yours:
  dMP17: 4159F035.

Going to try to trace the power circuit, maybe a bad cap or resistor somewhere.   I see a slight glow from the lamp.  "w" output below, removed the serial number.


AData:
  SCont: 6012
  SerNum: XXXX
  PwrHrs: 169DC
  PwrTicks: 117E242
  LHHrs: 169DB
  LHTicks: 15576AE
  RHHrs: 169DB
  RHTicks: 14CCDDD
  dMP17: 41306B00.
  dMP5: 3D526F32.
  dHtrVolt: 413FD842.
  PLmp: 3F749718.
  PRes: 3F9D564D.
  dLVthermC: 3C00C400.
  dRVthermC: B8B8C000.
  dLVolt: 3B729566.
  dMVoutC: C931DBB3.
  dTempLo: 41440000.
  dTempHi: 42AF0000.
  dVoltLo: 41389C7C.
  dVoltHi: 4177ACFA.
  iFpgaCtl: 2023
  dCurTemp: 42600000.
  dLVoutC: 3E070F74.
  dRVoutC: 3DECB6DA.
  dMV2demAvg: BA298800.

[EDIT 1] I removed the reply and updated this post instead.  I upped the voltage from a bench power supply to  16v and got a lock.  I was going to initially replace the LM2941CS, however, after tracing the power circuit some more under a microscope and trying to figure out the various parts, I noticed small pits on the solider around Z501, R108, R57, and R28, figuring maybe it was a dry solder.  Ended up apply using a heat gun, and soldering iron, cleaned up most of the solder that may have been marginal.  It's now running solid on 15v with the dMP17 under lady heather at 13.5v

[EDIT 2]  I've run this on a survey fixed location of a LEA-5T (one of those Huawei modules), seems to produce a be far more stable 1 PPS signal when compared to a TAU1201 GNSS module.    Although the unit doesn't seem to be producing any PPS out signal.   Am I missing something?

[cncjerry]

I did a quick scan, and I didn't see anybody mention x72. I have two of these. The second one I just bought, it was in a trutime module. Both mine have quite a few hours on them but they work great. I've never seen version 6 of the software. I also can't remember if the Acmos output is based on the RB disciplined circuitry?  They reference it to a the 60Mhz crystal though some have other crystals, 30Mhz is also known to be available. 

I like these units but they need a heatsink and that takes away from the size.  LH will set the tuning word in both of the versions I have (4.24 and 4.34).  You need version 6 of texaspyro's LH.  Then it is under the '&' command.  You feed it 1pps from somewhere, possibly a well surveyed GPSDO, and it calculates the tuning word and sets it.  Though I have then written it many times after setting it, if it reboots, it is back to factory.  Also, you can set the service pin phase to 0 or 1, that will keep you from thinking it is broken.  The more recent one I have has limits on the control word for output.

Mark (Texaspyro) and I worked together on some of the heatsink mechanics.  I drilled the heatsinks.  He sent me an adapter board, you can get others on eBay now, or design your own and JLCpcb will run them off and have 5 of them to you in a week.  The dimensions are in the manual.  Note that you need specific loading on the sine output as spec'ed in the manual.  Like 150pf and 50r within 4inches of the output.

I run one all the time and tune it twice a year against my symmetricom GPSDO.  Phase noise is poor but stability is good.  The 2nd I plan to discipline with a GPSDO.   

[ohmjke]

Hi everyone.

Worthy of note is the firmware version which predates the later version 6.05C which offers customer access to the 1PPS configuration, along with being able to enable sine wave output.

Johnny B Good, were you able to use 1PPS Synchronization with unit version 6.02c?
Maybe there is some command to enable it in versions earlier than 6.05C?
Or some way to update firmware?

[Johnny B Good]

 roma176 had kindly provided instructions on how to configure it using LH v6 in reply #17 last July by which time I'd just shelved the project in order to concentrate on the LPRO 101 based RFS project. So the answer is "Not just yet.".

 Thanks for attaching the LH screenshot BTW. That should give some clue as to what to expect when I upgrade LH from v 5.0 (I just checked the version installed in my winXP VM).

 I think I'm just about done with the LPRO project, essentially an issue of achieving a stable base plate temperature within +/- 5mK over an ambient temperature range of 14 to 27 deg C.

 I'd recently started experimenting with PID libraries as a possible alternative to my custom in-line coding efforts but finding the documentation as clear as mud on exactly how you're meant to pass a complex set of tuning parameters or even how to link my set point, base plate temperature and fan control variables to the PID.

 As a result I've resorted back to my custom code, based on feed forward with a sort of PID fine tuning of the feed forward control. I made a further refinement which seems to have extended the upper limits of the control range. Even though the fan is powerful enough to hold the base plate to its 36.05 deg set point at an ambient of 32 deg, getting it to perform with a reasonable level of accuracy and stability beyond a maximum of 29 deg has proven impossible to achieve thus far so I might just have to simply live with this shortcoming and take consolation in the fact that I'd managed to get it to cope with close to freezing temperatures (4 deg C) during previous low temperature test runs.

 As for getting a PID library function to work any better than my own controlling algorithm, I suspect it may not even come close (but I'm willing to be proved wrong).

 I'm planning to do another low temperature test Friday night / Saturday morning to make sure my high temperature improvement hasn't compromised its low temperature performance. If it passes the low temperature test, I'll leave it in my garage/workshop to keep the hobby room work bench uncluttered enough to allow me to further experiment with the SA.22C and LH. I might have some news to report in a few days time (or not).

 Whatever the result, I'll be putting that aside in order to complete my MK III ZED 9 T based GPSDO project which I'd also set aside some 5 or 6 months ago. Basically, my problem is that I've got two too many projects than I can cope with right now.

[ohmjke]

Oh, I missed "and so on".
Thought these are the only options:

pressing s and 40 you can set SINE 40%
pressing a and 0 you can disable ACMOS

Will check next time I return to this project.
Thanks.

One more question - does anyone have information where this oscillators (Sa.22c or LPRO-101, for example) actually used?
According to info from seller I bought mine unit it was extracted from some GSM(?) base station. But no more detailed info.
I thinking maybe it is possible to find entire base station on sale and it will be cheaper...
Mine Sa.22c cost was ~$450

[testpoint1]

Oh, I missed "and so on".
Thought these are the only options:

pressing s and 40 you can set SINE 40%
pressing a and 0 you can disable ACMOS

Will check next time I return to this project.
Thanks.

One more question - does anyone have information where this oscillators (Sa.22c or LPRO-101, for example) actually used?
According to info from seller I bought mine unit it was extracted from some GSM(?) base station. But no more detailed info.
I thinking maybe it is possible to find entire base station on sale and it will be cheaper...
Mine Sa.22c cost was ~$450

most of the Rb module just comes from CDMA base station, but SA.22C and X72 are not, since the strange interface of SA.22C, the price of SA.22C is cheap, I am design a mechanical adapter for it, in orfer to use the SA.22C for replace X72 and LPRO, and I will design 2 PCB for the SA.22C.

[lugaw]

Is it possible to change the factory reference crystal on the unit? 

I am planning to buy a unit that doesn't output 10Mhz it only ouput 9.8304MHz from factory.

[Name00]

One more question - does anyone have information where this oscillators (Sa.22c or LPRO-101, for example) actually used?
According to info from seller I bought mine unit it was extracted from some GSM(?) base station. But no more detailed info.
I thinking maybe it is possible to find entire base station on sale and it will be cheaper...
Mine Sa.22c cost was ~$450

If you get ones with 60K+ hours on them, they come from GPRS-EDGE base stations.

Is it possible to change the factory reference crystal on the unit? 

I am planning to buy a unit that doesn't output 10Mhz it only ouput 9.8304MHz from factory.

I don't believe it's possible without changing the firmware, If you have the unit and TTL serial hooked up first power up the unit and you should see the crystals listed there to confirm,

SA22C by Symmetricom, Inc., Copyright 2006
   SA22 Version 6.02C of 7/2006; Loader Version 3
   Mode CN41  Flag 0000  [5D68]ok

Unit serial code is XXXXXXXXXX-h, current tuning state is 6
Crystal: 60000000hz, ACMOS: 10000000.0hz, Sine: 10000000.0hz
Ctl Reg: 0000, Res temp off: -1.6261, Lamp temp off: -2.0584
FC: enabled, Srvc: low

Name00, did you buy from hamradiomarket? They claim all their modules are tested.

No, I got mine from a e-recycler that gets them sporadically and removes them from base stations.  I tried to convince him to give me the cables and heat sink mount, he wanted way too much for those, so I ended up building an adapter from 1.0mm headers, solder and shrink wrap, version 2 involved getting 1.0mm hole pitch breadboard, ethernet cable, and  DC-DC 15v to 5v, and soldering to secure the ethernet cable as my trace, primitive but usable.

most of the Rb module just comes from CDMA base station, but SA.22C and X72 are not, since the strange interface of SA.22C, the price of SA.22C is cheap, I am design a mechanical adapter for it, in orfer to use the SA.22C for replace X72 and LPRO, and I will design 2 PCB for the SA.22C.

I also noticed ebay now has pre-made boards from the "famous" BG7TBL (for those from familiar with his counters  and GPSDO).    I've ordered one and will test.

[Name00]

I decided to make it a separate post.

Some updates, I still have not been able to get my unit to output 1 pps, I ended using a picdiv to do this for sync from GPS pps then driven from the 10MHz from the SA.22C.

Second I've gotten the unit partially tuned to the GPS.  it's an involved process but will outline for anyone interested, I now have 3 unit totally in-sync with a small deviation but drift between them at about  7ns per 18 hours based on my scope (1 unit tuned below to the GPS and the other tuned to the pps of the first unit using picdiv).

Steps used:

1) Get LH 6.14, a GPS that outputs a PPS, a terminal software (putty?) for com access and of course a ttl - serial and interface working for the unit.
2) Use a very stable GPS module (I've used the "Huawei" GPS modules both the ublox LEA-8T and the trimble -- the trimble one is far superior as it actually does it's survey automatically and synthesizes the pps! while you need to manually tune the ublox and it's PPS will vary to the GPS signal quality)
3) start up your terminal software, set the control register to 0 (it enables everything) and exit
4) Make sure the SA.22C has been running for  at least 6 hours
5) Start lady heather, set the com port and issue /rxsa (/rxsb if confirm a non 60Mhz crystal??).
6) issue "&" then "a" in lady heather, and give it a period of 12 hours (43200)
7) let it run and complete note what it's set the DDS to, if you have any value at e-13 leave it there's no point it's already as good as it gets based on it's spec sheet..
if you have e-12 or worst (ie anything at e-11, e-10, or e-9), take the first set of numbers so let's say -5.1234e-10.  take that and do -5.1234 x 10^(12-##) so in this example -512.34
9) start up the terminal software
10) set the dds to 0 (f then 0)
11) set the dds to the value from 7 (from example f then -512.34)
12) save  (t and 5987717)
13) exit terminal software, repeat 5 to 12, until your last 2 reading are e-12 or you get a e-13, and if you never get to 2 e-12 then your GPS pps has way too much variability.

Notes:
-- if you have a scope you can check it or if you have a GPSDO, you can also compare it to that to verify you've moved to the right direction and stability before doing step 12.
-- from what I can tell the t does save the f value on save, once saved the f value seems to be reset to 0 again, or I lucked out in my limited testing between 3 units split in the method above.
-- j command in the terminal software clearly shows it is tracking the pps (you can remove the source and see the value change).

[zrq]

Beware of this ebay seller: Comp-Electronics 4U Online. I got a SA.22c from them in "Used" condition, but it apparently never lock. Let's see how he/she responds to my message.