CHIRP

Provide a list of the new settings choices. Then set the side keys to each of the various settings, one-by-one using the radio's menu system or the OEM software. Then finally download a CHIRP image for each one of the settings being very careful to have the only difference being the side key setting.

Also i just realised, if i want to write my own settings to the radio with Chirp (new module) i also miss most channels and there are additional frequencies

Kenny Unknown wrote in #note-5:

Sidekeys seem to work now. Loaded Stock settings with OEM,changed them in Chirp and confirmed them with OEM again Now i saw in OEM CH1 was 435.23000 CH2 438.05000 CH3 439.07500 CH4 144.95000 CH5 145.0000. Importing in CHirp, CH1 and CH5 are not listed and i habe multiple CH all over Memory as you will see in .img

I see what you mean. That is weird... nothing was changed that should affect detection of the memory channels. I try to look into it later today.

I read a littlebit in the code....in Line 270 (original th_uv88.py) Powerlevel is low 0,5W, mid 2,5W and high 5W but the radio has low 1W, mid 5W and high 10W.

In line 274 Scramble says off and 1-8, in OEM and radio menu it only says on or off.

I dont know if this helps, i just though maybe because of accuracy i tell you. Thanks for the quick response by the way, I am impressed how quick i got support.

seems to work fine now. I checked Scramble and the value 1-8 doesn't seem to make any difference, they all just switch scramble on.Is there away to add PTT ID ? in the table in chirp i can chose bot, eot and both, but where can i add the id? in OEM there is PTT ID beginn (123456) and PTT ID END (987654321)

Kenny Unknown wrote in #note-10:

seems to work fine now. I checked Scramble and the value 1-8 doesn't seem to make any difference, they all just switch scramble on.Is there away to add PTT ID ? in the table in chirp i can chose bot, eot and both, but where can i add the id? in OEM there is PTT ID beginn (123456) and PTT ID END (987654321)

The Scramble setting seems to be another difference in this radio. It is only Off or On. That probably needs to be fixed as well. I need an image with 2 channels next to each other. One with Scramble set to Off, the other with Scramble set to On.

As far as the PTT-ID goes. I'm not the original developer of this driver. A developer can implement as much or as little of the radio's capabilities as (s)he wants. Apparently the desire to implement them was not there. They have little use for ham radio so I don't have much desire to spend time implementing them either. They are not something that would be changed often, so just configure them using the OEM software.

Actually after looking at the OEM software, they don't appear to be fully implemented. You can configure the 16 PTT-IDs but there is no way to select them on a per channel basis like most other radios that have them. So you probably can't even set them up with the OEM software.

Sry forgot to delete half a sentence...

Playing around i just saw that the A/B Select doesn't work. No matter if you chose a or b frequency, it always is b when switching the radio on.

Kenny Unknown wrote in #note-14:

Playing around i just saw that the A/B Select doesn't work. No matter if you chose a or b frequency, it always is b when switching the radio on.

Are you saying that if the radio is set to A and you power cycle it, B is selected? That would be a firmware issue.

Ok everything seems to work nicely now.

No I mean when you pre-set A or B Channel it always turns on on B Channel the first time after writing. After that it keeps the last channel that was uses before switching off...if you read the radio, it shows the channel that was used last thoug...so if you chose A Channel it reads A Channel and same with B Channel...it just doesnt write the pre set the right way...

it doesnt matter, i would consider this issue closed. Thank you for your help.

Kenny Unknown wrote in #note-17:

Ok everything seems to work nicely now.

No I mean when you pre-set A or B Channel it always turns on on B Channel the first time after writing. After that it keeps the last channel that was uses before switching off...if you read the radio, it shows the channel that was used last thoug...so if you chose A Channel it reads A Channel and same with B Channel...it just doesnt write the pre set the right way...

it doesnt matter, i would consider this issue closed. Thank you for your help.

In that case, set the radio to A, download to CHIRP and save the tab. Repeat the process for B. Either the location has been moved or it has never been correct. Now is a good time to fix it.

Kenny Unknown wrote in #note-21:

Here you go

Thanks.

This must definitely be a firmware issue. CHIRP is setting the correct bit with the correct value. I would suspect that you would see the same problem when setting it with the factory software but the factory software doesn't support this setting. Because of this, they are probably unaware of the bug.

Yea you are right, its not in OEM.

BTW how can i add the driver in chirp without having to load the module every time?

Also, do you think there is a way to get dtmf running in chirp? i am a linux user and i have to run the oem in virtualbox, which is not as stable as i would wish it would be....also for usb port forward i need to run the vm as root....

Kenny Unknown wrote in #note-23:

Yea you are right, its not in OEM.

BTW how can i add the driver in chirp without having to load the module every time?

Stop finding issues and let me know that all of the changes are working as expected and are OK to submit to be included in CHIRP. ;-)

Kenny Unknown wrote in #note-24:

Also, do you think there is a way to get dtmf running in chirp? i am a linux user and i have to run the oem in virtualbox, which is not as stable as i would wish it would be....also for usb port forward i need to run the vm as root....

Yes, there is a way. An interested developer with access to a physical radio would need to reverse engineer the settings and develop settings. Each volunteer developer can provide as much or as little support as (s)he wants to. The original developer of the driver only supported cloning and the per-channel programming support. I was told that it was OK for me to further develop the driver. I continued by adding the global settings that would be the most useful to hams. I didn't feel that the DTMF settings were something that most hams would use so I didn't do the work to implement them. How do you use them?

I just saw that one of my messages wasnt send. I already wrote that everything you changed works fine.

I am still doing my license and right now i am just a listener, but i will need dtmf to get access to relais stations in my area, to chose talkgroups or select call. Thats also the reason i asked for pttID. As i say the oem doesnt run well. I dont know if it is because its a vm or because the Software itself.

You hava access to a physical Radio or am i your access?

Kenny Unknown wrote in #note-27:

I just saw that one of my messages wasnt send. I already wrote that everything you changed works fine.

I will try toe get a patch submitted in the next few days.

I am still doing my license and right now i am just a listener, but i will need dtmf to get access to relais stations in my area, to chose talkgroups or select call. Thats also the reason i asked for pttID. As i say the oem doesnt run well. I dont know if it is because its a vm or because the Software itself.

Can't you just key the access code in using the radio's keypad? This isn't a use that PTT-ID was intended to be used for. The PTT-ID would be transmitted every time to pressed the PTT button. Not something you would want to do as a ham.

So you would need at least 3 channels programmed. The first channel with the DTMF code to access the relay station. The second channel with no DTMF code for communicating with other stations. The third channel with the DTMF code for shutting down the link.

You hava access to a physical Radio or am i your access?

I believe I have an RA89 around here somewhere. The first thing I would have to do is find it. The second would be to update the firmware to the latest. The third would be to acquire the desire to do the development work that I didn't have previously and don't really have now. Maybe I would reconsider if I can get most of my many other project finished.

i wish it was that easy. i cant use the keyboard for dtmf, would be nice if it was that easy. the relais here have all echolink access so i need more than 3 channels with dtmf. i dont have access yet, but i know you need to open the relais and then choose between multiple option like local mode or i call another node...pttid i was told is needed so the ralais knows how to forward me to local mode or other node, but also for select call for example, if i want to selective call another radio... in my country you need a license and without you actualy commit a crime sending with the radio...also i live in a major city and every now and then people misuse the relais or misbehave and with pttid they can be locked out (and only can enter with the right pttid)

if this is to much for you i get it, it is also just a hobby for you. i think i will need to use that oem software in the vm then...

thank you for your help so far

Sidekeys are indexed strangely and few don't work at all. Long press functionality does not work with chirp settings, including base FM scan function.