January 2015 - Users - lists.chirpmyradio.com

[chirp_users] Unsupported Firmware
by Greg Hicks 06 Jan '15

06 Jan '15

Good Morning to All from new guy.... Greg here in Indianapolis, and brand new to the group & using CHIRP. Just received a BaoFeng BF-F8HP yesterday and have been playing with. I was amble to download from radio, but not upload. When I try to upload a new 'img' file, I get the following error message: Unsupported firmware version: N5R3401F8HP-1 Not sure how to look for this, nor where to find. Thanks, in advance for any help..... Greg <===><===><===><===><===> Greg Hicks, K9TLA Hancock County CERT Program Manager 317-501-5389 (cell) <===><===><===><===><===>

2 1

[chirp_users] Support for Icom ID-51E Special Edition
by Håken Hveem 06 Jan '15

06 Jan '15

Hello, is there any support for the Support for Icom ID-51E Special Edition at the moment, or is this planned ? LA1RMA -- Håken Hveem Gnup/PGP key ID: 45793A72

3 2

Re: [chirp_users] Raspberry PI rev level.
by Bob Boehme 04 Jan '15

04 Jan '15

Yes you have to go to the chirp site and download the latest.. Raspberry site has a really old version.. From: chirp_users-bounces(a)intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Chuck Hast Sent: Saturday, January 03, 2015 10:04 AM To: Discussion of CHIRP Subject: [chirp_users] Raspberry PI rev level. I noticed that the rev level for the RasPi is 0.1.12 is there newer rev level for the RasPi? if not what do i need to get to the 0.4.1 rev level for the RasPi?

1 0

[chirp_users] Raspberry PI rev level.
by Chuck Hast 03 Jan '15

03 Jan '15

I noticed that the rev level for the RasPi is 0.1.12 is there newer rev level for the RasPi? if not what do i need to get to the 0.4.1 rev level for the RasPi?

1 0

Re: [chirp_users] UV-5R Says "Radio did not respond"
by Bob Boehme 03 Jan '15

03 Jan '15

The plug does not go all the way in on some of the newer radios... trim a bit off the side with a knife and it will go all the way in.. -----Original Message----- From: chirp_users-bounces(a)intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Richard Dillman Sent: Friday, January 02, 2015 3:55 PM To: Jim Unroe; Discussion of CHIRP Subject: Re: [chirp_users] UV-5R Says "Radio did not respond" >Hi Richard, > >Since the programming cable already works with your radio, the driver >and programming cable must be OK. This means the problem is that you >are not getting the plug fully engaged in the radio. > >Jim KC9HI Hi Jim. You are always quick to respond with helpful advice. Thanks! Yeah, I encountered that plug seating issue with my own UV-5RA so with the UV-5R radio I really put some pressure on the connector - even trimmed the plug. But no joy. So maybe a defective connector on the radio side. Best, RD ================================= Richard Dillman, T2-GB-061170 Chief Operator, Coast Station KSM Maritime Radio Historical Society http://www.radiomarine.org ================================= _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users

1 0

[chirp_users] Account signup and FT1D
by Bret Palsson 03 Jan '15

03 Jan '15

Hi fellow CHIRP users/developers! Account signup: I never got my account verification email when registering. :( http://chirp.danplanet.com/login FT1D: I own this radio and I see support is being developed for it, just recently. I have already written a python program to dump the memory and I have decompiled the adms binary to source. I have the MemoryDataBase offsets, meanings, and code to generate the memory. Anyway I’d like to help out, I’m an software engineer with motivation to get my radio working. ;) -Bret public byte[] eepromDataArray = new byte[130496]; public Memory memData = new Memory(); public SetMode setData = new SetMode(); public Comment CommentData = new Comment(); private int memDtbsCpuType = 0; public const int EEPROM_ARRAY_SIZE = 130496; public const int EEPROM_MEM_BAND_COMMON_DATA_SIZE = 64; public const int EEPROM_MEM_BAND_SINGLE_DATA_SIZE = 128; public const int EEPROM_VFO_HONE_MEM_COMMON_DATA_SIZE = 32; public const int EEPROM_SP_TONE_SQL_DATA_SIZE = 1; public const int EEPROM_JR_SQL_DATA_SIZE = 1; public const int EEPROM_MEM_BANK_CH_NUM_DATA_SIZE = 2; public const int EEPROM_MEM_CH_DIR_DATA_SIZE = 1; public const int EEPROM_WX_MEM_AN_DATA_SIZE = 18; public const int EEPROM_BANK_NAME_DATA_SIZE = 18; public const int EEPROM_DTMF_MEM_DATA_SIZE = 16; public const int EEPROM_STATUS_TEXT_DATA_SIZE = 60; public const int EEPROM_WIRES_X_DATA_SIZE = 16; public const int EEPROM_GM_GROUP_NAME_DATA_SIZE = 16; public const int EEPROM_GM_MEMBER_NAME_DATA_SIZE = 15; public const int EEPROM_GM_MEMBER_NAME_RSV_DATA_SIZE = 5; public const int EEPROM_GM_MSG_SAVE_DATA_SIZE = 80; public const int EEPROM_GPS_POSITION_DATA_SIZE = 28; public const int EEPROM_DIGITAL_CALL_SIGN_DATA_SIZE = 10; public const int EEPROM_APRS_MYCALL_SSID_BIN_DATA_SIZE = 7; public const int EEPROM_APRS_MYCALL_SSID_STR_DATA_SIZE = 9; public const int EEPROM_APRS_MYCALL_STR_DATA_SIZE = 6; public const int EEPROM_APRS_SSID_STR_DATA_SIZE = 2; public const int EEPROM_APRS_DIGIPATH_DATA_SIZE = 8; public const int EEPROM_APRS_MSG_TEXT_DATA_SIZE = 16; public const int EEPROM_APRS_MSG_SET_DATA_SIZE = 9; public const int EEPROM1_RCV1_OFFSET = 0; public const int EEPROM1_BAND_INDIVIDUAL_BAK_A_OFFSET = 64; public const int EEPROM1_BAND_INDIVIDUAL_BAK_B_OFFSET = 576; public const int EEPROM1_SET_MODE_OFFSET = 1088; public const int EEPROM1_BAND_COMMON_OFFSET = 1472; public const int EEPROM1_BAND_COMMON_BAK_OFFSET = 1536; public const int EEPROM1_ABAND_INDIVIDUAL_OFFSET = 1600; public const int EEPROM1_ABAND_INDIVIDUAL_BAK_OFFSET = 1728; public const int EEPROM1_BBAND_INDIVIDUAL_OFFSET = 1856; public const int EEPROM1_BBAND_INDIVIDUAL_BAK_OFFSET = 1984; public const int EEPROM1_RBAND_INDIVIDUAL_OFFSET = 2112; public const int EEPROM1_RBAND_INDIVIDUAL_BAK_OFFSET = 2240; public const int EEPROM1_DTMF_MEM_OFFSET = 2368; public const int EEPROM1_RCV2_OFFSET = 2624; public const int EEPROM1_WX_MEM_AN_OFFSET = 3648; public const int EEPROM1_BANK_NAME_OFFSET = 3828; public const int EEPROM1_HOME_CH_OFFSET = 4288; public const int EEPROM1_ABAND_VFO_OFFSET = 4672; public const int EEPROM1_BBAND_VFO_OFFSET = 5056; public const int EEPROM1_MEM_BANK_CH_NUM_OFFSET = 5440; public const int EEPROM1_MEM_CH_DIR_OFFSET = 10240; public const int EEPROM1_MEM_CH_NORM_OFFSET = 11584; public const int EEPROM1_MEM_CH_SKIP_OFFSET = 40384; public const int EEPROM1_MEM_CH_RCV_OFFSET = 43552; public const int EEPROM1_MEM_CH_PMS_OFFSET = 43584; public const int EEPROM1_RCV3_OFFSET = 46784; public const int EEPROM1_SPTONE_SQL_OFFSET = 47744; public const int EEPROM1_JR_SQL_OFFSET = 47808; public const int EEPROM1_RCV4_OFFSET = 47872; public const int EEPROM1_APRS_OFFSET = 48832; public const int EEPROM1_GPS_POSI_OFFSET = 49472; public const int EEPROM1_STATUS_TEXT_OFFSET = 49760; public const int EEPROM1_RCV5_OFFSET = 50064; public const int EEPROM1_DIGITAL_OFFSET = 52928; public const int EEPROM1_RCV6_OFFSET = 53312; public const int EEPROM1_RCV7_OFFSET = 57024; public const int EEPROM1_POWER_SW_OFFSET = 65214; public const int EEPROM2_APRS_BEACON_DIR_OFFSET = 65216; public const int EEPROM2_APRS_BEACON_DATA_OFFSET = 67136; public const int EEPROM2_APRS_MESSAGE_DIR_OFFSET = 77696; public const int EEPROM2_APRS_MESSAGE_DATA_OFFSET = 79616; public const int EEPROM2_RCV1_OFFSET = 88256; public const int EEPROM2_GM_OFFSET = 114112; public const int EEPROM2_WIRES_X_OFFSET = 122304; public const int EEPROM2_RCV2_OFFSET = 126400; public const int MEMORY_NORM_DIR_OFFSET = 0; public const int MEMORY_SKIP_DIR_OFFSET = 900; public const int MEMORY_PMS_DIR_OFFSET = 1000; public const int MEMORY_WX_DIR_OFFSET = 1100; public const int MEMORY_JR_SQL_DIR_OFFSET = 1110; public const int MEMORY_INTERNATIONAL_VHF_DIR_OFFSET = 1130; public const int MEMORY_SPTONE_SQL_DIR_OFFSET = 1190; public const int MEMORY_WIRELESS_C_DIR_OFFSET = 1210; public const int MEMORY_EMERGENCY_DIR_OFFSET = 1230; public const int MEMORY_FIRE_DIR_OFFSET = 1250; public const int MEMORY_RCV_DIR_OFFSET = 1336; public const int GROUP_NAME_ORIGINAL_TBL_OFFSET = 160;

2 1

[chirp_users] UV-5R Says "Radio did not respond"
by Richard Dillman 02 Jan '15

02 Jan '15

I'm in a bit of a quandary. I volunteered to program a friend's UV-5R using Chirp, which works a treat with my UV-5RA. However when I try to download from the UV-5R Chirp complains that the radio did not respond. Since all is well with my own UV-5RA I assume the software/driver/cable are not an issue. I'm using Chirp Daily Build 20150102. All guidance will be much appreciated... especially since I promised to deliver the radio tomorrow! Thanks, RD ================================= Richard Dillman, T2-GB-061170 Chief Operator, Coast Station KSM Maritime Radio Historical Society http://www.radiomarine.org =================================

3 3

Re: [chirp_users] UV-5R Says "Radio did not respond"
by Richard Dillman 02 Jan '15

02 Jan '15

>Hi Richard, > >Since the programming cable already works with your radio, the driver >and programming cable must be OK. This means the problem is that you >are not getting the plug fully engaged in the radio. > >Jim KC9HI Hi Jim. You are always quick to respond with helpful advice. Thanks! Yeah, I encountered that plug seating issue with my own UV-5RA so with the UV-5R radio I really put some pressure on the connector - even trimmed the plug. But no joy. So maybe a defective connector on the radio side. Best, RD ================================= Richard Dillman, T2-GB-061170 Chief Operator, Coast Station KSM Maritime Radio Historical Society http://www.radiomarine.org =================================

1 0

[chirp_users] New Daily Build
by Build System 02 Jan '15

02 Jan '15

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-20150102 A list of the changes included in this build (since the last daily) follows: Changes for Build #315 [Marco Filippi <iz3gme.marco(a)gmail.com>] [FT1D] add image file for auto test In support of #967 [Marco Filippi <iz3gme.marco(a)gmail.com>] [FT1D] code cleanup No functional changes at all, only some code cleanup to make code look better and pylint happier In support of #159 [Jim Unroe <rock.unroe(a)gmail.com>] [VV-898] Add Settings to Leixen VV-898 Module - Part 3 Add the following settings: - Custom Display Message 1 - Custom Display Message 2 - System Message (display only) - Backlight - Key Lock Mode - A/B Select related to #2149 [Jim Unroe <rock.unroe(a)gmail.com>] [VV-898] Add Settings to Leixen VV-898 Module - Part 2 Add the following settings: - Monitor - VFO/MR - MR/CHA - Volume - User-Defined related to #2149 [Jim Unroe <rock.unroe(a)gmail.com>] [VV-898] Add Settings to Leixen VV-898 Module - Part 1 Add support infrastructure for radio settings. Add the following settings: - Automatic Power Off - Squelch Level - Scan Mode - Time Out Timer - Step related to #2149

2 1