Before sending the downloaded bug I thought I’d take a look at it and the comms 
were shutting down because the radio reported itself as a TM-271, when I 
changed the model to 271 it downloads just fine. This is bizarre as the radio 
is badged as a TM281 !



73 from
John W Holmes
K4VMG
G4VMG

________________________________
From: [email protected] 
<[email protected]> on behalf of Tony Fuller 
<[email protected]>
Sent: Monday, March 16, 2020 12:07:17 PM
To: Discussion of CHIRP <[email protected]>
Subject: Re: [chirp_users] Struggling to get download or upload from TM281

It sounds like the drive may have encountered a setting it didn't know how to 
handle. Can you create a debug log file and attach it to a new issue on the bug 
tracker?

Also how new/recent is the radio? We've seen firmware changes break the driver 
in unexpected ways (such as showing blank dialog windows and such)

https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues

http://chirp.danplanet.com/projects/chirp/issues/new

Tony
________________________________
From: [email protected] 
<[email protected]> on behalf of John Holmes 
<[email protected]>
Sent: Monday, March 16, 2020 11:42:50 AM
To: [email protected] <[email protected]>
Subject: [chirp_users] Struggling to get download or upload from TM281


I have the following set up



Kenwood TM281

Windows 10 updated 24hrs ago and latest version of chirp 20200227

FTDI lead from Bluemax49ers diver 2.12.28



I connect via the COM port shows as 7 which is fine and comms setting 9600,8 
bits,Parity none, Stop bits 1 Flow Control None



When I click on OK nothing happens the screen returns to the blank chirp page, 
no memories downloaded and the upload option is greyed out.



Any help appreciated.



73 from

John W Holmes

K4VMG
G4VMG


_______________________________________________
chirp_users mailing list
[email protected]
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to [email protected] at [email protected]
To unsubscribe, send an email to [email protected]

Reply via email to