Bug #9854
openSPLIT NOT WORK AGAIN
0%
Description
The split function does not work again.
Tried set the split on Baofeng UV5R, Yaesu FT-4x, Yaesu FT-818.
Files
Updated by Marek Zientarek over 2 years ago
- File chirp2017.mp4 chirp2017.mp4 added
in version 20170714, split works fine
Updated by Jim Unroe over 2 years ago
- File UV-5R_split.png UV-5R_split.png added
- File FT-4XE_split.png FT-4XE_split.png added
- Status changed from New to Feedback
In the latest CHIRP daily build, split works fine. I believe that your sequence of programming steps, as shown in the videos, is in the wrong order. You are putting the TX frequency into the Offset field before you are setting the Duplex field to "split". That is in reverse of what is required. You must set the Duplex field to "split" before you enter the TX frequency into the Offset field.
Until the Duplex field is set to "split", the value in the Offset field is an "offset". When the Duplex field is changed to "split", the "offset" value in the Offset field is thrown away and the Offset field, which is now intended to store a TX frequency, is initially populated with the same frequency as the one stored in the Frequency field (which would initially create a simplex channel when the switch to "split" is made). It is at this time that you would enter your desired TX frequency into the Offset field.
So using the test images in the CHIRP repository, I programmed a channel with "split" for both the Baofeng UV-5R and Yeasu FT-4XE using the latest (CHIRP daily-20220408) without any issues (see attached screen captures).
Jim KC9HI
Updated by Marek Zientarek over 2 years ago
I found a problem.
The split function error only affects the Polish, French, Hungarian, Spanish and Russian language versions.
Everything works fine in the other language versions.
Updated by Jim Unroe over 2 years ago
Marek Zientarek wrote:
I found a problem.
The split function error only affects the Polish, French, Hungarian, Spanish and Russian language versions.
Everything works fine in the other language versions.
Now that you mention it, I do recall seeing this issue in the past. See issue "@#9601@":https://chirp.danplanet.com/issues/9601. I believe that there might have been others but I wasn't able find them at this time.
Jim KC9HI
Updated by Bernhard Hailer almost 2 years ago
- Related to Bug #9601: Chirp no reconoce "Desplazamiento" added
Updated by Bernhard Hailer almost 2 years ago
I assume Chirp-next resolves this problem?