This forum is run by the BATC (British Amateur Television Club), it is service made freely available to all interested parties, please do not abuse this privilege.
Freq extension configuration : Ok
Receiving end: Tutioune with SERIT pro
Tests performed at 1255MhZ : All modes modes DVB-S and DVB-S2 (QPSK, 8PSK, 16APSK, 32APSK) Ok for SR from 125K to 2M maximum
MER from 10db (32APSK) to 14db (16APSK) to 16-17dB (8PSK) and to 18-19dB (QPSK)
Timing lock indicator only 41% for low SR / Up to 92-98% at 2M
Not detailed but quite similar figures at 2400Mhz
No image decoded at 437Mhz whatever the mode (signal too dirty ?)
Signal too small at 146Mhz (not usable for us in France, for tests purposes only)
There is a pike on the signal, due to not balanced IQ ?
See pictures taken : https://www.dropbox.com/s/nic2dqoulzftw ... DR.7z?dl=0
Pluto disconnects when I plug in a USB item (my logitech C920 cam) and select it in the menu (video input)
73's - Christian
I have not done any calibration of the Pluto (mainly because the link on the
Analog Devices website that tells you how to do it is broken).
On my system the spike is hardly noticeable.
I have primarily done my tests at 1.249 GHz so I can't comment on the
results you are seeing. Compared to DATV-Express the EVM (directly equivalent to MER)
is worse but that may well be due to lack of calibration.
I will power up my modulation analyser later today and do some tests at the
The signal at 146.5 and 437 looks fine (not as good as DATV-Express though).
I did find that I have set the level too high in DVB-S mode and there is a numerical
overflow in the AD9363's internal filter (it is OK with DVB-S2). I will reduce the
magnitude of the symbols I am sending to eliminate the overflow.
https://wiki.analog.com/university/tool ... users/name
I am getting no where near the claimed 7 - 11 MS/s performance.
All the other things I can live with
Spot on Charles. I've corrected that so I'll now have another go.Clive I don't think you have done the mod correctly, check that
# fw_printenv attr_name
# fw_printenv attr_val
return the right values someone else couldn't get the extended range to work and it turned out
fw_printenv attr_val was returning "ad9364" when it should have been ad9364 without quotes
The page at: https://wiki.analog.com/university/tool ... ustomizing incorrectly states:
The second line should be:To change things to the AD9364 configuration:
# fw_setenv attr_name compatible
# fw_setenv attr_val “ad9364”
# pluto_reboot reset
# fw_setenv attr_val ad9364
The app doesn't start for my DATV express card either, but in device manager it shows up under Atmel devices but does appear to have the correct libusb-win32 driver installed.
Any ideas as to what I've screwed up this time ?