Simple improvement suggestion

1

Hello all,

Please excuse me if I was wrong, but as far as I know, this one is not implemented and would be easy. I am using an old Raspberry SD image.

I would place a new button in the web interface, to enable a raw sample TCP server. That way, you click the button an then you can connect the Gnuradio block from a computer to the server in the Raspberry.

Or perhaps even better, just make the raw sample server always available with no button, even when DFing.

Could it be possible?

This would make very easy to implement beamforming, etc. in Gnuradio and still have the other features available.

Thank you very much.
Ger EA4GJA

2

We already have a GNU Radio block that can be used and instructions on how to set that up here GitHub - krakenrf/gr-krakensdr

If you are using the DFing image, you need to disable the direction finding software autoboot first. And by default to save resources on the Pi4, TCP mode is disabled in favor of shared memory transfers.

But if you’re using GNU Radio you can simply change heimdall to output data over ethernet, and use the GNU Radio block to connect to it.

3

Thank you, I suppose that will be enough for now.

I have tried DF and I am very happy with the quality of the product. Congratulations!

4

Just another related topic.

Instead of disabling DF autoboot, I would prefer not to change SD image, if possible, or make the minimum amount of changes.

I just have a very little understanding of your code and directory layout, but I manage myself OK with Unix shell and tools. If I am right, the process would be:

  1. boot the unmodified SD image in the Pi and log in from the PC using ssh
  2. stop DF (would it just be enough running ./kraken_doa_stop.sh?)
  3. backup daq_chain_config.ini
  4. modify daq_chain_config.ini to enable ethernet TCP server, the section would be [data_interface], just replacing shmem by eth
  5. stop and start heimdall daq firmware (would it be ok if I run ./daq_stop.sh, then ./daq_start_sm.sh?)
  6. run the custom Gnuradio flowgraph from the PC (assuming the kraken source block was already successfully installed)
  7. when the test is done, stop Gnuradio flowgraph in the PC
  8. restore the backup that was created in step 3
  9. shut down and power off the Pi until the next DF or custom application session, the DF should cleanly autoboot, if not check step 8

Please confirm the questions. If you can see any error or need to add anything, your view would be of great value.

What I need is a documented procedure to manually stop DF, enable serving the RF samples to the PC, and leave all unchanged in the SD card at the end. The main use of the system will remain DF, I just would to play a little with the Gnuradio block to experiment for a while.

If something goes wrong, I would burn a new SD image, but it is a boring process and is better not to break things :slight_smile:

Thank you again.

5

Best to follow the instructions on the gr-krakensdr GitHub as it mentions the heimdall_only_start.sh script which you need to use for gr-krakensdr GitHub - krakenrf/gr-krakensdr

But yes, instead of disabling autoboot you could try running kraken_doa_stop instead first.

I think the easiest thing would be to just have a second SD card dedicated to being a heimdall GNU Radio server.

6

Yes, it is better to follow the instructions, you were right :blush:.

I could successfully run the kraken gnuradio block. I have performed no difficult tests, but I connected it to null sink blocks and frequency sink instruments and all seems to work ok.

It is enough for me at the moment, thank you again and regards!

Ger EA4GJA

1 Like