- Users - lists.chirpmyradio.com

[chirp_users] ft 2800m
by Richard 09 Aug '16

09 Aug '16

radio keeps coming up failed to read header cable and everything works on my ft 1802 so cant be setup is their a bug or something wrong with the program it never did work for this radio fine with all my others thanks --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

2 1

[chirp_users] Baofeng UV-6R
by stephen johnston 09 Aug '16

09 Aug '16

i know this radio is not supported yet, i have some info to help driver writers. the "magic string" is: "\x50\xBB\xFF\x20\x14\x11\x22" and the firmware is: ["HDBF230"] i have put these into the driver, but i am now stuck with this: -------------------------- [2016-08-08 14:12:07,872] chirp.ui.mainapp - DEBUG: User selected Baofeng UV-6R on port /dev/ttyUSB0 [2016-08-08 14:12:07,912] chirp.ui.clone - DEBUG: Clone thread started [2016-08-08 14:12:07,916] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 20 14 11 22 00 P.....". [2016-08-08 14:12:09,045] chirp.drivers.uv5r - INFO: Ident: 000: aa 36 74 04 00 05 20 dd .6t..... [2016-08-08 14:12:09,296] chirp.ui.reporting - INFO: Reporting disabled [2016-08-08 14:12:09,297] chirp.ui.reporting - DEBUG: Reporting is disabled [2016-08-08 14:12:09,297] chirp.ui.common - ERROR: -- Exception: -- [2016-08-08 14:12:09,297] chirp.ui.common - ERROR: Traceback (most recent call last): File "/home/user/Downloads/radio/chirp/chirp-daily-20160802/chirp/ui/clone.py", line 249, in run self.__radio.sync_in() File "/home/user/Downloads/radio/chirp/chirp-daily-20160802/chirp/drivers/uv5r.py", line 675, in sync_in self._mmap = _do_download(self) File "/home/user/Downloads/radio/chirp/chirp-daily-20160802/chirp/drivers/uv5r.py", line 491, in _do_download radio_version = _get_radio_firmware_version(radio) File "/home/user/Downloads/radio/chirp/chirp-daily-20160802/chirp/drivers/uv5r.py", line 467, in _get_radio_firmware_version block2 = _read_block(radio, 0x1F00, 0x40, False) File "/home/user/Downloads/radio/chirp/chirp-daily-20160802/chirp/drivers/uv5r.py", line 436, in _read_block "Radio refused to send second block 0x%04x" % start) RadioError: Radio refused to send second block 0x1f00 --------------------------- does anybody have any idea's what to try next? i dont know python and cant really follow the code in the driver anyway! -- stephen johnston

2 1

[chirp_users] Introduction & Question
by Richard B. Emerson 09 Aug '16

09 Aug '16

Hello - I'm new to 2m and just started groping my way into what I need to know. I've held a General ticket for a couple of years. However, my main interest is PACTOR comms via Winlink while aboard our sailboat (/MM or /C6A). We've been to the Bahamas few times; having Winlink to back up other options is great. I inherited a Baofeng UV-5RE Plus from a friend, sadly SK. At this point I'm able to program the radio, etc. My biggest concern is a way to organize the entries. That is, being NW of Philadelphia, I want the 2m repeaters for the counties/areas I'm most likely to be in. So far, so good. Repeater Book is my friend. But! Is there some way to tag a cluster of calls with at least the country name in some form? I guess I could add a two letter code to the back of each call, but if I'm missing a useful option...? 73 de KC3DOO Rick Emerson

6 8

Re: [chirp_users] Introduction & Question
by NP3AR 09 Aug '16

09 Aug '16

My two cents. I use on my Baofeng HT this way: first three characters are the last digit in mhz followed by the khz digits and then the first 3 letters of the location. Sent from my Samsung Galaxy Tab®4 -------- Original message -------- From: "Richard B. Emerson" <pavilion(a)pinefields.com> Date:08/08/2016 7:05 PM (GMT-04:00) To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Subject: Re: [chirp_users] Introduction & Question I guess being a newbie is showing, huh. I figured that seeing the call beats the location. OTOH, if I do make an initial call, it's my call (KC3DOO listening) or whoever I'm talking with, not the repeater's call. Hmmm... gotta think about that. At least CHIRP makes it much easier to enter settings. If ever there was a manual designed to confuse and obfuscate, the UV-5etc. manual is it. 73 de KC3DOO PS If anyone is interested in operating in the Bahamas, there's no reciprocity. The "license" application process isn't that hard. The woman who handles the applications very helpful. Drop me a note and I can fill in the details. I assume there are no repeaters, except maybe on New Providence (the island Nassau's on). Otherwise, it's operating simplex. _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to joe at np3ar(a)gmx.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

5 4

[chirp_users] AUTO: Adam K Collins is out of the office. (returning 08/15/2016)
by Adam_K_Collins＠graco.com 08 Aug '16

08 Aug '16

I am out of the office until 08/15/2016. I will respond to your message when I return. thanks! Note: This is an automated response to your message "Re: [chirp_users] Kenwood TK-762H" sent on 08/08/2016 10:35:43. This is the only notification you will receive while this person is away.

1 0

[chirp_users] FT-8900 will not upload
by R Datus 07 Aug '16

07 Aug '16

Yaesu FT-8900 will download to CHIRP, but will not upload. I get "an error has occurred radio did not ack block at (various numbers, e.g., 520, 584, 9854)" Please help me find a solution to using Chirp to program the FT-8900 that my wife worked extra hours to give me for HER birthday. HRO wants another $40 for programming software. Please help. KD0RLZ@ yahoo.com

2 1

[chirp_users] USB LiveBoot ?
by Bruce LeGrande 07 Aug '16

07 Aug '16

Just looked at the LiveCD image file for Chirp and woah!, that seems MUCH larger than it needs to be... (600+Mb) I'm interested in setting up a bootable USB stick with an autorun Chirp session for programming my Baofeng UV-82HP. I'm getting the 'Unsupported firmware version: "N82-33 US2S35 /Uffffffff/Uffffffff" with Chirp v0.4.0 The hardware is an ACER AspireOne NetBook (AMD64). It would seem that this project SHOULD fit on a 1-Gb USB Stick with plenty of room to spare to store radio programming data. Anyone have an ISO for this... I'm getting Puppy Linux and DSLinux Live boot ISO's right now in case I have to use an IMG burn file of Chirp. PuppyLinux ISO is only 225Mb, and I think DamnSmallLinux is even smaller. And on a second note... Is anyone working on an Android App port of Chirp ? Sure would be nice to prgm the radios with a SmartPhone or Tablet... Of course, that would require a cable with a MicroUSB connector. 73 4 now Bruce Sent from BlueMail

11 27

[chirp_users] Baofeng UV6S83
by Marcus van Dam 06 Aug '16

06 Aug '16

Hi, I recently bought a Baofeng UV-6 at the 409shop, which I all exited hooked up and figured out that it gave the dreaded 'Radio did not respond' and 'Refused to clone' messages. After some digging and comparing to the Baofeng windows tool (UV6UV7_CPS) I found the following; When you try to read the radio with Chirp, the magic is send (50 bb ff 20 12 08 23 00), the ACK is received, 0x02 is send, and from here, Chirp seems to expect 8 bytes of data as ident (ident = serial.read(8)), but looking at the serial traffic of the BF software, the radio sends 12 bytes (AA 01 01 36 01 74 01 04 00 05 20 DD). As Chirp only read 8, the next write and read will not return the expected results and the clone fails. I tried to increase that initial ident read size in Chirp to 12 bytes (ident = serial.read(12)), which got me to the "Incorrect 'Model' selected" error, saying in the debug, that the model is actually ' Ver UV6S83 '. In a desperate attempt I added "UV6S83" to the array "BASETYPE_UV6", which allowed Chirp to read the data, but in the end it could not make sense of the content. This is where my debug skills ended and I hope your expertise comes in. I have attached a couple of captures to this email; UV6S83-CHIRP_8bytes-ident.txt = Chirp, all default trying to read the UV-6 UV6S83-CHIRP_12bytes-ident.txt = Chirp, modified the ident length and added the basetype as an UV-6 UV6S83-UV6UV7.txt = Original Baofeng software doing a full dump. The modified Chirp dump contains an interesting snippet in the first memory block: BAOFENG UV-5R .. Ver UV6S83 Would the have build a Frankenstein device? Let me know if there is anything I can do to help debugging. // Marcus

3 4

[chirp_users] FT-8900 will not upload from Chirp
by R Datus 06 Aug '16

06 Aug '16

Yaesu FT-8900 will download to CHIRP, but will not upload. I get "an error has occurred radio did not ack block at (various numbers, e.g., 520, 584, 9854)" Please help me find a solution to using Chirp to program the FT-8900 that my wife worked extra hours to give me for HER birthday. HRO wants another $40 for programming software. Please help. KD0RLZ@ yahoo.com

1 0

[chirp_users] UV-82, Ubuntu 16.04 LTS, can't connect...
by David McGuire 06 Aug '16

06 Aug '16

Hello. I need some help with getting my UV-82 to talk with my laptop. I'm using Ubuntu 16.04 LTS and Chirp. It had been working prior to the upgrade to 16.04. Don't know what happened. Here is the message I receive: Failed to communicate with radio: 'Serial' object has no attribute 'setTimeout'. Here are my settings for the radio: - Port: /dev/ttyUSB0 - Vendor: Baofeng - Model: UV-82 I am using a genuine Baofeng USB cable. This was working very nicely, so I am sure it is a setting someplace. Any help is appreciated. 73 de David AE4LH

4 6

Re: [chirp_users] UV-82, Ubuntu 16.04 LTS, can't connect...
by Angus Ainslie 06 Aug '16

06 Aug '16

On 2016-08-06 07:30, David McGuire wrote: > python --version > > Python 2.7.12 > > ------------------------- > That should work. Check the pyserial version apt-cache policy python-serial > FROM: Angus Ainslie <angus(a)akkea.ca> > SENT: Saturday, August 6, 2016 8:28 AM > TO: Discussion of CHIRP > CC: David Buss; David McGuire > SUBJECT: Re: [chirp_users] UV-82, Ubuntu 16.04 LTS, can't connect... > > It shouldn't be a driver problem with Ubuntu. > > That message sounds more like a python version or pyserial version > problem. > > What do you get from > > python --version > > On 2016-08-06 07:13, David Buss wrote: >> Double check your cable driver. "Genuine Baofeng" is still a > prolific >> clone. Will need to be driver version 3.2.2.0 [1] >> >> -----Original Message----- >> From: David McGuire <leviticus25_9(a)hotmail.com> >> To: "chirp_users(a)intrepid.danplanet.com" >> <chirp_users(a)intrepid.danplanet.com> >> Sent: Sat, 06 Aug 2016 8:07 >> Subject: [chirp_users] UV-82, Ubuntu 16.04 LTS, can't connect... >> >> Hello. I need some help with getting my UV-82 to talk with my > laptop. >> I'm using Ubuntu 16.04 LTS and Chirp. >> >> It had been working prior to the upgrade to 16.04. Don't know what >> happened. >> >> Here is the message I receive: Failed to communicate with radio: >> 'Serial' object has no attribute 'setTimeout'. >> >> Here are my settings for the radio: >> >> - Port: /dev/ttyUSB0 >> >> - Vendor: Baofeng >> >> - Model: UV-82 >> >> I am using a genuine Baofeng USB cable. >> >> This was working very nicely, so I am sure it is a setting > someplace. >> >> >> Any help is appreciated. >> >> 73 de David AE4LH >> >> >> >> Links: >> ------ >> [1] http://3.2.2.0 >> >> _______________________________________________ >> chirp_users mailing list >> chirp_users(a)intrepid.danplanet.com >> http://intrepid.danplanet.com/mailman/listinfo/chirp_users >> This message was sent to Angus Ainslie at angus(a)akkea.ca >> To unsubscribe, send an email to >> chirp_users-unsubscribe(a)intrepid.danplanet.com

1 0

[chirp_users] Programming for
by Stan M 02 Aug '16

02 Aug '16

Anysecu TM 218?

2 1

[chirp_users] New Daily Build
by Build System 02 Aug '16

02 Aug '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-20160802 A list of the changes included in this build (since the last daily) follows: Changes for Build #422 [Jim Unroe <rock.unroe(a)gmail.com>] [Luiton] Add Support for the Luiton LT-898UV Mobile Radio The LT-898UV mobile radio can be programmed using the Leixen VV-898 vendor/model selection. This pattach adds a LUITON LT-898UV vendor/model selection using the newly added (chirp_common.Alias) support. fixes #3705

1 0

[chirp_users] Is there a radio programming for dummies?
by Nigel A. Gunn G8IFF/W8IFF 01 Aug '16

01 Aug '16

Drop in and see me sometime and I'll sit down with you and explain. > Date: Mon, 1 Aug 2016 13:38:59 -0500 > From: "David Kimball" <david(a)lazycreek.com> > Subject: [chirp_users] Is there a radio programming for dummies? > To: <chirp_users(a)intrepid.danplanet.com> > Message-ID: <000f01d1ec23$f8346990$e89d3cb0$(a)lazycreek.com> > Content-Type: text/plain; charset="us-ascii" > > So, > > > > Very very new and was trying to program a new Baofebg GT-5TP. > > > > Found a radio in the drop down that appears to work on this model, UV-82HP. > > > > How do you remove a entry from the loc. I want to delete the information on > an entry. > > > > If I type 0.000 I get an error message. A blank also gives the same error. > > > > Dave

2 1

[chirp_users] Is there a radio programming for dummies?
by David Kimball 01 Aug '16

01 Aug '16

So, Very very new and was trying to program a new Baofebg GT-5TP. Found a radio in the drop down that appears to work on this model, UV-82HP. How do you remove a entry from the loc. I want to delete the information on an entry. If I type 0.000 I get an error message. A blank also gives the same error. Dave

2 2

[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 28 Jul '16

28 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 27 Jul '16

27 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