As for the missing calibration certificate, I still haven't had any reply from Telonic on the matter. I'll let it stew for another day or two before pressing them for an answer. As Tautec said (tnx btw) there's no excuse for withholding this piece of documentation from the end customer.
JBG
QuoteDoes anyone have any experience with the €138 bag? Is it really worth it?Yes I store and travel all my demo models in them and IMO they provide good protection although as you say they are not very cheap.
I asked the factory if we could get the Pelican hard case that Siglent NA offer but it's specific to the US market:
https://siglentna.com/product/hard-shell-carry-case/
QuoteI‘m dealing thisdays with my NOS schottky TTLs and a 65 MHz OCXO ( now VC)
to design a by-13-divider with my available ICs to bring it into suitable frequencies to
follow the GSPDO path
@ labrat: I‘m aware of the problems but it is hobby and learning by doing so let‘s see where it brings me to.
And I never expected to run in problems with this by-13-divider
QuoteQuoteI‘m dealing thisdays with my NOS schottky TTLs and a 65 MHz OCXO ( now VC)
to design a by-13-divider with my available ICs to bring it into suitable frequencies to
follow the GSPDO path
Hi Unless I have miss understood if you want 10Mhz from 65Mhz you need to divide by 6.5
if you divide by 13 then times which is 5Mhz then double that to get 10Mhz you will also be changing
the error from the 65mhz ocxo ie if your ocxo is say 100ppb the divide will give you better by 13 .but then x 2
will put the error out by a long way as there will be losses in such a large divide and then x2 .
In theory it should work . You will need really good JK flips flops with a high response time on the x 2
Also remember on the VC to use a zero drift op amp to control the voltage control.
Have fun
RNS
QuoteQuoteI‘m dealing thisdays with my NOS schottky TTLs and a 65 MHz OCXO ( now VC)
to design a by-13-divider with my available ICs to bring it into suitable frequencies to
follow the GSPDO path
Hi Unless I have miss understood if you want 10Mhz from 65Mhz you need to divide by 6.5
if you divide by 13 then times which is 5Mhz then double that to get 10Mhz you will also be changing
the error from the 65mhz ocxo ie if your ocxo is say 100ppb the divide will give you better by 13 .but then x 2
will put the error out by a long way as there will be losses in such a large divide and then x2 .
In theory it should work . You will need really good JK flips flops with a high response time on the x 2
Also remember on the VC to use a zero drift op amp to control the voltage control.
Have fun
RNS
You can divide all you want, error will stay the same in percentage (ppb) just smaller number of Hz (absolute value)...
Quote@ labrat: I‘m aware of the problems but it is hobby and learning by doing so let‘s see where it brings me to.
And I never expected to run in problems with this by-13-divider
I also did a lot of home experiments on this as well . I found some very good reading on the NIST site how the big guns do it and its basic the same principle as the clock divider 32.768hz divide by 16 to give 1hz good for a second
a year . from a low grade xtal.
As for the missing calibration certificate, I still haven't had any reply from Telonic on the matter. I'll let it stew for another day or two before pressing them for an answer. As Tautec said (tnx btw) there's no excuse for withholding this piece of documentation from the end customer.
JBGIf you get stuck let me know.
Flick me your SN# via PM and I can get a PDF copy from the factory.
Still, at some point I'll need your email so to forward it on to you.
The Error is also divided try it .
Can I assume that you can eliminate the error by continuous dividing?
The Error is also divided try it .
Can I assume that you can eliminate the error by continuous dividing?
No , It does work quite like that .. its like 22/7 Pi.Never ends.
The error will be smaller to 1012 . in your case
Forget the percentage which is 1/100 which will always look wrong as its a percentage of the last digit (12)
I have run some tests on a cheap 24.000 Mhz xtal Actual 24.00162843
divided it by 12 though my test setup with 2x HP 5385 (Now calibrated) comes out at 2.000135683
May not be to Nasa standards but the error did move by 12 .
I also ran the same test with 2 certified 20mhz ocxo @ 0.02ppb (New) the division by 2 before 20.0000000002 after 10.0000000001 .
Come to your own conclusion
The Error is also divided try it .
Can I assume that you can eliminate the error by continuous dividing?
No , It does work quite like that .. its like 22/7 Pi.Never ends.
The error will be smaller to 1012 . in your case
Forget the percentage which is 1/100 which will always look wrong as its a percentage of the last digit (12)
I have run some tests on a cheap 24.000 Mhz xtal Actual 24.00162843
divided it by 12 though my test setup with 2x HP 5385 (Now calibrated) comes out at 2.000135683
May not be to Nasa standards but the error did move by 12 .
I also ran the same test with 2 certified 20mhz ocxo @ 0.02ppb (New) the division by 2 before 20.0000000002 after 10.0000000001 .
Come to your own conclusionYou are wrong. The relative error (which is the only thing that counts) stays the same.
As for the missing calibration certificate, I still haven't had any reply from Telonic on the matter. I'll let it stew for another day or two before pressing them for an answer. As Tautec said (tnx btw) there's no excuse for withholding this piece of documentation from the end customer.
JBGIf you get stuck let me know.
Flick me your SN# via PM and I can get a PDF copy from the factory.
Still, at some point I'll need your email so to forward it on to you.
Thank you, I might well take you up on that offer - still no response from Telonic.
I can offer some initial observations on the subject of this topic thread, namely that my example (the 2104X+) consumes 4W in standby and 55.5W operating (turning channels off or on makes no difference - I haven't tested consumption using the FFT function so far). Also, I noticed that it takes 30 seconds longer to boot up than the 16 seconds boot time of the humble SDS1202X-E after being shutdown from the trace display mode - it takes a few seconds longer if it had been displaying an FFT on the previous shutdown, an effect I'd expect to see with the 2000X+ models when I eventually get to use the FFT features.
@Noreply,
The Error is also divided try it .
Can I assume that you can eliminate the error by continuous dividing?
No , It does work quite like that .. its like 22/7 Pi.Never ends.
The error will be smaller to 1012 . in your case
Forget the percentage which is 1/100 which will always look wrong as its a percentage of the last digit (12)
I have run some tests on a cheap 24.000 Mhz xtal Actual 24.00162843
divided it by 12 though my test setup with 2x HP 5385 (Now calibrated) comes out at 2.000135683
May not be to Nasa standards but the error did move by 12 .
I also ran the same test with 2 certified 20mhz ocxo @ 0.02ppb (New) the division by 2 before 20.0000000002 after 10.0000000001 .
Come to your own conclusionYou are wrong. The relative error (which is the only thing that counts) stays the same.Can you give A true working example of your statement that proves you right.
Can you give A true working example of your statement that proves you right.
Hi John,
short answer to the question regarding SDG2042 (2122) against SDG1032.
I‘m dealing thisdays with my NOS schottky TTLs and a 65 MHz OCXO ( now VC)
to design a by-13-divider with my available ICs to bring it into suitable frequencies to
follow the GSPDO path
The multisim simulation shows a problem above 50MHz I can not there identify.
For a breadboard design test it‘s helpfull to have the SG that goes easy above 60 MHz.
So this is for me the first advantage of my decision for the better and little bit more expensive SG.
And with the SDS as well
For testing on breadboard I built these simple probes:
http://nihtila.com/2019/03/16/tip-3-robust-high-bandwidth-passive-diy-probes/
I used selected 1k (0.1%) resistors and than the selectable divider factor (21) of the SDS inputs with 50 ohms
was first time used and appreceated.
btw: do you have a schematics of your MK2 design by the hand?