Feature #336
closed
Wouxun empty TX frequencies
Added by Johan Adler about 12 years ago.
Updated about 12 years ago.
Model affected:
Wouxun KG-UV6D
I read the instructions above:
Description
I have entered some channels with empty TX frequencies on my KG-UV6D, to ensure that I can not transmit by mistake on frequencies I am not authorized to transmit on, but that I want to be able to listen on.
In memory an empty frequency is represented by @0xffffffff@ at TX position, but when exporting to CSV Chirp daily converts this to 1666.666650 MHz. I have not tried re-importing the untouched CSV file but I expect it may be difficult since this frequency is well out of bounds.
On the subject of CSV export I would suggest enclosing all fields in double quotes to ensure that the spreadsheet software of your choice will not try to change any fields. LibreOffice is kind enough to change the decimal point of all floating point numbers to a comma, which is correct for my locale but usually frowned upon by re-importing software.
Note: The platform field should be Linux, not Windows. It may not be relevant in this case, but I want all facts to be correct.
I was wrong, it is not the CSV export part that makes the mistake, the incorrect frequencies are visible in the GUI part too. Prime suspect might be wouxun.py, I'll see if I can find it.
The problem lies in @get_memory(self, number)@, but I am not sure how to rewrite it to correctly interpret memory contents @0xffffffff@ at TX frequency as 'do not transmit' or an empty TX frequency. That is, I could probably patch the code to do this, but I am not sure how to play nice with the rest of Chirp in doing so, how Chirp represents an empty TX frequency, and what settings of @splitdup@, @duplex@ and @offset@ is expected in this case.
- Status changed from New to In Progress
- Assignee set to Filippi Marco
- Model affected changed from Wouxun to Wouxun KG-UV6D
- Platform changed from Windows to All
I'll take care of this also, tx inhibited channels will use "off" duplex as in UV-5R driver.
But we'll have to wait for Dan to fix #303 for full support of off duplex in CSV export.
- Tracker changed from Bug to Feature
- Subject changed from Wouxun to CSV misinterprets empty TX frequencies to Wouxun empty TX frequencies
- Status changed from In Progress to Feedback
I sent a patch to the developer list, please Johan test it and let us know so it can be added to the next daily build.
Sorry, where do I find the patch?
In the list I saw messages about a patch regarding modification of allowed frequency ranges, which is not quite what I meant here.
Sorry, I must have missed the "send mail" button.
I sent it minutes ago.
- Status changed from Feedback to Closed
Also available in: Atom
PDF