Yes there is an IP address for the Kraken Pi4 unit which is assigned by your router.
If hostname resolution is enabled on your network, you can just SSH into “krakensdr”. Otherwise you’ll need to find the IP address manually via your routers config page.
I was able to get the kraken working on a Raspberry Pi 3 Model B+ by uploading the raspbian image provided in Git to a bootable SDcard. Raspbian and Ubuntu are both Debian based linux environments
DAQ Subsystem Status
Update Rate: 748 ms
Latency: 2922 ms
Frame Index: 12256
Frame Type: Data
Frame Sync: OK
Power Level: OK
Connection Status: Connected
Sample Delay Sync: OK
IQ Sync: OK
Noise Source State: Disabled
Center Frequecy [MHz]: 416.588
Sampling Frequency [MHz]: 2.4
DSP Decimated BW [MHz]: 2.400
VFO Range [MHz]: 415.388 - 417.788
Data Block Length [ms]: 436
RF Gains [dB]: [15.7, 15.7, 15.7, 15.7, 15.7]
VFO-0 Power [dB]: -64.9
I considered it could be a cpu hardware. The Raspberry Pi cpu is an ARM architecture and the Intel Core i5 architecture is x86-64 architecture. However the kraken Git provides install scripts for both x86_64 and ARM64 systems. Assuming its confirmed that the kraken software will run on Intel x86-64 architecture? My next step would be to compare the working Raspbian image file paths, libraries, config files, etc with my Ubuntu install and for notional discrepancies that may give a clue to why its not working. Particularly how it rtl_daq.h is implemented as that was a FATAL error in the log files and will look into how rtlsdr is implemented.
Also I want to try using the Docker image provided on Git however, there is note that the docker image on works for x86. Can you confirm this is strictly for x86 systems and does not include x86_64 systems?
Best,
Patrick
So it looks like your Kraken is fully functional.
Yep confirmed to run on x86_64.
The Docker image - I’m not sure as it’s third party, but I assume by x86 he meant x86_64.
Your core error “rtlsdr_demod_write_reg failed with -9” is not related to anything to do with the KrakenSDR code btw. It’s entirely related to the USB failing to talk with the RTL-SDRs on the KrakenSDR. If you’re still getting that error with kraken_test, nothing else will work for sure.
So it really is most likely a USB issue, to do with a bad USB hardware on the machine, or poor quality cable.
How do I change the default password?