UniTrunker first public beta

[grosminet]

i retreive unitrunker work fine .

In france , we have (french cultural exception) some strange MPT1327 network . I order to work with Trunksniffer , i had to select : Ignore SYNC bit . Universal trunker said me : no signal . I m sure networks are working because i m using trunksniffer 3 , working fine .
Thanks to any comments

 

[SCPD]

Uni-Trunker does not support ingoring sync bits. Please try the next version (available soon) - if it does not work I may need to request an audio recording of the MPT1327 signal.

-rick

 

[joescanner]

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

FOr the text-labels, what is the maximum length?

 

[SCPD]

About 20 characters - you can make it as long as you want but there is only room enough to see roughly 16 to 20 characters. Use the "Notes" field to hold more verbose information - about 64 to 72 characters.

-rick

 

[joescanner]

Cool. I just didn't want to overflow any buffers or anything when I did a mass import of some data with additional identifiers. Thanks.

 

[BANDIT]

I'm getting itchy.

 

[SCPD]

Sorry guys ... I hope to start a new thread titled "Unitrunker Second Public Beta" soon.

 

[Joseph11]

Awesome! I can't wait.

 

[Forts]

It's under the system finder ...

From the main menu, type "F" for [F]ind; type "S" for ystem; press TAB key once; select type of system (eg. "Motorola"), press TAB key; type in the system ID; press TAB key; next to "RR DB User Id" - type your user id; press TAB again; and type your password.

Hmmm.... I can't seem to make this work. I go to Find, Then System and I can only tab between the SysID and System Type. I don't see anything for entering my RR user name and info.

 

[BANDIT]

Same here as it doesn't work for me either. Just tabs back and forth.

 

[Joseph11]

rfmobile: I tried to send you a PM about the Cecil County, MD EDACS system, but your PM box is full. Please empty it.

 

[ogoun]

Rfmobile,

Things seem to have quietened down a lot here recently.. Perhaps, like so many of us, life/work has caught up with your free time.. If lack of time for this project is a problem, then I am happy to volunteer to take on some, or all of the continuing code development for unitrunker. Send me a PM, and/or post the source for what you have done so far, if you want some extra assistance with this

Cheers,

Pete

 

[tennesseefreq]

Just wondering if this next beta will support the 300-400 Mhz 9600 baud trunking?

 

[SCPD]

Yes it does ... as does the first beta.

 

[tennesseefreq]

I wonder if I have a older version or something. It refuses to decode this 300-400 Mhz range system. I have tried it on two different computers. I know I saw on here where someone else had tried and had problems sometime ago. Thanks for the info though I will try it some more. You think it could be because of using a straight line in without a data slicer?

 

[SCPD]

You may need a small buffer amplifier to isolate the radio (with it's relatively weak signal) from the strain of the microphone input. While listening to the radio, you may hear the audio level drop as you plug the cable for the discriminator tap into the microphone input.

If it does not work for you using line input, try switching to microphone input. Sometimes that helps.

An easy way to tell is to look at the waveform using a program like dib-scope.

The data slicer won't work for 9600 bps APCO systems; you have to use sound input.

-rick

 

[tennesseefreq]

Yeah I have been talking to another guy having the same problem, but only on this type of system. He has also tried it on more then one computer and the slicer which I guess doesn't work. On my laptop that all I have in mic in. I will try that on my main PC too. I will keep you posted and maybe get this other guy in on this as well.

Thanks,
Dustin
GO VOLS!!!!

 

[jharr465]

Decoding 300-400 mhz Systems

I have successfully decoded a 380-390 mhz 9600 APCO system using the sound card input. However, I had to try three different sound cards before I found one that would work. and then the best decode rate I can get is around 60%, which is good enough to decode the system fine. The adjustments on volume for the mic input are very sensitive -- about 45% works good but more or less degrades the signal rapidly. The card that works is an old SoundBlaster PCI card that I had trouble finding drivers for XP. The radio is a BC796D with a discriminator tap and I feed through the mic input - no boost. The nice thing about decoding 9600 APCO systems is that it directly displays the actual channel frequencies, not the offsets. I am looking forward to the next release and increased functionality. Thanks for the wonderful tool, Rick!

John

 

[tennesseefreq]

Well thanks John.... Oh by the way I'm the one you talk to in e-mail. I guess I should have asked you.

Thanks,
Dustin
GO VOLS!!!!

 

[BANDIT]

Uniform Trunker and DSP

Are we there yet Daddy? All kidding aside Rick, keep in the back of your head to add DSP and auto AGC to Uniform for the digital comms. It would be better than anything we have so far from the top two scanners. You know it can be done don't you?