Port aux Basque Newfoundland

[jlo]

update in stephenville for what i have found

i've been monitoring the rcmp system today to see what i can get.
i hit the tune button on my pro 106. punched in both 161.2500 and 160.5900
the 161.2500 has the continuous monitoring sound on it and also gives me some details.
P25 161.2500
99% no2c w:-----
flashing back and forth
sy:--- r--- s---
then punch in 160.5900
DG 160.5900
p25 02c
vc* 1# s tgid 63504
now the tgid was really weird.
63504 seems to be stephenville, ramea
then as some other memebers were called from other are this would change.
here is what i found.
cornerbrook 61968
46160
30704

JAY i recorded some videos.
where you can see the tgid's.
could you send me a message with your email so i could send them to you if you don't mind.
also after i recorded the vids.
what i listed from top to bottom had reversed and now i here the continuous sound on the 160.2500

 

[Jay911]

If you're looking for me, jay911@gmail.com is my email - fire away.

 

[jlo]

no comms

will since i last posted yesterday. i now have had no comms on 160.5900 anyone from this area have the same issue. and or have fixed it.

 

[jlo]

back again

not sure what was on he go.
they are back on again now. under the tgsy and or the single channel 160.5900

 

[struct_dj]

Its been really weird lately jlo, 160.5900 used to be the control channel 161.2500 was talk, but now they seem to flip these two channels back and forth from control to talk a few times a day now, and for some reason the talk channel stays on even after transmission, with a bit of constant static that you can only hear when volume is turned all the way up, and you have to press scan to get it scanning again...very weird as of late i dunno what the hell their up to.

 

[struct_dj]

I also found a new control channel today 160.5950 seems to mirror the current control channle

 

[struct_dj]

Now 160.5950 isnt a control shows as a talk now WTF

 

[mikewazowski]

Nothing strange.

Trunking systems can rotate the control channel through all available repeaters on a daily basis.

If you've got the channels programmed in as a trunking system, there shouldn't be a problem.

 

[Jay911]

Nothing strange.

Trunking systems can rotate the control channel through all available repeaters on a daily basis.

If you've got the channels programmed in as a trunking system, there shouldn't be a problem.

Except that we're still discovering this trunk system.... :roll:

struct_dj, if .595 becomes a control channel again (and as the poster above indicates, it's very common for radio systems to switch the control channel anywhere from once an hour to once a week, mainly to keep the repeater hardware from burning out), throw Unitrunker on it for a while and see if you can get its LCN and the LCN of any other channels it might make mention of.

Just noticed - you are talking about 160.590 and 160.595. That is close enough that they normally can't be used as distinct, separate channels. Check to see if you are hearing the same thing on both of these frequencies always. If you are, odds are excellent that one frequency is false, that you're receiving "bleedover" from the other.

If you have 160.59 and 161.25 acting as a pair (one a continuous TG and the other voice traffic), I'd program them together in the same TSYS. Also, while you're not listening (i.e. when asleep), run Unitrunker. That will give us some great info to figure out.

After running Unitrunker for a while, after you shut it down, do me a favor - send me the data file and log files. If you're running Unitrunker with the default install info (and you probably are), they will all be in one folder. Do a search with Windows Explorer for "Unitrunker.xml". When you find it, go into that folder and zip up that file and any others like it (Unitrunker.xml.1, Unitrunker.xml.2, etc) into a zip file. Even Windows' "Send to ... Compressed Folder" will do. Then, in that folder, if you have any folders that start with S, i.e. "S00000001", etc., go into them, and zip up the UniTrunker-*.LOG files that are in there (plus any *.Z files in there). Email all those to me and I'll go over them, exploring what you have found in Unitrunker and see if I can't help you figure out which channels are which.

Also, jlo, if you were meaning me when you said you had some videos to send, I didn't receive them.

 

[struct_dj]

Ok jay ill run it after when i get a chance, also do you have any idea why the talk channel is sticking after transmission, which forces me to press scan to get it scanning again....I`ve also noticed if I make the talk channel a conventional object p25, it won't scan at all, will just hang there and pick transmissions and sounds like a low static noise in between transmissions when i put my volume on bust, this only started a few weeks ago and is driving me crazy

 

[Jay911]

I'm not sure why it's "sticking". I thought I saw someone else reporting that behavior on another P25 system somewhere else recently, though. I wonder if it's a non-standard P25 system, or maybe TDMA. Let me try to dig up the other post I saw about this and get back to you.

 

[struct_dj]

I'm not sure why it's "sticking". I thought I saw someone else reporting that behavior on another P25 system somewhere else recently, though. I wonder if it's a non-standard P25 system, or maybe TDMA. Let me try to dig up the other post I saw about this and get back to you.

Thanks much appreciated as always jay.

 

[Jay911]

I can't locate the thread I was thinking of - maybe it was here, or maybe it was relating to your situation. Sorry.

However, this thread - http://forums.radioreference.com/radio-shack-scanners/205753-pro-106-problem.html - has a tremendous amount of info that will help guys like me figure things out. As you can see, other people have already done some helping to Michael and looked some of the stuff up. Somewhere in there (on the 2nd page, I think) is a suggestion to add frequency 15x.xxx to your TSYS. I would try that. There may be voice traffic on that frequency.

I still don't know why the system is hanging on that frequency. Besides the fact that the carrier signal (essentially the voice transmission) goes away, trunk systems usually use what's called an "end code" or "turn-off code" to signal to the radios that a transmission has ended. Your scanner is smart enough to recognize this. It could be that you are getting so poor a signal that you are not receiving the end code. How decent is your signal strength?

One last thing to think of is to try to play with your squelch a little. Turn it in the opposite way to the point where the scanner makes noise, until the noise stops, then give it another 1/8th of a turn or so. Maybe more. A tight squelch shouldn't cause problems with trunking, but stranger things have happened.

I'm going to go through that stuff that Michael posted to the other thread - it's very similar to what I'm asking you to post from your Unitrunker configuration. It should help us figure out, at least, what the general makeup of the system is, if not help get you listening properly.

One more question - what do you use to program the scanner? Do you do it by hand, do you use PSRedit, WIN500, etc, or what? I personally use WIN500 - if you are using that, I can try to program the system in my copy and send you the resulting data file, so you can load it and program it into your scanner.

 

[struct_dj]

Not sure what you mean by add frequency 15x.xxx.... as for the squelch, i`ve tried it in every position, results stay the same no matter where it is, my signal seems fine at 5 bars. As for using a program I do not, I program it by hand, tsys p25 auto add my frequency's leave all defaults and away I go.... worked fine for me in the past.

 

[struct_dj]

hey jay i was testing my friends 396T, it works fine when trunk as mot 800 p25, but when talk channel is programed as a conventional, it hangs there too and say LNK in between transmissions, but his mot trunk p25 system handles the system fine, doesn't hang after transmission

 

[struct_dj]

Jay i should also note that sometimes it doesn't hang, but most of the time it does

I should note that when i listen to the talk channel in FM mode, it sounds like a motor boat

 

[Jay911]

Not sure what you mean by add frequency 15x.xxx....

Sorry. In that thread, somewhere, is a frequency someone's identified as being part of the system. It's in the 150 MHz range. I can't remember it right now exactly, but it's something like 154.325. Check the thread, find the frequency, and add it to your TSYS.

as for the squelch, i`ve tried it in every position, results stay the same no matter where it is, my signal seems fine at 5 bars. As for using a program I do not, I program it by hand, tsys p25 auto add my frequency's leave all defaults and away I go.... worked fine for me in the past.

I don't know what is causing the transmissions to "stick", then. It could be something they have done to the system that causes transmissions to stay open. Though I see you say the Uniden scanner doesn't lock up. That implies there's something that the Uniden (internal) programming handles better than the GRE.

 

[struct_dj]

Thanks jay, I'm sure the channel is staying open, I can tune right to it and it gives me info, which should only happen on transmissions not sure why they have it like this, wasn't like this a few weeks back.

 

[jlo]

the Stephenville area also has a 547 for the talkgroup.
i confirmed this on the weekend also.
it would show the 546 and then it seems when cornerbrook calls came through it then was showing 547 on the screen.

 

[jlo]

hey struct i did what jay had said with the instructions about putting it as a wildcard for the pro106
and mine now only stops on it when voice is heard.
but i loaded my 396xt and it too won't stop on it. i have to put it on hold
in order to hear anything.