Survival UK Forums

(6 November 2012, 23:26)Skean Dhude Wrote: [ -> ]I want to take this a step further and have a SUK verification system linked to the channels. Anyone interested in getting involved in the discussion let me know and I'll set something up.

HI SD

I was dead beat last night when I replied to you and made an error that I'd lke to correct. Paul's comment alerted me to this.

Channels 90 to 98 are the SUK emergency contact channels. they'd be open access channels that the survivor community could use to make contact after a major event.

IT IS CRITICAL FOR A COMMUNICATIONS SYSTEM TO BE PRIMARILY DESIGNED TO REAH AS MANY PEOPLE AS POSSIBLE. THIS IS ITS PRIMARY FUNCTION.

Channels 30 to 69 I've alloted to Private group usage and this is the area in which private ident could be setup if desired for the identification of individuals within the tribe so to speak.

[attachment=149]

Guys and girls and fellow SUK-ers

Attached is V3 of the proposed channel and frequency protocol for standard Survivor UHF and VHF radio coms.

Updates from last version are:

Coded PMR446 frequencies and tones defined (ch 11 -18)

Private IDENT ( Handshake) defined ( Ch 50)
Note that this configuration is for example only as it is illegal to use in UK at the current time. It is included for information, not to encourage any law breaking!

PMR emergency call channels ( coded and uncoded) defined (Ch 90&91)
Coded channel required as some Motorola PMR446s cannot operate with CTCSS turned off.

VHF emergency call channels (uncoded) defined (Ch 92 -94)
These are in the Amateur band and should only be used post SHTF, unless an Amateur license is held

UHF emergency call channels (un-coded) defined (Ch 95 -98)
These are shared Amateur and PMR446 LPD frequencies. They can be used straight away with compliant LPD devices such as the Midland Basecamp and Intek MT5050. On all non LPD specific devices these frequencies should only be used post SHTF, unless an Amateur license is held.

[b]This is all the development work I am going to do on this.[/b]

I need input from Marine experts on which Marine frequencies to include. PLEASE ADVISE.

Local Amateur repeater data must be input by individuals ( if they so choose) for their own location.
PLEASE DO NOT GO FIRING UP YOUR LOCAL REPEATERS BY DEAD KEYING THEM. THIS IS A GUARANTEED WAY TO GET ANGRY PEOPLE TRYING TO TRIANGULATE YOU ALERT OFCOM FOR PROSECUTION.

Not counting the Marine block that I’m asking to have defined, this leaves 62 channels un-occupies for user defined frequencies.

The big block of channels 30 to 69 are for individuals and groups to configure as they please, to meet their private reqiurements
==========================================

Once the Marine frequencies are defined, I’ll let this simmer for a week or two and will then create a code image for UV5r users.
We will sort out how to distribute it at that time, although the intention will ultimately to have it sitting in a future download area.

LS
If you want to pick up marine traffic and ship to shore communications then I’d suggest these simplex channels
06 - Intership Bridge to Bridge 156.300 S - 156.300
12 - Port Operations - 156.600 S 156.600
14 - Port Operations - 156.700 S 156.700
16 - Distress, Safety, & General Calling - 156.800 S 156.800
74 - Port Operations - 156.725 S 156.725
67 - Bridge to Bridge (1W) - 156.375 S 156.375
68 - Non-Commercial - 156.425 S 156.425
69 - Non-Commercial - 156.475 S 156.475
If you just want to communicate with other preppers/prepper groups then the following Duplex channels might be best
20 - Public Correspondance - 157.000 D 161.600
21 - Public Correspondance - 157.050 D 161.650
22 - Public Correspondence - 157.100 D 161.700
23 - Public Correspondence - 157.150 D 161.750
24 - Public Correspondence - 157.200 D 161.800
25 - Public Correspondence - 157.250 D 161.850
26 - Public Correspondence - 157.300 D 161.900
27 - Public Correspondence - 157.350 D 161.950
All of the above are dedicated Marine Channels and should only be used if you have a marine license and call sign. In a SHTF scenario I guess anything goes.

(7 November 2012, 11:57)gary5wift Wrote: [ -> ]LS
If you want to pick up marine traffic and ship to shore communications then I’d suggest these simplex channels
06 - Intership Bridge to Bridge 156.300 S - 156.300
12 - Port Operations - 156.600 S 156.600
14 - Port Operations - 156.700 S 156.700
16 - Distress, Safety, & General Calling - 156.800 S 156.800
74 - Port Operations - 156.725 S 156.725
67 - Bridge to Bridge (1W) - 156.375 S 156.375
68 - Non-Commercial - 156.425 S 156.425
69 - Non-Commercial - 156.475 S 156.475
If you just want to communicate with other preppers/prepper groups then the following Duplex channels might be best
20 - Public Correspondance - 157.000 D 161.600
21 - Public Correspondance - 157.050 D 161.650
22 - Public Correspondence - 157.100 D 161.700
23 - Public Correspondence - 157.150 D 161.750
24 - Public Correspondence - 157.200 D 161.800
25 - Public Correspondence - 157.250 D 161.850
26 - Public Correspondence - 157.300 D 161.900
27 - Public Correspondence - 157.350 D 161.950
All of the above are dedicated Marine Channels and should only be used if you have a marine license and call sign. In a SHTF scenario I guess anything goes.

Hi Gary,

That's good work and fast too. Well done.

I've got Coastguard Ch0 and Distress Ch16 covered, leaving 8 free slots for maine. Can you hone down your list to the 8 most useful remaining marine channels for preppers?

Please advise.

Cheers
LS

Hi LS
as you've already covered 0 and 16 and as most preppers will be shorebased then
12 - Port Operations - 156.600 S 156.600
14 - Port Operations - 156.700 S 156.700
74 - Port Operations - 156.725 S 156.725
67 - Bridge to Bridge (1W) - 156.375 S 156.375
Would be useful channels for keeping track of comms and activity close to shore

For inter-group comms then any of the public correspondence channels would be ok e.g.
20 - Public Correspondance - 157.000 D 161.600
21 - Public Correspondance - 157.050 D 161.650
22 - Public Correspondence - 157.100 D 161.700
23 - Public Correspondence - 157.150 D 161.750

---

FYI Channel 16 isn't just for safety, it's also the generally accepted calling channel - be aware that this is monitored by the Coast Guard 24/7

quote='gary5wift' pid='32237' dateline='1352286612']
Hi LS
as you've already covered 0 and 16 and as most preppers will be shorebased then
12 - Port Operations - 156.600 S 156.600
14 - Port Operations - 156.700 S 156.700
74 - Port Operations - 156.725 S 156.725
67 - Bridge to Bridge (1W) - 156.375 S 156.375
Would be useful channels for keeping track of comms and activity close to shore

For inter-group comms then any of the public correspondence channels would be ok e.g.
20 - Public Correspondance - 157.000 D 161.600
21 - Public Correspondance - 157.050 D 161.650
22 - Public Correspondence - 157.100 D 161.700
23 - Public Correspondence - 157.150 D 161.750

---

FYI Channel 16 isn't just for safety, it's also the generally accepted calling channel - be aware that this is monitored by the Coast Guard 24/7
[/quote]

Thanks Gary,

Your greater knowledge is invaluable.

I've plugged in your recommendations to the attached version (v4) I assume that I have the duplex frequencies the right way around? No time for me to check this today. If wrong, could you correct and repost as v5?

Re Channel 16, I pre planned to configure it up wth TX offset outside operating limit of the radio so that inadvertant misuse is minimized. Simple manual resetting via radio keyboad of the SHIFT function to ZERO / OFF will restore the ability to transmit on the distress frequency. See original notation on that channel.

Sorry to Marine users, there are not enough free channel numbers for me to give you easy channel number only alignment. My logic is that expected force of numbers favours PMR446 getting the prime allocations.

[attachment=150][

With duplex channels, the ship station transmits on the lower (A) frequency and listens on the upper (B) frequency. The shore station transmits on the upper (B) frequency and listens on the lower (A) frequency.

After a bit more research i've just found out that many of the duplex channels which were used for public correspondence are now being allocated for other services such as weather forecast broadcasts and AIS due to the increased use of mobile telephones and satellite services. These duplex channels can now be operated as Simplex on the lower frequency for both RX and TX, they have been designed with an A suffix, e.g.
21 157.050 161.650 Ship to Shore duplex
21A 157.050 157.050 Simplex

---

I guess either configuration would work after SHTF

(7 November 2012, 12:52)gary5wift Wrote: [ -> ]With duplex channels, the ship station transmits on the lower (A) frequency and listens on the upper (B) frequency. The shore station transmits on the upper (B) frequency and listens on the lower (A) frequency.

After a bit more research i've just found out that many of the duplex channels which were used for public correspondence are now being allocated for other services such as weather forecast broadcasts and AIS due to the increased use of mobile telephones and satellite services. These duplex channels can now be operated as Simplex on the lower frequency for both RX and TX, they have been designed with an A suffix, e.g.
21 157.050 161.650 Ship to Shore duplex
21A 157.050 157.050 Simplex

---

I guess either configuration would work after SHTF

Thanks Gary.

In light of this, I'd say we oughta go for Simplex Public frequencies on the lower frequency, but program OFFSET to 4.6, and leave the SHIFT to OFF /Zero ( same trick as with distress channel) but this time reactivating Shift to + will re-enable the corrcet Duplex operation. The defult position would be Simplex of course.

Do you agree? Update v 5 attached

[attachment=151]

I agree that this would make sense. Looks spot on to me LS - thank you for all the effort you've put in to this, on behalf off all of us that are struggling to define a common communications protocol - Top work, well done

(7 November 2012, 16:43)gary5wift Wrote: [ -> ]I agree that this would make sense. Looks spot on to me LS - thank you for all the effort you've put in to this, on behalf off all of us that are struggling to define a common communications protocol - Top work, well done

It needed doing Gary, taht's all.

Thanks for yur help, Likewise Paul and TLN.

The HP programming prorocol probably has some holes in it, but we can fix them as a work in progress.

Over the weekend I'll start building a program image file....it out to be pretty straight forward. As pereviously mentioned I'll wait a week or two before sharing it to see if any other bright ideas bubble up.