i need your agreement to put your memory map in the software chirp #183
Replies: 36 comments 29 replies
-
|
Sure, if you want, I'll appreciate help in that regard. I even started doing that. Here are my modifications if you can make use of that. |
Beta Was this translation helpful? Give feedback.
-
|
thank's, it's appreciated. i will let you know |
Beta Was this translation helpful? Give feedback.
-
|
Will this be a setting UVK5-EGZUMER or general UVK5 in Chirp ? |
Beta Was this translation helpful? Give feedback.
-
|
shoud be something like UVK5-EGZUMER ... not sure. i will see with chirp team |
Beta Was this translation helpful? Give feedback.
-
|
Hi,
many of the menu are add or change for chirp file but still have some question
1 - i can't find the RXMODE menu in memory map, i found the definition ( dual rx respond, cross band, main tx dual rx,main only ) in file menu.c i find a track of if but i dont see where it's store in memory map
case MENU_TDR: strcpy(String, gSubMenu_RXMode[gSubMenuSelection])
2 - battery calibration setting in the lock menu of the radio at address 0x1f46 (2 byte long) should we add capability to be change in chirp or leave only change in the radio ???
Let me know
Jocelyn
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Hummm... rxmode...a mix... ok,,, the original CB and DW have 3 value each ( off, band A , band B ) = ( 0, 1, 2 ). by mixing those, i will have to think how to handle those in chirp for user uses.... i think, i will have to remove the CB and DW in chirp to the new display RXMODE. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah I forgot about the upper/lower VFO selection. This is not used in the firmware at all. For me this is either on or off where: If the value is ON this is equal to address 0x0EAB (gEeprom.TX_VFO) +1 just for the compatibility sake |
Beta Was this translation helpful? Give feedback.
-
|
I wonder, what did you do with stock QS options that are disabled in my build by default? |
Beta Was this translation helpful? Give feedback.
-
|
for the option that you not enable it in your compile the memory map are just not uses and skip that option in the reading example in testing.c noaa_auto_scan at address 0xe73. not uses. i leave the option in the chirp . so if it. enable later. i will be programable . so in chirp all option can be programable either if the radio not uses it..that way it will be compatible in future version
what do you think???
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, that is probably the best option. I don't know how that would look, but there could be some marking added next to options that are not available by default. Maybe a star, and a note that options marked may not be available. This is just a proposition, you don't have to add this, I leave this to for you to decide. |
Beta Was this translation helpful? Give feedback.
-
|
the chirp file can't know what is the option that is enable or not by reading the radio. it just get data of the memory map. |
Beta Was this translation helpful? Give feedback.
-
|
Yes that would have be added manually, knowing which options are enabled and which are not. By default I mean the options that are present in the official release. For example there is no 1750Hz tone, no alarm, so choosing this option for configurable buttons will have no effect, the was already one question about it: #196 |
Beta Was this translation helpful? Give feedback.
-
|
what is QS??
|
Beta Was this translation helpful? Give feedback.
-
|
QS - quansheng |
Beta Was this translation helpful? Give feedback.
-
|
ok :) |
Beta Was this translation helpful? Give feedback.
-
|
after thinking about your * idea.....
for alarm and 1750:
In the version egzumer in chirp they will a * in front of the option not available and a message to tell user this might not be available...
in futur chirp , the text at arrow in picture number will be:
1: Side key 1 short press, The option begin with a * might not be available in this version
2: None Flashlight Power Monitor Scan VOX *Alarm FM radio *Transmit 1750Hz, Lock Keypad Switch VFO VFO/MR Switch Demodul
i think it's can be done that way... for those 2....
for the other.. l will check what it's involve.... need to talk with chirp team... it will be availaible mid december
Jocelyn
|
Beta Was this translation helpful? Give feedback.
-
|
ha the photo not show by email... i put it directely in github now.. |
Beta Was this translation helpful? Give feedback.
-
|
I would suggest putting the disclaimer in the "Infos" tab. It will be a little bit hidden, but wouldn't need to include the disclaimer on every option. I don't know how good you are at python, this would need some more work, but we could do it as I suggested in my last post on the bottom, then it wouldn't need any stars or disclaimers. |
Beta Was this translation helpful? Give feedback.
-
|
the problem with info tab, it's that info tab not their if the developper view not selected and most user will not gone put developer mode ON and can't see it..... so many question will pop up..... what is * meanning ..... |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, I meant "Driver information" in settings tab |
Beta Was this translation helpful? Give feedback.
-
|
can be a option... i will ask team chirp what they do with all kind of other radio option to do something similar... i will let you know... |
Beta Was this translation helpful? Give feedback.
-
|
If you are adjusting...
|
Beta Was this translation helpful? Give feedback.
-
|
Frequency table should be as follows
Also I got an idea, I could write to the EEPROM all options that have been built into the firmware. This would then be accessible in chirp. BTW. Where will you publish the driver code? |
Beta Was this translation helpful? Give feedback.
-
|
the guy that did quansheng in team chirp will contact me it a week, is to busy for now ... so will be later than that |
Beta Was this translation helpful? Give feedback.
-
|
It would be good thing to publish this driver in a repository on github eather way. That way changes can be tracked, it could be updated in the future, tested and so on. I can create a separate repository and make you a collaborator there. What do you think. Or will you start your own repo? |
Beta Was this translation helpful? Give feedback.
-
|
it' in .., #seekto 0x1FF0: #seekto 0x1FF1: |
Beta Was this translation helpful? Give feedback.
-
|
I added a function to write build options as bits in memory: 0x1FF0:
0x1FF1:
|
Beta Was this translation helpful? Give feedback.
-
|
ok, i will add it. in the file, :) to be sure, 1ff1 : if bit0 is = to 1, this is enable flashlight, else not implement in this version of firmware |
Beta Was this translation helpful? Give feedback.
-
|
Yes that is correct. bit0==1 means the FW was built with |
Beta Was this translation helpful? Give feedback.
-
I have no idea what that might be |
Beta Was this translation helpful? Give feedback.
-
|
If you are adjusting...
Also consider adjusting the frequency-limits checked by Chirp below 50 and above 600
good point :)
|
Beta Was this translation helpful? Give feedback.
-
|
If you are adjusting...
Also consider adjusting the frequency-limits checked by Chirp below 50 and above 600
change as be done by ezgumer in the file he star to modify it and i am continuing it :) ...
it was 76 to 108
|
Beta Was this translation helpful? Give feedback.
-
|
forget the it was 76 to 108 in my comment, it a cut a paste that was their.... that the fm radio range 76mhz to 108mhz |
Beta Was this translation helpful? Give feedback.
-
|
when it reproduce, i will take care how to do it.... and let you know.
Le jeudi 7 décembre 2023 à 19 h 36 min 40 s HNE, egzumer ***@***.***> a écrit :
keypad beep stop working, i change the frequency and the beep keypad came back
I have no idea what that might be
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
contact me direct : ***@***.*** if you want.
Le jeudi 7 décembre 2023 à 19 h 17 min 32 s HNE, egzumer ***@***.***> a écrit :
Use the github discussions page to communicate, emails make a mess, and you seem not to read some messages.
#183
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
what , it hiden my email address.... wouaw... |
Beta Was this translation helpful? Give feedback.
-
|
here is fine |
Beta Was this translation helpful? Give feedback.
-
|
the guy contact me this after noon and he will check it.....
all modification in the file i made, i add with a comment ( #joc + comment ad it... ) this is for debug and fast way to to find modif from the original file that you did and with what jacek lipkowsk put in the original chirpwith winmerge program.
her is the file where i am now with it. nothing testedi try to compile it but the compiler give me error in the library of python in the main chirp. that i do not change at all...
Le vendredi 8 décembre 2023 à 20 h 33 min 22 s HNE, egzumer ***@***.***> a écrit :
Well I don't understand. I don't know why would he feel bad. This is an open source and can be used freely. If it was published there would be a possibility of testing and 3rd party contribution. Testing is highly desired BEFORE the driver is added to CHIRP. Also it could be used right now as an external module, before it is incorporated into CHIRP.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
You don't need to compile anything for testing. You can load the driver as a module in chirp. You turn on the developer mode, then you go to file -> load external module |
Beta Was this translation helpful? Give feedback.
-
|
ok, this is a thing that i dont try.... that ... way. nice...
Le vendredi 8 décembre 2023 à 21 h 46 min 32 s HNE, egzumer ***@***.***> a écrit :
You don't need to compile anything for testing. You can load the driver as a module in chirp. You turn on the developer mode, then you go to file -> load external module
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
ok i was thinking # is a comment line as the begin of the file but it's not it's // i am changing it now
Le vendredi 8 décembre 2023 à 21 h 46 min 32 s HNE, egzumer ***@***.***> a écrit :
You don't need to compile anything for testing. You can load the driver as a module in chirp. You turn on the developer mode, then you go to file -> load external module
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
forget about the file i send to you... a working one will be done soon...i am correcting all menu.... this is the long press M bouton
Le vendredi 8 décembre 2023 à 21 h 46 min 32 s HNE, egzumer ***@***.***> a écrit :
You don't need to compile anything for testing. You can load the driver as a module in chirp. You turn on the developer mode, then you go to file -> load external module
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
i found out the comment when reading in chirp reading with a strange behaviour....i gone remove all ...
many menu working now...
i made a big mistake a the begining.... my error...;(
Le vendredi 8 décembre 2023 à 21 h 46 min 32 s HNE, egzumer ***@***.***> a écrit :
You don't need to compile anything for testing. You can load the driver as a module in chirp. You turn on the developer mode, then you go to file -> load external module
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Push changes to |
Beta Was this translation helpful? Give feedback.
-
|
ok, it will be their by monday.. i am out of the house for 2 days.
Le samedi 9 décembre 2023 à 11 h 09 min 19 s HNE, egzumer ***@***.***> a écrit :
Push changes to devel branch of https://github.com/egzumer/uvk5-chirp-driver
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
file is their on github... not finish bu working( rxmode mix with dualwatch and crossband. need to be tested all feature, try it, by reading data from the radio, and see what the result in chirp.
like compiler option, s0,s9, etc...
Jocelyn
Le samedi 9 décembre 2023 à 11 h 09 min 19 s HNE, egzumer ***@***.***> a écrit :
Push changes to devel branch of https://github.com/egzumer/uvk5-chirp-driver
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Nice work. and works OK for |
Beta Was this translation helpful? Give feedback.
-
|
When saving settings, the filename had (egzumer). Suggest to remove the () and place 1 - Not this format for filename Suggest this format for filename See line 657 in source... |
Beta Was this translation helpful? Give feedback.
-
|
trouble find and fixthank's
Le lundi 11 décembre 2023 à 15 h 49 min 45 s HNE, ErikS-web ***@***.***> a écrit :
Menu 32. MICBar is ON in radio, but not V in Chirp
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
ok...
but it's not more clear with (egzumer) in the filename for the chirp uv-k5...
Jocelyn
Le lundi 11 décembre 2023 à 16 h 03 min 58 s HNE, ErikS-web ***@***.***> a écrit :
When saving settings, the filename had (egzumer). Suggest to remove the () and place 1 -
Not this format for filename
Quansheng_UV-K5 (egzumer)_20231211.img
Suggest this format for filename
Quansheng_UV-K5 - egzumer_20231211.img
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
i just update the file to start adding text see on the radio to match chirp text., i saw you add a message box message. great, ok for desable from chirp. but a soon as your reatch this message box, it pop up at any change you try to make at any value on any option.
not sure what cause this...
Jocelyn
|
Beta Was this translation helpful? Give feedback.
-
|
It is because the validation routine is called every time there is a change on any setting, and for every possible option, not only the one that has been changed. Also because you have TX unlocked on your radio. |
Beta Was this translation helpful? Give feedback.
-
|
Download from radio When I read with first/previous version I see, these values... And with new version dd 12-12-2023 I see |
Beta Was this translation helpful? Give feedback.
-
|
Aha detected why |
Beta Was this translation helpful? Give feedback.
-
|
yes, egzumer correct my mistake... one is 130 and the other is 76
by the way, i am in the modification to make the setting option the more same listing as on the radio... it will be their very soon, on the web i add the name show on the radio in ( ) in chirp
Le mardi 12 décembre 2023 à 15 h 29 min 03 s HNE, ErikS-web ***@***.***> a écrit :
Aha detected why
Reason.-.code.change.png (view on web)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Please, please, please, use the |
Beta Was this translation helpful? Give feedback.
-
Hi
i want to put your memory map of the quansheng firmware you did in the chirp communication software.
i all ready contact chirp member (github project either) and they agree to implement it. But they ask to have your agreement to do it.
In the file setting, all the mapping memory is their, so it will take from their and make it full compatible in file driver in chirp
( key Menu, Backlight setting, etc... )
So, do you agree to take the memory mapping and transfert it in to chirp.
Thank's
Jocelyn
Beta Was this translation helpful? Give feedback.
All reactions