Project

General

Profile

Actions

Bug #2323

open

Marine Frequencies

Added by Donald Chillari almost 10 years ago. Updated almost 5 years ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
02/16/2015
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
(All models)
Platform:
All
Debug Log:
I read the instructions above:

Description

Frequencies listed do not correspond to the Frequencies listed on U. S. Coast Guard Website examples: Ch 16 should be 156.800 Ch 23 should be 157.150


Files

Marine VHF Channels.csv (4.18 KB) Marine VHF Channels.csv File from .chirp/stock_configs Jim Vachalek, 02/26/2015 01:03 PM
US Marine VHF Channels.csv (3.33 KB) US Marine VHF Channels.csv Based on US Coast Guard Chart Jim Vachalek, 02/26/2015 01:03 PM

Related issues 1 (1 open0 closed)

Related to Bug #4331: Incorrect Stock Configuration for US Marine VHF ChannelsNew12/26/2016

Actions
Actions #1

Updated by Galen Thurber almost 10 years ago

I think you are mistaking the slot/bank number with the channel number.
The generic import of CA/US marine channels
does label & allocate channel 16 correctly.
There is no channel 23 in the imported list.
Where are getting your imported list from?
hope this works

Updated by Jim Vachalek almost 10 years ago

My Stock config file US Marine frequencies includes includes a "K23" at 161.750 MHz, which is not a US marine VHF Frequency. Spot checking other frequencies/channels shows other errors; however Chan 16 "K16" is on the correct frequency of 156.800 MHz.

Ordering the stock file in channel sequence vice frequency is more user friendly.

Attached is the chirp "stock_configs" US Marine freqs file.

I have attached a US Marine VHF .CSV file based on the US Coast Guard chart (http://www.navcen.uscg.gov/?pageName=mtVhf)

Actions #3

Updated by Tyler Tidman almost 9 years ago

  • Assignee set to Tyler Tidman
Actions #4

Updated by Mike C about 5 years ago

Wow, this caused me much trouble. Please do update the stock configs!

The updated file appears to have an error for channel 63A. It should not have an offset.

Actions #5

Updated by Mike C about 5 years ago

Same with 77-83A and 88A. No offset.

Actions #6

Updated by Mike C about 5 years ago

66A is wrong frequency

Actions #7

Updated by Bernhard Hailer almost 5 years ago

  • Status changed from New to Feedback
  • Chirp Version changed from 0.4.0 to daily
  • Platform changed from Windows to All
Actions

Also available in: Atom PDF