summaryrefslogtreecommitdiffstats
path: root/10.-KerberosSDR-Setup-for-KrakenSDR-Software.md
blob: 2d08ace94d13e3ec008e4bf2027460fb80a241bc (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
# Using KerberosSDR with KrakenSDR Software

KerberosSDR is compatible with the new KrakenSDR software. The following describes how to set up your KerberosSDR to work with the KrakenSDR software.

## KerberosSDR BOOTING NOTE
(We note that the following problem may be actually fixed with the latest Pi 4 Firmware, but will leave this information here in case people continue to experience this issue). The Pi 4 hardware has a problem where it will not boot if a powered USB hub drawing current from the Pi 4 is plugged in. Inside the KerberosSDR is a powered USB hub and hence the Pi 4 will not boot if the KerberosSDR is plugged in. So please plug the KerberosSDR in after booting. For the KrakenSDR the hardware implementation forces external power only, so this problem does not occur. 
    
We strongly recommend making a small modification by removing a jumper on the KerberosSDR PCB to avoid this Pi 4 issue. This modification force external power only on the KerberosSDR by opening the enclosure, carefully removing the top calibration board, and then removing the `JP2` jumper from the PCB.

![kerberos_jumper_mod](https://user-images.githubusercontent.com/78108016/163519259-bc6c8f37-87fc-4742-8f03-c3cae849e133.jpg)

## KerberosSDR EEPROM Update
For KerberosSDR users you will need to initially flash the EEPROM to use the new serial numbering scheme. Connect a monitor and boot up the image file. The code will not start as the EEPROMs are incorrect.
   
There is a script in `~/krakensdr_doa/heimdall_daq_fw/util/kerberos_eeprom_init.sh` that can guide your through this. Just plug in your KerberosSDR (ensuring it is powered from the power port), and run the script `./kerberos_eeprom_init.sh`. The script will guide you to use the DIP switches to turn all units off, except the currently requested tuner. It will then flash the realtek_oem firmware, then the serial number, before asking you to turn off that tuner, and turn on the next one. Answer `Y` each time it asks to flash.

Once the EEPROM is flashed you can reboot and follow the reconfiguration step below.

## KerberosSDR Reconfiguration (For DoA Software)
The image is currently set up for the KrakenSDR. For KerberosSDR users, please update the EEPROM as described above first, then reboot. Once the web interface has loaded, expand the "Basic DAQ Settings" by clicking on the checkbox. Under "Preconfigured DAQ Files" select "kerberosSDR_default", and then click on "Reconfigure and Restart DAQ chain". This may take a minute or so, but after it's completed the software should connect and begin processing. If 'Reconfigure and Restart DAQ chain' does not fully restart the software after a few minutes, please perform a hard or soft reboot of the Pi4.

## KerberosSDR Retuning
The KrakenSDR code is designed to autocalibrate phase on each retune. Unfortunately this feature is not available on the KerberosSDR due to the lack of a noise source switching circuit. So with the KerberosSDR every time you change the frequency or DAQ settings, you must make sure that you have the antennas disconnected. (NOTE: This is only a problem for the DoA software which requires sample and phase calibration. For PR only sample calibration is required, and hence retuning should be fine without needing to disconnect antennas.)
    
Also if you make any custom changes to the DAQ settings (which is not recommended), always ensure that `Calibration Track Mode` is set to `No Tracking` otherwise the software will attempt to recalibrate every X-minutes.

Once you've set the center frequency, you can connect your antennas. In the Spectrum screen you can use 'click to tune' to tune to any frequency within the active bandwidth without needing to recalibrate.

## KerberosSDR External Switches
If you are using external switches from ckoval and compiling the code from scratch, make sure install PIGPIO and uncomment the PIGPIO build line in the _daq_core Makefile before compiling the _daq_core code.

`# Uncomment if you are using third party switches from ckoval on a Rpi device and have pigpio installed`

`#PIGPIO=-lpigpio -DUSEPIGPIO`

If you are using the ready to use Pi4 image, the GPIO control of the switches should already be enabled, so you do not need to recompile anything.