Jens,
I can confirm that the 2013-10-27 build WORKS, while the 2013-10-31 build does not.
Basil
On Thu, Jan 30, 2014 at 4:42 PM, Jens J. kd4tjx@yahoo.com wrote:
Looks like my change was committed ~ 2013-10-31. Can you verify that 2013-10-27 build works or does not work for you? http://trac.chirp.danplanet.com/chirp_daily/daily-20131027/
-Jens
*From:* Jens J. kd4tjx@yahoo.com
*To:* Discussion of CHIRP chirp_users@intrepid.danplanet.com *Sent:* Thursday, January 30, 2014 4:28 PM
*Subject:* Re: [chirp_users] yaesu 897
FWIW, I made a global change that moved the opening of the com port for upload operation to _before_ the clone message is displayed. This was done because in my testing with FT-90, it worked fine on linux, but radio would not go into clone mode on windows xp. I suspect it had something to do with port lines (DTR/CTS, etc) or with my homebrew cable, but whatever it was, opening the port before displaying the clone instructions worked for me across platforms, and so far have not heard any other negative side-effects.
http://chirp.danplanet.com/issues/1187#note-6
http://chirp.danplanet.com/projects/chirp/repository/diff/chirpui/mainapp.py...
I make this comment only in the off chance that it is somehow related to the issue being described here.
-Jens
*From:* Marco IZ3GME iz3gme.marco@gmail.com *To:* Discussion of CHIRP chirp_users@intrepid.danplanet.com *Sent:* Thursday, January 30, 2014 1:04 PM *Subject:* Re: [chirp_users] yaesu 897
I tested right now with development branch and can confirm it works like a charm. But ... you know I'm on linux, is there some one that can try with windows?
Tom, do we have something different in the build environment since the last working version?
Basil, I'm quite sure is not a cable issue as we do the same echo check on the cable during radio download, if it works in download I don't see a reason for it to refuse to work for upload. ...mmm... can you try with linux? May be with live CD if you don't have a linux machine, see http://chirp.danplanet.com/projects/chirp/wiki/Download#Live-CD
If we don't rule this out before, I'll try myself on a windows machine next week.
73 de IZ3GME Marco
On 01/30/2014 07:00 PM, Tom Hayward wrote:
On Thu, Jan 30, 2014 at 9:18 AM, Basil Copeland blcjr2@gmail.com
wrote:
I found the source code. Thanks.
Well, I can understand why a code readability update shouldn't matter.
But
before dismissing the matter, shouldn't someone try to replicate my
problem,
i.e. actually try to program an FT-60 or an FT-8800 with the builds I reported problems with? If they do, and it works for them, then I would think that narrows it to a cable issue, and we should look at what
cables
are being used successfully, versus what I'm using unsuccessfully.
While I
will not rule out a cable issue per se, I have to be jaundiced about
blaming
it on the cable since I have successfully used the FT-60 cable (FTDI)
with
the Commander software. I purchased an FTDI cable at the same time as
the
other two, for a VX-7, but haven't tried to program it yet. I think
I'll
try to get around to it today, and see if there are related issues.
Basil KE5GAE
Firstly, let's handle these two radios separately. I can only test one at a time.
I don't have a FT-8800 I can borrow for testing.
The last time I borrowed an FT-60 for testing was 2013-12-18 and Chirp was working fine then: http://chirp.danplanet.com/issues/1273
Tom KD7LXL _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users