• To anyone looking to acquire commercial radio programming software:

    Please do not make requests for copies of radio programming software which is sold (or was sold) by the manufacturer for any monetary value. All requests will be deleted and a forum infraction issued. Making a request such as this is attempting to engage in software piracy and this forum cannot be involved or associated with this activity. The same goes for any private transaction via Private Message. Even if you attempt to engage in this activity in PM's we will still enforce the forum rules. Your PM's are not private and the administration has the right to read them if there's a hint to criminal activity.

    If you are having trouble legally obtaining software please state so. We do not want any hurt feelings when your vague post is mistaken for a free request. It is YOUR responsibility to properly word your request.

    To obtain Motorola software see the Sticky in the Motorola forum.

    The various other vendors often permit their dealers to sell the software online (i.e., Kenwood). Please use Google or some other search engine to find a dealer that sells the software. Typically each series or individual radio requires its own software package. Often the Kenwood software is less than $100 so don't be a cheapskate; just purchase it.

    For M/A Com/Harris/GE, etc: there are two software packages that program all current and past radios. One package is for conventional programming and the other for trunked programming. The trunked package is in upwards of $2,500. The conventional package is more reasonable though is still several hundred dollars. The benefit is you do not need multiple versions for each radio (unlike Motorola).

    This is a large and very visible forum. We cannot jeopardize the ability to provide the RadioReference services by allowing this activity to occur. Please respect this.

Fixed: Issues with importing Talk Groups from RR CSV Download

Status
Not open for further replies.

w2lie

New York DB Admin
Database Admin
Joined
Mar 2, 2004
Messages
1,462
Location
Long Island, NY
I've noticed tonight that I am having issues importing a Radio Reference CSV Dump into the Group call section of the G-Series PPS.

It looks like a heading has changed on the export, at least on the systems I am importing tonight for a customer's profile.


The issue is that the second column is called "HEX". On earlier dumps of the CSV's, the second column was called "SUBFLEET".

My workaround at this time is to open each CSV file and change the heading of the second column. This fixes the import issue.
 

w2lie

New York DB Admin
Database Admin
Joined
Mar 2, 2004
Messages
1,462
Location
Long Island, NY
Can you post a link to the system in the database you are having issues with? I would like to see how it looks when I export it to a CSV file and also try to import it into my copy of PPS.
 

Webodisk

Silent key.
Database Admin
Joined
Dec 18, 2002
Messages
1,181
Location
Virginia Beach,VA
It seems affect to all imports, I tried NC VIPER yesterday got same error, edited CSV header from HEX to subfleet worked perfectly
 

rivardj

Member
Joined
Dec 19, 2009
Messages
251
Location
Michigan
That second column should never have been labeled as Subfleet, not aplicable to P25 systems. Changing it to Hex and populating it with the correct data makes sense.

I discovered the change a few days ago when I tried to up date my Excel Workbook that I use to create files in the proper format for DSDPlus and OP25. It took me about an hour to update my Workbook to accept the new file format.
 

LEH

Member
Premium Subscriber
Joined
Jan 23, 2003
Messages
1,467
Location
Yorktown, Virginia
That second column should never have been labeled as Subfleet, not aplicable to P25 systems. Changing it to Hex and populating it with the correct data makes sense.

I discovered the change a few days ago when I tried to up date my Excel Workbook that I use to create files in the proper format for DSDPlus and OP25. It took me about an hour to update my Workbook to accept the new file format.
So are you saying you got your TG file to import with 'Hex'? I messed around with two TG files last night, one with 'hex' values after the decimal and the other without any values after the 'decimal' field. If the header row had 'hex' in either case, it would not import.

I won't argue that 'subfleet' makes no sense, but that is the accepted format. Hopefully a fix to allow both may come forth (making 'hex' the preferred, but allowing older files with 'subfleet' to also still work).
 

jpolich7

Member
Premium Subscriber
Joined
Jan 16, 2006
Messages
66
As fmulder13 pointed out elsewhere, the problem persists. As I posted above, the fixes suggested do not work for Phoenix RWC and according to other posts the fixes do not work for them either. Appears to be a bug in the RR data files or the Unication PPS import utility.
 

w2lie

New York DB Admin
Database Admin
Joined
Mar 2, 2004
Messages
1,462
Location
Long Island, NY
I was able to import the Phoenix RWC system if I modified it.
I also imported the California East Bay Regional Communications System, The North Carolina VIPER system, Wake Systems, and Durham Systems, as well as local systems in NY.

So far any system I needed to import for customers has been successful.

What if you take the systems you couldn't import and change the headers to match what can import?
What happens if you remove the HEX values completely?

Can you share what systems didn't work for you? I'd like to see if I can get them to import.
 

jpolich7

Member
Premium Subscriber
Joined
Jan 16, 2006
Messages
66
PPS V0.3.17 Beta4 will not import Phoenix RWC talkgroups. Error message is same as others report for other systems in other locations: data format wrong. Editing HEX and other suggestions do not help, as mentioned a couple weeks ago. Also, files posted by others that they reported as working will not import. There is a new flaw in the RR files for Phoenix RWC and some/all other systems or in the PPS software or both.
 

rivardj

Member
Joined
Dec 19, 2009
Messages
251
Location
Michigan
LEH,

I muddied the waters with my comment. My situation has nothing to do with Unication hardware or associated software. I have an Excel Workbook that I created to generate files from Radio Reference csv files that are compatible with DSD+ and OP25 systems. I had the same sort of issue as the Unication software has when the change was made to the source files from Radio Reference. I was just acknowledging the issue.

Sorry for the confusion.
 

KevinC

Totally Awesome Moderator
Super Moderator
Joined
Jan 7, 2001
Messages
7,342
Location
Home again...
PPS V0.3.17 Beta4 will not import Phoenix RWC talkgroups. Error message is same as others report for other systems in other locations: data format wrong. Editing HEX and other suggestions do not help, as mentioned a couple weeks ago. Also, files posted by others that they reported as working will not import. There is a new flaw in the RR files for Phoenix RWC and some/all other systems or in the PPS software or both.
I just tried with the beta on RWC and it worked after I made the header change.

85425
 

fmulder13

Member
Joined
Sep 1, 2006
Messages
226
Location
Minneapolis, MN
I was able to import talk groups from Minnesota's statewide ARMER system, after using Excel to modify the "Hex" label to "Subfleet." Using Apple Numbers failed. Marking the same line "SubFleet," and "subfleet" also failed. It had to be "Subfleet" to work for me.
 

RFBURNS2

Monitoring is not a spectator sport.
Joined
Dec 9, 2018
Messages
28
Location
Over here
Thanks all for the fix. Changing the header to “Subfleet“ worked for me. I use google sheets. DL file from RR. Right click file and open in notepad. Remove hex replace with Subfleet.
 

W4BLR

Member
Premium Subscriber
Joined
Jun 24, 2014
Messages
5
Location
Lenoir,NC
OK Guys. Changing the header worked as far as importing the file...but...it will not import the ID tags ,HEX or otherwise. I will have to type in all the the ID's. What gives?
 
Status
Not open for further replies.
Top