- Users - lists.chirpmyradio.com

[chirp_users] How to save/upload after sorting the CHIRP rows?
by Knight, Dave 23 Mar '16

23 Mar '16

After clicking on a column heading to sort the chirp entries, the new sort order is lost on upload or save. Please advise how I can save/upload sorted rows.

7 22

[chirp_users] Yaesu FTM-100DR
by Don Goodrich 23 Mar '16

23 Mar '16

4 6

[chirp_users] Icom IC92AD
by Wenlock Burton 23 Mar '16

23 Mar '16

Hi Is there any progress on the issue please? Thanks Sent from my iPhone

1 0

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

23 Mar '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-20160323 A list of the changes included in this build (since the last daily) follows: Changes for Build #390 [Dan Smith <dsmith(a)danplanet.com>] Update experimental warning for btech driver #3015 [Dan Smith <dsmith(a)danplanet.com>] Add test images for #3015 >From Jim Unroe [Jim Unroe <rock.unroe(a)gmail.com>] [New Model] Support for the BTECH Mobile Radios, fixes issue #3015 This patch adds "basic support" for the the following radios: BTECH UV-5001, UV-2501 and UV-2501+220 WACCOM MINI-8900 Plus "Basic support" is a complete implementaton of the per-channel settings, including: Speaker mute Scramble Busy channel lockout PTT ID PTT ID signal code Optional signaling also related to #2673

1 0

[chirp_users] R: Re: help
by IW2GJV 22 Mar '16

22 Mar '16

have a NEW radio : POFUNG- BAOFENG BF-F9 version FW : BFP3.25 repeat my questions: a) this FW inside BFP3.25 work well ? have a problems or bug ? b) the new radio have only 144-146 and 430-440 band there is a possibility with CHIRP to expand in rx tha bands like 140-170 and 400-470 mhz ? in how mode with CHIRP ? tnx and 73

2 1

[chirp_users] Windows phone
by Gary Runningbear 21 Mar '16

21 Mar '16

Does anyone know if chirp or the prolific driver will work on a Windows phone?

5 5

[chirp_users] Baofeng UV-82 question
by Stephen Hutter 21 Mar '16

21 Mar '16

I seem to have inadvertently set channel A to receive only. That is, I cannot switchh to it via the A/B button or switch to it via the PTT top. I cannot find ant specific control that performs this function. Does anyone have any thoughts? Steve -- SRH

4 7

[chirp_users] help
by IW2GJV 21 Mar '16

21 Mar '16

POFUNG- BAOFENG BF-F9 version FW : BFP3.25 some questions about this radio : 1) how version i download of CHIRP to this radio with FW version BFP3.25 ? 2) i have a chirp image and CVS of my old UV-5R i can download into this new radio ? thanks 73

5 4

Re: [chirp_users] BAOFENG UV-5Rs acting strange when programming with Chirp
by kc6iih 17 Mar '16

17 Mar '16

I have 4 ( four ) diffrent rtsystems cables and they all work with CHIRP JOCK KC6IIH Sent from my Samsung Galaxy Tab®|PRO -------- Original message -------- From: Dan Smith <dsmith(a)danplanet.com> Date:03/17/2016 7:06 PM (GMT-08:00) To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Subject: Re: [chirp_users] BAOFENG UV-5Rs acting strange when programming with Chirp > I have four diffrent cables from Rtsystems and have never had any problems. > I have their cable for the US 5 series and have programmed over 30 of > the Baeofeng for club members and for the local C.E.R.T. and the cable > has NEVER failed me. > Maybe you are doing something wrong while attempting programming. The RTSystems cables changed at some point to cater to their newer generation of software. They stopped identifying as generic FTDI devices and getting assigned a COM port in windows (or tty on UNIX) so that the software could identify the cable and be "more automatic". This is, of course, the opposite of what CHIRP people need. Just because you have one cable that works well doesn't mean they are a good option for people looking for a new cable. I would recommend against them. FTDI cables, yes, but not those. --Dan _______________________________________________ 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

Re: [chirp_users] BAOFENG UV-5Rs acting strange when programming with Chirp
by kc6iih 17 Mar '16

17 Mar '16

I disagree. I have four diffrent cables from Rtsystems and have never had any problems. I have their cable for the US 5 series and have programmed over 30 of the Baeofeng for club members and for the local C.E.R.T. and the cable has NEVER failed me. Maybe you are doing something wrong while attempting programming. Jock KC6IIH JOCK KC6IIH Sent from my Samsung Galaxy Tab®|PRO -------- Original message -------- From: Fred Maxwell <_chirp(a)mail2fm.com> Date:03/16/2016 11:53 PM (GMT-08:00) To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Subject: Re: [chirp_users] BAOFENG UV-5Rs acting strange when programming with Chirp I disagree with the recommendation for RT Systems cables. They employ FTDI USB to serial TTL chips which have been reprogrammed with non-standard Vendor IDs and Product IDs. Their cables are no better or more reliable than any good quality cable using a standard (non-counterfeit) USB-to-serial chip. They are just a necessary evil in order to use RT Systems software and a poor choice for use with CHIRP. From http://chirp.danplanet.com/projects/chirp/wiki/CableGuide_FTDI_OEM_Cables : Some cable vendors use the FTDI serial chip in their USB radio cables, but have changed the chip's ID codes so that the cable will not be recognized as a generic serial communications port. By default CHIRP (and some other software) will not be able to use these cables because CHIRP needs a serial port. Most notably RT Systems sells such cables. The article at the link shown above goes on to say: [To] use such a cable with CHIRP there are two options. You can either get your computer to recognize the OEM cable as a generic serial port by tweaking the driver setup, or you can change the cable to use the default FTDI codes, so the standard FTDI driver present in most operating systems will recognize the cable and create a standard serial port. The first option may “break” after an OS upgrade and the second option leaves the expensive cable unusable with RT Systems software, which was the whole reason why it cost more in the first place. It’s even uglier under some versions of Windows and OS X; those interested in learning more can read what’s on the official CHIRP website. I spent $6.99 on a cable for my BaoFeng handheld, $8.99 on a cable for my Kenwood TM-281 mobile, and $14.99 on a cable for my Yaesu FT-2900R mobile, all from Amazon with free one or two day shipping. Total spent: $30.97. The first two use Prolific chips and the latter uses an FTDI chip. They have worked flawlessly under OS X and Windows 10, requiring no mucking around with drivers or reprogramming of the chips embedded in the cables. Buying RT Systems cables for those radios would have set me back $113.04 with equivalent 2-day shipping. That’s an $82 difference — and I can think of a lot of ham-related goodies to spend $82 on. 73, Fred Maxwell KM4QLB On Mar 16, 2016, at 11:34 PM, kc6iih via chirp_users <chirp_users(a)intrepid.danplanet.com> wrote: The best and most reliable cables come from www.rtsystems.com Yes they are not cheap but they work every time. Jock A. Soutar KC6IIH Sent via the Samsung Galaxy S™ III, an AT&T 4G LTE smartphone -------- Original message -------- From: John Randle Date:03/16/2016 7:03 PM (GMT-08:00) To: chirp_users(a)intrepid.danplanet.com Subject: Re: [chirp_users] BAOFENG UV-5Rs acting strange when programming with Chirp For what it is worth, I think I have isolated the second problem to a "defective" USB cable. While the "defective"cable requires the older driver (as do my other two "non-defective" cables) and does a download and upload without issues, this is the only cable that then causes the radio to go into transmit after uploading a configuration file ... followed by the normal power off/power on of the radio. Disconnecting the cable immediately after the power off seems to preclude the erroneous transmit indication. The first problem is still a puzzler. While the workaround of resetting the fields is acceptable, I am still curious as to why/how this was suddenly manifested as my UV5Rs are several years old. -- John 73's de K9RSQ On 3/14/2016 11:50 PM, John Randle wrote: > I have been maintaining several UV5R's with Chirp for a couple of > years without any issues. > I am currently running Chirp Daily Build 20151126 on W10 to program > several UV5R's. I have recently experienced two strange programming > operation issues, with all the UV5R's, that I have not previously > encountered. > First problem: After downloading the current configuration of the > UV5R's, I then proceeded to add some new memory channels that use > Digital Coded Squelch settings. > When programming the DCS settings, I first set "DTCS", then I set the > individual T-DCS and R-DCS codes and then I set Cross to "Tone -> > Tone" (as this is what the existing DCS memory channels reflect), but > as soon as I set the offset direction, Chirp changes "DTCS" to "Cross" > and changes "Tone -> Tone" to "DTCS->". As these settings are not what > is required (or at least what is currently reflected in the older DCS > memory channels), I then have to go back and reset "DTCS->" to "Tone > -> Tone" and "Cross" to "DTCS". Is there any reason why my initial > inputs are being over-ridden? > Second problem: After successfully uploading a new configuration to > the UV5-R's, the UV5R's automatically go into transmit mode about 5 > seconds after they restart if the programming cable is left connected > to the radio. This seems to be a new issue that I had not previously > experienced. > Any suggestions on either problem will be greatly appreciated. > -- > John > 73's de K9RSQ > _______________________________________________ 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 _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Fred at _chirp(a)mail2fm.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

3 2