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

Re: [softrock40] Re: Anybody using SoftRock RXTX6.3 + Dttsp + SDR-Shell ?

Expand Messages
  • Sid Boyce
    See my previous posting with the sdr-shell URL. qjackctl is a QT application that provides a sound card patch panel. 73 ... Sid. ... -- Sid Boyce ... Hamradio
    Message 1 of 34 , Aug 19, 2009
    • 1 Attachment
    • 627 KB
    See my previous posting with the sdr-shell URL. qjackctl is a QT
    application that provides a sound card patch panel.
    73 ... Sid.

    On 19/08/09 02:25, dahdahdidit wrote:
    >
    >
    > Edson,
    >
    > Jackd and sdr-core both run on my system. I don't know what qjackctl is
    > - I don't see it in your start.rx script which I am using to start
    > sdr-shell. Here is how I have gotten it to run without giving any errors
    > (but without displaying a signal either)::
    >
    > #!/bin/sh
    > # define name used in the RMI registry
    > NAME=SDR-SHELL
    > export SDR_DEFRATE=48000
    > export JACK_BUFFER=1024
    >
    > # start jackd (firewire fa-66)
    > echo "starting jackd ..."
    > #DELTA-44
    > /usr/bin/jackd -d alsa -d hw:0 -r$SDR_DEFRATE -p${JACK_BUFFER} -n3&
    >
    > sleep 5
    >
    > # 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&
    >
    > sleep2
    >
    > # start sdr-shell
    > sdr-shell&
    >
    > ------------------------- so that ^ seems to start everything but it
    > does not like NAME=SDR-SHELL.
    >
    > Am I using the wrong startup script? I found this one on your site.Again
    > what I am trying to do is get a signal displayed on SDR-Shell. I never
    > came across qjackctl anywhere in the documentation to date so if you
    > have some info on that it would be helpful.
    >
    > Thanks - Rob
    >
    > --- In softrock40@yahoogroups.com <mailto:softrock40%40yahoogroups.com>,
    > Edson Pereira <ewpereira@...> wrote:
    >>
    >>
    >> Rob,
    >>
    >> I haven't found your email in my mailbox. Can you resend it?
    >>
    >> I am a little confused about what you have wrote. Can you tell me
    >> exactly what issues you are facing are? Are they related to:
    >>
    >> 1. SDR-Shell
    >> 2. SDR-Shell library dependencies (i.e., Qt, etc.)
    >> 3. SDR-Core
    >> 4. jackd
    >>
    >> SDR-Shell has no dependency on jackd. SDR-Core does.
    >>
    >> The jack_connect is a command-line application to assist with the
    >> management of jackd connections. Does qjackctl run on your system?
    >>
    >> Have you been able to run jackd and sdr-core on your system?
    >>
    >> 73,
    >>
    >> -- Edson
    >>
    >>
    >> dahdahdidit wrote:
    >> >
    >> >
    >> > Hi Edson,
    >> >
    >> > Please take a look at the email I sent offline about some other
    >> > challenges that we are having that are specific to Angstrom and the
    >> > Beagelboard so I won't obfuscate the intent of this forum to bring
    >> > them up here.
    >> >
    >> > One thing that might be good though is to talk about all the
    >> > dependencies needed to get SDR-Shell fully functional not the least of
    >> > which is sdr-core (part of dttsp I think?) and jack_connect. I just
    >> > have not been able to find any definitive information about those as
    >> > they pertain to SDR-Shell. Plenty out there on other uses of the JackD
    >> > suite but need to know how to install it in our distro and then how it
    >> > actually works. Errors that I get are that jack_connect cannot be
    >> > found on the BB even though it is in the build chain on my PC::
    >> >
    >> >
    > /home/OE/tmp/work/armv7a-angstrom-linux-gnueabi/jack-0.116.2-r0/image/usr/bin/jack_connect
    >> >
    >> > I don't expect you to be able to tell me why it's not on there but I
    >> > think a clearer understanding of what it does and it's relation to
    >> > dttsp/jack/alsa will help me diagnose what the problem might be.
    >> >
    >> > Thanks and have a look at my email - Be Well
    >> >
    >> > Rob, KC4NYK
    >> >
    >> > --- In softrock40@yahoogroups.com <mailto:softrock40%40yahoogroups.com>
    >> > <mailto:softrock40%40yahoogroups.com>, Edson Pereira <ewpereira@>
    >> > wrote:
    >> > >
    >> > >
    >> > > Hi Rob,
    >> > >
    >> > > Regarding the Si570 control, the hard work has already been done by
    >> > > Andrew, vk6jbl, with the development of the usbsoftrock
    > application. To
    >> > > interface it with SDR-Shell, you could base your code using the DDS
    >> > code
    >> > > in sdr-shell-for-if branch and send the frequency info to usbsoftrock
    >> > > via udp datagrams. Andrew's program also handles PTT.
    >> > >
    >> > > For a test tone, take a look at the morse keyer code included with
    >> > > sdr-core sources. Sdr-core also has some built-in tone generators,
    >> > > including a two-tone generator. The control for the tone generators
    >> > > could be easily incorporated into sdr-shell.
    >> > >
    >> > > 73,
    >> > >
    >> > > -- Edson, pu1jte, n1vtn, jf1afn
    >> > >
    >> > >
    >> > >
    >> > > dahdahdidit wrote:
    >> > > >
    >> > > >
    >> > > > I think we should be clear in our SDR discussions about what the
    >> > > > intended goal is for an application to be counted successful.
    >> > First we
    >> > > > should realize that there is a vast difference between "rig control"
    >> > > > and "mode control".
    >> > > >
    >> > > > The first is self explanatory but the latter, which is usually
    >> > implied
    >> > > > but not necessarily implemented, is the ability of the software to
    >> > > > "DECODE" the various modes in both directions. If it does not have
    >> > > > this ability then you are only talking about being able to use
    > CW and
    >> > > > SSB. The latter of which I am not sure has been done on the v6.3. If
    >> > > > someone knows I'd be happy to hear that.
    >> > > >
    >> > > > Next, talking about the SR v6.3 - which is a TRANSCEIVER, we are
    >> > > > implying, at the lowest level, the ability to transmit, which means
    >> > > > engaging PTT and is not simplistic. At the highest level we must be
    >> > > > able to program the SI570 through the I2c device chip for continuous
    >> > > > tuning AND PTT. These both have very different dependencies and even
    >> > > > ancillary programs and dependencies that must be installed. So it
    >> > > > would be good to have a list of development goals and their
    > status as
    >> > > > well as a suggested order of development priorities. Right now,
    >> > for my
    >> > > > BeagleBrick project in Angstrom Linux, I am creating such a list and
    >> > > > there are several "layers" of functionality defined and SDR-Shell
    >> > > > fulfills <some> of those and the rest need to be developed.
    >> > > >
    >> > > > Here is a list of things that we are trying to accomplish to get
    >> > > > SDR-Shell running properly in Angstrom on the Beagleboard, OMAP3
    >> > device::
    >> > > >
    >> > > > 1) get a signal to display on sdr-shell from audio input
    >> > > > > holding up this show is getting jack_connect cross-compiled and
    >> > > > installed
    >> > > > 2) get a tone to be produced at audio output
    >> > > > > this has to happen to be able to transmit
    >> > > > 3) get PTT triggered for TX
    >> > > > > all of the above can be done without the I2C/Si570 interface by
    >> > > > using a serial cable - and there are no notes on how to do this
    >> > > > through SDR-Shell
    >> > > > 4) get Si570 control in place to tune the Si570 (especially SR6.3)
    >> > > > > this needs to be developed by the SDR-Shell author (or perhaps
    >> > > > the DTTSP group) so there is a real road block here.
    >> > > >
    >> > > > Those using other "flavors" of Linux like Ubuntu, etc. may or
    > may not
    >> > > > have similar roadblocks but I thought I would post the progress of
    >> > our
    >> > > > build in the hopes that it is useful to others and also that some
    >> > > > reader may be able to give us some suggestions that will help get us
    >> > > > to the next step.
    >> > > >
    >> > > > Regards & 73
    >> > > > Rob Thomas, KC4NYK
    >> > > > Author - The BeagleBrick Project
    >> > > >
    >> > > > --- In softrock40@yahoogroups.com
    > <mailto:softrock40%40yahoogroups.com>
    >> > <mailto:softrock40%40yahoogroups.com>
    >> > > > <mailto:softrock40%40yahoogroups.com>, Andrea Montefusco <andrew@>
    >> > > > wrote:
    >> > > > >
    >> > > > > richard wrote:
    >> > > > >
    >> > > > > > the other thing that needs doing is to sort out the Makefile, or
    >> > > > taming
    >> > > > > > qmake.
    >> > > > > > With most machines having KDE4 loaded, as well as QT3, there is
    >> > > > the need
    >> > > > > > to only use the qt3 libs, qmake will pick up the qt4 (KDE4)
    >> > libs and
    >> > > > > > the compile will fail. I did post on the dttsp group a modified
    >> > > > > > Makefile.
    >> > > > > > For anyone with a 64 bit machine sdr-shell needs to be
    >> > compiled, and
    >> > > > > > qmake adding the QT4 libs to the Makefile is a pain
    >> > > > >
    >> > > > > If the Qt3 is installed, you should have in the PATH a qmake-qt3
    >> > > > that picks up the right libs
    >> > > > > and generates the correct makefile.
    >> > > > > If not, you can try to run the qmake for Qt3 environment
    > specifying
    >> > > > > the full path to it.
    >> > > > >
    >> > > > > 73 *am*
    >> > > > >


    --
    Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
    Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
    Specialist, Cricket Coach
    Microsoft Windows Free Zone - Linux used for all Computing Tasks
  • Sid Boyce
    Rob/Alex, I remembered this a few moments ago and decided to dig into myb foler and pass them along if it s of help. 73 ... Sid. ... Andrew, 0.11 compiles
    Message 34 of 34 , Nov 23, 2009
    • 0 Attachment
      Rob/Alex,
      I remembered this a few moments ago and decided to dig into myb foler
      and pass them along if it's of help.
      73 ... Sid.

      On 18/08/09 17:40, Edson Pereira wrote:
      >
      >
      >
      > Hi Rob,
      >
      > Regarding the Si570 control, the hard work has already been done by
      > Andrew, vk6jbl, with the development of the usbsoftrock application. To
      > interface it with SDR-Shell, you could base your code using the DDS code
      > in sdr-shell-for-if branch and send the frequency info to usbsoftrock
      > via udp datagrams. Andrew's program also handles PTT.
      >
      > For a test tone, take a look at the morse keyer code included with
      > sdr-core sources. Sdr-core also has some built-in tone generators,
      > including a two-tone generator. The control for the tone generators
      > could be easily incorporated into sdr-shell.
      >
      > 73,
      >
      > -- Edson, pu1jte, n1vtn, jf1afn
      >

      ----------------11/05/09 -------------------
      Andrew,

      0.11 compiles cleanly here too. I am using Ubuntu 8.04.2 with Alex's
      latest AVR I2C emulator for the UBW. All working smoothly.

      I am implementing a new version of SDR-Shell for the SoftRock with Si570
      and your code will save me a lot of time. Much thanks!

      73,

      -- Edson, pu1jte, n1vtn, jf1afn

      -------------------28/07/09---------------------------------------
      Sid,

      I am working on a new version indeed. The development of the new version
      is slowly, but surely progressing. When it gets ready, I will announce
      it on the dttsp-linux list.

      73,

      -- Edson
      --------------------------------------------------------------------------

      73 ... Sid.
      --
      Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
      Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
      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.