Project

General

Profile

Actions

Feature #1163

closed

Simple instructions for setting rig for communication

Added by Predrag Supurovic about 9 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
10/08/2013
Due date:
% Done:

90%

Estimated time:
Chirp Version:
daily
Model affected:
(All models)

Description

Some rigs do have quite cumbersome procedure to turn cloning on which are hard to remember especially if not frequently used.

It would be very useful if user can get simple textual instructions how to set up rig to send or receive data with Chirp.

Instructions may show up when user starts option for download or upload data.


Related issues

Related to Bug #1319: Yeasu FT-8900 Vs. CHIRP is not workingRejected12/27/2013

Actions
Actions #1

Updated by Filippi Marco about 9 years ago

  • Status changed from New to In Progress

I started implementing this for some of the radios and I already sent a few patches to developers list.
Affected radios are vx7, ft60, ft817 and ft857/897
We can expect to have them in upcoming daily but the implementation for all other supported radio will take some longer.

Actions #2

Updated by Predrag Supurovic about 9 years ago

That is great!
My compliments!

Actions #3

Updated by Filippi Marco about 9 years ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 90

Today daily build includes instructions for a number of radio thanks to a 6 hand work with Tom and Dan.
I'll leave this issue in feedback status for a while for users to point out radios which still need instructions.

Actions #4

Updated by Predrag Supurovic about 9 years ago

Wow! That was quick! :) Nice work!

How can we help sending instructions for rigs?

Actions #5

Updated by Tom Hayward about 9 years ago

Predrag Supurovic wrote:

How can we help sending instructions for rigs?

If you are set up with a development environment, you can submit a patch.

If you are not a developer, just post the instructions to this page and we'll get it included.

Actions #6

Updated by Predrag Supurovic about 9 years ago

Baofeng UV-B5/UV-B6 Instructions

Download

  1. Turn radio off
  2. Connect cable to mic/spkr connector
  3. Make sure connector is firmly connected.
  4. Turn radio on
  5. Make sure CTCSS in current channel is turned off or move to other channel with CTCS turned off
  6. Make sure there is no receiving signal on current channel
  7. Click OK to download image from device

Upload

  1. Turn radio off
  2. Connect cable to mic/spkr connector
  3. Make sure connector is firmly connected.
  4. Turn radio on
  5. Make sure CTCSS in current channel is turned off or move to other channel with CTCS turned off
  6. Make sure there is no receiving signal on current channel
  7. Click OK to upload image to device

I believe this also counts for all other Baofeng radios.

Actions #7

Updated by Filippi Marco about 9 years ago

Hi Predrag
are you sure the step 5 "CTCSS turned off" is necessary?

Tnx
73 de IZ3GME Marco

Actions #8

Updated by Predrag Supurovic about 9 years ago

Filippi Marco wrote:

are you sure the step 5 "CTCSS turned off" is necessary?

Yes I am.

Actions #9

Updated by Filippi Marco about 9 years ago

New patch for uv-b5 have been sent, will be in upcoming daily build.

Tnx

Actions #10

Updated by Jim Unroe about 9 years ago

Marco,

The UV-B5/UV-B6 radios, depending on certain configuration settings, change the 'ack' value returned during the read/write process. This was an issue because when an unexpected 'ack' was received, CHIRP would abort the transfer with a "Radio not supported" error. CHIRP now recognizes something like 3 different 'ack' values and I have not heard about anyone having a "Radio not supported" error for quite some time.

This may have been the reason for the need to set CTCSS to off on the past, but I don't think it is necessary any longer. I certainly do not worry if my UV-B5 is set to a channel with (or without) CTCSS and never have any issues when it come to reading from or writing to my UV-B5.

Jim KC9HI

Actions #11

Updated by Jim Unroe about 9 years ago

Actually the error was "Unexpected response" for the changing 'ack'. The radio also changes its 'ident' based on certain settings and that error was "Unsupported model". The current driver works around both issues.
Jim

Actions #12

Updated by Filippi Marco about 9 years ago

After discussing in list I sent a new patch for UV-B5 with a cosmetic change in message and with out the CTCSS line.

Actions #13

Updated by Bernhard Hailer almost 3 years ago

  • Status changed from Feedback to Closed

This appears to be complete.

Actions

Also available in: Atom PDF