<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body >Antoon....welcome to the hobby! Hope you get your 857 going. Nice radio. Post back and let us know how it goes.<div><br></div><div>73 </div><div>Brady</div><div>K0UC</div><div><br></div><div>Using CHIRP on so many rigs I can't enumerate...</div><br><br><br>-------- Original message --------<br>From: chirp_users-request@intrepid.danplanet.com <br>Date: 10/04/2013 2:00 PM (GMT-06:00) <br>To: chirp_users@intrepid.danplanet.com <br>Subject: chirp_users Digest, Vol 58, Issue 5 <br> <br><br>Send chirp_users mailing list submissions to<br> chirp_users@intrepid.danplanet.com<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> http://intrepid.danplanet.com/mailman/listinfo/chirp_users<br>or, via email, send a message with subject or body 'help' to<br> chirp_users-request@intrepid.danplanet.com<br><br>You can reach the person managing the list at<br> chirp_users-owner@intrepid.danplanet.com<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of chirp_users digest..."<br><br><br>Today's Topics:<br><br> 1. CHIRP and the Yaesu FT-857D (Antoon Rubbens)<br> 2. Re: CHIRP and the Yaesu FT-857D (IZ3GME Marco)<br> 3. puxing px-777 anomalies (eric oyen)<br> 4. Re: puxing px-777 anomalies (Tom Hayward)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Fri, 4 Oct 2013 10:20:57 +0200<br>From: Antoon Rubbens <antoonr@gmail.com><br>Subject: [chirp_users] CHIRP and the Yaesu FT-857D<br>To: chirp_users@intrepid.danplanet.com<br>Message-ID:<br> <CADRhFpDfxRP2hWSqTi5fA=iEW+Zr1t3=VobNXhRLL2jWaze=kA@mail.gmail.com><br>Content-Type: text/plain; charset="iso-8859-1"<br><br>This question must have been asked a million times already, but as I'm a<br>new HAM in the Netherlands (since last Monday), I ask it one more time.<br><br>I have a Yaesu FT-857D (US model) and a cheap Chinese USB cable that I<br>bought from Ebay.<br>I have insalled HamRadioDeluxe and this program can communicate with the<br>radio over COM3. The cable is recognized as USB-SERIAL CH340 (COM3) in<br>Win7.<br><br>Now I installed CHIRP and I get the error 'Failed to communicate with<br>radio: Unable to read block 00 expected 4 got 0'<br><br>I searched the internet and found some hints:<br>- Press the send button on the radio after clicking OK in CHIRP (I wondered<br>what is 'the send button'? This radio has a million buttons)<br>- Press the A button under the screen after cliking OK in CHIRP (the A<br>button has manny functions on the 857, so which menu should be selected)<br>- Set the CAT speed to 9600bps (did that)<br><br>So basically the question is which menu I should select before pressing the<br>A button. Or a step by step for the FT-857D is also welcome.<br><br>Thanks for your help!<br>Antoon (PA2AR).<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20131004/7e5ea86c/attachment-0001.html <br><br>------------------------------<br><br>Message: 2<br>Date: Fri, 04 Oct 2013 10:53:59 +0200<br>From: IZ3GME Marco <iz3gme.marco@gmail.com><br>Subject: Re: [chirp_users] CHIRP and the Yaesu FT-857D<br>To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>Message-ID: <524E8227.1020803@gmail.com><br>Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br><br>Hi Antoon<br>the correct operation sequence to download from ft857 is:<br>- switch on the radio while pressing both <- > buttons to push it to <br>clone mode<br>- prepare chirp for download selecting menu Radio - download from radio <br>and setting the com port and radio type then press OK<br>- start send on the radio pressing C button<br>download (should) then start immediately and both radio and chirp show <br>the operation via a progress bar.<br><br>For upload the sequence is:<br>- switch on the radio while pressing both <- > buttons to push it to <br>clone mode<br>- prepare chirp for upload selecting menu Radio - Upload to radio and <br>setting the com port (do not press Ok yet)<br>- start receive on the radio pressing A button<br>- press Ok in chirp dialog to start upload<br><br>You can find some info on the clone procedure at the end of ft857 <br>manual, chirp simulate the second radio: the receiving one when you <br>download and the transmitting one when you upload.<br><br>I also must destroy the myth that the CAT speed have to be set in any <br>way: in clone the ft857 the serial communication always take place at <br>9600 and there's no menu that can influence the protocol in any way.<br><br>73 de IZ3GME Marco<br><br>On 04/10/2013 10:20, Antoon Rubbens wrote:<br>> This question must have been asked a million times already, but as I'm a<br>> new HAM in the Netherlands (since last Monday), I ask it one more time.<br>><br>> I have a Yaesu FT-857D (US model) and a cheap Chinese USB cable that I<br>> bought from Ebay.<br>> I have insalled HamRadioDeluxe and this program can communicate with the<br>> radio over COM3. The cable is recognized as USB-SERIAL CH340 (COM3) in<br>> Win7.<br>><br>> Now I installed CHIRP and I get the error 'Failed to communicate with<br>> radio: Unable to read block 00 expected 4 got 0'<br>><br>> I searched the internet and found some hints:<br>> - Press the send button on the radio after clicking OK in CHIRP (I<br>> wondered what is 'the send button'? This radio has a million buttons)<br>> - Press the A button under the screen after cliking OK in CHIRP (the A<br>> button has manny functions on the 857, so which menu should be selected)<br>> - Set the CAT speed to 9600bps (did that)<br>><br>> So basically the question is which menu I should select before pressing<br>> the A button. Or a step by step for the FT-857D is also welcome.<br>><br>> Thanks for your help!<br>> Antoon (PA2AR).<br>><br>><br>> _______________________________________________<br>> chirp_users mailing list<br>> chirp_users@intrepid.danplanet.com<br>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users<br>><br><br><br><br>------------------------------<br><br>Message: 3<br>Date: Fri, 4 Oct 2013 01:58:20 -0700<br>From: eric oyen <eric.oyen@gmail.com><br>Subject: [chirp_users] puxing px-777 anomalies<br>To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>Message-ID: <A000CAF5-FBEE-4305-A3B3-D05710B06F0D@gmail.com><br>Content-Type: text/plain; charset=us-ascii<br><br>hello there,<br><br>ok, I have tried both the stable release version that came with ubuntu 13.04 and the daily build produced yesterday.<br><br>both aren't reading my radio correctly.<br><br>on the stable release, only every 3rd memory location (frequency) is visible. On the development version, it shows values that are supposed to be in other fields (such as PL tone being in the frequency field, etc.).<br><br>unfortunately, I can't seem to make sense of how its arranged (I use a screen reader here as I am blind) and even in Braille, it displays much the same.<br><br>I need to be able to program this radio for some public service events and I can't do so in either OS X or windows (using the windows binaries provided by the manufacturer is equally as useless under jaws). Chirp there just displays a blank application screen. Under OS x, it displays some of the information, but none of the memory channels or other fields in that table.<br><br>I really would like to be able to use this package, but it seems to be beyond my reach right now. Also, as I am not a coder (my skills are in systems administration, security and database management), I can't just go in and change how the thing operates.<br><br>lastly, I don't have any method by which I can capture a screen output on the linux machine to show what is going on. I also don't have a lot of money to spare (as I live on disability), so sending a radio to be tested for development is out of my reach (and I only have the one radio).<br><br>Now, considering that I am a ham and also blind, I am really in a very small population group. Still, I would consider it a great favor if someone *(anyone) would help to make this project more accessible for those like me (there are several thousand blind hams in the US alone). Now I have tried getting hold of the manufacturer in china, only to be completely ignored (I have 2 strikes against me already: 1. I am american, 2. I am blind). so, how about it? anyone up to the challenge?<br><br>-eric<br><br><br><br>------------------------------<br><br>Message: 4<br>Date: Fri, 4 Oct 2013 09:48:07 -0700<br>From: Tom Hayward <esarfl@gmail.com><br>Subject: Re: [chirp_users] puxing px-777 anomalies<br>To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com><br>Message-ID:<br> <CAFXO5Z1WVAYHkD-KmpZm+d042xvKUwxEDdgnUkw=NmpWtKhmyg@mail.gmail.com><br>Content-Type: text/plain; charset=UTF-8<br><br>On Fri, Oct 4, 2013 at 1:58 AM, eric oyen <eric.oyen@gmail.com> wrote:<br>> hello there,<br>><br>> ok, I have tried both the stable release version that came with ubuntu 13.04 and the daily build produced yesterday.<br>><br>> both aren't reading my radio correctly.<br>><br>> on the stable release, only every 3rd memory location (frequency) is visible. On the development version, it shows values that are supposed to be in other fields (such as PL tone being in the frequency field, etc.).<br><br>Eric,<br><br>Send me the .img file you downloaded from the radio. I'll see if I can<br>figure out what's going on.<br><br>I have access to a PX-777 and it works perfectly with Chirp.<br><br>Tom KD7LXL<br><br><br>------------------------------<br><br>_______________________________________________<br>chirp_users mailing list<br>chirp_users@intrepid.danplanet.com<br>http://intrepid.danplanet.com/mailman/listinfo/chirp_users<br><br><br>End of chirp_users Digest, Vol 58, Issue 5<br>******************************************<br></body>