17 Jan
2019
17 Jan
'19
2:02 p.m.
It's in the DEBUG.LOG file stored somewhere on your hard drive (in the ~/chirp folder on Linux, no idea where in Windows)
On 17 January 2019 at 16:34 "D.J.J. Ring, Jr." n1ea@arrl.net wrote:
How do I get extended debugging info from CHIRP. I finally was able to test my USB cable. My cable is fine. My Wouxun KG-UV8E works fine on Wouxun's Windows software, but does not work on CHIRP, either on Windows 10 or Arch Linux. I went back to the January 2018 daily build of CHIRP and used the module that is for the UV8D Plus kguv8dplus.py and it doesn't work. How can I help with this? Regards, David N1EA _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Nigel A. Gunn, 1865 El Camino Drive, Xenia, OH 45385-1115, USA. tel +1 937 825 5032 Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail nigel@ngunn.net www http://www.ngunn.net