<div dir="ltr"><div dir="ltr">Hi Chip,<div><br></div><div>"/dev/cu.usbserial-RT3P07W9" is definitely the right device. Your error came from the python internals (and the pyserial library), and is more about code working badly, less about the cable or having the wrong device. Are you using CHIRP nightly or an older build?</div><div><br></div><div>If you are using nightly, then it's likely one of two problems:</div><div><br></div><div>- You have put a file called "serial.py" in your home directory (uncommon but possible)</div><div>- You have the wrong python serial library installed</div><div><br></div><div>Have you ever run "pip" to install a serial library? You can try these commands and see if it fixes things:</div><div><br></div><div><code style="margin:0px;padding:1px 5px;border:0px;font-variant-numeric:inherit;font-variant-east-asian:inherit;font-stretch:inherit;line-height:inherit;font-family:Consolas,Menlo,Monaco,"Lucida Console","Liberation Mono","DejaVu Sans Mono","Bitstream Vera Sans Mono","Courier New",monospace,sans-serif;font-size:13px;vertical-align:baseline;box-sizing:inherit;background-color:rgb(239,240,241);white-space:pre-wrap;color:rgb(36,39,41)">sudo python -m pip uninstall serial</code></div><div><code style="margin:0px;padding:1px 5px;border:0px;font-variant-numeric:inherit;font-variant-east-asian:inherit;font-stretch:inherit;line-height:inherit;font-family:Consolas,Menlo,Monaco,"Lucida Console","Liberation Mono","DejaVu Sans Mono","Bitstream Vera Sans Mono","Courier New",monospace,sans-serif;font-size:13px;vertical-align:baseline;box-sizing:inherit;background-color:rgb(239,240,241);white-space:pre-wrap;color:rgb(36,39,41)">sudo python -m pip install pyserial</code><br></div><br>I think the kk7ds runtime includes pyserial, but I don't have the package in front of me to check. Try those commands and be sure you are running nightly, and see if things go better.<br><br></div><div dir="ltr">--<br>Brian AF7MD</div><div dir="ltr"><br></div><div dir="ltr"><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 11, 2019 at 4:58 PM Jim Unroe <<a href="mailto:rock.unroe@gmail.com">rock.unroe@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div>Nothing that says "Bluetooth" would be the correct choice.<br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 11, 2019, 7:27 PM Chip Griffin via chirp_users <<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I’m getting an "AttributeError: 'Serial' object has no attribute ‘get_payload’” error when I try to read from my Icom IC-80AD. It’s instantaneous to when I start. I’ve looked at drivers and can’t find the alleged Apple FTDI driver. When I look in the directory IOUSBFamily.ktext I only see the following options:<br>
<br>
AppleLegacyUSBAudio.kext/ IOUSBCompositeDriver.kext/ IOUSBHIDDriverSafeBoot.kext/ <br>
AppleUSBLegacyHub.kext/ IOUSBHIDDriver.kext/ IOUSBLib.bundle/ <br>
AppleUSBMergeNub.kext/ IOUSBHIDDriverPM.kext/ IOUSBUserClient.kext/<br>
<br>
When I do a $ ls /dev/cu* I see:<br>
/dev/cu.Bluetooth-Incoming-Port /dev/cu.usbserial-RT3P07W9<br>
<br>
I’ve tried both. Bluetooth doesn’t even come close to happiness and the RT3P07W9 one gives me the above error.<br>
<br>
I do have the KK7DS stuff installed, even tried installing it a second time to be sure. <br>
<br>
<br>
I also tried on my Vista machine with even more pathetic results.<br>
<br>
<br>
--<br>
Chip<br>
<br>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com" rel="noreferrer" target="_blank">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Jim at <a href="mailto:rock.unroe@gmail.com" rel="noreferrer" target="_blank">rock.unroe@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" rel="noreferrer" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a></blockquote></div></div></div>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Brian Dickman at <a href="mailto:brian.maybe@gmail.com" target="_blank">brian.maybe@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a></blockquote></div></div>