MacOS Tips

Version 25 (Neil Katin, 11/14/2016 02:00 pm)

1 24 Tom Hayward
h1. MacOS Tips
2 24 Tom Hayward
3 18 Dave Nathanson
h1. CHIRP Beginners Guide
4 18 Dave Nathanson
5 18 Dave Nathanson
The Beginners Guide has general help. Click here for the [[Beginners Guide]] 
6 18 Dave Nathanson
If you need Mac-specific help, you are at the right page. 
7 18 Dave Nathanson
8 18 Dave Nathanson
Join the Mailing list & search the archives for similar problem reports & how they were resolved, and/or ask the group. Please include enough info about the problem and situation so the community will be able to help you. 
9 18 Dave Nathanson
10 18 Dave Nathanson
Not all functionality is supported on all radios. See "Model Support":
11 18 Dave Nathanson
12 25 Neil Katin
h1. Application Security in 10.9
13 13 Dan Smith
14 13 Dan Smith
As of 10.9, signed packages are required by default. Apple charges for this capability, and requires use of their tooling to do it. For the time being, MacOS users should disable signed package checking for CHIRP. Instructions provided by Jim, K2SON:
15 13 Dan Smith
16 19 Dave Nathanson
 # Locate the app in Finder. 
17 19 Dave Nathanson
 # Right click (control-click if you don't have a 2 button mouse) on the app and click Open.
18 13 Dan Smith
 # You will get a dialog box about it being an unsigned app, click the Open button.
19 19 Dave Nathanson
 # Enter an Administrator userid and password.
20 13 Dan Smith
 # The app will now be flagged to allow it to be opened normally in the future.
21 13 Dan Smith
22 13 Dan Smith
Alternately, you can disable them for your entire system, although this has security implications that should not be ignored. Instructions for this provided by Tom, KD7LXL:
23 13 Dan Smith
24 13 Dan Smith
 # Open your System Preferences
25 13 Dan Smith
 # Go to Security & Privacy, General tab.
26 13 Dan Smith
 # Click the lock
27 1 Dan Smith
 # Then choose Allow apps downloaded from: Anywhere.
28 25 Neil Katin
29 25 Neil Katin
h1. Application Security in 10.12+
30 25 Neil Katin
31 25 Neil Katin
As of 10.12 (Sierra) the UI for disabling app security was removed.  The functionality is still there, but must be enabled from the command line.
32 25 Neil Katin
33 25 Neil Katin
To whitelist a single application (like an unzipped
34 25 Neil Katin
# unzip
35 25 Neil Katin
# control click on the unzipped application and select ??New Terminal at Folder??
36 25 Neil Katin
# run this command in the newly opened terminal window:
37 25 Neil Katin
38 25 Neil Katin
spctl --add $PWD
39 25 Neil Katin
40 25 Neil Katin
41 25 Neil Katin
Alternately, you can disable them for your entire system, although this has security implications that should not be ignored. Run this command in a terminal:
42 25 Neil Katin
43 25 Neil Katin
sudo spctl --master-enable
44 25 Neil Katin
45 25 Neil Katin
46 25 Neil Katin
references: "single command": "global":
47 13 Dan Smith
48 17 Dave Nathanson
h1.  Mac USB Drivers
49 1 Dan Smith
50 17 Dave Nathanson
USB to serial cables are not merely wire, they contain small computer circuits at one end of the cable that respond as a USB device and convert the data to serial. These cables are not all the same, so the computer needs a software "driver" so it can recognize the cable and speak to it correctly. You will need to install one of these 5 below. 
51 1 Dan Smith
52 23 Tom Hayward
h2.  FTDI cables
53 1 Dan Smith
54 23 Tom Hayward
Note that with Mac OSX 10.9 "Mavericks", Apple provides their own driver for FTDI chipset. You may need to remove the OEM FTDI driver and use only the Apple FTDI driver, or you may need to disable the Apple FTDI driver and install the OEM FTDI drivers. YMMV.
55 23 Tom Hayward
56 23 Tom Hayward
57 23 Tom Hayward
Version 1.5.1 is available for Mac OS X on 64 bit, 32 bit and PPC machines. 
58 23 Tom Hayward
59 23 Tom Hayward
h2. Prolific PL-2303 cables - official drivers for the genuine Prolific cables
60 23 Tom Hayward
61 23 Tom Hayward
*FYI: your cable, if using Prolific chipset, is more likely to be using a counterfeit chip than an original.*
62 23 Tom Hayward
63 23 Tom Hayward 
64 23 Tom Hayward
Login as guest/ guest & look in the Support section. Specified to work with Mac OSX 10.6, 10.7, & 10.8. 
65 23 Tom Hayward
66 23 Tom Hayward
h2. Generic PL-2303 cables (counterfeit and/or “Generic”) If you aren't sure what kind of inexpensive cable you have, try this one first. 
67 23 Tom Hayward
68 23 Tom Hayward
h3. For Lion (10.7.x), Mountain Lion (10.8.x), and Mavericks (10.9.x):
69 23 Tom Hayward
70 23 Tom Hayward
You can try this one, which install open source pl2303 driver and remove any other driver versions:
71 23 Tom Hayward At this web page you may need to right-click or control-click to link to get it to download. After downloading, you may need to control-right click, then open in order to bypass Mac Gatekeeper. 
72 23 Tom Hayward
73 23 Tom Hayward
h3. For earlier versions of Mac OS X up to 10.5 Leopard. Also some reports of success with Snow Leopard, Lion:
74 23 Tom Hayward
75 23 Tom Hayward
76 23 Tom Hayward
77 23 Tom Hayward
h2. RTSystems cables
78 23 Tom Hayward
79 23 Tom Hayward
h3. for OSX 10.9.x (aka Mavericks):
80 23 Tom Hayward
81 23 Tom Hayward
see [[RTSystemsCablesAndMavericks]]
82 23 Tom Hayward
83 23 Tom Hayward
h3. for OSX < 10.9.x: 
84 23 Tom Hayward
85 23 Tom Hayward
86 23 Tom Hayward
87 23 Tom Hayward
88 23 Tom Hayward
h2. Silicon Labs CP210x USB to UART Bridge VCP Drivers (including Kenwood TH-D72)
89 23 Tom Hayward
90 23 Tom Hayward
91 23 Tom Hayward
Macintosh OSX driver for the Intel and PowerPC Platforms versions 10.4, 10.5, 10.6, 10.7, 10.8, and 10.9.
92 23 Tom Hayward
93 1 Dan Smith
h1. Tips
94 1 Dan Smith
95 11 Tom Hayward
* In many cases you need to connect the cable to the radio first, then power the radio on, while holding down some buttons. The exact procedure varies by radio.
96 11 Tom Hayward
* Some radios need to be put into a "clone" mode to transfer to PC, some radios may need to be configured to use the mic/speaker jacks for PC transfer instead of for the speaker/mic. The exact procedure varies by radio. 
97 11 Tom Hayward
* You will need to download from the radio to CHIRP first, before uploading anything to the radio. CHIRP creates a template from the radio download so it knows how to talk to the radio. 
98 11 Tom Hayward
* If you want to download from one radio and upload those settings to another radio, first download from each radio to a separate “tab” of CHIRP. Then copy/paste from one tab to the other & upload back to the same radio that produced that tab. Do not try to upload to a radio directly from a tab that was not downloaded from that same radio. 
99 11 Tom Hayward
* Many USB to serial cables include a counterfeit Prolific chip. This can cause connection problems because the official Prolific driver will ignore the counterfeit chip. Some people have reported success by using an older version of the Prolific driver, or a 3rd party driver. 
100 11 Tom Hayward
* If you are using multiple USB cables, each will create a different “virtual port”, meaning that you will need to select the correct virtual port for your radio when connecting to your radio. CHIRP will give you this opportunity each time you download from the radio. 
101 11 Tom Hayward
* If CHIRP won’t launch & won't run, you may have neglected to install the Python runtime. CHIRP needs that. Even though Mac OS X includes Python built-in, the runtime has to be installed is because it includes PyGTK and some other libraries that Chirp requires, in addition to Python itself:
102 11 Tom Hayward
* If your radio is not "Supported", you can try downloading the newest Daily Build to see if support was recently added.
103 1 Dan Smith
104 11 Tom Hayward
h1. Troubleshooting
105 8 Dave Nathanson
106 11 Tom Hayward
You can verify that the drivers are installed & working by connecting the USB cable to your Mac, then running “System Profiler”, or “System Information” (found in  /Applications/Utilities ). When the USB cable is connected and drivers correctly installed, the cable will show up in the USB section of the System Profiler. 
107 6 Dave Nathanson
108 11 Tom Hayward
Another way to see that the driver is correctly installed is to open Terminal and type:
109 6 Dave Nathanson
110 11 Tom Hayward
    ls /dev/cu*
111 6 Dave Nathanson
112 11 Tom Hayward
It will return a list of virtual serial ports including something similar to:
113 6 Dave Nathanson
114 11 Tom Hayward
    /dev/cu.usbserial-A501XQ5I     (suffix will vary)
115 6 Dave Nathanson
116 11 Tom Hayward
You may also type:
117 6 Dave Nathanson
118 11 Tom Hayward
119 6 Dave Nathanson
120 6 Dave Nathanson
That will return a long list of kexts, including something similar to this at the bottom (most recently installed are listed last):
121 6 Dave Nathanson
122 11 Tom Hayward
    142    0 0xffffff7f81fc8000 0x8000      0x8000     com.FTDI.driver.FTDIUSBSerialDriver (2.2.18) <112 32 5 4 3 1>
123 11 Tom Hayward
124 6 Dave Nathanson
Look at the CHIRP log for clues.
125 6 Dave Nathanson
126 11 Tom Hayward
127 11 Tom Hayward
128 23 Tom Hayward
Join the Mailing list & search the archives for similar problem reports & how they were resolved, and/or ask the group. Please include enough info about the problem and situation so the community will be able to help you.