Loading ...
Sorry, an error occurred while loading the content.

dttsp + sdr-shell

Expand Messages
  • robers97
    After a few days, I m eager to get the final configurations tweeks and see a spectrum and hear something with my Ensemble II and Linux workstation running
    Message 1 of 6 , Aug 30, 2013
    • 0 Attachment
      After a few days, I'm eager to get the final configurations tweeks and see a spectrum and hear something with my Ensemble II and Linux workstation running

      dttsp tag 1162 (ab2kt branch)
      sdr-shell-v2 tag 158

      Everything is compiling fine, but like some other posts, the communication mechanism between these programs is not clear.  sdr-shell gives:

      ::: Unable to get SDR_PARMPATH environment variable.
      Using default: /dev/shm/SDRcommands
      /dev/shm/SDRcommands: No such file or directory
      ::: Unable to get SDR_METERPATH environment variable.
      Using default: /dev/shm/SDRmeter
      /dev/shm/SDRmeter: No such file or directory
      ::: Unable to get SDR_SPECPATH environment variable.
      Using default: /dev/shm/SDRspectrum
      /dev/shm/SDRspectrum: No such file or directory

      /dev/shm shows these -->
      sem.sdr.buffer
      sem.sdr.meter
      sem.sdr.spectrum
      sem.sdr.update

      Am I using compatile code bases?
      Can I match these up and expect results? 
      If so, which is used for the commands?

      uname -a -->
      Linux hobbytime 3.8.0-29-lowlatency #21-Ubuntu SMP PREEMPT Thu Aug 15 12:50:08 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

      Thanks in advance,
      Steven (KC8ERT)

       
    • Sid Boyce
      The last time I used sdr-shell was in 2010. svn checkout http://sdr-shell.googlecode.com/svn/branches/sdr-shell-v2-rxtx I don t know if there is any special
      Message 2 of 6 , Aug 30, 2013
      • 0 Attachment
        The last time I used sdr-shell was in 2010.
        svn checkout http://sdr-shell.googlecode.com/svn/branches/sdr-shell-v2-rxtx

        I don't know if there is any special reason you want to run sdr-shell.

        ghpsdr3-alex uses dttsp and has been receiving updates.
        http://napan.ca/ghpsdr3/index.php/Main_Page

        The easiest program to get running is quisk
        http://james.ahlstrom.name/quisk/index.html

        I must dash, later I'll post the pre-req packages needed for quisk, I think there are at least a few more than listed for ghpsdr3-alex.
        73 ... Sid.

        On 31/08/13 04:23, robers97@... wrote:
         

        After a few days, I'm eager to get the final configurations tweeks and see a spectrum and hear something with my Ensemble II and Linux workstation running

        dttsp tag 1162 (ab2kt branch)
        sdr-shell-v2 tag 158

        Everything is compiling fine, but like some other posts, the communication mechanism between these programs is not clear.  sdr-shell gives:

        ::: Unable to get SDR_PARMPATH environment variable.
        Using default: /dev/shm/SDRcommands
        /dev/shm/SDRcommands: No such file or directory
        ::: Unable to get SDR_METERPATH environment variable.
        Using default: /dev/shm/SDRmeter
        /dev/shm/SDRmeter: No such file or directory
        ::: Unable to get SDR_SPECPATH environment variable.
        Using default: /dev/shm/SDRspectrum
        /dev/shm/SDRspectrum: No such file or directory

        /dev/shm shows these -->
        sem.sdr.buffer
        sem.sdr.meter
        sem.sdr.spectrum
        sem.sdr.update

        Am I using compatile code bases?
        Can I match these up and expect results? 
        If so, which is used for the commands?

        uname -a -->
        Linux hobbytime 3.8.0-29-lowlatency #21-Ubuntu SMP PREEMPT Thu Aug 15 12:50:08 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

        Thanks in advance,
        Steven (KC8ERT)

         



        -- 
        Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
        Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
        Senior Staff Specialist, Cricket Coach
        Microsoft Windows Free Zone - Linux used for all Computing Tasks
        
      • Sid Boyce
        Packages needed for quisk:- apt-get install libfftw3-dev libasound2-dev libportaudio2 portaudio19-dev libncurses5-dev libwxbase2.8-0 libwxgtk2.8-0
        Message 3 of 6 , Aug 31, 2013
        • 0 Attachment
          Packages needed for quisk:-
          "apt-get install libfftw3-dev libasound2-dev libportaudio2 portaudio19-dev libncurses5-dev libwxbase2.8-0 libwxgtk2.8-0 python-wxgtk2.8 python-wxversion libusb-dev python2.7-dev"

          ------------------------------------------------------------------- CUT ------------------------------------------------------

          Copy and paste the next to /etc/udev/rules.d/99-softrock.rules
          ----------------------------------------------------------------- CUT -------------------------------------------------------
          SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="16c0", ATTR{idProduct}=="05dc", MODE="0666", GROUP="dialout"
          ----------------------------------------------------------------  CUT ----------------------------------------------------
          73 ... Sid.

          On 31/08/13 07:28, Sid Boyce wrote:
           

          The last time I used sdr-shell was in 2010.
          svn checkout http://sdr-shell.googlecode.com/svn/branches/sdr-shell-v2-rxtx

          I don't know if there is any special reason you want to run sdr-shell.

          ghpsdr3-alex uses dttsp and has been receiving updates.
          http://napan.ca/ghpsdr3/index.php/Main_Page

          The easiest program to get running is quisk
          http://james.ahlstrom.name/quisk/index.html

          I must dash, later I'll post the pre-req packages needed for quisk, I think there are at least a few more than listed for ghpsdr3-alex.
          73 ... Sid.

          On 31/08/13 04:23, robers97@... wrote:
           

          After a few days, I'm eager to get the final configurations tweeks and see a spectrum and hear something with my Ensemble II and Linux workstation running

          dttsp tag 1162 (ab2kt branch)
          sdr-shell-v2 tag 158

          Everything is compiling fine, but like some other posts, the communication mechanism between these programs is not clear.  sdr-shell gives:

          ::: Unable to get SDR_PARMPATH environment variable.
          Using default: /dev/shm/SDRcommands
          /dev/shm/SDRcommands: No such file or directory
          ::: Unable to get SDR_METERPATH environment variable.
          Using default: /dev/shm/SDRmeter
          /dev/shm/SDRmeter: No such file or directory
          ::: Unable to get SDR_SPECPATH environment variable.
          Using default: /dev/shm/SDRspectrum
          /dev/shm/SDRspectrum: No such file or directory

          /dev/shm shows these -->
          sem.sdr.buffer
          sem.sdr.meter
          sem.sdr.spectrum
          sem.sdr.update

          Am I using compatile code bases?
          Can I match these up and expect results? 
          If so, which is used for the commands?

          uname -a -->
          Linux hobbytime 3.8.0-29-lowlatency #21-Ubuntu SMP PREEMPT Thu Aug 15 12:50:08 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

          Thanks in advance,
          Steven (KC8ERT)

           



          -- 
          Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
          Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
          Senior Staff Specialist, Cricket Coach
          Microsoft Windows Free Zone - Linux used for all Computing Tasks
          


          -- 
          Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
          Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
          Senior Staff Specialist, Cricket Coach
          Microsoft Windows Free Zone - Linux used for all Computing Tasks
          
        • Steve Roberts
          Thanks for the pointers Sid! I m not tied to either program, but as you realized am just looking to get something going. I should have mentioned I m tied to
          Message 4 of 6 , Aug 31, 2013
          • 0 Attachment

            Thanks for the pointers Sid!  I'm not tied to either program, but as you realized am just looking to get something going.  I should have mentioned I'm tied to my FA-66 firewire attach which I believe dictates that I use JACK.

            ghpsdr3-alex looks promising. I see the JACK and softrock support is there.  I'll work to ensure Qt5 installed correctly and try to get it going.

            Like you said, Quisk got going quick.  However, it was using my MIC as a line in.  I see no mention that it will work with JACK and see no native connection to the JACK server.  I need to see if I can route JACK to the JACK Pulse Audio connection and then configure Quisk to use that instead of the hw0 or what ever default is causing it to use the MIC.  If that doesn't sound right, maybe someone can post a quisk_config py file I can use to compare.



          • Sid Boyce
            The only one I know who was using firewire was Graeme (ZL2APV) - doc at http://mobokits.stormwarning.org/content/mobo-43-files InstallingLinuxSDRs-006.odt
            Message 5 of 6 , Sep 1, 2013
            • 0 Attachment
              The only one I know who was using firewire was Graeme (ZL2APV) - doc at
              http://mobokits.stormwarning.org/content/mobo-43-files InstallingLinuxSDRs-006.odt  describes using firewire.

              Other things took over so Graeme and I never got around to doing version 007 which would have had the addition for running sdr-core/sdr-shell.
              I think this is the last script I used for sdr-shell back in early Jan 2011 when the distros only came with jack1 and we had to build (jack2) jackmp locally.
              ----------------------------- CUT ----------------------------------------------------
              #!/bin/bash

              # define name used in the RMI registry
              NAME=SDR-SHELL
              export SDR_DEFRATE=48000
              export JACK_BUFFER=2048
              export LD_LIBRARY_PATH=/usr/local/lib64

              # start usbsoftrock daemon
              echo "starting usbsoftrock..."

              usbsoftrock -a -d &

              # start jackd
              echo "starting jackd ..."

              /usr/local/bin/jackd -m -r -dalsa -dhw:2 -r${SDR_DEFRATE} -p${JACK_BUFFER} -n2&

              sleep 1

              echo "starting audioadater to add the other soundcard channels"
              /usr/local/bin/jack_load audioadapter -i "-dhw:1 -r${SDR_DEFRATE} -p${JACK_BUFFER} -n2"

              sleep 3
              # start RX DttSP
              echo "starting DttSP ${NAME}_RX ..."
              /usr/bin/sdr-core --spectrum --metering --client-name=${NAME}_RX --buffsize=${JACK_BUFFER} --ringmult=4 --command-port=19001 --spectrum-port=19002 --meter-port=19003&
              sleep 3

              # connect receiver
              echo "connecting receiver ..."
              /usr/local/bin/jack_connect audioadapter:capture_1 ${NAME}_RX:il
              sleep 1
              /usr/local/bin/jack_connect audioadapter:capture_2 ${NAME}_RX:ir
              sleep 1
              /usr/local/bin/jack_connect ${NAME}_RX:ol system:playback_1
              sleep 1
              /usr/local/bin/jack_connect ${NAME}_RX:or system:playback_2
              sleep 1

              # start the tx dttsp
              /usr/bin/sdr-core -s -m -v --client-name=${NAME}_TX --spectrum-port=19006 --meter-port=19007 --command-port=19005 &
              sleep 3

              # connect transmitter
              echo "connecting transmitter"
              /usr/local/bin/jack_connect ${NAME}_TX:ol audioadapter:playback_1
              sleep 1
              /usr/local/bin/jack_connect ${NAME}_TX:or audioadapter:playback_2
              sleep 1
              /usr/local/bin/jack_connect system:capture_1 ${NAME}_TX:il
              sleep 1
              /usr/local/bin/jack_connect system:capture_2 ${NAME}_TX:ir
              sleep 1

              jack_lsp -c

              # start sdr-shell
              # sdr-shell-rxtx-qt4 &
              sdr-shell &
              -------------------------------------- CUT ------------------------------------

              Below is ~/.quisk_conf.py I used when I had a working Ensemble RXTX.

              On 01/09/13 04:05, Steve Roberts wrote:
               

              Thanks for the pointers Sid!  I'm not tied to either program, but as you realized am just looking to get something going.  I should have mentioned I'm tied to my FA-66 firewire attach which I believe dictates that I use JACK.

              ghpsdr3-alex looks promising. I see the JACK and softrock support is there.  I'll work to ensure Qt5 installed correctly and try to get it going.

              Like you said, Quisk got going quick.  However, it was using my MIC as a line in.  I see no mention that it will work with JACK and see no native connection to the JACK server.  I need to see if I can route JACK to the JACK Pulse Audio connection and then configure Quisk to use that instead of the hw0 or what ever default is causing it to use the MIC.  If that doesn't sound right, maybe someone can post a quisk_config py file I can use to compare.



              -------------------------------------- CUT ------------------------------
              # This is a sample quisk_conf.py configuration file for a SoftRock Rx/Tx Ensemble.

              # Please do not change this sample file.
              # Instead copy it to your own .quisk_conf.py and make changes there.
              # See quisk_conf_defaults.py for more information.

              # Attach your SoftRock Rx/Tx Ensemble to the line in and line out of a high quality
              # sound card.  Set name_of_sound_capt and name_of_mic_play to this card.  You need
              # a second (lower quality) sound card to play radio audio named name_of_sound_play.
              # This is sufficient for CW.  To transmit SSB, you need a capture sound card named
              # microphone_name.  The microphone_name and name_of_sound_play can be the same device.

              from softrock import hardware_usb as quisk_hardware
              from softrock import widgets_tx   as quisk_widgets

              # In Linux, ALSA soundcards have these names.  The "hw" devices are the raw
              # hardware devices, and should be used for soundcard capture.
              #name_of_sound_capt = "hw:0"
              name_of_sound_capt = "hw:2"
              #name_of_sound_capt = "plughw"
              #name_of_sound_capt = "plughw:1"
              #name_of_sound_capt = "default"

              # Vendor and product ID's for the SoftRock
              usb_vendor_id = 0x16c0
              usb_product_id = 0x05dc
              softrock_model = "RxTxEnsemble"

              # If you want to monitor the hardware key state, enter a poll time in milliseconds.
              key_poll_msec = 0

              sample_rate = 48000                             # ADC hardware sample rate in Hertz
              #name_of_sound_capt = "hw:0"                    # Name of soundcard capture hardware device.
              name_of_sound_play = "hw:0"                     # Name of soundcard playback hardware device.

              # Microphone capture:
              microphone_name = "hw:0"                        # Name of microphone capture device
              #name_of_mic_play = name_of_sound_capt          # Name of play device if CW or mic I/Q is sent to a sound card
              name_of_mic_play = "hw:2"
              mic_playback_rate = sample_rate         # Playback rate must be a multiple 1, 2, ... of mic_sample_rate
              mic_out_volume = 1.0                            # Transmit sound output volume (after all processing) as a fraction 0.0 to 1.0
              -------------------------------------- CUT -----------------------------------------------------

              -- 
              Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
              Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
              Senior Staff Specialist, Cricket Coach
              Microsoft Windows Free Zone - Linux used for all Computing Tasks
              
            • graemevj
              Hi Steve, Have a look at this document. I had SDR-Shell running with an FA-66 firewire and documented some of the setup here ...
              Message 6 of 6 , Sep 1, 2013
              • 0 Attachment

                Hi Steve,


                Have a look at this document. I had SDR-Shell running with an FA-66 firewire and documented some of the setup here ... http://mobokits.stormwarning.org/sites/default/files/mobo/InstallingLinuxSDRs-005.odt

                Hope it helps. I did this a few years ago so will be scratching to be of further help. Sid slso added some setup help for Quisk which I also used with the FA-66. Nowadays I use a Mobo/softrock6.3/Widget or HiQSDR.


                73 Graeme



                --- In softrock40@yahoogroups.com, <sboyce@...> wrote:

                The only one I know who was using firewire was Graeme (ZL2APV) - doc at
                http://mobokits.stormwarning.org/content/mobo-43-files InstallingLinuxSDRs-006.odt  describes using firewire.

                Other things took over so Graeme and I never got around to doing version 007 which would have had the addition for running sdr-core/sdr-shell.
                I think this is the last script I used for sdr-shell back in early Jan 2011 when the distros only came with jack1 and we had to build (jack2) jackmp locally.
                ----------------------------- CUT ----------------------------------------------------
                #!/bin/bash

                # define name used in the RMI registry
                NAME=SDR-SHELL
                export SDR_DEFRATE=48000
                export JACK_BUFFER=2048
                export LD_LIBRARY_PATH=/usr/local/lib64

                # start usbsoftrock daemon
                echo "starting usbsoftrock..."

                usbsoftrock -a -d &

                # start jackd
                echo "starting jackd ..."

                /usr/local/bin/jackd -m -r -dalsa -dhw:2 -r${SDR_DEFRATE} -p${JACK_BUFFER} -n2&

                sleep 1

                echo "starting audioadater to add the other soundcard channels"
                /usr/local/bin/jack_load audioadapter -i "-dhw:1 -r${SDR_DEFRATE} -p${JACK_BUFFER} -n2"

                sleep 3
                # start RX DttSP
                echo "starting DttSP ${NAME}_RX ..."
                /usr/bin/sdr-core --spectrum --metering --client-name=${NAME}_RX --buffsize=${JACK_BUFFER} --ringmult=4 --command-port=19001 --spectrum-port=19002 --meter-port=19003&
                sleep 3

                # connect receiver
                echo "connecting receiver ..."
                /usr/local/bin/jack_connect audioadapter:capture_1 ${NAME}_RX:il
                sleep 1
                /usr/local/bin/jack_connect audioadapter:capture_2 ${NAME}_RX:ir
                sleep 1
                /usr/local/bin/jack_connect ${NAME}_RX:ol system:playback_1
                sleep 1
                /usr/local/bin/jack_connect ${NAME}_RX:or system:playback_2
                sleep 1

                # start the tx dttsp
                /usr/bin/sdr-core -s -m -v --client-name=${NAME}_TX --spectrum-port=19006 --meter-port=19007 --command-port=19005 &
                sleep 3

                # connect transmitter
                echo "connecting transmitter"
                /usr/local/bin/jack_connect ${NAME}_TX:ol audioadapter:playback_1
                sleep 1
                /usr/local/bin/jack_connect ${NAME}_TX:or audioadapter:playback_2
                sleep 1
                /usr/local/bin/jack_connect system:capture_1 ${NAME}_TX:il
                sleep 1
                /usr/local/bin/jack_connect system:capture_2 ${NAME}_TX:ir
                sleep 1

                jack_lsp -c

                # start sdr-shell
                # sdr-shell-rxtx-qt4 &
                sdr-shell &
                -------------------------------------- CUT ------------------------------------

                Below is ~/.quisk_conf.py I used when I had a working Ensemble RXTX.

                On 01/09/13 04:05, Steve Roberts wrote:
                 

                Thanks for the pointers Sid!  I'm not tied to either program, but as you realized am just looking to get something going.  I should have mentioned I'm tied to my FA-66 firewire attach which I believe dictates that I use JACK.

                ghpsdr3-alex looks promising. I see the JACK and softrock support is there.  I'll work to ensure Qt5 installed correctly and try to get it going.

                Like you said, Quisk got going quick.  However, it was using my MIC as a line in.  I see no mention that it will work with JACK and see no native connection to the JACK server.  I need to see if I can route JACK to the JACK Pulse Audio connection and then configure Quisk to use that instead of the hw0 or what ever default is causing it to use the MIC.  If that doesn't sound right, maybe someone can post a quisk_config py file I can use to compare.



                -------------------------------------- CUT ------------------------------
                # This is a sample quisk_conf.py configuration file for a SoftRock Rx/Tx Ensemble.

                # Please do not change this sample file.
                # Instead copy it to your own .quisk_conf.py and make changes there.
                # See quisk_conf_defaults.py for more information.

                # Attach your SoftRock Rx/Tx Ensemble to the line in and line out of a high quality
                # sound card.  Set name_of_sound_capt and name_of_mic_play to this card.  You need
                # a second (lower quality) sound card to play radio audio named name_of_sound_play.
                # This is sufficient for CW.  To transmit SSB, you need a capture sound card named
                # microphone_name.  The microphone_name and name_of_sound_play can be the same device.

                from softrock import hardware_usb as quisk_hardware
                from softrock import widgets_tx   as quisk_widgets

                # In Linux, ALSA soundcards have these names.  The "hw" devices are the raw
                # hardware devices, and should be used for soundcard capture.
                #name_of_sound_capt = "hw:0"
                name_of_sound_capt = "hw:2"
                #name_of_sound_capt = "plughw"
                #name_of_sound_capt = "plughw:1"
                #name_of_sound_capt = "default"

                # Vendor and product ID's for the SoftRock
                usb_vendor_id = 0x16c0
                usb_product_id = 0x05dc
                softrock_model = "RxTxEnsemble"

                # If you want to monitor the hardware key state, enter a poll time in milliseconds.
                key_poll_msec = 0

                sample_rate = 48000                             # ADC hardware sample rate in Hertz
                #name_of_sound_capt = "hw:0"                    # Name of soundcard capture hardware device.
                name_of_sound_play = "hw:0"                     # Name of soundcard playback hardware device.

                # Microphone capture:
                microphone_name = "hw:0"                        # Name of microphone capture device
                #name_of_mic_play = name_of_sound_capt          # Name of play device if CW or mic I/Q is sent to a sound card
                name_of_mic_play = "hw:2"
                mic_playback_rate = sample_rate         # Playback rate must be a multiple 1, 2, ... of mic_sample_rate
                mic_out_volume = 1.0                            # Transmit sound output volume (after all processing) as a fraction 0.0 to 1.0
                -------------------------------------- CUT -----------------------------------------------------

                -- 
                Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
                Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
                Senior Staff Specialist, Cricket Coach
                Microsoft Windows Free Zone - Linux used for all Computing Tasks
                
              Your message has been successfully submitted and would be delivered to recipients shortly.