The Kraken is ready the instant you connect power and USB, there’s no computer or software on it, so there’s nothing to boot.
It is possible that the Kraken is faulty. It shouldn’t be twitchy at all.
It would be best if you can provide the logs when it fails by SSHing into the device so we can better tell what is going on.
Ok. I will do that as soon as I figure out how to get it to talk to my home Wifi. I don’t think this will be something I want to tackle using my phone.
Once I get it connected, I will light up the sections one by one and record current draw for each step.
I agree, it shouldn’t be twitchy. Yet watching it go from working to non-working multiple times in the space of a few minutes kinda screams “twitchy”.
Gave up trying to get it on home network, instead I used a screen and keyboard. The micro HDMI was a challenge.
Screen, Pi, and kraken each have their own powerbank and are using the same 1’ USB-A to USB-C power cables. All power banks at 100% at beginning of test.
First try:
Kraken powered up, drawing 0.194A at 5.05V
Pi powered up, kraken drawing 0.856A at 5.13V
Attempted kraken_test -d0 through d4, none worked. “USB claim interface error -6”
Removed all power.
Second try:
Kraken powered up, drawing 0.194A at 5.05V
Pi powered up, kraken drawing 0.856A at 5.13V
kraken_test -d0 ok 1.99A at 5.13V
kraken_test -d1 ok 1.99A at 5.13V
kraken_test -d2 ok 1.99A at 5.13V
kraken_test -d3 ok 1.99A at 5.13V
kraken_test -d4 ok 1.99A at 5.13V
Then I opened five windows and ran all five at the same time.
No issues noted, 1.97A at 5.13V.
Now what?
Has the software been modified in any way? Generally you would need to stop the KrakenSDR software first before running kraken_test or you’d get the USB claim interface error, because the autobooting KrakenSDR software would be running.
So I’m surprised that your second try worked straight away. Presumably the autobooting software couldn’t start for some reason.
Please paste the logs from:
~/krakensdr_doa/krakensdr_doa/_share/logs/krakensdr_doa/ui.log
and
~/krakensdr_doa/heimdall_daq_fw/Firmware/_logs
No modofication to the software.
I don’t remember seeing anything in the power supply test doc talking about stopping the krakensdr software first.
So apparently it was running on the first try, and not on the second?
I just added that clarification to the wiki now. Initially, we didn’t expect the need for troubleshooting with the ready to use image on known devices, and that troubleshooting would only be required on custom device installations that don’t autoboot by default.
Yes it would seem that the software started on the first run, because when you tried to run kraken_test, it said that the tuners were busy, which means that the DOA software is using them.
On the second try, assuming you didn’t purposely stop the autoboot, the software may have failed to start because the tuners were free to be accessed by kraken_test. In this case it would be interesting to see what the logs showed.
All I did was remove and re apply power, and after the gui came up, proceed as instructed.
Right now, I’m not sure what’s the best way to get at the log files. Copy to flashdrive and then email from here? It’s been a while since I was under the hood in linux.
Yeah that is a good way if you can’t get it connected to the internet via WiFi or a network cable.