<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>I have 4 ( four ) diffrent rtsystems cables and they all work with CHIRP</div><div><br></div><div><br></div><div><br></div><div>JOCK KC6IIH</div><div>Sent from my Samsung Galaxy Tab®|PRO</div><br><br>-------- Original message --------<br>From: Dan Smith <dsmith@danplanet.com> <br>Date:03/17/2016 7:06 PM (GMT-08:00) <br>To: Discussion of CHIRP <chirp_users@intrepid.danplanet.com> <br>Subject: Re: [chirp_users] BAOFENG UV-5Rs acting strange when programming
with Chirp <br><br>> I have four diffrent cables from Rtsystems and have never had any problems.<br>> I have their cable for the US 5 series and have programmed over 30 of<br>> the Baeofeng for club members and for the local C.E.R.T. and the cable<br>> has NEVER failed me.<br>> Maybe you are doing something wrong while attempting programming. <br><br>The RTSystems cables changed at some point to cater to their newer<br>generation of software. They stopped identifying as generic FTDI devices<br>and getting assigned a COM port in windows (or tty on UNIX) so that the<br>software could identify the cable and be "more automatic". This is, of<br>course, the opposite of what CHIRP people need.<br><br>Just because you have one cable that works well doesn't mean they are a<br>good option for people looking for a new cable.<br><br>I would recommend against them. FTDI cables, yes, but not those.<br><br>--Dan<br>_______________________________________________<br>chirp_users mailing list<br>chirp_users@intrepid.danplanet.com<br>http://intrepid.danplanet.com/mailman/listinfo/chirp_users<br>This message was sent to Jock at kc6iih@aol.com<br>To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com<br></body>