All are listed for 2 watts out. So HTs?
Iowa Statewide Interoperability Communication System (ISICS)
All are listed for 2 watts out. So HTs?
nd5y
Member
90.531 (b) (3), (4) and (7) limits the ERP to 2 W on the 700 MHz regional low power channels, national low power itinerant channels, and by airborne aircraft on the national air-to-ground channels.
Maybe they have radios capable of 2 W or less on certain channels. Maybe they ignore the FCC rules. I don't know what they are doing.
What is the best way to figure out what the actual frequencies are. Lower down the page you linked, I would like to have a generic system in the scanner for listening t=for transmissions:
(7) Air-ground channels. The following channels are reserved for air-ground communications to be used by low-altitude aircraft and ground based stations: 21/981, 22/982, 101/1061, 102/1062, 181/1141, 182/1142, 261/1221, 262/1222, 659/1619, 660/1620, 739/1699, 740/1700, 819/1779, 820/1780, 899/1859, and 900/1860.
(i) Airborne use of these channels is limited to aircraft flying at or below 457 meters (1500 feet) above ground level.
(ii) Aircraft are limited to 2 watts effective radiated power (ERP) when transmitting while airborne on these channels.
(iii) Aircraft may transmit on either the mobile or base transmit side of the channel pair.
nd5y
Member
See https://wiki.radioreference.com/index.php/700_MHz_Public_Safety_Band_Plan for the FCC channels numbers.
A complete list of nationwide frequencies is at https://wiki.radioreference.com/index.php/Common_Public_Safety and several different database pages at https://www.radioreference.com/apps/db/?coid=1&tab=nationwide
A complete list of nationwide frequencies is at https://wiki.radioreference.com/index.php/Common_Public_Safety and several different database pages at https://www.radioreference.com/apps/db/?coid=1&tab=nationwide
nd5y
Member
Application for 800 MHz SOA channels.
ULS Application - PubSafty/SpecEmer/PubSaftyNtlPlan,806-817/851-862MHz,Conv - 0008060585 - IOWA, STATE OF - STATEWIDE INTEROPERABILITY BOARD (ISICSB)
ULS Application - PubSafty/SpecEmer/PubSaftyNtlPlan,806-817/851-862MHz,Conv - 0008060585 - IOWA, STATE OF - STATEWIDE INTEROPERABILITY BOARD (ISICSB)
I am sorry but I am not sure what is SOA
nd5y
Member
I assume SOA means Scene of Action. That's what tactical simplex channels are called in some places.
https://forums.radioreference.com/industry-discussion/50491-soa-frequencies.html
While not authoritative, this thread indicates SOA is "scene of action".
While not authoritative, this thread indicates SOA is "scene of action".
This is a start. Running a decoding program will get you the rest of the frequencies, site NAC, and other interesting information.
Tim
autovon
Ø
- Joined
- Jul 10, 2008
- Messages
- 431
OK, here we go. Site 141 isn't up currently, but I'll post that when it's back on. If there's a different thread preferred to post ISICS finds in, please let me know. Once TGs start showing up, I'll submit those the normal way.
770.43125c 04C9h-0134
site ID 034
769.93125a
770.18125a
adjacent site 110 (T010A) 4C9 770.45625
770.45625c 04C9h-0110
site ID 010
769.95625a
770.20625a
adjacent site 134 (770.43125) and 141 (774.29375)
770.43125c 04C9h-0134
site ID 034
769.93125a
770.18125a
adjacent site 110 (T010A) 4C9 770.45625
770.45625c 04C9h-0110
site ID 010
769.95625a
770.20625a
adjacent site 134 (770.43125) and 141 (774.29375)
The 4 numbers following the system ID are the RFSS and Site Number. So Ø4c9h-Ø134 means System ID 4C9(in hex) and RFSS Ø1 Site # 34. The RFSS and Site # are in decimal form. Hopefully this helps you moving forward.
You can start see how the frequencies are being re-used as more sites are coming on-line.
Tim
I made a google earth .KMZ file. Ballons are single sites. Push pins are simulcast cells. Red dots are unidentified sites. Work in progress.....
Tim
Tim
Des Moines to join ISICS
Des Moines City Counsil voted last night to go ahead with a proposal to join ISICS.
http://www.dmgov.org/Government/CityCouncil/Communications/2018/18-396.pdf
Looks like the additional sites should be active and switchover in 2021.
Des Moines City Counsil voted last night to go ahead with a proposal to join ISICS.
http://www.dmgov.org/Government/CityCouncil/Communications/2018/18-396.pdf
Looks like the additional sites should be active and switchover in 2021.
- Joined
- Aug 23, 2002
- Messages
- 3,620
I've skipped the other pages above, but here is a reminder for those submitting information to the database on this system:
Sites
Please state which RFSS it is and the site number independanty. For example, do not submit RFSS 1, Site 50 as Site 150.
If possible, please submit the site NAC as well.
Most common decoding software packages will give you the site, NAC, neighbors etc. Scanners with built in decoding are typically not as specific.
If possible, please include the area where you are hearing a site. As they have been using blanket licenses on build out, its difficult to properly GPS the sites. What should not happen, is putting a site with a statewide range or no general location reference. Submitting "Here are all the channels for site 50" and no location, makes it hard to place it properly in the backend.
It makes our life easier as well as keeping the data as accurate as possible.
Talkgroups
Make sure you specify what county, city/town (agency) and if its TDMA or FDMA. Majority of the talkgroups are TDMA, and a bunch of submissions have been silent about the mode of operation - so looking at the DB, its about 50/50.
Based on feedback/concerns/complaints, I went in polished up the database.
Its setup similar to how most statewide systems are (should be). The basic organization is:
Interoperbility talkgroups
Highway Patrol
State Fire
State EMS
Emergency Management
DOT
Federal Agencies
Counties
-Towns/cities
Non-governmental agencies/regional transit, etc.
Once the framework is in place a little better, it will read pretty nicely, have all the correct GPS ranges and will self maintain itself. Just when these are new they are a bit chaotic.
Sites
Please state which RFSS it is and the site number independanty. For example, do not submit RFSS 1, Site 50 as Site 150.
If possible, please submit the site NAC as well.
Most common decoding software packages will give you the site, NAC, neighbors etc. Scanners with built in decoding are typically not as specific.
If possible, please include the area where you are hearing a site. As they have been using blanket licenses on build out, its difficult to properly GPS the sites. What should not happen, is putting a site with a statewide range or no general location reference. Submitting "Here are all the channels for site 50" and no location, makes it hard to place it properly in the backend.
It makes our life easier as well as keeping the data as accurate as possible.
Talkgroups
Make sure you specify what county, city/town (agency) and if its TDMA or FDMA. Majority of the talkgroups are TDMA, and a bunch of submissions have been silent about the mode of operation - so looking at the DB, its about 50/50.
Based on feedback/concerns/complaints, I went in polished up the database.
Its setup similar to how most statewide systems are (should be). The basic organization is:
Interoperbility talkgroups
Highway Patrol
State Fire
State EMS
Emergency Management
DOT
Federal Agencies
Counties
-Towns/cities
Non-governmental agencies/regional transit, etc.
Once the framework is in place a little better, it will read pretty nicely, have all the correct GPS ranges and will self maintain itself. Just when these are new they are a bit chaotic.
I just tried this and it shows one site.
The newly added ISCIS Site 54 & 58 locations are showing in the Bermuda Triangle.
I moved the unknown sites further North out of the Bermuda Triangle. We can't GPS them until we know where they are at.
Tim
Similar threads
- Locked
- Locked
- Locked