Project

General

Profile

Actions

Bug #543

closed

VX-8 flags.valid is never set (introduced revision 1496)

Added by Sean Burford over 11 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
02/11/2013
Due date:
% Done:

100%

Estimated time:
0:30 h
Chirp Version:
0.3.0
Model affected:
vx-8dr
Platform:
All
Debug Log:
I read the instructions above:

Description

Hi,

Chirp daily and release 0.3.0 do not save or apply new channel memories because the valid flag for the memory is never set to True. Existing channel memories can be modified, but attempts to populate empty channel memories do not succeed. The UI shows the new settings, however uploading them to the radio or saving/loading them does not result in the change being applied.

The reason for this is that revision 1496 changed flags handling in vx8.py from setting opaque u8 values to manipulating named bit fields. Here is the diff:
http://chirp.danplanet.com/projects/chirp/repository/diff/chirp/vx8.py?rev=36ece7b1a4af&rev_to=d1aa69eb5fe9
The lines where flag.valid used to be set are:

  • 256 flag.flag = 0x83 # Masked from VFO B
  • 270 flag.nosubvfo = True # Masked from VFO B And:
  • 258 flag.flag = 0x03 # Available in both VFOs
  • 272 flag.nosubvfo = False # Available in both VFOs

As shown above, set_memory() in vx8.py used to (blindly) set the used (0x02) and valid (0x01) flags. Now it sets used (elsewhere in set_memory()) but never sets valid.

I don't know the difference between used and valid, however I expect that modifying line 263 to set flag.valid = flag.used would fix this.


Files

vx8-valid.patch (299 Bytes) vx8-valid.patch Sean Burford, 02/11/2013 01:30 PM

Related issues 1 (0 open1 closed)

Has duplicate Bug #575: Not save frequenciesRejected02/16/2013

Actions
Actions #1

Updated by Sean Burford over 11 years ago

I have confirmed that setting flag.valid = flag.used results in new channel memories showing on the radio and also in saved/loaded image files.

Actions #2

Updated by Tom Hayward over 11 years ago

Please email your patch for this fix to the chirp_devel mailing list. More info at Developers. Welcome aboard!

Actions #3

Updated by Sean Burford over 11 years ago

Mailed the patch to chirp_devel (in moderation?). Attached here for completeness.

Actions #5

Updated by Stu Gee over 11 years ago

Yes, this exact issue happens for me. Introduced in 0.3.0

Actions #6

Updated by Tom Hayward over 11 years ago

  • Status changed from New to Resolved
  • Assignee set to Sean Burford
  • % Done changed from 0 to 100
Actions #7

Updated by Tom Hayward over 11 years ago

  • Status changed from Resolved to Needs Backport
  • Target version set to 0.3.1

Stu Gee wrote:

Introduced in 0.3.0

and fixed in r1898.

Actions #8

Updated by Dan Smith over 11 years ago

  • Status changed from Needs Backport to Closed
Actions

Also available in: Atom PDF