- Users - lists.chirpmyradio.com

[chirp_users] B to Y
by djkwasny＠aol.com 10 Aug '16

10 Aug '16

I have nothing in the Yaesu now. When I import a Baofeng the proplem is as explained in my first post. Joe

1 0

[chirp_users] Yaesu FT-8900 Not Accepting File
by Deane Bouvier 09 Aug '16

09 Aug '16

The FT-8900 returns an error message that it doesn't ack block 0 when I try to write to it. That is after a successful read. The USB to serial device is operating properly and Chirp is pointed to the correct Com Port. OS is Windows 7. I have been successful before so this seems to be a new problem. Any help would be appreciated. Thanks. N5DQ

1 0

[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 08 Aug '16

08 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 08 Aug '16

08 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 06 Aug '16

06 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