Kirk, KN7UMV, posted this info in the codeplugs IO groups on 10-7-25. Excellent info...Mike, NO7RF For those of you who have both a 878 and a new 168 (AnyTone D168 or Airiton DM168) and want to transfer your 878’s CSV files into your 168, here are my notes for doing so for a 878 running FW 3.02 and a 168 running FW 1.07.  The steps for doing this with 878 FW newer than 3.02 may be different. Identical: RadioID, TalkGroups, ScanLists *Note* Although the structures of the 878 and 168 Talkgroup files are the same, the 168 will fail to load a Talkgroup flle that contains a TG number that exists more than once while the 578 and 878 allow this.  This bit me when I had both “9999 Audio Test” for PNW and “9999 OS4 Parrot” for my OpenSPOT 4 hotspot defined in my 878 but it wouldn’t load into my 168. Similar: Zones – 168’s CSV files don’t have last column “Zone Hide”.  Thus any zones marked as hidden in 878 don’t get marked as hidden when loaded into 168 – user must manually use 168’s CPS to hide any zones after import. *Note* 1) The structure of the exported Zone file depends on whether CPS’s Tool->Mode->”Contacts name is not unique” is checked or not.  I have not assessed the impact of exporting it with one setting and loading with the other. 2) The 168’s 1.07 CPS not only doesn’t export Zone Hide information, but if you attempt to load a file with Zone Hide information (like loading 878’s Zone CSV file) it’s not imported either. Channels: 878’s 12th column named “Contact TG/DMR ID” doesn’t exist in 168.  Delete column before loading into 168 878’s 21st column named “Color Code” is named “RX Color Code” in 168.  Rename it. 878’s 27th column named “Simplex TDMA” is named “Idle TX” in 168.  Rename it. 168 has 7 additional columns at the end of its CSV file that are not in 878’s CSV.  Add following columns: “idle_tx”, “Compand”, “DisturEn”, DisturFreq, Rpga_mdc”, “dmr_crc_ignore”, and “TxCc”.  Put 0’s into all fields except TxCc which should be a copy of what is in existing “Rx Color Code” column. Be sure to delete the 878’s column named “Contact TG/DMR ID” because if you don’t, the last column added to the 878’s Channels (TxCc) will not be imported into the 168 – it will be ignored.  It appears the 168’s CPS does a column-count during import.  Once you delete that column, then the last column (TxCc) will be imported into the 168. Do all of these things to 878’s CSV file before loading into 168.  If you’ve already imported your 878’s Contacts CSV file into your 168 through some means (even if it loaded with no error messages), I’d suggest checking to see if the TxCc column (Excel BI) contains the same values as the RX Color Code column (Excel T).  If not, I’d suggest copying Column T to Column BI. Anyway, that's what I did before loading 878 CSV files into my 168.  To make keeping my 578, 878, and 168 codeplugs in sync easier in the future, I now use a program I wrote that takes my master578 CSV files and converts them into the correct CSV formats for my 878 and 168 so I can do the conversions quickly and consistently. _._,_._,_ Groups.io Links: You receive all messages sent to this group. View/Reply Online (#5085)