- Users - lists.chirpmyradio.com

Re: [chirp_users] Thanks
by lasomrak 31 Aug '16

31 Aug '16

How did you find the correct port. I went through 1-9 with no luck. KK4RCC -------- Original message -------- From: Dick Smith <w4rss(a)radioclub.org> Date: 08/29/2016 5:50 PM (GMT-05:00) To: Discussion of CHIRP <chirp_users(a)intrepid.danplanet.com> Subject: [chirp_users] Thanks Back on August 23, I had posted regarding a problem with a Valley Enterprises cable. I neglected to let all of you know how much I appreciated your replies. Evidently it was a com port issue and after making sure it was seeing the right com port, everything worked as advertised. Thanks to all of you who had responded. 73 Dick W4RSS _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to larry at lasomrak(a)bellsouth.net To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

2 1

[chirp_users] D-Star Programming
by Dick Smith 30 Aug '16

30 Aug '16

I have an ID-880H and want to program some D-star repeaters. I've down the registration and have been okayed. I've read so many different posts about programming and watched so many videos, that I'm more or less completely confused about the operation. I downloaded what I have currently in the radio and noticed that in Chirp there seem to be fewer spots to put the D-star info. I feel like what is shown is all that's needed, but I want to make sure first. I do have the original programming I did with the Icom software saved so I can reload it if necessary. I've also looked through the last 6-8 months of list archives and didn't find anything that was to helpful regarding the programming aspect. Any 880H users who might be able to shed some light on the whole subject for me? 73 Dick W4RSS

3 3

[chirp_users] FTDI good - not FTDI bad
by Richard B. Emerson 29 Aug '16

29 Aug '16

Following the traffic here, I think the following should be (if it isn't) a FAQ item. Nonetheless it bears repeating here: FTDI conversion chips and drivers are extremely stable. Anything else, including Prolific, is a gamble with poor odds. It's that simple. Background: On our sailboat, I do a number of serial/USB conversions. This converts (admittedly ancient) NMEA 183 serial data from instrumentation for a USB port on a laptop running a navigation program (Coastal Explorer - don't leave port without it). Initially I used Prolific-based convertes (what did I know?). Simply put, it became one non-stop headache. Data wouldn't come through, drivers stopped functioning, etc., etc. I switched to an FTDI-based 10-port serial/USB converter. The only changes to the system was to plug the DB-9 pigtails into the new converter and load the FTDI driver. End of problems, no crashes, full functionality. To clarify, one port services the full NMEA 183 data stream from the autopilot computer (speed through the water, depth, wind direction and speed, full GPS data stream [position, speed over the bottom, direction, GPS status, time of day)) and the port sends steering information to the autopilot, waypoint location data, and more. Another port sends data to the VHF and SSB radios (position, time of day) and receives data from the VHF (Digital Selective Calling data including emergency data received). Another port sends position, time of day, waypoint location data and receives target data from the radar including Modified Automatic Radar Plotting Aid data. The last active port receives data from the Automatic Identification System and an auxiliary GPS receiver (part of the AIS system). (full translation of "NMEA 183", "waypoint", etc. available off-list) This is a long and probably very boring summary of what goes through FTDI devices at a mix of data rates (4800 baud for all but the AIS, which works at 38400 baud). If the FTDI part fails, life gets ugly fast (yes, there are backups). I bet a lot on FTDI and have no cause to regret it. Prolific devices were... my wife wore earplugs when the converters failed. Again, FTDI good - not FTDI bad. 73 de KC3DOO Rick

9 11

[chirp_users] Thanks
by Dick Smith 29 Aug '16

29 Aug '16

Back on August 23, I had posted regarding a problem with a Valley Enterprises cable. I neglected to let all of you know how much I appreciated your replies. Evidently it was a com port issue and after making sure it was seeing the right com port, everything worked as advertised. Thanks to all of you who had responded. 73 Dick W4RSS

1 0

[chirp_users] Downloading
by lasomrak 29 Aug '16

29 Aug '16

Trying to download from UV82 radio to chirp but computer or chirp won't recognize a port screen shows error 2,any suggestions. Thanks.

3 2

[chirp_users] Baofeng UV5R hack
by Glenn 28 Aug '16

28 Aug '16

I have been reading on-line that Chirp will open up my Baofeng for listening to frequencies outside the current bands. Is this true? And if so, How do I do this? Thanks Glenn

5 11

[chirp_users] Yes Btech
by Paul Harris 28 Aug '16

28 Aug '16

Use the right name and it works like a charm. Used BTECH instead of Bao. and programed in seconds all my local repeaters. Thank you .Paul KB2VEC

1 0

[chirp_users] Baojie bj-218 programming?
by Ivano 28 Aug '16

28 Aug '16

Anyone use Chirp for programming the BJ-218 (or TM-218, same thing).? Thanks for any info Ivano i4ifl

1 0

[chirp_users] Radio did not respond error
by Paul Harris 27 Aug '16

27 Aug '16

Baofeng UV-5X3Cable PCO3 Had to get drivers to get to this stage but radio does not respond. Do the red and green lights on cable usb end have to remain on or just flash on when you plug in. Computers is a HP windows 7.Paul KB2VEC

6 6

[chirp_users] UV-5x3
by Robert Stelmock 27 Aug '16

27 Aug '16

I can chirp download with my uv5r and Uv82x but I can not get the uv-5x3 to download... Same comuter program and cable....but the uv5x3 will not work,any ideas? Robert Stelmock bobdotfla(a)verizon.net

2 2