|
|
|
|
| Scanner Programming Software This is the place to discuss scanner programming and control software. |

03-07-2008, 06:21 PM
|
 |
Member
|
|

Audio Feed Provider
|
|
Join Date: Nov 2006
Location: Paragould/Greene County AR
Posts: 1,338
|
|
WIN 97/PRO 97 Problem
I have a problem with my pro 97 win 97 software. I have trunking LTR banks saved in the scanner that I have found by searching and when I open win97 to edit things on it it tells me that 0-02-002 etc. is not a valid format it must be in the A-AA-AAA or AAAAAA format..I have tried both ways and neither way will accept it, If there is no way edit it in the software with it and I erase them from the software, How Can I get them back, What should I do... I posted in the Radio Shack Scanner Forum and They sent me here because we thought it was a software glitch.. What should I do to fix it?
Thanks!
__________________
Brian Paragould/Greene County Arkansas 72450
|

03-07-2008, 06:51 PM
|
|
|
Win97 Question
I just started messing around with an LTR system on my PRO-2055 using Win97. I suggest you check all the settings as follows;
1. On the "Channels" Tab, make sure "Type" is set to LTR.
2. Make sure your frequencies are correct and in order, in the right channels.
3. Under "Rx Mode", those frequencies should be "LTR".
4. On the trunk side of the page, make sure the "DEC" button is selected.
5. Under the "ID" tab, make sure your UID follows proper format, which yours seems to, AND, (and this has happened to me,) make sure you don't have any "invisible spaces". By that I mean, make sure you didn't accidently hit the space bar before, within, or after the UID.
6. Make sure your frequncy entries don't have those spaces either.
I can't tell you how much time I wasted on ALL conventional and trunked systems because of setting errors or (most annoying) typing errors. Good Luck!
__________________
Eric
FDNY*EMS Captain
Citywide Dispatch Supervisor
KC2SDZ
WQKB645
|

03-07-2008, 06:54 PM
|
|
|
Ltr
Quote:
|
Originally Posted by btritch
I have a problem with my pro 97 win 97 software. I have trunking LTR banks saved in the scanner that I have found by searching and when I open win97 to edit things on it it tells me that 0-02-002 etc. is not a valid format it must be in the A-AA-AAA or AAAAAA format..I have tried both ways and neither way will accept it, If there is no way edit it in the software with it and I erase them from the software, How Can I get them back, What should I do... I posted in the Radio Shack Scanner Forum and They sent me here because we thought it was a software glitch.. What should I do to fix it?
Thanks!
|
I hit this in programming manually.
The talkgroup trunking type must be set to LTR. And manually the Pro-97 doesn't want the dashes in the TGID.
Also I've seen an LTR system where it sends the cwid on TGID 0-07-255 and all other channels (0-0x-255) the Pro-97 will not allow a 255 setting for the end number.
|

03-07-2008, 07:21 PM
|
 |
Member
|
|

Audio Feed Provider
|
|
Join Date: Nov 2006
Location: Paragould/Greene County AR
Posts: 1,338
|
|
Ltr
Quote:
|
Originally Posted by NW0U
I hit this in programming manually.
The talkgroup trunking type must be set to LTR. And manually the Pro-97 doesn't want the dashes in the TGID.
Also I've seen an LTR system where it sends the cwid on TGID 0-07-255 and all other channels (0-0x-255) the Pro-97 will not allow a 255 setting for the end number.
|
So how should I fix that?
__________________
Brian Paragould/Greene County Arkansas 72450
|

03-07-2008, 07:25 PM
|
 |
Member
|
|

Audio Feed Provider
|
|
Join Date: Nov 2006
Location: Paragould/Greene County AR
Posts: 1,338
|
|
I took the 03-03-255, 05-05-255 and 07-07-255 groups out and it accepted the others, however, these are the main three.. What will I have to do? Go back and add those in when they key up again?
__________________
Brian Paragould/Greene County Arkansas 72450
|

03-07-2008, 07:50 PM
|
 |
Member
|
|
|
Join Date: Mar 2007
Location: Jackson Square, East Weymouth, MA.
Posts: 710
|
|
LTR systems don't have talk groups higher than 253, 254 and 255 as the last three digits. Usually a 253, 254 or 255 are for the morse code identifier. I don't put them in. I think that the software is designed to reject that talk group out of hand. All the morse identifier does is send the call sign of the system.
__________________
Clyde, N1BHH, A Know Code Amateur Radio Operator, since 1970
WQBX787 = GMRS
Pro2055 Pro94A Pro2006 Pro2015 Pro2021 Pro164
Yaesu FT-60R, 8000R & 8800R, Motorola MTX9250, Alinco DR635T
|

03-07-2008, 08:27 PM
|
 |
Member
|
|

Audio Feed Provider
|
|
Join Date: Nov 2006
Location: Paragould/Greene County AR
Posts: 1,338
|
|
And most of the time when the clicking is going on (about every 4seconds or so) this is the three that pop up or when the morse code goes across the system this is the one that pops up. Now I know why this is.. Wonder why they do that anyway? Anyways, it's accepting them as long as I leave those off.. Thanks For The Help All!!
__________________
Brian Paragould/Greene County Arkansas 72450
|

03-10-2008, 10:05 AM
|
 |
Member
|
|
|
Join Date: Mar 2007
Location: Jackson Square, East Weymouth, MA.
Posts: 710
|
|
Read up on LTR here: http://wiki.radioreference.com/index.php/LTR
Actually only goes to 254 for group numbers.
__________________
Clyde, N1BHH, A Know Code Amateur Radio Operator, since 1970
WQBX787 = GMRS
Pro2055 Pro94A Pro2006 Pro2015 Pro2021 Pro164
Yaesu FT-60R, 8000R & 8800R, Motorola MTX9250, Alinco DR635T
|

03-10-2008, 11:52 AM
|
|
|
255
Quote:
|
Originally Posted by N1BHH
Usually a 253, 254 or 255 are for the morse code identifier. I don't put them in. All the morse identifier does is send the call sign of the system.
|
Folks- don't underestimate the information that's contained in the ID! With that ID you can look up the info on the FCC database and learn a great deal about the system such as possible additional channels, location of the transmitters and other systems the same company might own/operate. (But of course you won't want to listen to it after you know what it's saying.)
(Knowing morse has proven handy for me in lots of ways throughout my life. From reading blinking light signals on Navy ships to verifying nav aid ids while flying light aircraft, to being able to use radio system id for further research. Code has been very good for me!)
|

03-10-2008, 02:03 PM
|
|
|
Quote:
|
Originally Posted by NW0U
Folks- don't underestimate the information that's contained in the ID! With that ID you can look up the info on the FCC database and learn a great deal about the system such as possible additional channels, location of the transmitters and other systems the same company might own/operate. (But of course you won't want to listen to it after you know what it's saying.)
(Knowing morse has proven handy for me in lots of ways throughout my life. From reading blinking light signals on Navy ships to verifying nav aid ids while flying light aircraft, to being able to use radio system id for further research. Code has been very good for me!)
|
Can you elaborate on that......If btritch gave ya an ID could you teach us how to look it up in the FCC database?
__________________
Bubbaearle
Pro 62
Pro 83
Pro 97
GRE 500
BC 350C
|

03-10-2008, 03:17 PM
|
 |
Member
|
|
|
Join Date: Mar 2007
Location: Jackson Square, East Weymouth, MA.
Posts: 710
|
|
Quote:
|
Originally Posted by bubbaearle
Can you elaborate on that......If btritch gave ya an ID could you teach us how to look it up in the FCC database?
|
http://www.fcc.gov/searchtools.html
__________________
Clyde, N1BHH, A Know Code Amateur Radio Operator, since 1970
WQBX787 = GMRS
Pro2055 Pro94A Pro2006 Pro2015 Pro2021 Pro164
Yaesu FT-60R, 8000R & 8800R, Motorola MTX9250, Alinco DR635T
|

03-10-2008, 08:11 PM
|
|
|
Quote:
|
Originally Posted by N1BHH
|
Where from there do I go to search for system info with just a TGID?
I understand how to search the FCC Database........no stanger to that.......
Just never came across the function to search out system info with only a TGID.
__________________
Bubbaearle
Pro 62
Pro 83
Pro 97
GRE 500
BC 350C
|

03-10-2008, 11:34 PM
|
 |
Member
|
|
|
Join Date: Jul 2007
Location: Ames, IA
Posts: 2,541
|
|
I think they are talking about the System ID a TGID has no meaning outside of the system. The Ames and ISU systems have TGIDs that are the same.
__________________
Jerri
VX-5
FT-60R
Pro-97
BC246T
BC780XLT
BR330T
BCT15
Grundig Satellit 700
|

03-11-2008, 05:50 PM
|
|
|
Quote:
|
Originally Posted by n2mdk
I think they are talking about the System ID a TGID has no meaning outside of the system. The Ames and ISU systems have TGIDs that are the same.
|
I was hoping to learn something new.........
__________________
Bubbaearle
Pro 62
Pro 83
Pro 97
GRE 500
BC 350C
|

03-11-2008, 06:22 PM
|
|
|
ID vs TGID
Quote:
|
Originally Posted by bubbaearle
Can you elaborate on that......If btritch gave ya an ID could you teach us how to look it up in the FCC database?
|
The discussion seems confused between the two.
The ID I was referring to was the FCC Callsign (Station identifier) which is often sent in morse code. The system I'm working on currently sends: WNWJ207 in code.
A talkgroup ID is an arbitrary assignment by the system administrator. Blocks of TGIDs may be assigned to departments. This is of no interest or involvement by the FCC so they have nothing of use in their database.
|

03-11-2008, 06:23 PM
|
|
|
Something new
Quote:
|
Originally Posted by bubbaearle
I was hoping to learn something new.........
|
Well, you *could* learn Morse Code........ :-)
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 02:17 AM.
|
|
|
|
| |
|
|