Have you considered fldigi? Brian KE6IYC
Sent from my iPhone > On Aug 2, 2017, at 18:31, vk2war via HackRF-dev > <hackrf-dev@greatscottgadgets.com> wrote: > > G'day everyone ! > > First thing Is first. Thankyou Dominic for replacing my faulty HackRF One. > > That I really appreciate. > > I am an Advanced Amateur Radio Operator (Full Call Ham if you like, my call > is VK2WAR. > > I was in the Royal Australian Navy, recuperating from multiple injuries, > and subsequently over a dozen surgeries. I am still having surgeries, > albeit minor ones now day, when I got my Licence and started working HF > specifically the 40 meter band, for the most. > > I have sold all of my HF equipment. I got sick of arguing with councils > over Antenna issues. Ive moved home multiple times, and even though I > still have a couple of HF Antennas, for instance a Titan DX worth half a > mint, in the back yard, Im firstlhy unable to physicaly put it up, and I > don't want to fight over putting up antennas at my new home with my current > council. > > Anyways, I spent a lot of time on HF. Even came second in QC Magazines 2010 > competition, for High Power 40 metres. > > But one thing I liked was using software to operate my radios. My last HF > radio was a Yaesu FT-950. I had an FT-897 prior to that. > > I almoat cried the day I sold my Emtron DX-2SP Amplifier. > > I sold all my equipment to purchase Cameras, Audio Equipment, and Video > Switching equipment, to produce podcasts/Vblogs etc. Which I have not > really done, save a few reviews on Youtube, on FPV Racing Drones and > equipment. > > Ive spent a lot of time putting drones together, usually because my dominant > right hand is screwed and everything takes so much longer for mw. > > Anyways, that's a quick intro. My QRZ page is here > https://qrz.com/db/VK2WAR > > I have been using my HackRF mostly for reception. I have tried a couple of > replay attacks and it works well. > > GQRX and SDR# are all nice and cool to use to operate the HackRF. But I > have a query. > > I love Ham Radio Deluxe. I especially like DM780. > > Is there any way that you can get a HackRF working with DM780 especially for > digital modes, which is what It is for. Decoding PSK31, CW, and other > digital modes are so much easier to decode, rather than using software > designed for each specific modulation type. DM780 has it all. > > I just tried a trialware version of the latest HRD. It does not recognise > the HackRF. > > Is there a way of getting it to? Or do I need to repurchase something like a > signalink, and retransmit signals into DM780 for demodulation/decoding ? > > Jason > VK2WAR > > -----Original Message----- > From: HackRF-dev [mailto:hackrf-dev-boun...@greatscottgadgets.com] On Behalf > Of hackrf-dev-requ...@greatscottgadgets.com > Sent: 02 August 2017 01:29 > To: hackrf-dev@greatscottgadgets.com > Subject: HackRF-dev Digest, Vol 59, Issue 2 > > Send HackRF-dev mailing list submissions to > hackrf-dev@greatscottgadgets.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://pairlist9.pair.net/mailman/listinfo/hackrf-dev > or, via email, send a message with subject or body 'help' to > hackrf-dev-requ...@greatscottgadgets.com > > You can reach the person managing the list at > hackrf-dev-ow...@greatscottgadgets.com > > When replying, please edit your Subject line so it is more specific than > "Re: Contents of HackRF-dev digest..." > > > Today's Topics: > > 1. Re: what is the story with gr-osmosdr not building? > (Chuck McManis) > 2. Re: Transmitt (Andrew Rich) > 3. Re: what is the story with gr-osmosdr not building? (Anon Lister) > 4. Re: Transmitt (Andrew Rich) > 5. Re: Transmitt (Andrew Rich) > 6. Re: what is the story with gr-osmosdr not building? > (Chuck McManis) > 7. Need a hand (Andrew Rich) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 31 Jul 2017 22:50:35 -0700 > From: Chuck McManis <chuck.mcma...@gmail.com> > To: Dominic Spill <domini...@gmail.com> > Cc: Hackrf-dev <hackrf-dev@greatscottgadgets.com> > Subject: Re: [Hackrf-dev] what is the story with gr-osmosdr not > building? > Message-ID: > <cahtjpipgcjnwjn8okj4zmrtoyc7vc6gjbhr4vu-sybonbvg...@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hi Dominic, > >> We're not in a position to support LimeSDR on this mailing list, > > I know, I much prefer my HackRF :-). Up to now I've "gotten away" with just > using the packages rather than go into the FOSS dungeon to smelt metal to > cast parts for a lathe so that I can create the tools that I need to get > something done. Consider it an expression of my frustration. So begins my > entry into the third level of hell, perhaps I'll blog about it :-). It does > surprise me that HEAD on a 'major' > package like gr-osmosdr would not even be buildable, (because that is > typically the first test prior to merge a commit, does it still build) but > as I've been digging into it, some of the inter-relationships between > gnuradio, what Ettus started with (aka the uhd API) and the current state of > affairs (about a half dozen SDRs bodged into the framework in one way or > another) that the situation is far from "simple." > > Since the HackRF stuff seems to be the most effectively integrated SDR I > just assume all the pros are here who already know all this stuff. > > --Chuck > >> On Mon, Jul 31, 2017 at 10:22 PM, Dominic Spill <domini...@gmail.com> wrote: >>> On 30 July 2017 at 22:51, Chuck McManis <chuck.mcma...@gmail.com> wrote: >>> >>> Every day I regret spending money on this LimeSDR unit, and the only >>> way to talk to it is with 'SoapSDR' driving it through gr-osmosdr. >>> Now why gr-osmosdr can't drive it directly? Who knows but still I >>> thought I would rebuild gr-osmosdr from source and it dies horribly >>> trying to build RTL stuff. >> >> Hi Chuck, >> >> We're not in a position to support LimeSDR on this mailing list, >> there's no link between the projects and I don't have access to the >> hardware. I don't know if LimeSDR has a support channel, but I would >> recommend contacting them or other LimeSDR users as they will likely >> have experience with building LimeSDR support for GNU Radio. >> >> Thanks, >> Dominic > > > ------------------------------ > > Message: 2 > Date: Tue, 1 Aug 2017 16:00:22 +1000 > From: Andrew Rich <vk4...@tech-software.net> > To: Dominic Spill <domini...@gmail.com> > Cc: OP Imbiber <opimbi...@gmail.com>, hackrf-dev > <hackrf-dev@greatscottgadgets.com> > Subject: Re: [Hackrf-dev] Transmitt > Message-ID: <aaa71164-4294-4c8f-9b08-3699f83f0...@tech-software.net> > Content-Type: text/plain; charset="us-ascii" > > Perfect thank you ! > > Sent from my iPhone > >> On 1 Aug 2017, at 3:24 pm, Dominic Spill <domini...@gmail.com> wrote: >> >> On 30 July 2017 at 14:48, Andrew Rich <vk4...@tech-software.net> wrote: >>> >>> Sorry it's suck abroad question s >>> >>> Can my hack rf Tx a carrier anywhere between 1 MHz and 6ghz ? >> >> Yes. >> >>> What software can I use ? >> >> hackrf_transfer -c >> >> Remember, you need to comply with local laws when transmitting. >> >>> I have gnu radio installed and I have already received >> >> You can also use a signal source connected to an osmocom_sink block to > transmit. >> >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <https://pairlist9.pair.net/pipermail/hackrf-dev/attachments/20170801/4c3603 > bf/attachment-0001.html> > > ------------------------------ > > Message: 3 > Date: Tue, 1 Aug 2017 02:49:32 -0400 > From: Anon Lister <listera...@gmail.com> > To: Chuck McManis <chuck.mcma...@gmail.com> > Cc: hackrf-dev@greatscottgadgets.com > Subject: Re: [Hackrf-dev] what is the story with gr-osmosdr not > building? > Message-ID: > <CAMp204QZbxva0TGbTJD4RA46ThHJaqVmRFpJ2vcrwh=ffnk...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Builds fine for me. I suggest you try posting on discuss-gnuradio (if that > is your end goal, see below,) however I suggest you first read [1] and [2]. > Specifically, list your goal(you mention gr-osmosdr, then the LimeSDR, on > the hackrf mailing list, with no mention of your end goal), what you have > tried sofar(did you build any other pieces of code first? What was the > result of that?), and any error messages you encountered. This will help > people better understand what your trying to do and explain the meaning of > any error messages you are getting. > > The LimeSDR is a fairly new device, and the best place to ask questions > about it seems to be the discourse page from myriadrf, found at [3] or you > can visit their wiki found at [4] (However, once again, read [1] first.) It > sounds like your new to Linux, if you just want to listen to radio, perhaps > look at SDRConsole for a native windows program, which has a lower learning > curve, and is closed source.) > > [1] http://www.catb.org/esr/faqs/smart-questions.html > [2] http://xyproblem.info > [3] https://discourse.myriadrf.org/c/projects/limesdr > [4] https://wiki.myriadrf.org/Lime_Suite > > Cheers, > -Anon > > On Aug 1, 2017 1:50 AM, "Chuck McManis" <chuck.mcma...@gmail.com> wrote: > > Hi Dominic, > >> We're not in a position to support LimeSDR on this mailing list, > > I know, I much prefer my HackRF :-). Up to now I've "gotten away" with just > using the packages rather than go into the FOSS dungeon to smelt metal to > cast parts for a lathe so that I can create the tools that I need to get > something done. Consider it an expression of my frustration. So begins my > entry into the third level of hell, perhaps I'll blog about it :-). It does > surprise me that HEAD on a 'major' > package like gr-osmosdr would not even be buildable, (because that is > typically the first test prior to merge a commit, does it still build) but > as I've been digging into it, some of the inter-relationships between > gnuradio, what Ettus started with (aka the uhd API) and the current state of > affairs (about a half dozen SDRs bodged into the framework in one way or > another) that the situation is far from "simple." > > Since the HackRF stuff seems to be the most effectively integrated SDR I > just assume all the pros are here who already know all this stuff. > > --Chuck > >> On Mon, Jul 31, 2017 at 10:22 PM, Dominic Spill <domini...@gmail.com> wrote: >>> On 30 July 2017 at 22:51, Chuck McManis <chuck.mcma...@gmail.com> wrote: >>> >>> Every day I regret spending money on this LimeSDR unit, and the only >>> way to talk to it is with 'SoapSDR' driving it through gr-osmosdr. >>> Now why gr-osmosdr can't drive it directly? Who knows but still I >>> thought I would rebuild gr-osmosdr from source and it dies horribly >>> trying to build RTL stuff. >> >> Hi Chuck, >> >> We're not in a position to support LimeSDR on this mailing list, >> there's > no >> link between the projects and I don't have access to the hardware. I > don't >> know if LimeSDR has a support channel, but I would recommend >> contacting > them >> or other LimeSDR users as they will likely have experience with >> building LimeSDR support for GNU Radio. >> >> Thanks, >> Dominic > _______________________________________________ > HackRF-dev mailing list > HackRF-dev@greatscottgadgets.com > https://pairlist9.pair.net/mailman/listinfo/hackrf-dev > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <https://pairlist9.pair.net/pipermail/hackrf-dev/attachments/20170801/82f52f > 75/attachment-0001.html> > > ------------------------------ > > Message: 4 > Date: Tue, 1 Aug 2017 18:15:00 +1000 > From: Andrew Rich <vk4...@tech-software.net> > To: Andrew Rich <vk4...@tech-software.net> > Cc: Dominic Spill <domini...@gmail.com>, OP Imbiber > <opimbi...@gmail.com>, hackrf-dev <hackrf-dev@greatscottgadgets.com> > Subject: Re: [Hackrf-dev] Transmitt > Message-ID: <18204830-45d6-4969-9ef3-2d20390c1...@tech-software.net> > Content-Type: text/plain; charset=utf-8 > > Hi > > Hey I was wanting to know what blocks I can install in GNURADIO > > I installed GNU-RADIO using ports or macports > > sudo install gnuradio > > and subsequent > > sudo install gr-osmocom > sudo install gr-rtl-sdr > > Is there a ports query command that I can get a list of ?gr-<blocks>? > > Cheers > > Andrew > > > > > > ------------------------------ > > Message: 5 > Date: Tue, 1 Aug 2017 18:32:51 +1000 > From: Andrew Rich <vk4...@tech-software.net> > To: Andrew Rich <vk4...@tech-software.net> > Cc: Dominic Spill <domini...@gmail.com>, OP Imbiber > <opimbi...@gmail.com>, hackrf-dev <hackrf-dev@greatscottgadgets.com> > Subject: Re: [Hackrf-dev] Transmitt > Message-ID: <b2caa581-ae45-4b65-909e-2ae2c32c6...@tech-software.net> > Content-Type: text/plain; charset="utf-8" > > Ignore that I read up on ports > > Andrew > > ------------------------------------------ > Andrew Rich VK4TEC > e vk4...@internode.on.net <mailto:vk4...@internode.on.net> > m 0419 738 223 > http://59.167.159.165 <http://59.167.159.165/> > > > >> On 1 Aug 2017, at 6:15 pm, Andrew Rich <vk4...@tech-software.net> wrote: >> >> Hi >> >> Hey I was wanting to know what blocks I can install in GNURADIO >> >> I installed GNU-RADIO using ports or macports >> >> sudo install gnuradio >> >> and subsequent >> >> sudo install gr-osmocom >> sudo install gr-rtl-sdr >> >> Is there a ports query command that I can get a list of ?gr-<blocks>? >> >> Cheers >> >> Andrew >> >> >> > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <https://pairlist9.pair.net/pipermail/hackrf-dev/attachments/20170801/c742d9 > 4d/attachment-0001.html> > > ------------------------------ > > Message: 6 > Date: Tue, 1 Aug 2017 12:43:58 -0700 > From: Chuck McManis <chuck.mcma...@gmail.com> > To: Anon Lister <listera...@gmail.com> > Cc: Hackrf-dev <hackrf-dev@greatscottgadgets.com> > Subject: Re: [Hackrf-dev] what is the story with gr-osmosdr not > building? > Message-ID: > <cahtjpipfkszhvrzntzfhq7jbaeyjremj6jxpn+b_o7hnejd...@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Okay, that was funny. > --Chuck > >> On Mon, Jul 31, 2017 at 11:49 PM, Anon Lister <listera...@gmail.com> wrote: >> Builds fine for me. I suggest you try posting on discuss-gnuradio (if >> that is your end goal, see below,) however I suggest you first read [1] > and [2]. >> Specifically, list your goal(you mention gr-osmosdr, then the LimeSDR, >> on the hackrf mailing list, with no mention of your end goal), what >> you have tried sofar(did you build any other pieces of code first? >> What was the result of that?), and any error messages you encountered. >> This will help people better understand what your trying to do and >> explain the meaning of any error messages you are getting. >> >> The LimeSDR is a fairly new device, and the best place to ask >> questions about it seems to be the discourse page from myriadrf, found >> at [3] or you can visit their wiki found at [4] (However, once again, >> read [1] first.) It sounds like your new to Linux, if you just want to >> listen to radio, perhaps look at SDRConsole for a native windows >> program, which has a lower learning curve, and is closed source.) >> >> [1] http://www.catb.org/esr/faqs/smart-questions.html >> [2] http://xyproblem.info >> [3] https://discourse.myriadrf.org/c/projects/limesdr >> [4] https://wiki.myriadrf.org/Lime_Suite >> >> Cheers, >> -Anon >> >> On Aug 1, 2017 1:50 AM, "Chuck McManis" <chuck.mcma...@gmail.com> wrote: >> >> Hi Dominic, >> >>> We're not in a position to support LimeSDR on this mailing list, >> >> I know, I much prefer my HackRF :-). Up to now I've "gotten away" with >> just using the packages rather than go into the FOSS dungeon to smelt >> metal to cast parts for a lathe so that I can create the tools that I >> need to get something done. Consider it an expression of my >> frustration. So begins my entry into the third level of hell, perhaps >> I'll blog about it :-). It does surprise me that HEAD on a 'major' >> package like gr-osmosdr would not even be buildable, (because that is >> typically the first test prior to merge a commit, does it still build) >> but as I've been digging into it, some of the inter-relationships >> between gnuradio, what Ettus started with (aka the uhd API) and the >> current state of affairs (about a half dozen SDRs bodged into the >> framework in one way or another) that the situation is far from >> "simple." >> >> Since the HackRF stuff seems to be the most effectively integrated SDR >> I just assume all the pros are here who already know all this stuff. >> >> --Chuck >> >> On Mon, Jul 31, 2017 at 10:22 PM, Dominic Spill <domini...@gmail.com> > wrote: >>> On 30 July 2017 at 22:51, Chuck McManis <chuck.mcma...@gmail.com> wrote: >>>> >>>> Every day I regret spending money on this LimeSDR unit, and the only >>>> way to talk to it is with 'SoapSDR' driving it through gr-osmosdr. >>>> Now why gr-osmosdr can't drive it directly? Who knows but still I >>>> thought I would rebuild gr-osmosdr from source and it dies horribly >>>> trying to build RTL stuff. >>> >>> Hi Chuck, >>> >>> We're not in a position to support LimeSDR on this mailing list, >>> there's no link between the projects and I don't have access to the >>> hardware. I don't know if LimeSDR has a support channel, but I would >>> recommend contacting them or other LimeSDR users as they will likely >>> have experience with building LimeSDR support for GNU Radio. >>> >>> Thanks, >>> Dominic >> _______________________________________________ >> HackRF-dev mailing list >> HackRF-dev@greatscottgadgets.com >> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev >> >> > > > ------------------------------ > > Message: 7 > Date: Wed, 2 Aug 2017 15:28:46 +1000 > From: Andrew Rich <vk4...@tech-software.net> > To: Chuck McManis <chuck.mcma...@gmail.com> > Cc: Anon Lister <listera...@gmail.com>, Hackrf-dev > <hackrf-dev@greatscottgadgets.com> > Subject: [Hackrf-dev] Need a hand > Message-ID: <2bca1a38-03bc-4625-996f-4f700f59c...@tech-software.net> > Content-Type: text/plain; charset=us-ascii > > I can't get osmocom source to come up in Mac OS X so I can use my hack rf > > I have issued > > sudo port install gnuradio +full > sudo port install gr-osmosdr +full > sudo port install hackrf > > What am I missing ? > > Andrew > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > HackRF-dev mailing list > HackRF-dev@greatscottgadgets.com > https://pairlist9.pair.net/mailman/listinfo/hackrf-dev > > > ------------------------------ > > End of HackRF-dev Digest, Vol 59, Issue 2 > ***************************************** > > --- > This email has been checked for viruses by AVG. > http://www.avg.com > > > _______________________________________________ > HackRF-dev mailing list > HackRF-dev@greatscottgadgets.com > https://pairlist9.pair.net/mailman/listinfo/hackrf-dev _______________________________________________ HackRF-dev mailing list HackRF-dev@greatscottgadgets.com https://pairlist9.pair.net/mailman/listinfo/hackrf-dev