- Users - lists.chirpmyradio.com

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

31 Jul '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-20160731 A list of the changes included in this build (since the last daily) follows: Changes for Build #419 [Pavel Milanes (CO7WT) <pavelmc(a)gmail.com>] [PATCH][Kenwood Serie 60G] Widen the band limits for some radios, fixes #3813 The OEM software for this radios can program it out of it's default band limits, some of the models has ranges of operations close but outside the ham bands. This patch widen the default band limits for this radios, allowing the programming of these for hamm radio use, some of the new limits are tested by me and others by Stephen GN5SWP, other are just guesses. Changes for Build #420 Changes for Build #421

1 0

[chirp_users] Baofeng x Misuta uv-82plus
by Brian Battison 30 Jul '16

30 Jul '16

Hi, I have just purchased as stated by seller the latest model Baofeng x Misuta uv-82plus, a new crossover version. The firmware version reads N822413 when switched on, and the S/N is uv-82 plus00086. I cannot find any information for programming software for this model and wanted to ask if I just treat it as the using the older uv-82 model information. Thank you. Regards. Brian. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

3 4

[chirp_users] Website maintenance this weekend
by Dan Smith 29 Jul '16

29 Jul '16

Hi all, I need to move the CHIRP website to a new location, and I'm planning to do that this weekend. While it's down I will have a stub of a site up with working current-version download links for anyone that needs it during the transition. However, the main site with the wiki and issue trackers will be unavailable during that time. I apologize for the downtime, but it's the easiest way to do the move. Thanks for your understanding! --Dan

2 1

Re: [chirp_users] FTDI drivers
by kc6iih 27 Jul '16

27 Jul '16

It doesn't pay to be cheap with the cables . I have found thru experience that good cables like those from www.rtsystems are the best . Sent from my Samsung Galaxy Tab®|PRO -------- Original message -------- From: Jim Pruitt <jpruitt67(a)gmail.com> Date:07/26/2016 9:44 PM (GMT-08:00) To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Subject: Re: [chirp_users] FTDI drivers Hello John. What you missed (or I did not make clear) was that when I switched cables to the real FTDI cable (also says Baoefeng) it worked. When I went back to the other cable (FTDI clone) the same GT3 (UR5 definitions) then it said radio was not responding. The only change was the cable itself. It works now but none of the 4 cheap cables that appear to be FTDI clones do not work. That was why I was looking for the old drivers and info as to which drivers worked with the FTDI copies. I also have an XP machine that I have to set up as well and that will be fun. Thank you. Jim Pruitt On Tue, Jul 26, 2016 at 5:21 PM, John LaMartina <JohnLa(a)usa.net> wrote: Jim, I don’t believe your issue is driver related. When you stated Win7 stated the cable was recognized and everything was working, I believe that is correct. The cable and driver are not the issue. The GT3 is more than likely the issue. http://www.miklor.com/COM/UV_ErrorMess.php#error1 Radio did Not Respond is stating the radio isn’t seeing the cable. You may need to trim the cable or the yellow rubber on the case. The lip on the yellow GT3 edge may be preventing some cables to plug in completely. I hope this assists. John Miklor From: chirp_users-bounces(a)intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Jim Pruitt Sent: Tuesday, July 26, 2016 7:19 PM To: Discussion of CHIRP Subject: [chirp_users] FTDI drivers I set up my pc for the latest build of Chirp this past weekend. I ran into trouble as I went out and grabbed the (latest) drivers from FTDI as suggested. When I tried to upload the current list from my GT3's it reported that they were not responding. Windows 7 said the cable was recognized and everything was working. I fought this for several minutes then switched cables. Then it worked so the first cable had to have been a clone even though it had the Baeofeng stamp on it. I see some other posts with new users having trouble and it looks similar to what I was experiencing until I changed cables. This cable cost $21 (Amazon) compared to $3 for the other cables so I am sure others will have the non FTDI cables and not know it. I know that there has been a lot of discussion on here in the past about this. I didn't see a link on FTDI's site to get the older drivers that work with clone cables. Does anyone have that link for the older FTDI drivers that still work with FTDI clone cables? Is there any problem with replacing the new drivers with the older ones? Thank you. Jim Pruitt _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jim at jpruitt67(a)gmail.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

4 5

[chirp_users] FTDi, HT, driver or user issue? Help
by Dennis Yocom, President & CEO 27 Jul '16

27 Jul '16

John et. al.: I'm completely confused now. I bought one PC03 FTDI Authentic <https://www.amazon.com/gp/product/B00HUB0ONK/ref=oh_aui_detailpage_o04_s00? ie=UTF8&psc=1> Genuine USB Programming Cable for BaoFeng, Kenwood, etc from Amazon, which said, Sold by: <https://www.amazon.com/gp/help/seller/at-a-glance.html/ref=oh_aui_sellerpro file_o04_s00?ie=UTF8&isAmazonFulfilled=1&marketplaceSeller=1&orderID=115-982 3267-6753002&seller=AA3MGRC7F9EI2> BaoFeng Tech for $20.46 The cable, which doesn't have any ID on it anywhere (except for a USB symbol and something else near it which I don't recognize) was supposed to be the correct cable to use in programming a pair of new Baofeng F8HPs. With my Windows 7 machine, I got the "Radio did not respond" message about a dozen times. I've pushed that cable in so hard I surprised it didn't come out the other side. I realize I'm not the brightest crayon in the box, but does this sound like a cable issue, HT, user or a driver issue ( I've tried several times to manually install a driver with no luck)? The BaofengTech instructions with the cable indicate the cable was supposed to initiate the proper downloads, and it was supposed to be a snap. Can someone lighten this poor fool? DR Yocom - dryocom(a)comcast.net <javascript:window.top.ZmObjectManager.__doClickObject(document.getElementBy Id(%22OBJ_PREFIX_DWT2282_com_zimbra_email%22));> DR Yocom - Dennis(a)basiclifetraining.com

5 4

[chirp_users] FTDI drivers
by Jim Pruitt 27 Jul '16

27 Jul '16

I set up my pc for the latest build of Chirp this past weekend. I ran into trouble as I went out and grabbed the (latest) drivers from FTDI as suggested. When I tried to upload the current list from my GT3's it reported that they were not responding. Windows 7 said the cable was recognized and everything was working. I fought this for several minutes then switched cables. Then it worked so the first cable had to have been a clone even though it had the Baeofeng stamp on it. I see some other posts with new users having trouble and it looks similar to what I was experiencing until I changed cables. This cable cost $21 (Amazon) compared to $3 for the other cables so I am sure others will have the non FTDI cables and not know it. I know that there has been a lot of discussion on here in the past about this. I didn't see a link on FTDI's site to get the older drivers that work with clone cables. Does anyone have that link for the older FTDI drivers that still work with FTDI clone cables? Is there any problem with replacing the new drivers with the older ones? Thank you. Jim Pruitt

3 3

Re: [chirp_users] FTDI drivers
by awake 26 Jul '16

26 Jul '16

1 0

Re: [chirp_users] Default settings for programming
by Randy McKenzie 25 Jul '16

25 Jul '16

Is there a way to default chirp to settings such as "skip" for scan lists? With the slow scan rates of many of the radios, I only want to scan a few channels, by default it selects scan. Just a thought. Randy On Monday, July 25, 2016 1:37 PM, Randy McKenzie <kk4ej(a)yahoo.com> wrote: Is there a way to default chirp to settings such as "skip" for scan lists? With the slow scan rates of many of the radios, I only want to scan a few channels, by default it selects scan. Just a thought. Randy

2 1

[chirp_users] European characters in Windows user name
by Björn Ekelund 25 Jul '16

25 Jul '16

Chirp crashes/aborts when the Windows user name contains European/Cyrillic characters. The last line of the debug.log file reads: "UnicodeDecodeError: 'utf8' codec can't decode byte 0xf6 in position 9: invalid start byte" Is there a workaround? Like a command like option to set the file location to a location without "strange characters"? Changing the user name to something else isn't really an option since it used for other systems... Björn Ekelund SM7IUN

6 10

Re: [chirp_users] No response from radio, TM-V71 and DR-235, Debian
by guncrafter 25 Jul '16

25 Jul '16

Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Keith Murlless <kmurlless(a)gmail.com> Date:07-25-2016 6:08 AM (GMT-05:00) To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Cc: Subject: Re: [chirp_users] No response from radio, TM-V71 and DR-235, Debian At the risk of offending our highly technical brethren, I'd like to compliment CHIRP for producing an excellent "plug - n-play" version for Mac. Honestly, aside from having to maintain separate files for each Baofeng firmware set, my experience in up/down-loading from Baofeng to Mac, via CHIRP, has truly been just that easy. Good thing too... The frustrations and technical details that you discuss in this thread are beyond me. Good luck with that... I will offer that cable quality has popped up in various threads as a likely culprit in the case of up/down-load fails Keith On Jul 24, 2016 23:56, "CN85rq" <chirp-info(a)aberle.net> wrote: Ken: Thanks for your suggestions. Since both radios are mobiles with serial ports, the PTT isn't an issue. I was testing with both USB-to-serial cables (with chips) and serial-to-serial cables (no chips). The CheckChipVersion appears to be Windoze-only (an OS I haven't had in over a decade), and I don't see an equivalent linux tool. Tom: I appreciate you pointing me in the right direction on breaking the problem in half, and the "ID" command for the TM-V71. I moved over to testing with a 3rd computer, one known to connect with my Kantronics 9612. Using the serial port monitor in Outpost PM and the linux minicom utility I was able to isolate issues, solve part of the problem, and better characterize the remaining difficulties. All: The dual-port MCS9865-based serial card on the Gigabyte GA-MA790X-UD4P motherboard uses /dev/ttyS1 and /dev/ttyS2. The USB-to-serial cable uses /dev/USB0 on both the Gigabyte motherboard and the Raspberry Pi. Both USB-to-serial cables (FTDI and unknown) and the Kenwood PG-5G PC Serial Programming Cable all work. Note to self: In order to make problem isolation easier, clearly mark the three special APC 940-0024C cables so they don't get mixed in with the other serial cables. So, chirp works with the Kenwood TM-V71 using both a straight serial cable and the both USB-to-serial cables. Neither chirp, minicom, nor the serial port monitor in Outpost PM will communicate with the Alinco DR-235 MkIII. In fact, when I put the mini-tester in line on the serial cable, there is no signal (neither a green nor a red LED lit) on the Receive Data line. This is true for all three computers using both cable types. Is a special cable needed for the Alinco DR-235 to work with chirp? Tom Hayward wrote on 07/24/2016 11:19 AM: > > You might try removing Chirp from the equation and test just the > serial port on the TM-V71. First, note the rate set in menu 519, > PC.SPD. Then launch a terminal emulator at this rate. Type ID and hit > enter. You should get the model number of the radio printed to your > console. If not, you've got a problem with your computer/USB serial > port, cable, or the radio's serial port. > > If you do get a response, move on to Chirp. Use only the latest daily > build, available on the PPA or here: > http://trac.chirp.danplanet.com/chirp_daily/LATEST/ > > Tom KD7LXL Ken Cone wrote on 07/24/2016 10:58 AM: > Hello, > In my recent experience programming an Yaesu FT60R, two issues popped up: > 1) finding the correct driver for the cable chipset, and 2) holding the PTT > button long enough. > The chipset driver information was here: > http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41 > > About half way down the page, in red is a link to an app that identified > the Prolific the chipset. Other chipset manufacturers may have similar > tools. > "Run PL2303 CheckChipVersion tool..." This helped tremendously in > identifying the correct driver. > Holding the PTT button long enough came from page 65 of the FT-60R manual, > in the section on Cloning. After resolving these two issues, I was able to > download memory contents to CHiRP, edit, and upload back to the HT. > > Hope this helps. > 73, > Ken > KI7EIH > > > Ken Cone > kencone(a)gmail.com > KI7EIH _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Keith Murlless at kmurlless(a)gmail.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

1 0