SDS100/SDS200: Way to log site/freq signal strength, error rate?

[NoahWL]

I have a favorites list I have set up for a certain long drive I make fairly regularly. I'm scanning a statewide trunked system with 10+ sites along my route. The sites and talk groups for each particular area on my route are controlled via GPS so I can minimize unnecessary scanning of sites out of range. My goal is to scan at most 3 sites at a time, preferably 2 (I have a favorites list for each direction of the route so I can ignore sites/talkgroups that I have passed, but scan those up ahead).

Obviously I cannot watch the signal strength, digital error rate, etc, for each site's control channel while I'm driving, much less how the decode rate holds up when the scanner switches to traffic channels. Is there a way I can log these statistics over time while I drive so I can fine-tune the location boundaries for each site? I have recording enabled but that only works when there is active traffic. Bonus points if the scanner's GPS location can be logged as well so I don't have to cross-match the scanner's time with a route logging app on my phone.

Would the scanner's debug log be a way to do this? I couldn't find much information on interpreting the log info. I'd prefer something easy to use but if I have to I guess I can write a simple tool that pulls signal strength and time/location from the logs.

 

[nessnet]

Are you using rectangles?

If not, start there.

 

[NoahWL]

Are you using rectangles?

If not, start there.

Yes. I want to fine-tune the boundaries of the rectangles to scan as efficiently as I can with my single receiver. No point in scanning a site nearby if the signal doesn't make it to the portion of the road I'm on, for whatever reason. Or, if I think I should be hearing something I'm not, it's a good indicator I should try a different filter setting for that area.

 

[nessnet]

Because of the way RF propagates, always use circles for sites.
Also, your range setting is key, as is using well thought out quick keys..
A range of 0 will get your 'changeover(s) at the boundaries.
1 - a mile before, etc, etc...

Filters...
They are are almost 100% location dependent.
In a mobile environment, I would leave off or normal.

 

[NoahWL]

Because of the way RF propagates, always use circles for sites.
Also, your range setting is key, as is using well thought out quick keys..
A range of 0 will get your 'changeover(s) at the boundaries.
1 - a mile before, etc, etc...

Filters...
They are are almost 100% location dependent.
In a mobile environment, I would leave off or normal.

Range is set to 0. Rectangles are ideal in my case as this is for a known route on mostly straight highways. It's easier to set up the boundaries with a single rectangle, whereas with circles I'd need multiple of them to avoid "spilling over" state boundaries so I'm not scanning the state I just left as a travel parallel to it. If my route was more uncertain I'd agree circles would be the way to go, but in this case I know exactly where I'll be and exactly what I wish to scan. I just want to fine tune (i.e. down to the mile) where I begin scanning specific sites.

Filter of off/normal on my 700/800 MHz trunked systems does not work well; wide invert or wide normal is best for keeping the bursty cellular signals out of the passband. I currently have the VHF/UHF systems set to normal, but off or invert might be better. I can't know unless I have a more continous way of logging the strength, noise, BER, etc. at specific locations.