Great news! :)
Cheers,
Magnus
On 08/17/2015 09:33 AM, Ole Petter Ronningen wrote:
Fantastic, just what I needed. Thank you!
On Sun, Aug 16, 2015 at 9:16 PM, Magnus Danielson <
mag...@rubidium.dyndns.org> wrote:
Ole,
I checked with a former Pendulum employee, and free off memory, he
recommen
Fantastic, just what I needed. Thank you!
On Sun, Aug 16, 2015 at 9:16 PM, Magnus Danielson <
mag...@rubidium.dyndns.org> wrote:
> Ole,
>
> I checked with a former Pendulum employee, and free off memory, he
> recommend trimming up the 100 MHz until Error 2 does not show. Sensing it
> directly can
David and others,
I will have to come back on the details. However, I'll give you the
overview from the top of my head.
The one calibration value kept in CMOS backup is the length of the
calibration pulse. This can be altered over GPIB. The program will sweep
over the value range (don't know
Magnus,
I have a few of these counters and would love to see the details of the
calibration process you mention.
Cheers.
david
On 17/08/2015 5:16 AM, Magnus Danielson wrote:
Ole,
I checked with a former Pendulum employee, and free off memory, he
recommend trimming up the 100 MHz until Er
.
Cheers;
Thomas Knox
> Date: Sun, 16 Aug 2015 21:16:22 +0200
> From: mag...@rubidium.dyndns.org
> To: time-nuts@febo.com
> CC: mag...@rubidium.se
> Subject: Re: [time-nuts] Troubleshooting Fluke PM6681
>
> Ole,
>
> I checked with a former Pendulum employee, and free
Ole,
I checked with a former Pendulum employee, and free off memory, he
recommend trimming up the 100 MHz until Error 2 does not show. Sensing
it directly can be difficult, FET-probe essentially mandatory.
Indirectly a 10 MHz is possible. A problem is that trimming with the
hood off causes a
Hello.
I have a Fluke PM6681 that has issues. When I got it, it gave results all
over the place, but after adjusting the 100Mhz multiplier-chain, it seems
to be much better; at least I get std.deviationwell within spec using a
split pulse to input A and B, 100 samples. I'd like to get it
professio
