wwhitby said:
I was wondering if you wouldn't mind sharing the algorithm that links the groups to the subscribers?
I'm not sure what you mean by algorithm. If you're asking how the data in the text file is laid out ... here 'tis.
comint said:
Could you please supply a list of the field_names for all the records in the various files used by UniTrunker. Would make it easier to work out what the program is doing (or NOT doing, as the case may be).
Just beware that the file structure may change in future releases (someone has already fussed at me for not including a version number as part of the file structure). The text files contain CSV (also known as CDF) data - very easily imported into a spreadsheet program like Excel. Each line of text is a record. For the following file types, the records are laid out like so:
RID file ...
radio-id #, listen (1 or 0), lockout (1 or 0), RGB color, text-label, first-seen-timestamp, last-seen-timestamp, talkgroup, text-notes
GID file ...
talkgroup #, listen (1 or 0), lockout (1 or 0), RGB color, text-label, first-seen-timestamp, last-seen-timestamp, text-notes
HZ file ...
site #, LCN #, control (1 or 0), listen (1 or 0), lockout (1 or 0), frequency (hertz), CTCSS tone, DCS, text-label, first-seen-timestamp, last-seen-timestamp, text-notes
SIT file ...
site #, listen (1 or 0), lockout (1 or 0), RGB-color, text-label, first-seen-timestamp, last-seen-timestamp, text-notes
SYS file ...
system-id, type (Motorola, EDACS48, etc.), listen (1 or 0), lockout (1 or 0), trunked (1 or 0), RGB-color, text-label, first-seen-timestamp, last-seen-timestamp, delegate-system-id, text-notes
I won't bother documenting the FLT and PLN files - these may change (the fleetmap feature is broken so this file is most likely to change).
Also, someone has previously complained about the program not saving the priority for a talkgroup. Looking at this, I think I know why! I'll need to insert a column for "priority" - most likely just before the "text-notes" column.
-rick