CHIRP

joe street wrote:

When downloading memories from UV50X3 which have been programmd for satellites the TX frequencies are not read properly from the radio and show up in the 220Mhz band instead of the 144Mhz band. I include the similar image file from the UV-5R which has similar memories for comparison. The memories are configured in the UV50X3 and work as expected but when downloading to CHIRP there is an error when they are displayed.

The UV-50X3 image loads with no errors. The debug.log file has no errors. Please explain which channel is wrong for the UV-50X3 and which channel it is supposed to be like in the UV-5R.

Jim

Hi Jim

If you load the two image files I attached and scroll to the bottom you'll see that in the UV5R image memories 107 tto 120 are programmed to receive on 70cm and transmit on 2m with frequency ranges to accommodate doppler shift for satellite operation using split as the offset option which works on air. The UV5R and UV50X3 are both programmed the same although I had to do it manually on the UV50X3 because CHIRP messes it up. The similar memories in the UV50X3 image are numbered 479 thru 492. If you look at the image file as read from the radio last evening, you can see that both the offset field and the TX frequencies have been corrupted from the actual programmed values. I hope I explained that more clearly this time.

Joe

Hi Jim

I tried it on an older version also. I could copy and paste the memories just fine (Which doesn't work in the latest CHIRP) but they got corrupted when I tried to save the image to hard disk. Upon re-opening they were corrupted. I could set them manually without the copy and paste, but upon upload to the radio or save to HD the corruption happened even with the legacy version.

joe street wrote in #note-4:

Hi Jim

I tried it on an older version also. I could copy and paste the memories just fine (Which doesn't work in the latest CHIRP) but they got corrupted when I tried to save the image to hard disk. Upon re-opening they were corrupted. I could set them manually without the copy and paste, but upon upload to the radio or save to HD the corruption happened even with the legacy version.

After looking at if further, CHIRP is actually working correctly.

What you are seeing in the UV-5R is memory row is setup using "split" to define the TX frequency. When Duplex is set to "split", the Offset field contains the direct TX frequency instead of the offset (difference between RX frequency and TX frequency).

Frequency: 436.815 (the RX frequency)
Duplex: split
Offset: 145.845 (the direct TX frequency)

When it is transferred to the UV-50X3, the above is immediately converted into and displayed in the shift direction/offset format. In CHIRP-legacy the conversion doesn't happen until the spreadsheet style editor is refreshed (at the end of the download, after a file is loaded or the [Refresh] button is clicked).

Frequency: 436.815 (the RX frequency)
Duplex: - (the TX frequency is lower than the RX frequency)
Offset: 290.970 (the difference/offset between the RX frequency and the TX frequency)

And 436.815 - 290.970 = 145.845 (the TX frequency)

So nothing is corrupted. What you see is expected. You can still enter the TX frequency directly into the UV-50X3 tab using "split" and the direct TX frequency (or copy and paste from the UV-5R tab to the UV-50X3 tab. It is just going to be converted to shift direction/offset in the UV-50X3 tab.

Jim KC9HI

Makes sense. This issue started with me using a legacy version which I installed through synaptic not realising it was out dated. That version did not upload the right TX frequency I know because I tested it on the hardware. This led to me installing the latest and when I downloaded from the radio (which I had manually programmed) and saw the wrong numbers where I was expecting 2m TX frequencies, I didn't do the math to see that it was actually a proper minus offset and assumed the problem was still there. All working now and I appreciate your time and help Jim and I hope it didn't feel like a waste of your time on this red herring. My apology for not catching the error.
Best regards...Joe

Yes certainly I can test that. Just reading about how to do that It looks like loading the test module is automated and requires web access which isn't the case right where the UV50X3 is so can I load the module, disconnect the laptop from ethernet and then do the test without having web access through the stage where it interfaces with the radio? I can keep the laptop running while I go to the radio location. Will that work?

joe street wrote in #note-8:

Yes certainly I can test that. Just reading about how to do that It looks like loading the test module is automated and requires web access which isn't the case right where the UV50X3 is so can I load the module, disconnect the laptop from ethernet and then do the test without having web access through the stage where it interfaces with the radio? I can keep the laptop running while I go to the radio location. Will that work?

Yes. You will be good until you close CHRIP.

Jim

Mission accomplished Jim,

With that module I downloaded memories from the rig and all frequencies and spit mode appeared as expected. Saved to disk. Again all well. Read from disk, good. Upload to radio and confirmed TX frequency with second receiver. So what happens now, will that module go into the next daily build?

Thanks for your kind help with this Jim. I do appreciate being able to work with direct frequencies rather than calculating offsets which just seems more cryptic and awkward when setting up a radio. In addition it is now consistent with the way the UV5R is handled.

Best regards...Joe ve7xo

I will have to work up and submit an official patch. Maybe I can get that done tomorrow.

Jim

Got it. Thanks for your efforts Jim it is much appreciated.

Best regards...Joe ve7vxo