Re: ProgRock not working #progrock
Alan de G1FXB
Hi Sid,toggle quoted messageShow quoted text
No intention to make you look an idiot.
The "insertion" of ?????? is something related to use of a particular mail client, it has being present for a while since an "upgrade", and on two machines
especially prevalent when quoting in posts where the original poster does not share identical character sets?
(We may both "speak English" but different variations there of...........)
I do have a propensity to use a string of ....... to encourage stop & think, over topics. ?:-)?
To make it clear to all readers, I make a conscious effort to highlight through the use of bold type to draw attention to, or adding colour to the text where I cut and paste quotes.
Please do not feel singled out, check back on some of my past replies to others as far back as April(?), hopefully you should see similar findings.
Being open source and donation ware it perhaps owes me what I pay for it....... & off topic for this board.
To Progrock Business & recap.......
" But that is not the issue, the issue to me is that the controller is not making the necessary corrections. "
It's strange both you and Robin both have similar(?) setting problems currently.....
a/. searching the progrock threads is something encouraged for all for a global view to what the group knowledge is.
the progrock kit has being sold since, early 2016.
Hans hasn't indicated any recent changes, indeed he is otherwise occupied elsewhere.
If there were major flaws to it's operation it would be revealed by now.
It's a simple & cheap $18 kit it does what it advertises very well.
Indeed it has a unique PSU noise filter not found in any other kit?
b/. Enabling GPS correction resulting in 2 - 3KHz frequency swings in the 10MHz output over 15 minutes while a straight out of the box progrock is expected to have a 1KHz accuracy without any GPS correction
is a plain indication something is wrong.
c/. A none intentional problem in the assembly or out of spec components.
There is little on the progrock PCB to go wrong without showing in areas other than the known 2-3KHz errors, you are communicating with the AVR fine through Hyperterminal.
The Si5351 pcb is harder to identify, but at the instance of manually updating the reg2 bin resulting a more stable condition, then increasing wild swings infers a clean bill of health to this as well,
as it can be be disciplined albeit manually.....
A next case check could be to make a observation of the 27MHz Osc, stability. It's what everything depends on.........
d/. Incorrect settings causing a race condition.
My initial post encouraged a reply to what you had modified beyond the defaults....
(especially the opportunity to reveal if you had opened "Pandora's box" and modified register 28 contents.)
e/. something I take aspects as a nothing more than perhaps a typo and inadvertently transferred the values, inconveniently it is also in a greater finding....
" Some additional details...
4) I have tried different values for Reg 5 with no observable difference. It is otherwise set to 0. "
(Register 5 is reserved to set output frequency of Bank 0, Clk 1)
Without putting words in your mouth,
You meant to type something approximating
Register 3 (which has a default value of 5)
you have tried different settings beyond a value of 0, (0 being the instruction applying "continuous" GPS discipline.)
With no observable difference?
The no " observable difference " is perhaps a red flag as I'm sure you realise.
5 should equate to 5KHz threshold before correction, presumably values up to 9 are equally acceptable in the absence of a max value in the manual .
Which brings you back to your starting point, why have you residual 2-3KHz deviations.....
f/. Out of interest have you tried setting up another Bank & CLK 0/1 and does it exhibit the same fault symptoms, science suggests it will
g/. Hans has not revealed use of register 0.
h/. There is no chance you have anything generating EM / RF field around your measurement bench getting into either the progrock or test gear?
i/. A honest thought, having so many unknowns?
(Having easy serial access to editing some powerful registers and not pointing fingers.)
Nothing to loose in a factory reset, at this stage and taking stock of the symptoms again from a known, out of the box starting point..........
If Robin is reading this thread and makes similar checks he can perhaps provide the most useful second findings.
On 13/07/2019 17:21, w7qjq wrote: