Author Topic: Timebase Stability Specification  (Read 2095 times)

0 Members and 1 Guest are viewing this topic.

Offline KSPTopic starter

  • Regular Contributor
  • *
  • Posts: 98
  • Country: gb
Timebase Stability Specification
« on: April 26, 2014, 10:30:28 am »
Hi all

So the issue is whenever I am trying to verify the accuracy of the timebase of an item (in this case an Agilent 53131A counter) I never get given a true spec for accuracy, they always have temp stability, aging rate, etc. But what I want is just basically to take a measurement and determine whether it needs adjusting, yes or no. I'm so used to working with absolutes; i.e. it will be accurate to +/-1ppm etc, so all this nonsense throws me. See attachment for timebase 'spec', I am using option 001
 

Offline TMM

  • Frequent Contributor
  • **
  • Posts: 471
  • Country: au
Re: Timebase Stability Specification
« Reply #1 on: April 26, 2014, 10:43:44 am »
I don't see the issue to be honest. If you want a 'one accuracy fits all', perhaps add them all up and multiply by 10? =6x10^-6
 

Offline KSPTopic starter

  • Regular Contributor
  • *
  • Posts: 98
  • Country: gb
Re: Timebase Stability Specification
« Reply #2 on: April 26, 2014, 10:51:22 am »
Well say for example it had a drift rate of 1x10^7/day, but hadn't been used for 10 years... Does this mean that it could have an error of 3.650x10^4 and still technically be within its working tolerances? Because that seems rediculous. Surely in order to have confidence in something there needs to be something that states that it will perform to a certain level of accuracy...
 

Offline T3sl4co1l

  • Super Contributor
  • ***
  • Posts: 22436
  • Country: us
  • Expert, Analog Electronics, PCB Layout, EMC
    • Seven Transistor Labs
Re: Timebase Stability Specification
« Reply #3 on: April 27, 2014, 03:20:27 am »
Well say for example it had a drift rate of 1x10^7/day, but hadn't been used for 10 years... Does this mean that it could have an error of 3.650x10^4 and still technically be within its working tolerances? Because that seems rediculous. Surely in order to have confidence in something there needs to be something that states that it will perform to a certain level of accuracy...

Yes, but no.  See, it's probably in need of cal by then. ;)

Drift being what it is, 1/rtDays is probably more representative, in which case the error looks more like 6.0 x 10^-6.  Which sounds kind of reasonable.

Tim
Seven Transistor Labs, LLC
Electronic design, from concept to prototype.
Bringing a project to life?  Send me a message!
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf