external refclock

[Basil]

I have got the Pluto to accept a 40MHz reference from the Leo, but now when I interrogate it it thinks the LO is 39999787 which is 213Hz out. So I am not sure where it has the new hex figure for the LO of 0262 592b from...

I may regret fiddling with this!

cat /proc/device-tree/clocks/clock@0/clock-frequency | xxd
00000000: 0262 592b .bY+


EDIT AGAIN


And after a power off reboot we have:

cat /proc/device-tree/clocks/clock@0/clock-frequency | xxd
00000000: 0262 5a00 .bZ.

40,000,000 Hz LO


This is where I go back to my favourite adage of if it's not broken leave the damned thing alone

[G4FRE]

The

00000000: 0262 592b .bY+

(the 0262 592b bit is the important part)



does convert from hex to 39,999,787

Dave
G4FRE

[Basil]

Thanks Dave, it's now reverted to the strange figure of 399,997,87 from 40,000,000 again. The Bodnar is definitely set to 40,000,000. I can't see the Pluto "reading" it's own LO frequency, so where is that odd number being generated? I am loathe to fiddle any more as the thing locked up and needed a paper clip reset.

Way out of my comfort zone with this....

[Basil]

I believe that I have found the cause of the Pluto sometimes seeming to be using the external Leo Bodnar reference and sometimes not, as well as the origin of the odd frequency given when interrogating the LO frequency.

The odd figure is a pre programmed frequency put in at manufacture to supposedly take account of any imperfection oin the output frequency of the stock LO source.

The reason it appeared to lock to the Leo Bodnar, and sometimes not, as well as sometimes refusing to TX was down to an Ebay sourced, Chinese made piece of *$£@ described as a high quality terminated SMA cable. It was intermittent. I made one up myself and so far it is behaving again and locked to the Leo Bodnar using the 8mA output level for both the Pluto and my GPS locked LNB.

One oddity is when I was messing with the Leo Bodnar dual output box I took the opportunity to update the firmware. Now it seems to take 10 or more minutes to lock every time it's powered down. I rang Bodnar's and as mine is the older silver box type with two BNC sockets for the outputs it appears the latest firmware can do this and they have offered to send a "possible software fix" by e-mail. So beware updating firmware if you have the older silver, BNC socketed ones...

Fingers are firmly crossed I am not speaking too soon.