UniTrunker - turn off EDACS "Dat" messages?

[brandon]

Is it possible to turn off the EDACS Dat messages or have the option to ignore them. I get these in both the Destination Party and Calling Party fields. They look like i-calls but the CT column says "Dat" instead of "Analog". If you listen to the freq on a scanner when this occurs there is just EDACS burping noises. Is it possible to have UniTrunker ignore these since they just clutter up the display window. They also continously flash throughout the LCN order and make it harder to visually watch legit traffic.

Here is an example of what I am referring to.

Thanks for the help.

 

[blah546]

Currently, I don't think there's anyway to ignore them. I believe they're data transmissions and technically are legit as far as the system is concered and what channel is doing what, but I know what you're getting at.

 

[cg]

If the radio IDs are data only radios, try making them BLACK or very dark (although I think that may need to be edited from the file as I don't think choosing black on the menu will work)

chris

 

[BJ_NORTON]

I change all of mine to dark blue. They kind of blend into the background

 

[CrazyCalifornian]

The Radio ID's on the Riverside Edacs system that Receive Data Bursts (MDT Messages), are valid Sheriff Units. If you monitor this site for awhile, you'll also see these Radio ID's in a normal conversation...

Also I see that LCN's 29 to 31 are being displayed as a valid channel, when in fact these should be treated as a message:
LCN 0: // CW ID?
26: // Downlink Channel
27: // Reserved
28: // Convert to Callee - Where someone wants to talk on a group already in use
29: // Call Qeued - System has Placed the Call in Que
30: // System is Busy
31: // Call Denied - Radio Not Allowed on the System

Jay

 

[SCPD]

Hi Brandon;

Is it possible to have UniTrunker ignore these since they just clutter up the display window.

No ... that display is meant to show just how busy the system is. If you removed the DAT calls, systems like this would appear under-used. Seeing nearly every channel occupied combined with queue'd and busy messages tells you the system has reached max call capacity.

Speaking of queue'd and busy messages, Jay brings up a good point.

Also I see that LCN's 29 to 31 are being displayed as a valid channel, when in fact these should be treated as a message

These should appear in the Affiliations history along with other non-call events. There was a bug a while back where some of these messages leaked through as voice calls. I haven't heard any complaints on this in a while.

Brandon - please check your channel list. If these LCNs were added due to that bug - the "Last Seen" timestamp should be form the last time you ran the old version before upgrading. If you have a recent timestamp on any LCNs numbered 27 and above - please let me know. Hopefully not.

You can of course, delete those channels. They serve no purpose and reduce the scroll area for the detail views underneath.

 

[brandon]

Thanks for the input. You were right about the LCN above 27 they had 2005 time stamps. Went ahead and removed and will report back if they return.