KrakenSDR API endpoints and documentation

Hello. Can I write my own client to get the current DOA? What I mean is that there is a web server on Raspberry PI on port 8080, that provides a web interface for KrakenSDR configuration and DOA estimation. And I would like to write a client software for personal use, that will extract the current DOA (the one on the compass on the “DOA Estimation” tab). Can I do that? I mean your web client gets this data somehow, as well as the Android application.

So my questions are:

  1. Does a Raspberry PI’s :8080 Kraken web server have an API that could be queried and is it documented somewhere?
  2. If there are no documented APIs, how can I get a current DOA (and current frequency if possible) in the same way the Android app (allegedly) does? I.e. is there an endpoint like GET http://krakensdr:8080/doa that returns something like { angle: 180, frequency: 446.031 } ?

I have tried monitoring web clients’ requests to the raspberry server using the chrome console, but haven’t seen any queries. I thought that the web client makes a request every N ms to get a DOA and then draws the data on the compass, but apparently, I was wrong.

Thank you

Is this what you are looking for?

When set to the ‘Kraken App’ DOA Data Format the latest bearing data will be output to an HTML page at “http://PI4_IP_ADDR:8081/DOA_value.html” in the CSV format every update period.

The output format CSV ordering is as follows:

1. UNIX Epoch Time : (13 Digit LONG),
2. Max DOA Angle in Degrees in Compass Convention : (3 Digit 000 - 359, 90deg East),
3. Confidence Value : (0-99 float, higher indicates a better quality reading),
4. RSSI Power in dB : (0 dB is max power),
5. Channel Frequency in Hz,
6. Antenna Array Arrangement : ("UCA"/"ULA"/"Custom"),
7. Latency in ms : (Time from signal arrival at antenna, to result. NOT including network latency.),
8. Station ID : (Name of the KrakenSDR station inputted in the Station Information box in the Web GUI),
9. Latitude,
10. Longitude,
11. GPS Heading,
12. Compass Heading (if available),
13. Main Heading Sensor Used ("GPS"/"Compass"),
14-17. Reserved for possible future use,
18-377. Full 360 degrees DOA output. First element specifies DOA power output at 0 degrees, second element power at 1 degrees etc. NOTE: Uses unit circle convention, so due EAST is classed as 0 degrees, NORTH 90 degrees and so on. Needs to be rotated into compass convention.

If multiple VFO channels are used, each channel will output it’s own unique CSV data from 1-377 separated by a newline character “\n”.

1 Like