Project

General

Profile

Actions
Copy link

Bug #6165

closed

Settings empty Baofeng BF-T1

Added by Pavel Korshikov about 6 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Pavel Korshikov
Category:
-
Target version:
0.4.1
Start date:
10/13/2018
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Baofeng BF-T1
Platform:
All
Debug Log:
I read the instructions above:

Description

Expected behavior:
See settings when clicking on settings tab for my radio

Observed behavior:
Blank area where settings should be

Problem reproduces 100% of the time.

Reproduction steps:
#Launch CHIRP
#Download from radio
#click settings tab and observe no settings

test on last build (3003:ad3e6fc729ad) for linux and Windows

Exception in terminal


ERROR: Exception running RadioJob: Value 130 not in range 136-174
ERROR: -- Exception: --
ERROR: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/chirp/ui/common.py", line 116, in _execute
    result = func(*self.args, **self.kwargs)
  File "/usr/lib/python2.7/site-packages/chirp/drivers/bf-t1.py", line 845, in get_settings
    _settings.vhfl) / 10))
  File "/usr/lib/python2.7/site-packages/chirp/settings.py", line 83, in __init__
    self.set_value(current)
  File "/usr/lib/python2.7/site-packages/chirp/settings.py", line 92, in set_value
    (value, self._min, self._max))
InvalidValueError: Value 130 not in range 136-174

ERROR: ----------------
ERROR: Job Args:   ()
ERROR: Job KWArgs: {}
ERROR: Job Called from:
  File "/usr/bin/chirpw", line 149, in 
    gtk.main()
  File "/usr/lib/python2.7/site-packages/chirp/ui/mainapp.py", line 503, in cb_clonein
    self.do_open_live(radio, tempname="(" + _("Untitled") + ")")
  File "/usr/lib/python2.7/site-packages/chirp/ui/mainapp.py", line 428, in do_open_live
    eset = editorset.EditorSet(radio, self, tempname=tempname)
  File "/usr/lib/python2.7/site-packages/chirp/ui/editorset.py", line 148, in __init__
    editor = settingsedit.SettingsEditor(rthread)
  File "/usr/lib/python2.7/site-packages/chirp/ui/settingsedit.py", line 71, in __init__
    job = common.RadioJob(self._get_settings_cb, "get_settings")

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/chirp/ui/settingsedit.py", line 219, in _build_ui
    raise Exception("Invalid Radio Settings")
Exception: Invalid Radio Settings
Actions
Copy link
 #1

Updated by Pavel Korshikov about 6 years ago

some error. CHIRP version is 0.3.0

➜  ~ chirpw --version
CHIRP 0.3.0dev on Linux delfX240 4.18.12-arch1-1-ARCH #1 SMP PREEMPT Thu Oct 4 01:01:27 UTC 2018 x86_64 (Python 2.7.15)
Actions
Copy link
 #2

Updated by Pavel Korshikov about 6 years ago

send patch. do not understand how to close it issues.

Actions
Copy link
 #3

Updated by Jim Unroe about 6 years ago

The problem is that the VHF band limit is set to 130. It must be in the range of 136-174.

Jim KC9HI

Actions
Copy link
 #4

Updated by Pavel Korshikov about 6 years ago

Jim Unroe wrote:

The problem is that the VHF band limit is set to 130. It must be in the range of 136-174.

Jim KC9HI

@ Jim Unroe it config from device bought from JD. I don't edit any settings.
Test reset configuration to factory. It still 130. How I can see at https://trac.chirp.danplanet.com/chirp_daily/LATEST/Model_Support.html device support 130-174.
I thing validation range for limit in driver incorrect.

So I create patch and sent it 

diff --git a/chirp/drivers/bf-t1.py b/chirp/drivers/bf-t1.py
--- a/chirp/drivers/bf-t1.py
+++ b/chirp/drivers/bf-t1.py
@@ -841,25 +841,25 @@
             setattr(obj, setting.get_name(), int(setting.value) * 10)

         rs = RadioSetting("vhfl", "VHF Low Limit",
-                          RadioSettingValueInteger(136, 174, int(
+                          RadioSettingValueInteger(130, 174, int(
                               _settings.vhfl) / 10))
         rs.set_apply_callback(apply_limit, _settings)
         adv.append(rs)

         rs = RadioSetting("vhfh", "VHF High Limit",
-                          RadioSettingValueInteger(136, 174, int(
+                          RadioSettingValueInteger(130, 174, int(
                               _settings.vhfh) / 10))
         rs.set_apply_callback(apply_limit, _settings)
         adv.append(rs)

         rs = RadioSetting("uhfl", "UHF Low Limit",
-                          RadioSettingValueInteger(400, 470, int(
+                          RadioSettingValueInteger(400, 520, int(
                               _settings.uhfl) / 10))
         rs.set_apply_callback(apply_limit, _settings)
         adv.append(rs)

         rs = RadioSetting("uhfh", "UHF High Limit",
-                          RadioSettingValueInteger(400, 470, int(
+                          RadioSettingValueInteger(400, 520, int(
                               _settings.uhfh) / 10))
         rs.set_apply_callback(apply_limit, _settings)
         adv.append(rs)

test with it. work fine for my devices.

Actions
Copy link
 #5

Updated by Henk Groningen almost 6 years ago

I do understand this patch, but wonder if we should not add a warning to novice users.
The BF-T1 is limited to 400-470 in real live. Outside this limits it kind'a works since the
basic rx/tx unit is a generic one. VHF tx is very limited in range because the end-stage is not designed
for it and prolonged tx on these frequencys may even damage the end-stage.
The original chip supports 136-174 and 400-470 ( and possibly even the 220 range ). However it can be stretched to 130-174 and 400-520,
like most Baofeng units. But advertising these limits as usable limits without a warning seems not very wise.

Actions
Copy link
 #6

Updated by Bernhard Hailer over 4 years ago

  • Status changed from New to Closed
  • Chirp Version changed from 0.4.0 to daily
  • Model affected changed from (All models) to Baofeng BF-T1

This appears to be complete.

Actions
Copy link

Also available in: Atom PDF

Copyright 2023 CHIRP Software LLC