I don't have a 950P to test/develop with... However, if you could post the Wouxun CPS codeplug from your radio with the 950P CPS and the Chirp img file when using the 980P driver, I may be able to figure some stuff out and make a test 950P driver for you to work and test with. Having both files will help me figure out the "text" decoding issue you reported.

I assume other than the text decoding issue... most of the other settings and channel memory values are correct?

No problem a can to these, but there it starts what is the wouxun cps codeplug

Channel memory are okay

i will make after work some screenshots

The Wouxun CPS codeplug is what you read from the radio with the Wouxun factory programming SW.

https://www.buytwowayradios.com/downloads/dl/file/id/66/product/2658/wouxun_kg_uv950p_software.zip

You will read from your radio with the SW, save the file and then attach it here.
Then do the same thing with Chirp and select the 980P radio, read from the radio and then save the file and attach it here.

With those 2 files, I will hopefully be able to figure out the encoding of the text and make a test driver.

It would be good if you could try and create channels that have names that show many different characters ... not just letters ( /,&,!,-,_, etc) so I can see the whole set. But I will take what you can give me.

Thanks

Correct...you should not be using 980P CPS on the 950P radio. Each radio has specific settings decoding. Chirp and 980P CPS are doing the same decoding which is clearly not correct for the 950. Hopefully you attached a 950P CPS read and not a 980P CPS read.

The codplug is from the the 950 no worry i am only played with the wouxun software long time ago

The same company does different decoding, i've been angry about that for a long time

Damm so fast, i will test it in evening
Okay?

Strange.. can you please duplicate the issue after writing to the radio and attach the debug.log file and the img file you sent.

I was not expecting any issues because the decoding was all perfect.

I see the issue with the channel names. stay tuned.
Can you post a picture of what the FM broadcast values look like after writing?
The values look correct in the image.

strange after a reread and a resend the fm broadcast are correct on the radio
really strange

a quick test bevor work looks good
the name are correct on the radio

only the names in scan groups does have the same behavor as the names in the channel names

more test on evening

Thanks. Happy the names are working now. If you could change some names in the scan group names and send me the CPS codeplug used to program them and the read image from Chirp I can look at that. I don't expect it to be too far off with real names. Just the default ones with all 0000000 likely is off. Seen that with all the other radios...

Markus Scherer wrote in #note-22:

written with wouxun
read out with chirp see foto

max

Please attach the requested img from Chirp after the read from radio. And any debug log from the write and read sequence.

Thanks. So the test driver reads the scan names correctly now. Great news. I understand that they don't show up correctly on the radio after changing them with Chirp. I need to make the same changes to the writing routine for scan names and then it will be good.

I do seem to recall other radios requiring specific freq ranges in the first 1 or 2 channel memories. I think that is a CPS/radio issue.

I will update the driver later today to encode the names correctly for a write and then it should be all good.

Thanks again for the data.

could it be that the character length is the problem
chirp has 8 the cps has 6

did chrip write in an memory place and the radio don't know what to do with it

why did you say cps to the wouxun software???

Length 8 vs length 6 is not the problem. The radio seems to interpret the letters different than CPS or Chirp. Can you use all capital letters into the scan names... like ABCDEF, GHIJKL, MNOPQR, STUVWX, YZ,
then all lowercase, abcdef, ghijkl, mnopqr, stuvwx, yz for scan names with the CPS and write radio . See what the radio shows for each then read with Chirp and post the pics and image file? We are getting real close.

I don't see any issues between CHiRP and CPS in your pictures.

For me to continue, I will need the following :
Picture of the radio displayed value for a scan name that is not correct.
The img file from the radio in this state.
What the intended scan name should be.

It would ve very helpful if you could manually program the scan names on the radio and then upload the image and send it to me here.

Does the radio show the strange scan names if programmed by the CPS? If yes, then something is really wrong. We're you able to manually edit the scan names directly on the radio and then read from radio with Chirp?

All your screen shots show that Chirp and CPS agree on what the scan names are. It seems the radio has a problem displaying the data. I am really interested in the data when the radio shows good names when entered directly on the radio.

CPS and Chirp shows it in correct way only the radio did have troubles when it was programed with chirp

The shot shows it in order i programed the radio.

1. write with CPS to the radio -> all is good -> file saved and upload
2. read with Chirp from radio -> all is good - > file saved and upload
3. write with Chrip TO radio -> Radio shows the strange names -> file saved and upload
4. read with CPS FROM radio -> CPS shows the correct names -> screenshot -> file saved and upload
5. take pictures from radio

i hope these was in a right order for you

okay i will put names direkt on the radio an then due a read out

I dont know if i to stupid or the radio does not have the feature to change the names direktly.
I have read out the manual an there are no description to do so.

sorry

YOU DID IT !!!!!!!!!!!!!!!!!!!

Take a big bug of cooffee

I am not able to write how happy i am

Markus

Cool
i will test it after work

did you know why your driver is not in the package of chrip next??

Markus Scherer wrote in #note-47:

Cool
i will test it after work

did you know why your driver is not in the package of chrip next??

Yes - because I have not had time to do all the testing and formally submit it for inclusion.
I will see if I can get the testing done and submit it in the near future.

Hello
driver works again you are the best

max