- Users - lists.chirpmyradio.com

[chirp_users] New Daily Build
by Build System 24 Jun '16

24 Jun '16

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20160624 A list of the changes included in this build (since the last daily) follows: Changes for Build #411 [Dan Smith <dsmith(a)danplanet.com>] Add TYT TH-7800 test image Related to #3477

1 0

Re: [chirp_users] Icom ic-t70
by Adam_K_Collins＠graco.com 23 Jun '16

23 Jun '16

I'm not familiar with debug logs. Does anything here suggest a course of action? Thanks, __________________ Here is the wording: [2016-06-22 22:10:36,045] chirp.logger - DEBUG: CHIRP daily-20160615 on WinVista/7 (Python 2.7.10) [2016-06-22 22:10:36,140] chirp.directory - INFO: Registered Alinco_DR03T = DR03Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DR06T = DR06Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DR135T = DR135Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DR235T = DR235Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DR435T = DR435Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DJ596 = DJ596Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Jetstream_JT220M = JT220MRadio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DJ175 = DJ175Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered AnyTone_5888UV = AnyTone5888UVRadio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Intek_HR-2040 = IntekHR2040Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Polmar_DB-50M = PolmarDB50MRadio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Powerwerx_DB-750X = PowerwerxDB750XRadio [2016-06-22 22:10:36,142] chirp.directory - INFO: Registered AnyTone_TERMN-8R = AnyToneTERMN8RRadio [2016-06-22 22:10:36,142] chirp.directory - INFO: Registered AnyTone_OBLTR-8R = AnyToneOBLTR8RRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-3R = UV3RRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baojie_BJ-9900 = BJ9900Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-5R = BaofengUV5RGeneric [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_F-11 = BaofengF11Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-82 = BaofengUV82Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-6 = BaofengUV6Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Intek_KT-980HP = IntekKT980Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_BF-F8HP = BaofengBFF8HPRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-82HP = BaofengUV82HPRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baojie_BJ-UV55 = BaojieBJUV55Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered BTECH_UV-2501 = UV2501 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered BTECH_UV-2501+220 = UV2501_220 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered BTECH_UV-5001 = UV5001 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered WACCOM_MINI-8900 = MINI8900 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered QYT_KT-UV980 = KTUV980 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered QYT_KT8900 = KT9800 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered QYT_KT8900R = KT9800R [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-268A = FD268ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-268B = FD268BRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-288A = FD288ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-288B = FD288BRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-150A = FD150ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-160A = FD160ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-450A = FD450ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-460A = FD460ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-1802M = FT1802Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-1D_R = FT1Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-2800M = FT2800Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-2900R_1900R = FT2900Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-2900E_1900E_E = FT2900ERadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-2900_1900_Modded_Opened_Xmit = FT2900ModRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-50 = FT50Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-60 = FT60Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-7800_7900 = FT7800Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-8800 = FT8800Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-8900 = FT8900Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-8100 = FT8100Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-817 = FT817Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-817ND = FT817NDRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-817ND_US = FT817NDUSRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-857_897 = FT857Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-857_897_US = FT857USRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-90 = FT90Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FTM-350 = FTM350Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Generic_CSV = CSVRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Commander_KG-UV = CommanderCSVRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered RT_Systems_CSV = RTCSVRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered ARRL_Travel_Plus = TpeRadio [2016-06-22 22:10:36,191] chirp.directory - INFO: Registered Generic_XML = XMLRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Baofeng_BF-888 = H777Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-208H = IC208Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-2100H = IC2100Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-2200H = IC2200Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-2720H = IC2720Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-2820H = IC2820Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-91_92AD = IC9xRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_7200 = Icom7200Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-7000 = Icom7000Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_746 = Icom746Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-Q7A = ICQ7Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-T70 = ICT70Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-T7H = ICT7HRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-T8A = ICT8ARadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-W32A = ICW32ARadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-W32E = ICW32ERadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-V82_U82 = ICx8xRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-31A = ID31Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-51 = ID51Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-51_Plus = ID51PLUSRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-800H_v2 = ID800v2Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-880H = ID880Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-80H = ID80Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_HMK = HMKRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_ITM = ITMRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-D7 = THD7Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-D7G = THD7GRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-D700 = TMD700Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-V7 = TMV7Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-G707 = TMG707Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-G71 = THG71Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-F6 = THF6ARadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-F7 = THF7ERadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-D710 = TMD710Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-D72_live_mode = THD72Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-V71 = TMV71Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-D710G = TMD710GRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-K2 = THK2Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-271 = TM271Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-281 = TM281Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-471 = TM471Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-UV8D = KGUV8DRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered KYD_NC-630A = NC630aRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered KYD_IP-620 = IP620Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Leixen_VV-898 = LeixenVV898Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Jetstream_JT270M = JetstreamJT270MRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-UVD1P = KGUVD1PRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-UV6 = KGUV6DRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-816 = KG816Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-818 = KG818Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Puxing_PX-777 = Puxing777Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Puxing_PX-2R = Puxing2RRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-7800_File = TYTTH7800File [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-7800 = TYTTH7800Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH9000_220 = Th9000220Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH9000_144 = Th9000144Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH9000_440 = Th9000440Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-9800_File = TYTTH9800File [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-9800 = TYTTH9800Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-UV3R = TYTUV3RRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-UV3R-25 = TYTUV3R25Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-UVF8D = TYTUVF8DRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TH-D72_clone_mode = THD72Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-UVF1 = TYTTHUVF1Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-260 = TK260_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-270 = TK270_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-272 = TK272_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-278 = TK278_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-360 = TK360_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-370 = TK370_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-372 = TK372_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-378 = TK378_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-760 = TK760_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-762 = TK762_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-768 = TK768_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-860 = TK860_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-862 = TK862_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-868 = TK868_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-868G = TK868G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-862G = TK862G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-860G = TK860G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-768G = TK768G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-762G = TK762G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-760G = TK760G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-278G = TK278G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-272G = TK272G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-270G = TK270G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-260G = TK260G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-7102 = KenwoodTK7102Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-8102 = KenwoodTK8102Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-7108 = KenwoodTK7108Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-8108 = KenwoodTK8108Radio [2016-06-22 22:10:36,239] chirp.directory - INFO: Registered Kenwood_TS-2000 = TS2000Radio [2016-06-22 22:10:36,239] chirp.directory - INFO: Registered Baofeng_UV-B5 = BaofengUVB5 [2016-06-22 22:10:36,240] chirp.directory - INFO: Registered Yaesu_VX-170 = VX170Radio [2016-06-22 22:10:36,240] chirp.directory - INFO: Registered Yaesu_VX-2 = VX2Radio [2016-06-22 22:10:36,240] chirp.directory - INFO: Registered Yaesu_VX-3 = VX3Radio [2016-06-22 22:10:36,240] chirp.directory - INFO: Registered Yaesu_VX-5 = VX5Radio [2016-06-22 22:10:36,242] chirp.directory - INFO: Registered Yaesu_VX-6 = VX6Radio [2016-06-22 22:10:36,243] chirp.directory - INFO: Registered Yaesu_VX-7 = VX7Radio [2016-06-22 22:10:36,243] chirp.directory - INFO: Registered Yaesu_VX-8_R = VX8Radio [2016-06-22 22:10:36,243] chirp.directory - INFO: Registered Yaesu_VX-8_DR = VX8DRadio [2016-06-22 22:10:36,243] chirp.directory - INFO: Registered Yaesu_VX-8_GE = VX8GERadio [2016-06-22 22:10:36,244] chirp.directory - INFO: Registered Vertex_Standard_VXA-700 = VXA700Radio [2016-06-22 22:10:36,244] elib.intl - DEBUG: Set environment variable 'LANG' to 'en_US' ('kernel32.SetEnvironmentVariableW') [2016-06-22 22:10:36,244] elib.intl - DEBUG: Set environment variable 'LANG' to 'en_US' ('msvcrt._putenv') [2016-06-22 22:10:36,244] elib.intl - DEBUG: Set environment variable 'LANG' to 'en_US' ('msvcr90._putenv') [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,592] chirp.ui.reporting - DEBUG: Checking for updates [2016-06-22 22:10:36,760] chirp.ui.reporting - DEBUG: Server reports version daily-20160615 is latest [2016-06-22 22:10:42,934] chirp.ui.mainapp - DEBUG: User selected Icom IC-T70 on port COM4 [2016-06-22 22:10:42,950] chirp.ui.clone - DEBUG: Clone thread started [2016-06-22 22:10:43,477] chirp.ui.reporting - DEBUG: Reporting exception [2016-06-22 22:10:43,477] chirp.ui.common - ERROR: -- Exception: -- [2016-06-22 22:10:43,477] chirp.ui.common - ERROR: Traceback (most recent call last): File "chirp\ui\clone.pyo", line 249, in run File "chirp\drivers\icf.pyo", line 616, in sync_in File "chirp\drivers\icf.pyo", line 322, in clone_from_radio RadioError: Failed to communicate with the radio: Unexpected response from radio [2016-06-22 22:10:43,477] chirp.ui.common - ERROR: ---------------- [2016-06-22 22:10:43,477] chirp.ui.clone - ERROR: Clone failed: Failed to communicate with the radio: Unexpected response from radio [2016-06-22 22:10:43,614] chirp.ui.clone - DEBUG: Clone thread ended [2016-06-22 22:10:43,614] chirp.ui.reporting - DEBUG: Reporting model usage: Icom_IC-T70,download,True [2016-06-22 22:10:43,614] chirp.ui.reporting - DEBUG: Reporting exception [2016-06-22 22:10:43,614] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Failed to communicate with the radio: Unexpected response from radio --- [2016-06-22 22:10:43,614] chirp.ui.inputdialog - ERROR: Traceback (most recent call last): File "chirpw", line 67, in <module> AttributeError: 'NoneType' object has no attribute 'split' [2016-06-22 22:10:43,614] chirp.ui.inputdialog - ERROR: ---------------------------- ——————————————————————————— Adam Collins Principal Designer Graco Process Division Office: 612-623-6449 Fax: 612-378-3510 www.graco.com/process __________________ Tom, I have my debug file here: The issue is "failed to communicate with radio, unexpected response from > radio." on my Icom ic-t-70. Thanks, ——————————————————————————— Adam Collins Principal Designer Graco Process Division Office: 612-623-6449 Fax: 612-378-3510 www.graco.com/process From: Tom Hayward <tom(a)tomh.us> To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com>, Date: 06/21/2016 12:05 PM Subject: Re: [chirp_users] Icom ic-t70 Sent by: chirp_users-bounces(a)intrepid.danplanet.com On Tue, Jun 21, 2016 at 9:52 AM, <Adam_K_Collins(a)graco.com> wrote: > > Hi, I'm looking for help with my ic-t70. > > For months I have been trying to get an image file into Chirp. > > I have confirmed correct drivers, COM ports, and no faulty cables. All I > ever get is "failed to communicate with radio, unexpected response from > radio." "Unexpected response" means it did receive something, but that something wasn't what Chirp identifies as an IC-T70. Your debug log might tell you more, but since you didn't provide it I'll just go hunting myself... http://chirp.danplanet.com/projects/chirp/repository/entry/chirp/drivers/ic… It looks like that error comes up when your radio responds to the clone request with more than one frame of data. What's in that extra data? Who knows. You might find more in your debug log. http://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues#Getting… Tom KD7LXL _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Adam at adam_k_collins(a)graco.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

2 1

[chirp_users] USB port 'Serial' object has no attribute 'setTimeout'
by Bob (KB3SYZ) 23 Jun '16

23 Jun '16

Running Chirp on Ubuntu 16.05 LTS. I am a total newbie to Linux. Learning as I go.I am having a hard time getting Chirp to work. I am attempting to connect to a Baofeng UV-5RA and, Wouxun KG-UV8D, also a Yeasu FT-2900R. I have made sure that I added myself to the group Dialout. I am getting the error; Failed to communicate with radio: 'Serial' object has no attribute 'setTimeout'. I have googled and searched for a solution to no avail. Any and all help greatly appreciated. Bob (KB3SYZ)

3 3

[chirp_users] Ubuntu
by NP3AR 23 Jun '16

23 Jun '16

Error on update attempt "The repository 'http://ppa.launchpad.net/dansmith/chirp-snapshots/ubuntu xenial Release' does not have a Release file. Sent from my Samsung Galaxy Tab®4

1 0

[chirp_users] Fwd: [chirp_devel] Build test results: Still Failing
by Pavel Milanes (CO7WT) 23 Jun '16

23 Jun '16

A new clone for the btech/qyt/waccom family has support now: Luiton LT-588UV TIP: I'm working on solving the Waccom mini8900 bugs, so far I'm nailing it, I have to do some extra testing with Jim KC9HI before patching. 73 Pavel CO7WT -------- Mensaje reenviado -------- Asunto: [chirp_devel] Build test results: Still Failing Fecha: Wed, 22 Jun 2016 18:47:38 -0700 (PDT) De: Build System via chirp_devel <chirp_devel(a)intrepid.danplanet.com> Responder-a:: Build System <donotreply(a)danplanet.com>, chirp_devel(a)intrepid.danplanet.com A: chirp_devel(a)intrepid.danplanet.com Tested changes: [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][BTECH][LT-588UV] Add a new model to the BTECH family, fixes #3067 A new model for the btech driver family: the LUITON LT-588UV, it's not a clone it's a variant of the early QYT KT8900. Also some tidy of the radio variants in the code to group the vendors. [Tom Hayward <tom(a)tomh.us>] [ui] Default file name to include model and date. #3753 During Save As, default the filename to {vendor}_{model}_{date}.img. The user is free to edit the field to their liking before saving. In case you don't like {vendor}_{model}_{date}.img, a new configuration variable "default_filename" is provided. By setting this variable in your config file, you can reorder or omit parts of the default format. Example: [global] default_filename = {vendor}_{model} This omits the date. Example: [global] default_filename = Tom's_{vendor}_{model}_{date} This begins each filename with my name. Full log: Started by an SCM change Building in workspace /var/lib/jenkins/jobs/chirp-test/workspace [workspace] $ hg showconfig paths.default [workspace] $ hg pull --rev default [workspace] $ hg update --clean --rev default 2 files updated, 0 files merged, 0 files removed, 0 files unresolved [workspace] $ hg log --rev . --template {node} [workspace] $ hg log --rev . --template {rev} [workspace] $ hg log --rev cd4630e4151a435810e1eb3089f63927dfe2c626 [workspace] $ hg log --template "<changeset node='{node}' author='{author|xmlescape}' rev='{rev}' date='{date}'><msg>{desc|xmlescape}</msg><added>{file_adds|stringify|xmlescape}</added><deleted>{file_dels|stringify|xmlescape}</deleted><files>{files|stringify|xmlescape}</files><parents>{parents}</parents></changeset>\n" --rev default:0 --follow --prune cd4630e4151a435810e1eb3089f63927dfe2c626 No emails were triggered. [workspace] $ /bin/sh -xe /tmp/hudson3886142960528785677.sh [workspace] $ /bin/sh -xe /tmp/hudson4300370065474325300.sh + PATH=/usr/bin:/bin:/usr/local/bin ./run_all_tests.sh test_bit_array (tests.unit.test_bitwise.TestBitType) ... ok test_bit_array_fail (tests.unit.test_bitwise.TestBitType) ... ok test_bitfield_u16 (tests.unit.test_bitwise.TestBitfieldTypes) ... ok test_bitfield_u24 (tests.unit.test_bitwise.TestBitfieldTypes) ... ok test_bitfield_u8 (tests.unit.test_bitwise.TestBitfieldTypes) ... ok test_bitfield_ul16 (tests.unit.test_bitwise.TestBitfieldTypes) ... ok test_bitfield_ul24 (tests.unit.test_bitwise.TestBitfieldTypes) ... ok test_bbcd (tests.unit.test_bitwise.TestBitwiseBCDTypes) ... ok test_bbcd_array (tests.unit.test_bitwise.TestBitwiseBCDTypes) ... ok test_lbcd (tests.unit.test_bitwise.TestBitwiseBCDTypes) ... ok test_lbcd_array (tests.unit.test_bitwise.TestBitwiseBCDTypes) ... ok test_int_array (tests.unit.test_bitwise.TestBitwiseBaseIntTypes) ... ok test_type_u16 (tests.unit.test_bitwise.TestBitwiseBaseIntTypes) ... ok test_type_u24 (tests.unit.test_bitwise.TestBitwiseBaseIntTypes) ... ok test_type_u32 (tests.unit.test_bitwise.TestBitwiseBaseIntTypes) ... ok test_type_u8 (tests.unit.test_bitwise.TestBitwiseBaseIntTypes) ... ok test_type_ul16 (tests.unit.test_bitwise.TestBitwiseBaseIntTypes) ... ok test_type_ul24 (tests.unit.test_bitwise.TestBitwiseBaseIntTypes) ... ok test_type_ul32 (tests.unit.test_bitwise.TestBitwiseBaseIntTypes) ... ok test_char (tests.unit.test_bitwise.TestBitwiseCharTypes) ... ok test_string (tests.unit.test_bitwise.TestBitwiseCharTypes) ... ok test_string_invalid_chars (tests.unit.test_bitwise.TestBitwiseCharTypes) ... ok test_string_wrong_length (tests.unit.test_bitwise.TestBitwiseCharTypes) ... ok test_comment_cppstyle (tests.unit.test_bitwise.TestBitwiseComments) ... ok test_comment_inline_cppstyle (tests.unit.test_bitwise.TestBitwiseComments) ... ok test_missing_semicolon (tests.unit.test_bitwise.TestBitwiseErrors) ... ok test_seek (tests.unit.test_bitwise.TestBitwiseSeek) ... ok test_seekto (tests.unit.test_bitwise.TestBitwiseSeek) ... ok test_struct_one_element (tests.unit.test_bitwise.TestBitwiseStructTypes) ... ok test_struct_two_elements (tests.unit.test_bitwise.TestBitwiseStructTypes) ... ok test_struct_writes (tests.unit.test_bitwise.TestBitwiseStructTypes) ... ok split_tone_encode_test_cross_dtcs_tone (tests.unit.test_chirp_common.TestSplitTone) ... ok split_tone_encode_test_cross_none_dtcs (tests.unit.test_chirp_common.TestSplitTone) ... ok split_tone_encode_test_cross_none_tone (tests.unit.test_chirp_common.TestSplitTone) ... ok split_tone_encode_test_cross_tone_dtcs (tests.unit.test_chirp_common.TestSplitTone) ... ok split_tone_encode_test_cross_tone_tone (tests.unit.test_chirp_common.TestSplitTone) ... ok split_tone_encode_test_dtcs (tests.unit.test_chirp_common.TestSplitTone) ... ok split_tone_encode_test_none (tests.unit.test_chirp_common.TestSplitTone) ... ok split_tone_encode_test_tone (tests.unit.test_chirp_common.TestSplitTone) ... ok split_tone_encode_test_tsql (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_cross_dtcs_dtcs (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_cross_dtcs_tone (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_cross_none_dtcs (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_cross_none_tone (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_cross_tone_dtcs (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_cross_tone_tone (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_dtcs (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_none (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_tone (tests.unit.test_chirp_common.TestSplitTone) ... ok test_split_tone_decode_tsql (tests.unit.test_chirp_common.TestSplitTone) ... ok test_fix_rounded_step_250 (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_fix_rounded_step_500 (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_fix_rounded_step_750 (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_is_12_5 (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_is_2_5 (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_is_5_0 (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_is_6_25 (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_is_fractional_step (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_required_step (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_required_step_fail (tests.unit.test_chirp_common.TestStepFunctions) ... ok test_format_freq (tests.unit.test_chirp_common.TestUtilityFunctions) ... ok test_parse_freq_bad (tests.unit.test_chirp_common.TestUtilityFunctions) ... ok test_parse_freq_decimal (tests.unit.test_chirp_common.TestUtilityFunctions) ... ok test_parse_freq_whitespace (tests.unit.test_chirp_common.TestUtilityFunctions) ... ok test_parse_freq_whole (tests.unit.test_chirp_common.TestUtilityFunctions) ... ok test_ensure_has_calls_almost_full (tests.unit.test_import_logic.DstarTests) ... ok test_ensure_has_calls_empty (tests.unit.test_import_logic.DstarTests) ... ok test_ensure_has_calls_partial (tests.unit.test_import_logic.DstarTests) ... ok test_ensure_has_calls_rptcall_full1 (tests.unit.test_import_logic.DstarTests) ... ok test_ensure_has_calls_rptcall_full2 (tests.unit.test_import_logic.DstarTests) ... ok test_ensure_has_calls_urcall_full (tests.unit.test_import_logic.DstarTests) ... ok test_import_bank (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_dtcs_diffA_dtcs (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_dtcs_diffB_dtcs (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_duplex_negative (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_duplex_too_big_vhf (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_duplex_uhf (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_duplex_vhf (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_mem (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_mem_with_errors (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_mem_with_warnings (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_mode_invalid (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_mode_valid_am (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_mode_valid_fm (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_name (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_power_closest (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_power_no_dst (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_power_no_src (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_power_same (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_tone_diffA_tsql (tests.unit.test_import_logic.ImportFieldTests) ... ok test_import_tone_diffB_tsql (tests.unit.test_import_logic.ImportFieldTests) ... ok test_mapping (tests.unit.test_mappingmodel.TestBaseBank) ... ok test_mapping_eq (tests.unit.test_mappingmodel.TestBaseBank) ... ok test_base_class (tests.unit.test_mappingmodel.TestBaseBankModel) ... ok test_get_name (tests.unit.test_mappingmodel.TestBaseBankModel) ... ok test_mapping (tests.unit.test_mappingmodel.TestBaseMapping) ... ok test_mapping_eq (tests.unit.test_mappingmodel.TestBaseMapping) ... ok test_base_class (tests.unit.test_mappingmodel.TestBaseMappingModel) ... ok test_get_name (tests.unit.test_mappingmodel.TestBaseMappingModel) ... ok test_base_class (tests.unit.test_mappingmodel.TestBaseMappingModelIndexInterface) ... ok test_add_memory_to_mapping (tests.unit.test_mappingmodel.TestIcomBankModel) ... ok test_get_mapping_memories (tests.unit.test_mappingmodel.TestIcomBankModel) ... ok test_get_mappings (tests.unit.test_mappingmodel.TestIcomBankModel) ... ok test_get_memory_mappings (tests.unit.test_mappingmodel.TestIcomBankModel) ... ok test_get_num_mappings (tests.unit.test_mappingmodel.TestIcomBankModel) ... ok test_remove_memory_from_mapping (tests.unit.test_mappingmodel.TestIcomBankModel) ... ok test_remove_memory_from_mapping_no_bank (tests.unit.test_mappingmodel.TestIcomBankModel) ... ok test_remove_memory_from_mapping_wrong_bank (tests.unit.test_mappingmodel.TestIcomBankModel) ... ok test_icom_bank (tests.unit.test_mappingmodel.TestIcomBanks) ... ok test_mapping (tests.unit.test_mappingmodel.TestIcomBanks) ... ok test_mapping_eq (tests.unit.test_mappingmodel.TestIcomBanks) ... ok test_add_memory_to_mapping (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_get_index_bounds (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_get_mapping_memories (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_get_mappings (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_get_memory_index (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_get_memory_mappings (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_get_next_mapping_index (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_get_num_mappings (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_remove_memory_from_mapping (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_remove_memory_from_mapping_no_bank (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_remove_memory_from_mapping_wrong_bank (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_set_memory_index (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_set_memory_index_bad_bank (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_set_memory_index_bad_index (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_auto_tone_mode_cross (tests.unit.test_memedit_edits.TestEdits) ... ok test_auto_tone_mode_dtcs (tests.unit.test_memedit_edits.TestEdits) ... ok test_auto_tone_mode_dtcs_pol (tests.unit.test_memedit_edits.TestEdits) ... ok test_auto_tone_mode_dtcs_rx (tests.unit.test_memedit_edits.TestEdits) ... ok test_auto_tone_mode_tone (tests.unit.test_memedit_edits.TestEdits) ... ok test_auto_tone_mode_tsql (tests.unit.test_memedit_edits.TestEdits) ... ok test_init (tests.unit.test_platform.Win32PlatformTest) ... ok test_serial_ports_bad_portnames (tests.unit.test_platform.Win32PlatformTest) ... ok test_serial_ports_sorted (tests.unit.test_platform.Win32PlatformTest) ... ok test_apply_callback (tests.unit.test_settings.TestSettingContainers) ... ok test_radio_setting (tests.unit.test_settings.TestSettingContainers) ... ok test_radio_setting_group (tests.unit.test_settings.TestSettingContainers) ... ok test_radio_setting_multi (tests.unit.test_settings.TestSettingContainers) ... ok test_changed (tests.unit.test_settings.TestSettingValues) ... ok test_radio_setting_value_boolean (tests.unit.test_settings.TestSettingValues) ... ok test_radio_setting_value_float (tests.unit.test_settings.TestSettingValues) ... ok test_radio_setting_value_integer (tests.unit.test_settings.TestSettingValues) ... ok test_radio_setting_value_list (tests.unit.test_settings.TestSettingValues) ... ok test_radio_setting_value_string (tests.unit.test_settings.TestSettingValues) ... ok test_validate_callback (tests.unit.test_settings.TestSettingValues) ... ok test_delete_hole_with_all (tests.unit.test_shiftdialog.ShiftDialogTest) ... ok test_delete_hole_with_all_full (tests.unit.test_shiftdialog.ShiftDialogTest) ... ok test_delete_hole_with_hole (tests.unit.test_shiftdialog.ShiftDialogTest) ... ok test_delete_hole_without_hole (tests.unit.test_shiftdialog.ShiftDialogTest) ... ok test_insert_hole_with_space (tests.unit.test_shiftdialog.ShiftDialogTest) ... ok test_insert_hole_without_space (tests.unit.test_shiftdialog.ShiftDialogTest) ... ok ---------------------------------------------------------------------- Ran 151 tests in 0.050s OK Patch 'tip' is OK Checking for PEP8 regressions... ./chirp/drivers/ft60.py:521:45: W291 trailing whitespace ./chirp/drivers/ft60.py:522:25: E128 continuation line under-indented for visual indent ./chirp/drivers/ft60.py:523:13: E301 expected 1 blank line, found 0 ./chirp/drivers/ft817.py:587:41: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:684:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:688:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:691:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:692:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:695:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:696:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:699:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:702:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:705:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:708:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:711:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:714:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:717:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:720:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:721:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:724:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:725:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:728:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:731:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:732:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:735:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:736:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:739:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:740:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:743:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:744:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:747:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:750:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:753:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:754:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:757:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:758:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:761:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:764:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:767:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:768:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:771:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:772:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:775:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:776:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:779:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:782:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:783:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:786:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:789:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:790:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:793:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:794:29: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:810:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:811:31: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:814:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:817:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:821:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:827:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:832:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:836:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:840:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:844:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:848:25: E128 continuation line under-indented for visual indent ./chirp/drivers/kguv8d.py:893:25: E128 continuation line under-indented for visual indent ./chirp/drivers/thd72.py:188:1: E302 expected 2 blank lines, found 1 ./chirp/drivers/thd72.py:203:23: E201 whitespace after '[' ./chirp/drivers/thd72.py:203:80: E501 line too long (171 > 79 characters) ./chirp/drivers/thd72.py:203:170: E202 whitespace before ']' ./chirp/drivers/thd72.py:204:13: E201 whitespace after '[' ./chirp/drivers/thd72.py:204:61: E202 whitespace before ']' ./chirp/drivers/thd72.py:205:23: E201 whitespace after '[' ./chirp/drivers/thd72.py:205:74: E202 whitespace before ']' ./chirp/drivers/thd72.py:206:18: E201 whitespace after '[' ./chirp/drivers/thd72.py:206:65: E202 whitespace before ']' ./chirp/drivers/thd72.py:595:1: W293 blank line contains whitespace ./chirp/drivers/thd72.py:603:1: W293 blank line contains whitespace ./chirp/ui/mainapp.py:646:13: E128 continuation line under-indented for visual indent ./chirp/ui/mainapp.py:660:5: E303 too many blank lines (2) ./chirp/ui/mainapp.py:1363:80: E501 line too long (81 > 79 characters) ./chirp/ui/mainapp.py:1367:80: E501 line too long (80 > 79 characters) ./chirp/ui/mainapp.py:1652:80: E501 line too long (85 > 79 characters) real 0m7.378s user 0m7.269s sys 0m0.048s ================================================ Tests FAILED: driver tests Build step 'Execute shell' marked build as failure Email was triggered for: Failure Sending email for trigger: Failure

1 0

Re: [chirp_users] Icom ic-t70
by Adam_K_Collins＠graco.com 23 Jun '16

23 Jun '16

Here is the wording: [2016-06-22 22:10:36,045] chirp.logger - DEBUG: CHIRP daily-20160615 on WinVista/7 (Python 2.7.10) [2016-06-22 22:10:36,140] chirp.directory - INFO: Registered Alinco_DR03T = DR03Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DR06T = DR06Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DR135T = DR135Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DR235T = DR235Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DR435T = DR435Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DJ596 = DJ596Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Jetstream_JT220M = JT220MRadio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Alinco_DJ175 = DJ175Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered AnyTone_5888UV = AnyTone5888UVRadio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Intek_HR-2040 = IntekHR2040Radio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Polmar_DB-50M = PolmarDB50MRadio [2016-06-22 22:10:36,141] chirp.directory - INFO: Registered Powerwerx_DB-750X = PowerwerxDB750XRadio [2016-06-22 22:10:36,142] chirp.directory - INFO: Registered AnyTone_TERMN-8R = AnyToneTERMN8RRadio [2016-06-22 22:10:36,142] chirp.directory - INFO: Registered AnyTone_OBLTR-8R = AnyToneOBLTR8RRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-3R = UV3RRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baojie_BJ-9900 = BJ9900Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-5R = BaofengUV5RGeneric [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_F-11 = BaofengF11Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-82 = BaofengUV82Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-6 = BaofengUV6Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Intek_KT-980HP = IntekKT980Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_BF-F8HP = BaofengBFF8HPRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baofeng_UV-82HP = BaofengUV82HPRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Baojie_BJ-UV55 = BaojieBJUV55Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered BTECH_UV-2501 = UV2501 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered BTECH_UV-2501+220 = UV2501_220 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered BTECH_UV-5001 = UV5001 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered WACCOM_MINI-8900 = MINI8900 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered QYT_KT-UV980 = KTUV980 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered QYT_KT8900 = KT9800 [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered QYT_KT8900R = KT9800R [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-268A = FD268ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-268B = FD268BRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-288A = FD288ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-288B = FD288BRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-150A = FD150ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-160A = FD160ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-450A = FD450ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Feidaxin_FD-460A = FD460ARadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-1802M = FT1802Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-1D_R = FT1Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-2800M = FT2800Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-2900R_1900R = FT2900Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-2900E_1900E_E = FT2900ERadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-2900_1900_Modded_Opened_Xmit = FT2900ModRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-50 = FT50Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-60 = FT60Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-7800_7900 = FT7800Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-8800 = FT8800Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-8900 = FT8900Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-8100 = FT8100Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-817 = FT817Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-817ND = FT817NDRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-817ND_US = FT817NDUSRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-857_897 = FT857Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-857_897_US = FT857USRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FT-90 = FT90Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Yaesu_FTM-350 = FTM350Radio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Generic_CSV = CSVRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered Commander_KG-UV = CommanderCSVRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered RT_Systems_CSV = RTCSVRadio [2016-06-22 22:10:36,144] chirp.directory - INFO: Registered ARRL_Travel_Plus = TpeRadio [2016-06-22 22:10:36,191] chirp.directory - INFO: Registered Generic_XML = XMLRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Baofeng_BF-888 = H777Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-208H = IC208Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-2100H = IC2100Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-2200H = IC2200Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-2720H = IC2720Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-2820H = IC2820Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-91_92AD = IC9xRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_7200 = Icom7200Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-7000 = Icom7000Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_746 = Icom746Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-Q7A = ICQ7Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-T70 = ICT70Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-T7H = ICT7HRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-T8A = ICT8ARadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-W32A = ICW32ARadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-W32E = ICW32ERadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_IC-V82_U82 = ICx8xRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-31A = ID31Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-51 = ID51Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-51_Plus = ID51PLUSRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-800H_v2 = ID800v2Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-880H = ID880Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Icom_ID-80H = ID80Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_HMK = HMKRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_ITM = ITMRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-D7 = THD7Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-D7G = THD7GRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-D700 = TMD700Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-V7 = TMV7Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-G707 = TMG707Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-G71 = THG71Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-F6 = THF6ARadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-F7 = THF7ERadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-D710 = TMD710Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-D72_live_mode = THD72Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-V71 = TMV71Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-D710G = TMD710GRadio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TH-K2 = THK2Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-271 = TM271Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-281 = TM281Radio [2016-06-22 22:10:36,207] chirp.directory - INFO: Registered Kenwood_TM-471 = TM471Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-UV8D = KGUV8DRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered KYD_NC-630A = NC630aRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered KYD_IP-620 = IP620Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Leixen_VV-898 = LeixenVV898Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Jetstream_JT270M = JetstreamJT270MRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-UVD1P = KGUVD1PRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-UV6 = KGUV6DRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-816 = KG816Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Wouxun_KG-818 = KG818Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Puxing_PX-777 = Puxing777Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Puxing_PX-2R = Puxing2RRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-7800_File = TYTTH7800File [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-7800 = TYTTH7800Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH9000_220 = Th9000220Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH9000_144 = Th9000144Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH9000_440 = Th9000440Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-9800_File = TYTTH9800File [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-9800 = TYTTH9800Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-UV3R = TYTUV3RRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-UV3R-25 = TYTUV3R25Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-UVF8D = TYTUVF8DRadio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TH-D72_clone_mode = THD72Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered TYT_TH-UVF1 = TYTTHUVF1Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-260 = TK260_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-270 = TK270_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-272 = TK272_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-278 = TK278_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-360 = TK360_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-370 = TK370_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-372 = TK372_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-378 = TK378_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-760 = TK760_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-762 = TK762_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-768 = TK768_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-860 = TK860_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-862 = TK862_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-868 = TK868_Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-868G = TK868G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-862G = TK862G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-860G = TK860G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-768G = TK768G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-762G = TK762G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-760G = TK760G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-278G = TK278G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-272G = TK272G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-270G = TK270G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-260G = TK260G_Radios [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-7102 = KenwoodTK7102Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-8102 = KenwoodTK8102Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-7108 = KenwoodTK7108Radio [2016-06-22 22:10:36,223] chirp.directory - INFO: Registered Kenwood_TK-8108 = KenwoodTK8108Radio [2016-06-22 22:10:36,239] chirp.directory - INFO: Registered Kenwood_TS-2000 = TS2000Radio [2016-06-22 22:10:36,239] chirp.directory - INFO: Registered Baofeng_UV-B5 = BaofengUVB5 [2016-06-22 22:10:36,240] chirp.directory - INFO: Registered Yaesu_VX-170 = VX170Radio [2016-06-22 22:10:36,240] chirp.directory - INFO: Registered Yaesu_VX-2 = VX2Radio [2016-06-22 22:10:36,240] chirp.directory - INFO: Registered Yaesu_VX-3 = VX3Radio [2016-06-22 22:10:36,240] chirp.directory - INFO: Registered Yaesu_VX-5 = VX5Radio [2016-06-22 22:10:36,242] chirp.directory - INFO: Registered Yaesu_VX-6 = VX6Radio [2016-06-22 22:10:36,243] chirp.directory - INFO: Registered Yaesu_VX-7 = VX7Radio [2016-06-22 22:10:36,243] chirp.directory - INFO: Registered Yaesu_VX-8_R = VX8Radio [2016-06-22 22:10:36,243] chirp.directory - INFO: Registered Yaesu_VX-8_DR = VX8DRadio [2016-06-22 22:10:36,243] chirp.directory - INFO: Registered Yaesu_VX-8_GE = VX8GERadio [2016-06-22 22:10:36,244] chirp.directory - INFO: Registered Vertex_Standard_VXA-700 = VXA700Radio [2016-06-22 22:10:36,244] elib.intl - DEBUG: Set environment variable 'LANG' to 'en_US' ('kernel32.SetEnvironmentVariableW') [2016-06-22 22:10:36,244] elib.intl - DEBUG: Set environment variable 'LANG' to 'en_US' ('msvcrt._putenv') [2016-06-22 22:10:36,244] elib.intl - DEBUG: Set environment variable 'LANG' to 'en_US' ('msvcr90._putenv') [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,576] chirp.ui.mainapp - INFO: Skipping existing stock config [2016-06-22 22:10:36,592] chirp.ui.reporting - DEBUG: Checking for updates [2016-06-22 22:10:36,760] chirp.ui.reporting - DEBUG: Server reports version daily-20160615 is latest [2016-06-22 22:10:42,934] chirp.ui.mainapp - DEBUG: User selected Icom IC-T70 on port COM4 [2016-06-22 22:10:42,950] chirp.ui.clone - DEBUG: Clone thread started [2016-06-22 22:10:43,477] chirp.ui.reporting - DEBUG: Reporting exception [2016-06-22 22:10:43,477] chirp.ui.common - ERROR: -- Exception: -- [2016-06-22 22:10:43,477] chirp.ui.common - ERROR: Traceback (most recent call last): File "chirp\ui\clone.pyo", line 249, in run File "chirp\drivers\icf.pyo", line 616, in sync_in File "chirp\drivers\icf.pyo", line 322, in clone_from_radio RadioError: Failed to communicate with the radio: Unexpected response from radio [2016-06-22 22:10:43,477] chirp.ui.common - ERROR: ---------------- [2016-06-22 22:10:43,477] chirp.ui.clone - ERROR: Clone failed: Failed to communicate with the radio: Unexpected response from radio [2016-06-22 22:10:43,614] chirp.ui.clone - DEBUG: Clone thread ended [2016-06-22 22:10:43,614] chirp.ui.reporting - DEBUG: Reporting model usage: Icom_IC-T70,download,True [2016-06-22 22:10:43,614] chirp.ui.reporting - DEBUG: Reporting exception [2016-06-22 22:10:43,614] chirp.ui.inputdialog - ERROR: --- Exception Dialog: Failed to communicate with the radio: Unexpected response from radio --- [2016-06-22 22:10:43,614] chirp.ui.inputdialog - ERROR: Traceback (most recent call last): File "chirpw", line 67, in <module> AttributeError: 'NoneType' object has no attribute 'split' [2016-06-22 22:10:43,614] chirp.ui.inputdialog - ERROR: ---------------------------- ——————————————————————————— Adam Collins Principal Designer Graco Process Division Office: 612-623-6449 Fax: 612-378-3510 www.graco.com/process __________________ Tom, I have my debug file here: The issue is "failed to communicate with radio, unexpected response from > radio." on my Icom ic-t-70. Thanks, ——————————————————————————— Adam Collins Principal Designer Graco Process Division Office: 612-623-6449 Fax: 612-378-3510 www.graco.com/process From: Tom Hayward <tom(a)tomh.us> To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com>, Date: 06/21/2016 12:05 PM Subject: Re: [chirp_users] Icom ic-t70 Sent by: chirp_users-bounces(a)intrepid.danplanet.com On Tue, Jun 21, 2016 at 9:52 AM, <Adam_K_Collins(a)graco.com> wrote: > > Hi, I'm looking for help with my ic-t70. > > For months I have been trying to get an image file into Chirp. > > I have confirmed correct drivers, COM ports, and no faulty cables. All I > ever get is "failed to communicate with radio, unexpected response from > radio." "Unexpected response" means it did receive something, but that something wasn't what Chirp identifies as an IC-T70. Your debug log might tell you more, but since you didn't provide it I'll just go hunting myself... http://chirp.danplanet.com/projects/chirp/repository/entry/chirp/drivers/ic… It looks like that error comes up when your radio responds to the clone request with more than one frame of data. What's in that extra data? Who knows. You might find more in your debug log. http://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues#Getting… Tom KD7LXL _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Adam at adam_k_collins(a)graco.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

1 0

[chirp_users] New Daily Build
by Build System 23 Jun '16

23 Jun '16

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20160623 A list of the changes included in this build (since the last daily) follows: Changes for Build #410 [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][BTECH][LT-588UV] Add a new model to the BTECH family, fixes #3067 A new model for the btech driver family: the LUITON LT-588UV, it's not a clone it's a variant of the early QYT KT8900. Also some tidy of the radio variants in the code to group the vendors. [Tom Hayward <tom(a)tomh.us>] [ui] Default file name to include model and date. #3753 During Save As, default the filename to {vendor}_{model}_{date}.img. The user is free to edit the field to their liking before saving. In case you don't like {vendor}_{model}_{date}.img, a new configuration variable "default_filename" is provided. By setting this variable in your config file, you can reorder or omit parts of the default format. Example: [global] default_filename = {vendor}_{model} This omits the date. Example: [global] default_filename = Tom's_{vendor}_{model}_{date} This begins each filename with my name.

1 0

[chirp_users] seeing my posting
by Richard Castleberry 21 Jun '16

21 Jun '16

I am confused how this users group works. I posted an question but am not sure how to get back to see responses. Is there also a web site version I might access? Thx, Richard

6 6

[chirp_users] basic programming
by Richard Castleberry 18 Jun '16

18 Jun '16

Super basic question about CHIRP programming... I have the latest 'daily build' and loaded some local freqs into my Baofeng. Have Chirp open on my PC (Windows 7) and can't seem to sort out how to re-load my settings back into my radio. (my programming cable seems to be fine) I had no trouble loading it the first time but now not sure where to find the backup file I made. Can someone advise? Thx!

10 101

[chirp_users] Resending message
by Wenlock Burton 18 Jun '16

18 Jun '16

Hi We seem to have a message stuck on repeat??? Wenlock Sent from my iPhone

1 0

Re: [chirp_users] PL tones (was Chirp's new Alias feature.)
by Jim Unroe 16 Jun '16

16 Jun '16

On Wed, Jun 15, 2016 at 5:13 PM, Curley Frazier <ricknbrook(a)gmail.com> wrote: > Love Chirp! Thanks for all you do. One question please? In my Baofung UV-5R+ > if I open menu to look at settings go tell a freind what PL tone a repeater > had on a stored frequency, or to to program another radio in the field, it > shows blank.....? Can this be edited to show each repeaters PL? > This discussion thread is about CHIRP's new alias feature. You should start a new thread instead of hijacking this one. You don't have to open the settings to see the tones programmed in a stored memory because they are all displayed in the spreadsheet style memory editor. That being said, if you try to open the settings tab and the menu is blank, then there is most likely a setting that is out-of-range. Attach a debug.log file and we should be able to determine which one it is and help you correct it in your radio so it will then show up properly in CHIRP (and possibly use that information to update CHIRP to handle the out-of-range value in the future). See the "how to report issues" page to learn how to find your debug.log file. http://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues Jim KC9HI

2 1

[chirp_users] New Daily Build
by Build System 15 Jun '16

15 Jun '16

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20160615 A list of the changes included in this build (since the last daily) follows: Changes for Build #409 [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][Feature] Add the know clones of the btech with the new alias feature, fixes #3749 This patch explicitly adds the following Btech clones to the UI: * Jetstream JT2705M * Juentai JT-6188 Mini * Juentai JT-6188 Plus * Sainsonic GT-890 This radios do show properly now in the download/upload dialog as vendor/model, this will ease the handling of clones in the user side. But it has a catch and the users will be notified on the chirp_user list: when you opens a saved image of a clone it will show in Chirp as the real radio, not the clone. 73 Pavel CO7WT [Dan Smith <dsmith(a)danplanet.com>] Add radio alias support This introduces a small class called Alias which defines the identifying attributes of a radio model. Radio inherits from that, and also has a list of ALIASES that can be zero or more of those classes. When we construct the clone box where a user chooses a model, show them all the models, including aliases. #0 [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][KT-8900R] Fix the second ID to cope with a new variant, fixes #3547 The latest added variant has the second ID without the leading spaces, instead it's filled with '123456' We removed the leading spaces as the ID is the same of the others but they changed the leding spaces. [Nathan Crapo <nathan(a)n4nc3o.com>] Make radio model identification for TH-7800 and TH-9800 more specific so they don't interfere with each other, or completely different radios. The TH-7800 was ahead of the TH-9800 in the list of Radios to identify against, so Chirp would use it for TH-7800 _and_ TH-9800 radios. This patch makes both TH-7800 and TH-9800 drivers check their model more carefully so order of Radios Classes doesn't matter. It's more robust that way. TH-7800 seems to use "TH9800" for a model string too. Check for a "TH9800" _or_ "TH7800" string in the th7800.py driver in case TYT doesn't consistently set the model or in case owners change their model name. Fixes #3737.

4 3

[chirp_users] UV-5RA - latest build
by Steve London 11 Jun '16

11 Jun '16

Long story....but I'll summarize the current issue. I had my old UV-5RA talking to a 2014-vintage version of Chirp. Worked fine. Got a new UV-5RV2+. Doesn't talk to the 2014 version. Downloaded/Installed the latest nightly Chirp build - 20160604 . Won't talk to either the previously-working UV-5RA or the new UV-5RV2+. Radio does not respond. Where do I go from here ? 73, Steve, N2IC

10 21

[chirp_users] New Daily Build
by Build System 11 Jun '16

11 Jun '16

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20160611 A list of the changes included in this build (since the last daily) follows: Changes for Build #408 [Dan Smith <dsmith(a)danplanet.com>] Add some extra debug to kguv8d driver download process To help with diagnosing #3733 [Nathan Crapo <nathan(a)n4nc3o.com>] Adding support for TYT TH-7800. Fixes #3477. [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][KT-8900R] Add a new discovered variant, fixes #3547 A new variant of this radio was found on the wild. Also my IDE (Geany) has a strict policy for leading spaces, so it removed automaticaly some of them. 73 [Tom Hayward <tom(a)tomh.us>] Support pySerial 3+. Fixes #3167 #3209 #3521 #3671 #3703

1 0

[chirp_users] More UV8D Issues
by Chris Levi 09 Jun '16

09 Jun '16

Gentlemen, I have done the menu resets and attempted to program the radios by hand with no joy even after a hard reset with the language being Chinese and all settings reset I still am having transmit and receive issues. I have re-tried with Chirp and still no success. Best I can figure it has something to do with the "QT" modes not allowing the audio out, but that is a W.A.G. on my part and most likely only the tip of the iceberg. Is there a diagnostic suite available like moto-labs for these radios? Thank you for any help, Chris KG6TTN

1 0

Re: [chirp_users] Settings to match Motorola PL tones
by Rich Messeder 08 Jun '16

08 Jun '16

I think this is a good question. I have recently acquired 2 BaoFeng UV-5RTP. I have programmed them "successfully", but not tested the results. Here is my take on it. I think that CHIRP allows the user to select TSQL, indicating that the ToneSql value is used for repeater access. It is unfortunate that we all don't use the same terms. I opine that CTCSS is the same thing as PL; one is a generic term and the other a vendor term. I understand that Tone in CHIRP is used for receive. If you have Tone selected, then the sender must use the agreed tone to open your squelch. For repeaters, I am not sure that all repeaters use tone (PL, CTCSS) on transmit, as they do on receive. A repeater first senses the carrier on the inbound freq, and then look for the PL tone. My impression is that many radios do not (can not) use PL codes /from/ a repeater that are different from the sending PL tone. Now to 2 radios. The sending unit must send the same tone that the receiving unit is filtering on. So if you are both working simplex, and you both have tone squelch enabled and are using the same PL|CTCSS tones, it should work. I might try that later today or tomorrow if I have the time. From http://chirp.danplanet.com/projects/chirp/wiki/MemoryEditorColumns Tone This sets the CTCSS tone to be transmitted if the Tone Mode is set to Tone. In Cross mode, it has additional meanings (see description of Cross Mode for more details). ToneSql This sets the CTCSS tone to be transmitted and used for receiver squelch if the Tone Mode is set to TSQL. In Cross mode it has additional meanings (see description of Cross Mode for more details). I too have used TSQL for many entries, and now wonder if I should be using Tone, because I want to trigger the repeater with a PL tone, but then want the reply no matter what. ~R~ NE1EE Short email? No html? Here's why: http://emailcharter.org/ On 2016-06-08 09:26:-0400, Jeffrey wrote: >Hey everyone, > >I'm pretty new to radios in general, and more so programming them, but I'll do my best to get the terminology right. > >I'm trying to use CHIRP to program a UV-5R so that it can communicate with a Motorola radio on a certain frequency.� The Motorola is set to use 151.9400 with a PL tone of 67.0 for both send and receive. > >PL is the same as CTCSS correct? > >On the UV-5R, I've got Tone Mode set as TSQL and ToneSql set to 67.0 - and it does not work? The two radios are not communicating.� Am I missing something? Something special about Motorola PL tones? Should be a standard right? > >Thanks for any advice. > >Jeff >Jeffrey Fongemie � � >_______________________________________________ >chirp_users mailing list >chirp_users(a)intrepid.danplanet.com >http://intrepid.danplanet.com/mailman/listinfo/chirp_users >This message was sent to WeatheredSoul at rich.messeder(a)gmail.com >To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

8 8

[chirp_users] Settings to match Motorola PL tones
by Jeffrey 08 Jun '16

08 Jun '16

Hey everyone, I'm pretty new to radios in general, and more so programming them, but I'll do my best to get the terminology right. I'm trying to use CHIRP to program a UV-5R so that it can communicate with a Motorola radio on a certain frequency. The Motorola is set to use 151.9400 with a PL tone of 67.0 for both send and receive. PL is the same as CTCSS correct? On the UV-5R, I've got Tone Mode set as TSQL and ToneSql set to 67.0 - and it does not work? The two radios are not communicating. Am I missing something? Something special about Motorola PL tones? Should be a standard right? Thanks for any advice. Jeff -- ______________ Jeffrey Fongemie <http://instagram.com/jfongemie>

7 10

Re: [chirp_users] Settings to match Motorola PL tones
by Rich Messeder 08 Jun '16

08 Jun '16

Thanks, "Rich". ;-) "Direct" is called simplex. On my Kenwood TH-F6A, I can select "Tone" to activate a repeater that requires it, or I can select CTCSS (PL) to filter incoming calls according to a tone. But using one cancels the other. Some radio permit the use of both, hence the CROSS value in CHIRP. IMO. setting the ToneMode to Tone should have resulted in the UV5 /sending/ a tone. If it were earlier TSQL, and the Motorola were NOT sending a tone, then the UV5 would have not opened its squelch, and you would not receive the call. And yes the transmission is open to everyone to hear. All that TSQL does is tell your radio to ignore all transmissions it receives EXCEPT for those that also carry the CTCSS tone. Please note that if two radios are transmitting on the same freq, and one uses the tone to open your squelch, you will hear both transmissions simultaneously. Gotta go offline for the rest of the day...sorry. ~Rich~ On 2016-06-08 10:15:-0400, Jeffrey wrote: >Thanks Rick. > >I just tried setting Tone Mode to "Tone" with a tone of 67.0 it the UV5R was able to receive from the Motorola, but the Motorola could not receive from the UV5R. > >"Tone: A single CTCSS tone is transmitted, receive squelch is open or carrier-triggered. The tone used is that which is set in the Tone column.:" > >So, if I read this correctly, the Motorola radio transmission is open to everyone? And will filter out everything that does not transmit with the correct tone?� > >Tone mode as "Tone" should work if I have the correct tone, and the radio is sending it correctly. Right? > >Jeff > >On Wed, Jun 8, 2016 at 9:55 AM, Rich Messeder <<mailto:rich.messeder@gmail.com>rich.messeder(a)gmail.com> wrote: >I think this is a good question. I have recently acquired 2 BaoFeng UV-5RTP. I have programmed them "successfully", but not tested the results. > >Here is my take on it. > >I think that CHIRP allows the user to select TSQL, indicating that the ToneSql value is used for repeater access. It is unfortunate that we all don't use the same terms. I opine that CTCSS is the same thing as PL; one is a generic term and the other a vendor term. > >I understand that Tone in CHIRP is used for receive. If you have Tone selected, then the sender must use the agreed tone to open your squelch. For repeaters, I am not sure that all repeaters use tone (PL, CTCSS) on transmit, as they do on receive. A repeater first senses the carrier on the inbound freq, and then look for the PL tone. > >My impression is that many radios do not (can not) use PL codes /from/ a repeater that are different from the sending PL tone. > >Now to 2 radios. >The sending unit must send the same tone that the receiving unit is filtering on. So if you are both working simplex, and you both have tone squelch enabled and are using the same PL|CTCSS tones, it should work. I might try that later today or tomorrow if I have the time. > >From ><http://chirp.danplanet.com/projects/chirp/wiki/MemoryEditorColumns>http://chirp.danplanet.com/projects/chirp/wiki/MemoryEditorColumns >Tone >This sets the CTCSS tone to be transmitted if the Tone Mode is set to Tone. In Cross mode, it has additional meanings (see description of Cross Mode for more details). > >ToneSql >This sets the CTCSS tone to be transmitted and used for receiver squelch if the Tone Mode is set to TSQL. In Cross mode it has additional meanings (see description of Cross Mode for more details). > >I too have used TSQL for many entries, and now wonder if I should be using Tone, because I want to trigger the repeater with a PL tone, but then want the reply no matter what. > >~R~ NE1EE >Short email? No html? Here's why: <http://emailcharter.org/>http://emailcharter.org/ > >On 2016-06-08 09:26:-0400, Jeffrey wrote: >>Hey everyone, >> >>I'm pretty new to radios in general, and more so programming them, but I'll do my best to get the terminology right. >> >>I'm trying to use CHIRP to program a UV-5R so that it can communicate with a Motorola radio on a certain frequency.Â� The Motorola is set to use 151.9400 with a PL tone of 67.0 for both send and receive. >> >>PL is the same as CTCSS correct? >> >>On the UV-5R, I've got Tone Mode set as TSQL and ToneSql set to 67.0 - and it does not work? The two radios are not communicating.Â� Am I missing something? Something special about Motorola PL tones? Should be a standard right? >> >>Thanks for any advice. >> >>Jeff >>Jeffrey Fongemie Â� Â >>_______________________________________________ >>chirp_users mailing list >><mailto:chirp_users@intrepid.danplanet.com>chirp_users(a)intrepid.danplanet.com >>http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>This message was sent to WeatheredSoul at <mailto:rich.messeder@gmail.com>rich.messeder(a)gmail.com >>To unsubscribe, send an email to <mailto:chirp_users-unsubscribe@intrepid.danplanet.com>chirp_users-unsubscribe(a)intrepid.danplanet.com > > >_______________________________________________ >chirp_users mailing list ><mailto:chirp_users@intrepid.danplanet.com>chirp_users(a)intrepid.danplanet.com >http://intrepid.danplanet.com/mailman/listinfo/chirp_users >This message was sent to <mailto:fongemie@gmail.com>fongemie(a)gmail.com at <mailto:fongemie@gmail.com>fongemie(a)gmail.com >To unsubscribe, send an email to <mailto:chirp_users-unsubscribe@intrepid.danplanet.com>chirp_users-unsubscribe(a)intrepid.danplanet.com > > > > >-- >______________ > >Jeffrey Fongemie � � > > >_______________________________________________ >chirp_users mailing list >chirp_users(a)intrepid.danplanet.com >http://intrepid.danplanet.com/mailman/listinfo/chirp_users >This message was sent to WeatheredSoul at rich.messeder(a)gmail.com >To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

3 2

[chirp_users] firmware
by digitdan 07 Jun '16

07 Jun '16

How can I find out what firmware is in my BaoFeng GT-2 Mark ll Dan

2 1

Re: [chirp_users] BaoFeng GT-3 Mark ll problem with channel name not uploading
by NP3AR 06 Jun '16

06 Jun '16

I don't have that specific radio but I have a Baofeng and there is an option in the menus to turn names on. Sent from my Samsung Galaxy Tab®4 -------- Original message -------- From: digitdan <digitdan(a)edifax.com> Date:06/06/2016 2:13 PM (GMT-04:00) To: chirp_users(a)intrepid.danplanet.com Subject: [chirp_users] BaoFeng GT-3 Mark ll problem with channel name not uploading I downloaded the most recent Chirp software to program a BaoFeng GT-3 Mark ll. I programed all the info for 12 channels, then read the radio then uploaded the program but when I check the radio the channel names did not show up. All the frequencies where there and the radio RX and TX fine but no channel names. I tried it in both channel and frequency modes. Can anyone help??? Dan H.

1 0

[chirp_users] BaoFeng GT-3 Mark ll problem with channel name not uploading
by digitdan 06 Jun '16

06 Jun '16

I downloaded the most recent Chirp software to program a BaoFeng GT-3 Mark ll. I programed all the info for 12 channels, then read the radio then uploaded the program but when I check the radio the channel names did not show up. All the frequencies where there and the radio RX and TX fine but no channel names. I tried it in both channel and frequency modes. Can anyone help??? Dan H.

2 1

[chirp_users] Problems programming ICOM IC-V82
by Larry Gagnon 06 Jun '16

06 Jun '16

Using Chirp v daily-20160301 on Linux and an ICOM IC-V82 VHF handheld. Was able to successfully connect and download from the radio. Added some channels, then uploaded. Upload seemed to go fine but with an error message at the end that reads: "Failed to communicate with the radio. Did not get clone result from radio." On rebooting the handheld all appears fine, new channels are there but all the channels that have offsets do not take, in other words it transmits/receives on same frequency, even though file is virtually identical to that uploaded from the radio and I have double checked to offset and duplex are correct. Any ideas appreciated. Larry VE7EA

4 4

Re: [chirp_users] Baofeng UV-5R firmware upgrade?
by Stormy 06 Jun '16

06 Jun '16

I think I open a new thread each reply, sorry, using yahoo mail, and not sure how to reply on same thread (I get the daily digest). I'm worried to get a "new" radio, but in fact seller sends old inventory , hence I'm checking the firmware before purchasing since as u say it is a one-time programming firmware :) Can someone confirm is getting anything from the last block on this list: http://www.miklor.com/uv5r/UV5R-Firmware.php Managed to find: N5R-2401 is this good enough? or should I try to get a higher number? like NR5R-3409? Thanks!!Stormy.

3 3

[chirp_users] New Daily Build
by Build System 04 Jun '16

04 Jun '16

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20160604 A list of the changes included in this build (since the last daily) follows: Changes for Build #407 [Tom Hayward <tom(a)tomh.us>] [ui] Dismiss shift dialog with enter key. Fixes #3695 [Tom Hayward <tom(a)tomh.us>] [ui] Default memory editor view to 0-999 (was 0-25). Fixes #3629

1 0

Re: [chirp_users] Baofeng UV-5R firmware upgrade?
by Stormy 03 Jun '16

03 Jun '16

WOW, really appreciate your comprehensive reply, now it's archived, so others hopefully can benefit.. Is that really true that since 2014 there have been newer firmware but no detected changes? or this list is out of date: http://www.miklor.com/uv5r/UV5R-Firmware.php I'm trying to figure the best firmware to look for in a new purchase. Thanks.

4 3

Re: [chirp_users] Take me off your list
by Randy Rushing 02 Jun '16

02 Jun '16

As sent you an email on a earlier date I repeat it again ((((((Take me off your list))))))_) And stop sending the email/ Or I will report. this.

4 3

[chirp_users] Baofeng UV-5R firmware upgrade?
by Stormy 02 Jun '16

02 Jun '16

Hi, Newbie question, sorry :) Not sure where else to ask... Noticed here: http://www.miklor.com/uv5r/UV5R-Firmware.php it says firmwares are not changable on the Baofeng UV-5R radios.. but then reading some postings led to this directory: http://kc9hi.dyndns.org/uv5r/programming/CHIRPrecovery/ with list of firmwares.. and someone alluding to being able to switch or flush these? If I have a device with a given firmware, then for the life it cannot be changed? Thanks much. Stormy.

2 1

[chirp_users] Accessing Repeaterbook from chirp
by Scott Brewster 01 Jun '16

01 Jun '16

I am trying to get a list of 2m and 70cm repeaters for my area with no luck. Steps taken: Start ChirpFile: NewRadio: Query Data Source: Repeaterbook Initial dialog box comes up; I select Arizona for state; Maricopa for County and 2 Meters for Band. Clicking ok results in the "standard" busy mouse icon (small greenish blue circle). Data from Repeaterbook never shows up.Even though busy mouse icon is showing, I am able to click and use options within chirp. Attempts to use other sources appears to work (albeit I am not subscribed or premium with those other sources). Reading/writing from radio otherwise works, no other issues noticed. I have tried this with the last couple of windows daily builds - latest is today's - with no luck. Am I missing something? >From chirp about: Chirp daily - 20160531 OS: Windows 7.

7 9

[chirp_users] New Daily Build
by Build System 01 Jun '16

01 Jun '16

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20160601 A list of the changes included in this build (since the last daily) follows: Changes for Build #406 [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][QYT KT-8900R] Add support for a new variant, fixes #3547 A new variant of this radios was found, this patch adds support for it. All points that the previously found version was Generation 2 and this new one is from Generation 1 as the ID string shows, this patch also name the versions correctly. [Robert Morris <chirp.shopping(a)iloc.com>] Fix for Bug #3679 - Keyboard shortcuts are non-standard for Mac OS X. To improve standard cut/copy/paste UI conformity, re-mapped export shortcut to use <Ctrl>e. <Ctrl>x is for cut.

4 3

[chirp_users] Hello all Chirpers :-)
by neil - ee 01 Jun '16

01 Jun '16

Hi fellow Chirpers :) I got myself a baofeng uv5r radi and a cable. Was looking for a good program to edit its memorys. Found this one first and tried it and loved it. I then found the oem programmer for it, but chirp much better I then discovered that chirp will also do the settings of the radio, and also my other radio, yaesu 857d too. So both radios got a full memory makeover with the help of excel too. I have a few other radios, one to ask about is my icom e90 quadband handheld (6m,4m,2m,70cm) I have a icom cable and its own software. It works. But was wondering if chirp is likely to come along to support as well. My comments on the program itself that I love, are 1. Keyboard shoutcuts, not standardised, ie, alt f a for save as ; alt f o for open; silly little thing like that :) 2. Unsure if bug, but regarding cts codes, and the 2 coloums Tone and ToneSql - edit in chirp, ok. But if you export, edit both coloums in excel and re-import, ToneSql gets ignored on all lines back to 88.5 3. Anuther possible bug, when typing a frequency in, and you fluff it on enter, it pops a error up, Error setting memory: Frequency 0.000000 is out of supported range" as example. But then it dumps you back up to line 1, so in a long list, you got to scroll back down to as line 200 to find and fix it again. 4. When using a mouse, the roller on the mouse does not seem to use the same speed of page/line scroll as it does in other windows apps. Takes longer in chirp. 5. Maybe another silly comment..if I have a chrip img file open.when I open another, I expect it to show the new opened file. But it don't, it stays with the current opened one. Not the new one, I have to tab across. Not hard to do of course. Its just tweaks :) Hope all is ok with that above. 73's Ne

1 0

Re: [chirp_users] Accessing Repeaterbook from chirp
by jl_wilkerson＠att.net 31 May '16

31 May '16

Repeaterbook is free. ------ Original message------From: Jock via chirp_users Date: Tue, May 31, 2016 4:51 PMTo: chirp_users@intrepid.danplanet.com;Subject:Re: [chirp_users] Accessing Repeaterbook from chirp I believe Repeater Book requires a subscription. KC6IIH JockJock Soutar KC6IIH Sent via Samsung Galaxy S7 on AT&T 4G LTE Smartphone On Tuesday, May 31, 2016 Scott Brewster via chirp_users <chirp_users(a)intrepid.danplanet.com> wrote: I am trying to get a list of 2m and 70cm repeaters for my area with no luck. Steps taken: Start ChirpFile: NewRadio: Query Data Source: Repeaterbook Initial dialog box comes up; I select Arizona for state; Maricopa for County and 2 Meters for Band. Clicking ok results in the "standard" busy mouse icon (small greenish blue circle). Data from Repeaterbook never shows up.Even though busy mouse icon is showing, I am able to click and use options within chirp. Attempts to use other sources appears to work (albeit I am not subscribed or premium with those other sources). Reading/writing from radio otherwise works, no other issues noticed. I have tried this with the last couple of windows daily builds - latest is today's - with no luck. Am I missing something? From chirp about: Chirp daily - 20160531 OS: Windows 7. _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jock at kc6iih(a)aol.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

1 0

[chirp_users] pySerial
by Ryan Barber 31 May '16

31 May '16

Hi all, Are there plans to fix the depreciated calls to pySerial setBaudrate? -Ryan

2 3

Re: [chirp_users] New Daily Build
by Rich Messeder 31 May '16

31 May '16

I linked to the messages (see bottom of email), and saw some comments about the background for this mod. Here are my comments, just FYI, no complaints. Windows 10 Pro x64. 1. I am using the standalone version. Wish that there is an x64 version. 2. Copy | Paste of records and record blocks twixt 2 instances if CHIRP, using ctrl-c, -v, works for records now. 3. Twould be nice if the confirmation dialog showed up on the same display as the main program. I run CHIRP on a an extended display in Windows. 4. Ctrl-x does not work in a field. Delete does not work in a field. Ctrl-v does not work in a field. 5. RMC: Copy //does// work in a field, but then RMC: Paste is disabled in the 2nd instance. I /can/ RMC: Paste into a different file in a different tab in the same instance. 6. I use the standalone version because I find it more controllable than installing multiple versions of the same product, though I imagine that upgrading the installed version in place works fine. Not tested. I do this so that it is easy for me to roll back, if I wish. 7. I use multiple instances of the standalone version because I can alt-tab twixt them to copy | paste. Ctrl-tab does not work for me, though it does shift the focus from a memory to a tab. So I can't easily cut from one tab and paste to another. 8. I understand deprecating .chirp files, even if I don't know the history. If .csv files are the ne way of exporting, that works for me. 9. Still don't know why I can't save Kenwood TH-F6A .img in CHIRP, but can in Kenwood's Memory Control Program (MCP). MCP is not "live". I just did this test. While CHIRP was open, I ran MCP. I downloaded from the F6A. I modified a memory. I saved the file as .fx. I ended MCP. The F6A remained unchanged. I interpret this to mean that I could save the F6A in CHIRP as a .img file (which I can't). 10. It's nice that both MCP and CHIRP do not take control of the COM port; that is, they open it, use it, and release it. This allows me to run both programs at the same time. Currently, there are advantages and disadvantages to using both MCP and CHIRP with the F6A, so I use both. ~R~ NE1EE Short email? No html? Here's why: http://emailcharter.org/ On 2016-05-31 00:09:-0700, Build System wrote: >Greetings, >http://trac.chirp.danplanet.com/chirp_daily/daily-20160531 > >A list of the changes included in this build (since the last daily) follows: > >Changes for Build #405 >[Tom Hayward <tom(a)tomh.us>] [ui] Change clipboard target to support cross-process copy/paste on Windows. #3693 > >Clipboard target was PRIMARY, the X clipboard. Changed to CLIPBOARD, the >default clipboard, for better Windows support including the ability >to copy/paste between multiple instances of Chirp. > >http://intrepid.danplanet.com/pipermail/chirp_devel/2016-May/004018.html > >[Tom Hayward <tom(a)tomh.us>] [ui] Store clipboard outside of app, so paste works after quitting. #3691 > >[Tom Hayward <tom(a)tomh.us>] [ui] Deprecate .chirp file format by disabling export. #3689 > >The .chirp file format provides no additional features compared to .CSV and is >therefore redundant. .chirp is the more complex and less frequently used format >of the two, so to eliminate the redundancy it should be deprecated. > >This patch removes the ability to export as .chirp, leaving no way to generate >new .chirp files. It preserves the ability to open and import .chirp files, so >any existing .chirp files can still be opened, edited, and exported to other >formats. > >chirp_users mailing list >chirp_users(a)intrepid.danplanet.com >http://intrepid.danplanet.com/mailman/listinfo/chirp_users

2 2

[chirp_users] New Daily Build
by Build System 31 May '16

31 May '16

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20160531 A list of the changes included in this build (since the last daily) follows: Changes for Build #405 [Tom Hayward <tom(a)tomh.us>] [ui] Change clipboard target to support cross-process copy/paste on Windows. #3693 Clipboard target was PRIMARY, the X clipboard. Changed to CLIPBOARD, the default clipboard, for better Windows support including the ability to copy/paste between multiple instances of Chirp. http://intrepid.danplanet.com/pipermail/chirp_devel/2016-May/004018.html [Tom Hayward <tom(a)tomh.us>] [ui] Store clipboard outside of app, so paste works after quitting. #3691 [Tom Hayward <tom(a)tomh.us>] [ui] Deprecate .chirp file format by disabling export. #3689 The .chirp file format provides no additional features compared to .CSV and is therefore redundant. .chirp is the more complex and less frequently used format of the two, so to eliminate the redundancy it should be deprecated. This patch removes the ability to export as .chirp, leaving no way to generate new .chirp files. It preserves the ability to open and import .chirp files, so any existing .chirp files can still be opened, edited, and exported to other formats.

1 0

[chirp_users] win 10
by William Coleman 31 May '16

31 May '16

Hi everyone ! Just a quick note. I have the latest release version of chirp working OK with Windows 10 64bit on my desktop . There have been no issues so far with chirp while running windows 10 with either reading or transferring data to and from my GT-5 . I had to roll back the 3.6 driver to 3.2.2.0 that windows had initially installed . It was giving me a cannot start device error message. Once I rolled back the drivers there was no further issues. Will C. KF7SSF

5 5

[chirp_users] TYT th-9800 Memory
by Daniel Chater 31 May '16

31 May '16

Hello all, I am having huge issue using Chirp in windows 10 so I have installed chirp on a Ubuntu and i worked first time first try. I bought the TYT because it is a quad band and I wanted this to be a mobile that I could use as a house rig as well. The only thing I cannot figure out is that the TH-9800 has a 800 channel Memory but all i am getting is 25 total. Can someone tell me what I have to do to add additional memories and Bands? -- 73, Dan ve3zxs http://www.callsign.ca/ind.php

3 6

[chirp_users] New dev driver with a new variant of the QYT KT-8900R
by Pavel Milanes (CO7WT) 30 May '16

30 May '16

Hi to all, Attached is a dev driver for the btech's radio series for your consideration, it has support for a recently discovered version of the QYT KT-8900R. As I don't have this radio I need your help to validate this solution before pushing it into Chirp. Al the bits shows that the initial support for the QYT KT-8900R in Chirp was for a Generation 2 of this radios, now the recently found variant is for the 1st generation of this radios. Please test it if you have a QYT KT-8900R that was not recognized by Chirp after it's addition, all the success/failure stories are welcomed (the failure are more appreciated if come with the debug.log file) To try it you must follow this steps: 1. save the "btech.py" file attached to this post to where you keep your chirp radio image files 2. click "Help" 3. enable "Enable Developer Functions" 4. click "File" 5. click "Load Module" 6. find and load the "btech.py" file that was saved in step 1 *Note:* This special test module only temporarily changes your CHIRP. You must load this module every time you load CHIRP. Remember that this is a dev version and I need your feedback to make this solution into Chirp. -- 73 Pavel CO7WT.

1 0

[chirp_users] Luiton radios
by Jack Schlachter 28 May '16

28 May '16

I've ask several times about adding Luiton radios to chirp and one of your responses in another thread stated how busy you are and I get that. I was just wondering if you could take the two minutes to let us Luiton users know if you plan at all to add it to the Chirp radio list. That way I'll at least know and can explore other avenues which for me means sending the radio back because actually there is no other options except to spend the $50 at RMS to get support. Living on SS won't let me do that. I hope I don't sound too aggressive because I don't mean to be, Just would like some answer. Thanks

3 2

[chirp_users] Chirp windows version not updated?
by Tom Consodine 27 May '16

27 May '16

The latest Linux daily build is 20160522. The latest Windows daily build is 20160517. Why is that? Tom ND5Y

4 4

[chirp_users] New Daily Build
by Build System 27 May '16

27 May '16

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20160527 A list of the changes included in this build (since the last daily) follows: Changes for Build #403 [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][KT8900R] Settings fix about the 220Mhz band, fixes #3547 Now we have two of this radios that has 220/240 Mhz support in the base class and we need to validate the freq ranges for each one of them, this patch is to realize that. Thanks to Jim Unroe for the help with it. [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][KT8900R] Initial support for the QYT KT8900R, fixes #3547 This radio is like the BTECH UV-2501+220 but it has the 220 band in the Chinese area (240-270 Mhz) well outside the USA ham band. This is the initial support patch for this radio, it may need further work on the settings part. Changes for Build #404 [Jim Unroe <rock.unroe(a)gmail.com>] [BTECH] Add new settings for BTECH gen3 radios * Mic Gain * DTMF Gain related to #3015

1 0

[chirp_users] back to Linux
by Jack Schlachter 27 May '16

27 May '16

I thought with the great success I had with my Linux box and my Baofeng that I would try the LT-Luiton 588UV. So hooked everything up and I chose as radio type Leixen which someone in my club told me worked for them on Chirp. My first attempt I got Failed to download from radio: Radio refused program mode. Anyone know what might be causing this error? On my second attempt I thought well it worked so well with the Baofeng maybe I'd try making it think it's a Baofeng. So I selected Baofeng Model BF888 which I think is a mobile radio like mine. The error this time read No response from radio. Any idea? Thanks, Jack

3 2

Re: [chirp_users] CHIRP and the Kenwood TH-F6A; syncing with Icom
by Rich Messeder 27 May '16

27 May '16

On 2016-05-26 18:43:-0400, you wrote: >Rich, > >I have a Kenwood TH-F6a. So just for the fun of it, I attached CHIRP >to it and read it in live mode. I copied and pasted on of the channels >from the TH-F6 tab to a tab from one of my Baofeng radios (a loaded >.img file). No problem. I did this, too. Interesting inconsistency. In fact, I copied a block successfully, which was my goal. >Then I followed the instructions that you pasted into your post and >exported the TH-F6a to a .csv file. I imported this into the image of >my Baofeng radio also without any problem. I had saved to a .chirp file. >And just for good measure, I exported the TH-F6a to a .chirp file and >imported it into my Baofeng radio image. No problem. I could not load the F6A .chirp file into the tab with the Icom image. Same error. Tried rewriting the .chirp. Same result. I can achieve my goal, so that meets my needs now, but still leaves the question...maybe I am still missing a point? >Part of the difference, I suppose, is that I am not trying to load 2 >instances of CHIRP. I am doing it with multiple tabs in a single >instance of CHIRP. Indeed...dunno why it didn't occur to me to try...guess I figured that multi-instances worked the same as tabs. ~R~ p.s. This still leaves a few questions from the original post unanswered...why is the F6A live? Why not save an image (likely related to previous question)? >Jim KC9HI >_______________________________________________ >chirp_users mailing list >chirp_users(a)intrepid.danplanet.com >http://intrepid.danplanet.com/mailman/listinfo/chirp_users >This message was sent to WeatheredSoul at rich.messeder(a)gmail.com >To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

1 0

[chirp_users] limitations of baofeng uv-5r
by Ted Roby 26 May '16

26 May '16

The default settings for Baofeng uv-5r include the following ranges: 130 - 176 (VHF) 400 - 520 (UHF) However, I was able to successfully raise the VHF range to 130 - 225. I did not attempt to go higher than 225 as I wanted to cover HAM frequencies in my area. After raising the limit of VHF in Other Settings, I was able to manually program a range of fm simplex frequencies through the radio itself. However, CHIRP does not allow me to program the 135cm band into memory, and states that it is out of supported range for this radio. I am able to download these modifications from the radio, but I cannot modify through CHIRP. Can this limit be raised in the driver? For verification I was able to tx from one uv-5r to another on 223.580 simplex.

3 2

[chirp_users] CHIRP and the Kenwood TH-F6A; syncing with Icom
by Rich Messeder 26 May '16

26 May '16

Using the Kenwood Memory Control Program (MCP), I can create and save radio images independent of the radio. But when I use CHIRP, I get "The Kenwood TH-F6 operates in live mode. This means that any changes you make are immediately sent to the radio. Because of this, you cannot perform the Save or Upload operations. If you wish to edit the contents offline, please Export to a CSV file, using the File menu." In the first place, why the behaviour? It does not appear necessary. I have verified that a change in MCP is not written until I write it. But CHIRP is indeed live. Why? It would be nicer if it were not. And why not save an image, even if the edits are live? This leads to my current puzzle. I have downloaded from the F6A in CHIRP. I save as a *.chirp file. I wanted to copy that to my Icom IC-T8A. I followed the beginner's guide and FAQ to merge the Kenwood data with the Icom data. Of course, the Kenwood data is not a *.img file, but a *.chirp file, and I get a schema error. The error makes sense, but only to a point...I guess that I am missing how to update different radios with the same data. I tried opening both the Icom img and the Kenwood in different instances of CHIRP, but I cannot copy from one and paste to the other. I'm sure that there is a simple step that I am missing. ~R~ NE1EE Short email? No html? Here's why: http://emailcharter.org/

4 3

[chirp_users] Cut and paste issue?
by Dennis Carr 26 May '16

26 May '16

Greetings! New user here, Still getting used to the software so I can get back on the air after eight years of no radio. (It sucked.) While working the software and rearranging a few layouts (using a BF-F9V2+), I noticed that Ctrl-X seems to behave much like Ctrl-C: it will copy, but it will not delete the original memory location once I have pasted elsewhere using Ctrl-V. I'm using XFCE on Debian Jessie at this time and running the daily from 20160517. This seems to be the only program where there are issues. Any words on this? Thanks, -Dennis KE7KIF

5 7

Re: [chirp_users] Cut and paste issue?
by Rich Messeder 26 May '16

26 May '16

Do I understand correctly that this feature applies to a few Yaesus, but exists in CHIRP for all radios to accommodate those few? I tried clicking after ctrl-x, and I see that the memory is active again, and this is on a download for a Kenwood F6A. OK as a backup, but not intuitive. It works on ctrl-x, where I can recover by following up with either clicking or by pasting (as long as no other actions overwrite the buffer), but does not work for deletion. I've been in a habit of thinking that cutting is more or less permanent, and I guess that it is here, too, but only after I write to the radio and complete the process. Whether the memory is grey or zeroed, I can always paste over it or edit it, so there is no loss of generality. ~R~ NE1EE On 2016-05-25 21:45:-0700, Tom Hayward wrote: >On Wed, May 25, 2016 at 6:44 PM, Rich Messeder <rich.messeder(a)gmail.com> wrote: >> But there is a comment below that reference data on the radio that is not accessible. This is puzzling to me. Does that mean that the data exists in the radio, but there is a flag also in the radio that says not to access that memory? Or recall it? Or tune to it? What is the point? Seems to me that if I delete a memory from the radio panel or from CHIRP, it ought to be gone. It's up to me to have a backup file if I want it... > >Yes, in a few Yaesu radios, deleted (or "masked") channels are set >with a flag. I believe the design goal by Yaesu here was to allow the >opportunity to undo a delete. In addition to supporting this, Chirp >also has the capability to write zeros over the whole block of memory. >For these select few radios, Chirp supports both delete mechanisms in >a two-stage delete (as described). The goal here was to make the Chirp >support as many of the radios' features as possible, and for the >experience to be as close to the radios' interface as possible. > >When a channel is masked (the first stage of the two-stage delete on >Yaesu radios), it can be unmasked from the front panel of the radio >(see the manual) or in Chirp, just click the greyed-out text to >resurrect it. > >Tom KD7LXL

1 0

Re: [chirp_users] Cut and paste issue?
by Rich Messeder 26 May '16

26 May '16

This is a key reply for me...I had originally thought that if CHIRP knew enough to turn the entry grey, it should know enough to reset the entry to empty. Why not? It would save the confusion that I have had, and that others seemingly have had. But there is a comment below that reference data on the radio that is not accessible. This is puzzling to me. Does that mean that the data exists in the radio, but there is a flag also in the radio that says not to access that memory? Or recall it? Or tune to it? What is the point? Seems to me that if I delete a memory from the radio panel or from CHIRP, it ought to be gone. It's up to me to have a backup file if I want it... Well, that was why I gave it a +1...I found (find) it confusing (now just distracting) to delete a memory and have it turn grey, not reset to "empty". If there is a requirement of the radio that makes the grey data necessary, so be it. I am not sure that I see this in effect on any of my radios...? ~R~ On 2016-05-25 13:15:-0700, you wrote: >On Wed, May 25, 2016 at 12:30 PM, Dennis Carr ><dennisthetiger(a)chez-vrolet.net> wrote: >> On Wed, 25 May 2016 14:15:17 -0500 >> Todd Bloomingdale <tbloomingdale(a)gmail.com> wrote: >> >>> Dennis, >>> >>> Once you cut a memory it will go grey. After you have pasted your cut >>> that location is now open to add another frequency into its spot even >>> though it shows as a greyed out. >> >> I should probably rephrase. It doesn't remove the settings from the >> old memory slot - this, in my mind, would be the correct behavior. > >Are you saying that after pasting, seeing the old line greyed out, and >uploading to the radio, that channel is still usable in the radio? > >I don't know how the BF-F9V2+ works, but on many Chirp radios there is >two stage delete: the first delete or ctrl-x will mask the channel. >This is illustrated in Chirp by light gray text. The data will still >be in the radio, but you won't be able to recall or tune it (common on >Yaesu radios). The second delete will zero out the channel so there is >no evidence of it ever being there. > >Tom KD7LXL >_______________________________________________ >chirp_users mailing list >chirp_users(a)intrepid.danplanet.com >http://intrepid.danplanet.com/mailman/listinfo/chirp_users >This message was sent to WeatheredSoul at rich.messeder(a)gmail.com >To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

2 1

[chirp_users] Success w/Linux
by Jack Schlachter 26 May '16

26 May '16

I want to thank the guys that help me with my Baofeng HH. Chirp loaded fine in Linux but I had trouble picking the right port the USB cable was on. One of you suggested USB0 and I did that "ls" command and it added it to the drop down list or it was always there at the very bottom. Then I ran that permissions command sudo usermod -aG dialout username and then logged out and back in and it finally worked. Now to get my Luiton working. Does anyone know if there is a radio on the Chirp list that would be compatable with the model LT- Luiton 588UV? Failing that does anyone know of any plans to add this radio. TIA I was wondering if you could tell me where I can get a list of commands to use in terminal with explanations of what they do, I know there's one out there somewhere if you could just point me. Again thank you for your help. Jack KM4TDJ

1 0

Re: [chirp_users] Problem reading memory on my UV5R
by S Allan Wilson 26 May '16

26 May '16

I am hoping this gets to the correct thread. I am using a Prolific Cable to interface with my Rugged Radios RH-5R. I think this is a clone of the Baofeng UV5R (?). I also run Windows 10. I found a discussion about Code 10 on Family Software (http://www.ifamilysoftware.com/news37.html). I read this article and then down loaded the file PL2303_64bit_Installer.exe. I run this first and follow onscreen instructions about when to plug in the cable. This has worked at allowing me to communicate with my radios. Maybe this will help someone here. Al Wilson -- Home is where the RV is *Home is where the RV is.* *Our Current Location <http://map.datastormusers.com/user1.cfm?user=1487> * *"OUR MISSION STATEMENT"* *Life's journey is not to arrive at our grave safely in a well preserved body, * *but to skid in sideways totally worn out, shouting * *"Holy Crap", what a ride!"*

1 0

[chirp_users] Baofeng UV-6R
by Geoff Hicks 25 May '16

25 May '16

Will CHIRP support this radio anytime soon? Is there some way that I can assist with the process? Thanks for creating this application! Sent from my iPad

2 1