# Using on a Mac?

**URL:** <https://discussions.flightaware.com/t/using-on-a-mac/61904>\
**Category:** ADS-B Flight Tracking\
**Created:** [March 7, 2020, 5:45pm UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904 "2020-03-07T17:45:31Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![pforkes](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/pforkes/32/59916_2.png) [@pforkes](https://discussions.flightaware.com/u/pforkes)\
**Post date:** [March 7, 2020, 5:45pm UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/1 "2020-03-07T17:45:31Z")

</div>

I have a Mac Mini running MacOS Catalina 10.15.

When I bought the FlightAware Pro Stick Plus I assumed that it would come with something other than the plastic bag that it came in!

Where can I find software AND step by step instructions on how to get it to work on my Mac?

I have installed CocoaRTLServer 2.0 and it CAN find the USB stick so the stick IS working, BUT everything that I have followed on the Internet just keeps coming back saying that it cannot open the device!

So, where can I get clear, concise step by step instructions on how to get it to work on my Mac?

---

<div class="post-metadata">

**Author:** ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)\
**Post date:** [March 7, 2020, 5:50pm UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/2 "2020-03-07T17:50:40Z")

</div>

> [@pforkes](#):
>
> So, where can I get clear, concise step by step instructions on how to get it to work on my Mac?

[PiAware - build your own ADS-B ground station for integration with FlightAware - FlightAware](https://flightaware.com/adsb/piaware/build)

It’s meant for use with a Raspberry Pi.  
Not sure if there ADS-B reception applications ported for OS X, but i don’t think so.

There is some ADS-B decoding software around for Windows.  
The typical dump1090-fa used on the Raspberry Pi also works on Debian or Ubuntu on x86 PCs.

The typical use case is that you connect to a Raspberry Pi that you run 24/7.  
Obviously that’s Flightawares intent as you can read on the build page.  
Supporting other platforms costs lots of money, plus most computers don’t run 24/7.

---

<div class="post-metadata">

**Author:** ![pforkes](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/pforkes/32/59916_2.png) [@pforkes](https://discussions.flightaware.com/u/pforkes)\
**Post date:** [March 7, 2020, 5:54pm UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/3 "2020-03-07T17:54:14Z")

</div>

So I have just bought something that does not work with my hardware/operating system?

---

<div class="post-metadata">

**Author:** ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)\
**Post date:** [March 7, 2020, 5:57pm UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/4 "2020-03-07T17:57:01Z")

</div>

[Macintosh macOS Mode S (ADS-B) aircraft transponder decoder](https://www.blackcatsystems.com/software/cocoa1090.html)

The above is the first google hit for “OS X ADS-B decoder”.

Anyhow it’s much more practical to run it with a Raspberry Pi and then view the planes via a webinterface running on the RPi.

---

<div class="post-metadata">

**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\
**Post date:** [March 7, 2020, 6:01pm UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/5 "2020-03-07T18:01:00Z")

</div>

You may be able to build dump1090-fa from source; at one point it would build under OS X. But that’s not maintained or tested so it may need some TLC to get it working. You’ll need to sort out a build environment and build libusb / librtlsdr at a minimum.

---

<div class="post-metadata">

**Author:** ![pforkes](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/pforkes/32/59916_2.png) [@pforkes](https://discussions.flightaware.com/u/pforkes)\
**Post date:** [March 7, 2020, 7:43pm UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/6 "2020-03-07T19:43:36Z")

</div>

I was using these directions: `https://www.blackcatsystems.com/software/cocoa1090.html`.

I am getting this error:  
"Found 1 device(s):  
0: Generic RTL2832U (e.g. hama nano)

Using device 0: Generic RTL2832U (e.g. hama nano)  
Failed to open rtlsdr device #0."

…and I have ABSOLUTELY NO IDEA what could possibly be causing this or what I would have to type into Google to find the answer.

---

<div class="post-metadata">

**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\
**Post date:** [March 7, 2020, 7:54pm UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/7 "2020-03-07T19:54:07Z")

</div>

> [@pforkes](#):
>
> "Found 1 device(s):  
> 0: Generic RTL2832U (e.g. hama nano)
> 
> Using device 0: Generic RTL2832U (e.g. hama nano)  
> Failed to open rtlsdr device #0."

&nbsp;

Does it give any error number such as `"error -3"` or `"error -6"` like below?

```auto
Found 1 device(s):
  0: Realtek, RTL2832U, SN: 00000101

Using device 0: Generic RTL2832U
usb_claim_interface error -6
Failed to open rtlsdr device #0.

```

---

<div class="post-metadata">

**Author:** ![pforkes](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/pforkes/32/59916_2.png) [@pforkes](https://discussions.flightaware.com/u/pforkes)\
**Post date:** [March 7, 2020, 8:05pm UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/8 "2020-03-07T20:05:35Z")

</div>

It does NOT give an error number! I copied and pasted the output.

---

<div class="post-metadata">

**Author:** ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)\
**Post date:** [March 7, 2020, 8:15pm UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/9 "2020-03-07T20:15:47Z")

</div>

Trying sudo never hurt … (might be a permission problem)

---

<div class="post-metadata">

**Author:** ![pforkes](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/pforkes/32/59916_2.png) [@pforkes](https://discussions.flightaware.com/u/pforkes)\
**Post date:** [March 7, 2020, 8:18pm UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/10 "2020-03-07T20:18:41Z")

</div>

I have tried that…and the same thing happens…

---

<div class="post-metadata">

**Author:** ![mikkyo](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/mikkyo/32/119240_2.png) [@mikkyo](https://discussions.flightaware.com/u/mikkyo)\
**Post date:** [March 7, 2020, 8:31pm UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/11 "2020-03-07T20:31:22Z")

</div>

If you using his

> **[Macintosh Mac OS X RTL Dongle SDR Server](https://www.blackcatsystems.com/software/cocoa_rtl_server.html)**
>
> Macintosh Mac OS X RTL Dongle SDR Server App

it is probably claiming the device.

You have to configure it to match what Coco1090 is expecting. The directions should be on his site.  
If you installed any other SDR SW, it could be claiming the device, so only you could know what that might be.

BTW, you can pretty much run all the SDR stuff on the Mac, Flight Air Map, VRS, ACARS, etc, but you have to install homebrew or MacPorts and build a bunch of stuff yourself - Not for the non-programming folks.  
Much easier to buy a super cheap raspberry pi,and burn the piaware image to an SD card, and get an instantly working set up.

---

<div class="post-metadata">

**Author:** ![SoNic67](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/sonic67/32/119872_2.png) [@SoNic67](https://discussions.flightaware.com/u/SoNic67)\
**Post date:** [March 7, 2020, 11:46pm UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/12 "2020-03-07T23:46:03Z")

</div>

> [@pforkes](#):
>
> So I have just bought something that does not work with my hardware/operating system?

You bought a computer with an OS that has nothing working on it. Nothing else that is not from Apple walled garden.

---

<div class="post-metadata">

**Author:** ![chrislfa](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/chrislfa/32/113808_2.png) [@chrislfa](https://discussions.flightaware.com/u/chrislfa)\
**Post date:** [March 8, 2020, 1:20am UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/13 "2020-03-08T01:20:40Z")

</div>

You can run whatever you like on the Mac. The problem @pforkes has is to find a suitable demodulator that can talk to the Pro Stick Plus, perhaps a dump1090 variant like [dump1090-mac](https://github.com/mxswd/dump1090-mac), a suitable local viewer for the data and a process for feeding FlightAware. That’s a lot of work researching and gluing things together.

If the goal is to get it up and running, then, as @wiedehopf suggested, a Raspberry Pi is the way to go. Grab PiAware, write it to a card. Instant results.

---

<div class="post-metadata">

**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\
**Post date:** [March 8, 2020, 2:38am UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/14 "2020-03-08T02:38:24Z")

</div>

&nbsp;

`curl https://github.com/mxswd/dump1090-mac/releases/download/1/dump1090-mac.pkg -o dump1090-mac.pkg`

---

<div class="post-metadata">

**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\
**Post date:** [March 8, 2020, 2:44am UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/15 "2020-03-08T02:44:21Z")

</div>

> **[Set up RTL-SDR, dump1090, and dump978 for ADS-B/TIS-B/FIS-B/UAT on macOS](https://bl.ocks.org/fasiha/c123a9c6b6c78df7597bb45e0fed808f)**
>
> Ahmed Fasih’s Block c123a9c6b6c78df7597bb45e0fed808f

**NOTE:**  
In above page following command is given:  
`git clone https://github.com/mutability/dump1090.git`

Replace above command by:  
`git clone -b "unmaintained" https://github.com/mutability/dump1090.git`

---

<div class="post-metadata">

**Author:** ![pforkes](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/pforkes/32/59916_2.png) [@pforkes](https://discussions.flightaware.com/u/pforkes)\
**Post date:** [March 8, 2020, 2:51am UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/16 "2020-03-08T02:51:06Z")

</div>

The FlightAware Pro Stick is inserted into a USB drive on my Mac Mini and if I run CocoaRTL Server 2.0 it shows the device name “ _Generic RTL2832U (e.g. Hama nano)_ ” which suggests (to me) that the device is being recognized by the operating system as having the name " _Generic RTL2832U (e.g. Hama nano)_ "

I have downloaded SDRplay\_RSP\_API-MacOSX-2.13.2.pkg and run the installer program to completion.

1. Running _SoapySDRUtil —info_ shows me:

> ######################################################
> 
> ## Soapy SDR – the SDR abstraction library
> 
> ######################################################  
> Lib Version: v0.7.0-g69c16e98  
> API Version: v0.7.0  
> ABI Version: v0.7  
> Install root: /usr/local  
> Search path: /usr/local/lib/SoapySDR/modules0.7  
> Module found: /usr/local/lib/SoapySDR/modules0.7/libsdrPlaySupport.so (0.1.0-12c3db6)  
> Available factories… sdrplay  
> Available converters…
> 
> - CF32 → [CF32, CS16, CS8, CU16, CU8]
> - CS16 → [CF32, CS16, CS8, CU16, CU8]
> - CS32 → [CS32]
> - CS8 → [CF32, CS16, CS8, CU16, CU8]
> - CU16 → [CF32, CS16, CS8]
> - CU8 → [CF32, CS16, CS8]
> - F32 → [F32, S16, S8, U16, U8]
> - S16 → [F32, S16, S8, U16, U8]
> - S32 → [S32]
> - S8 → [F32, S16, S8, U16, U8]
> - U16 → [F32, S16, S8]
> - U8 → [F32, S16, S8]

Which (to me) does **NOT** imply that ‘ _driver xxx is installed and is working_ ’.

1. Running _SoapySDRUtil --probe=sdrplay_ shows me:

> ######################################################
> 
> ## Soapy SDR – the SDR abstraction library
> 
> ## ###################################################### Probe device sdrplay
> 
> ## – Device identification
> 
> ## driver=null hardware=null
> 
> ## – Peripheral summary
> 
> Channels: 0 Rx, 0 Tx  
> Timestamps: NO

This is definitely not showing anything to me that says _’this driver is installed and is working’_ .

If you can suggest anything that might help me to get my FlightAware Pro Stick to be accessible for use on may Mac mini then it would very much be appreciated.

---

<div class="post-metadata">

**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\
**Post date:** [March 8, 2020, 2:58am UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/17 "2020-03-08T02:58:22Z")

</div>

Try this

```auto
brew install librtlsdr

rtl_test -t

```

---

<div class="post-metadata">

**Author:** ![pforkes](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/pforkes/32/59916_2.png) [@pforkes](https://discussions.flightaware.com/u/pforkes)\
**Post date:** [March 8, 2020, 3:01am UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/18 "2020-03-08T03:01:03Z")

</div>

> [@abcd567](#):
>
> brew install librtlsdr

command not found: brew

I am guessing that “brew” is part of MacPort (?)

I took a look att this and could not figure out which/what I should download. If you can send a link to me then I will give it another shot.

---

<div class="post-metadata">

**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\
**Post date:** [March 8, 2020, 3:04am UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/19 "2020-03-08T03:04:43Z")

</div>

`brew` is used by package manager `Homebrew`. You need to install it on Mac

> **[How to Install Packages with Homebrew for OS X](https://www.howtogeek.com/211541/homebrew-for-os-x-easily-installs-desktop-apps-and-terminal-utilities/)**
>
> Homebrew is the most popular package manager for Mac OS X. Homebrew Cask extends Homebrew with support for quickly installing Mac applications like Google Chrome, VLC, and more. No more dragging and dropping applications!

---

<div class="post-metadata">

**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\
**Post date:** [March 8, 2020, 3:18am UTC](https://discussions.flightaware.com/t/using-on-a-mac/61904/20 "2020-03-08T03:18:23Z")

</div>

You can test dongle by using it as FM radio.

On a Mac, the following command will do reception of commercial wide-band FM signals. This assumes that the sox package is installed by command: `port install sox`

`rtl_fm -f 90100000 -M wbfm -s 200000 -r 48000 - | play -r 48000 -t s16 -L -c 1 -`

[Next page](https://discussions.flightaware.com/t/using-on-a-mac/61904.md?page=2)
