0.1.0622.5 Download from radio

[oh3mbc]

When reading with mentioned version, i get APRS settings like this:

RT73_OH3MBC_APRS.jpg

[MM7DBT]

I assume you mean that the TX Frequency is wrong? Latitude and Longitude will be 0 if you have never set it before.

Download it again, it will be the same version number but I'll set the TX Frequency to use 6 decimal places so it shows all 9 digits. Not sure why it would be wrong as it's simply dividing by 1,000,000 to convert the Hz to MHz and then doing the opposite to get back to Hz when saving or uploading (144800000 -> 144.800000 -> 144800000)

I'll try forcing the regional characters to 'en-GB' as that's what the editor (and python script) is expecting. For example;
The script will store CTCSS Tones as 63.4 and not 63,4 for regions that use a comma.. however the editor isn't set so it would then export the channels with 63,4 if that's what your region uses.. however when trying to import that again it's not expecting a comma.. so will probably fail. It did when I tested it just now but forcing the regional characters fixed it.. It's not a perfect solution but saves re-writing the import/export code to be region independent

This is a download from my radio just now, using the same version.

aprs.PNG

[MM7DBT]

Changed to 0.1.0624.1 - As it's based on build date it automatically updates the version to todays date

[kd2wll]

Hi;
I am running 0.1.0624.1
APRS TX is UPLOADED as 144.390
when read back it displays as 1443.900000.
It DOES accept 1443.900000 when I just go and UPLOAD back to the radio.
Not critical for me, just letting you know, as I'm just going to turn APRS off at this point.
***CORRECTION***
If I physically TURN OFF the radio and THEN try to read the codeplug back it generates an error:
JSON Integre 14439000000 is too large or small for a Int32 Path 'APRS('AX25 TX Freq')" line 154 position 31

[MM7DBT]

The issue here is that the Python Script still had a line of code that multiplied the TX Freq by 10. Hence 144.390000 was becoming 1443.90000

I had my radio in my car when I last made an update so didn't fully test it writing to the radio, only testing with saving and loading the JSON files but as the issue was in the Python Script I never noticed this error.. I would love to have another radio for development/testing purposes so I can keep one programmed and in the car, I've barely used my own radio as it's always being used for testing and writing test codeplugs so rarely has my own codeplug programmed on to it

I believe this should now be fixed, I removed the offending line of code and uploaded a few different frequencies to the radio and they all read back correctly. I also modified the frequency on the radio and then read it and it displayed correctly.

I'll upload a version that fixes this issue soon