chuot
Unable to record LTR from ProScan
When trying to record LTR it appears RDIO does not like the way LTR formats the talkgroups with dashes. Is there another way around this, I am using the recommended proscan file formatting.
You will for sure have to adjust the ProScan formatting to match your dirwatch mask definition, or vice versa. What does your dirwatch mask look like?
My dirwatch mask is as follows #DATE_#TIME_#SYSLBL_#GROUP_#TGLBL_#TGMHZ with the ProScan file name set to be %YY-%M-%DD_%TT_%S_%G_%C_%FT which is Year_Month_Date_Time_System_Group_Channel_Talkgroup. However LTR has Talkgroups formatted like this '0-06-002' which I think is confusing rdio. Is RDIO smart enough to create its own TGs if I was to remove the TGID from the formatting?
I have analog channels on the same device that pull through no issue, although it appears proscan takes the frequency and makes that the TG. That would not work for LTR as since it is trunking, many talkgroups can be using the same frequency.
Actually, now that I look at the mask, I need it to be set to TGAFS, i will need to figure out how to acomplish this while retaining the ability to record analog channels as they come off the same scanner, but use the TGMHZ mask, any suggestions?
There has not, Rdio was still not pulling it in even when set to TG AFS, I did do a temporary workaround by setting the home repeater frequency up in SDRTrunk but that means missed and unwanted calls as if the home repeater is in use it will kick the TG over to another frequency
So I gave this a shot today, see below for my config info, but I am now getting an error that the TG does not exist. I went to try to manually create the TGs in the Systems tab but it wont let me do it in AFS format 0-06-02. So in the meantime I have set the DirWatch to direct everything into a shared TG on Rdio but this is not ideal.
RDIO Mask: #DATE_#TIME_#SYSLBL_#GROUP_#TGLBL_#TGAFS
System 5 set as an AFS system on Options tab.
ProScan file format
In its current state, the latest version of Rdio Scanner does not interpret 0-06-002 as AFS when using the #TGAFS metatag. And the AFS system option is only for displaying the talkgroup ID in AFS format on the main screen.
I will modify the #TGAFS metatag in the upcoming v7 so that it can decipher talkgroup ids like "0-06-002".