High power in the CPS is Turbo in the CSV

[sdt16]

At least for the DJ-MD5, in order for a channel to get imported as high power, it has to be listed as Turbo in the CSV. High in the CSV is then translated to mid. PNW Digital suggests high power all the time, so I'm thinking the example file should be changed to turbo if the Anytone does the same thing.

I've attached an export from my CPS as an example (renamed to .txt so github will accept it).

channel_md5_format.txt

[nreisbeck]

@sdt16

I ran across this with the Alinco CPS the other month, the Alinco CPS software uses a different naming:power convention than the Anytone radios do, and their CPS software is... different.

{
    "RadioName": "Alinco DJ-MD5",
    "PowerSettings": {
        "High": "5 W",
        "Mid": "2.5 W",
        "Low": "1 W",
        "Small": "0.2 W"
    }
}

{
    "RadioName": "Anytone 878UVII",
    "PowerSettings": {
        "VHF": {
            "Turbo": "7 W",
            "High": "5 W",
            "Mid": "2.5 W",
            "Low": "1 W"
        },
        "UHF": {
            "Turbo": "6 W",
            "High": "5 W",
            "Mid": "2.5 W",
            "Low": "1 W"
        }
    }
}

Power:  0.2W , 1W , 2W , 5W  , 7W  
DJ-MD5: Small, Low, Mid, High, NULL
D878UV: NULL , Low, Mid, High, Turbo

I did some fiddling around just now with ACB & the Alinco DJ_MD5 v1.13e version of the CPS, and I'm pretty certain this isn't an ACB problem, and the Alinco CPS is doing something weird with the Tx Power mappings in their software. Take a look at the channels-alinco_power.csv attached here.

I hand programmed in 4 channels in the Alinco DJ-MD5 v1.13e CPS, Small, Low, Mid, High with the corresponding power levels, then exported the Channel listing to a CSV file. The power settings in the CSV file in the Transmit Power column came back as Low, Mid, High, Turbo.

So if you wanted an answer as to WHY you have to put the power levels in as Turbo in your ACB files, in order to have them appear in the CPS as High, it's because the Alinco CPS software is weird and does not map the Transmit Power options correctly on Import/Export.

Hope that answers your question? I'd certainly try to file a bug with Alinco (or raise it on an Alinco mailing list) because what their ("""their""" ??) software is doing, isn't correct, or what a user of the software should expect to have happen.

Here's a picture of the ACB Output, imported into the Alinco CPS v1.13e showing the same behavior on Import.

If you want to double check the Import/Export behavior, here are two CSV files. Import File: channels_alinco.csv Export File: channels-alinco_output.csv

I think @K7ABD can close this issue based on the above, but I'll leave that up to you and him.