Call sign ID for a “homebrew” or improvised repeater? The Next CEO of Stack OverflowBuilding a portable event repeaterTips on how to setup a MOTOTRBO XPR-8300 Repeater for DMR Ham operation?Max legal power with nearly zero BWCan I use a Hawaiian call sign on the mainland?V/U Packet Rate LimitsWhy is repeater post-xmit “burst” stronger than repeated signal?Why can't I hear myself from a second radio when bouncing off a repeater?Using a Deceased Club Member's Call Sign for Field DayRepeater for 1/4 square mile campusHow can I tell if someone is mistakenly transmitting on a repeater output frequency, instead of the (offset) input frequency?
Example of a Mathematician/Physicist whose Other Publications during their PhD eclipsed their PhD Thesis
Should I tutor a student who I know has cheated on their homework?
How to use tikz in fbox?
Rotate a column
Trouble understanding the speech of overseas colleagues
What can we do to stop prior company from asking us questions?
Implement the Thanos sorting algorithm
How do I go from 300 unfinished/half written blog posts, to published posts?
How do we know the LHC results are robust?
WOW air has ceased operation, can I get my tickets refunded?
Robert Sheckley short story about vacation spots being overwhelmed
Anatomically Correct Mesopelagic Aves
Why didn't Khan get resurrected in the Genesis Explosion?
How to start emacs in "nothing" mode (`fundamental-mode`)
How to write the block matrix in LaTex?
Would this house-rule that treats advantage as a +1 to the roll instead (and disadvantage as -1) and allows them to stack be balanced?
Why do remote companies require working in the US?
Why is there a PLL in CPU?
What makes a siege story/plot interesting?
How do I solve this limit?
Why doesn't a table tennis ball float on the surface? How do we calculate buoyancy here?
What happens if you roll doubles 3 times then land on "Go to jail?"
MAZDA 3 2006 (UK) - poor acceleration then takes off at 3250 revs
How can I quit an app using Terminal?
Call sign ID for a “homebrew” or improvised repeater?
The Next CEO of Stack OverflowBuilding a portable event repeaterTips on how to setup a MOTOTRBO XPR-8300 Repeater for DMR Ham operation?Max legal power with nearly zero BWCan I use a Hawaiian call sign on the mainland?V/U Packet Rate LimitsWhy is repeater post-xmit “burst” stronger than repeated signal?Why can't I hear myself from a second radio when bouncing off a repeater?Using a Deceased Club Member's Call Sign for Field DayRepeater for 1/4 square mile campusHow can I tell if someone is mistakenly transmitting on a repeater output frequency, instead of the (offset) input frequency?
$begingroup$
I saw a couple YouTube videos last night about setting up a repeater using a pair of cheap hand-held radios and, at its simplest, an audio patch cable to connect the speaker output of one radio to the mic input on the other. Set frequencies correctly, turn VOX on, and what one HT receives will be retransmitted by the other -- potentially even cross-repeating between 2m and 70cm bands, or whatever bands your radios can use.
There are potential issues with doing this on a non-emergency basis -- protecting the radios from weather, keeping their batteries charged, preventing someone from finding the setup and saying "Hey, free radios!" The one I'm concerned with at the moment, however, is FCC legality. It's my understanding that periodic ID, at least when active, is legally required, but none of the other repeaters I've listened to seem to do this.
Since the cheap HT sets don't have this capability, I'm concerned about the legality of operating a repeater that doesn't identify itself. Just another receiver doesn't (that I've heard), doesn't mean it's legal to do things that way.
Is there an inexpensive way to insert an ID generator between the receive and transmit HT units in this kind of setup? It would need to detect activity, wait some period of time, and then send an ID, as well as sending periodically if there's no activity. Either voice or Morse is legal, but presuming this will be a digital playback system of some kind, either one is easy to set up.
united-states legal repeater callsign
asked 17 hours ago
Zeiss IkonZeiss Ikon
681113
$endgroup$
add a comment |
$begingroup$
I saw a couple YouTube videos last night about setting up a repeater using a pair of cheap hand-held radios and, at its simplest, an audio patch cable to connect the speaker output of one radio to the mic input on the other. Set frequencies correctly, turn VOX on, and what one HT receives will be retransmitted by the other -- potentially even cross-repeating between 2m and 70cm bands, or whatever bands your radios can use.
There are potential issues with doing this on a non-emergency basis -- protecting the radios from weather, keeping their batteries charged, preventing someone from finding the setup and saying "Hey, free radios!" The one I'm concerned with at the moment, however, is FCC legality. It's my understanding that periodic ID, at least when active, is legally required, but none of the other repeaters I've listened to seem to do this.
Since the cheap HT sets don't have this capability, I'm concerned about the legality of operating a repeater that doesn't identify itself. Just another receiver doesn't (that I've heard), doesn't mean it's legal to do things that way.
Is there an inexpensive way to insert an ID generator between the receive and transmit HT units in this kind of setup? It would need to detect activity, wait some period of time, and then send an ID, as well as sending periodically if there's no activity. Either voice or Morse is legal, but presuming this will be a digital playback system of some kind, either one is easy to set up.
united-states legal repeater callsign
asked 17 hours ago
Zeiss IkonZeiss Ikon
681113
$endgroup$
2
$begingroup$
I've never encountered a repeater that didn't ID — but bear in mind it only has to ID when it's active. Not every 10 minutes, just every 10 minutes in which it's transmitting. And audio or morse ID is sufficient, both aren't needed.
$endgroup$
– hobbs - KC2G
13 hours ago
$begingroup$
Periodic morse ID and timeouts is a task for a cheap MCU, which is the way it's been being done for several decades now. An "Arduino" would work if you plan to DIY without previous familiarity. Ideally you make a little effort to produce somewhat sinusoidal audio.
$endgroup$
– Chris Stratton
12 hours ago
$begingroup$
Given I've seen video of Arduino used as frequency synth for HF WSPR transmitters, I expect it's got plenty of spare cycles to make at least an 8-step audio at 600 Hz.
$endgroup$
– Zeiss Ikon
11 hours ago
add a comment |
$begingroup$
I saw a couple YouTube videos last night about setting up a repeater using a pair of cheap hand-held radios and, at its simplest, an audio patch cable to connect the speaker output of one radio to the mic input on the other. Set frequencies correctly, turn VOX on, and what one HT receives will be retransmitted by the other -- potentially even cross-repeating between 2m and 70cm bands, or whatever bands your radios can use.
There are potential issues with doing this on a non-emergency basis -- protecting the radios from weather, keeping their batteries charged, preventing someone from finding the setup and saying "Hey, free radios!" The one I'm concerned with at the moment, however, is FCC legality. It's my understanding that periodic ID, at least when active, is legally required, but none of the other repeaters I've listened to seem to do this.
Since the cheap HT sets don't have this capability, I'm concerned about the legality of operating a repeater that doesn't identify itself. Just another receiver doesn't (that I've heard), doesn't mean it's legal to do things that way.
Is there an inexpensive way to insert an ID generator between the receive and transmit HT units in this kind of setup? It would need to detect activity, wait some period of time, and then send an ID, as well as sending periodically if there's no activity. Either voice or Morse is legal, but presuming this will be a digital playback system of some kind, either one is easy to set up.
united-states legal repeater callsign
asked 17 hours ago
Zeiss IkonZeiss Ikon
681113
$endgroup$
I saw a couple YouTube videos last night about setting up a repeater using a pair of cheap hand-held radios and, at its simplest, an audio patch cable to connect the speaker output of one radio to the mic input on the other. Set frequencies correctly, turn VOX on, and what one HT receives will be retransmitted by the other -- potentially even cross-repeating between 2m and 70cm bands, or whatever bands your radios can use.
There are potential issues with doing this on a non-emergency basis -- protecting the radios from weather, keeping their batteries charged, preventing someone from finding the setup and saying "Hey, free radios!" The one I'm concerned with at the moment, however, is FCC legality. It's my understanding that periodic ID, at least when active, is legally required, but none of the other repeaters I've listened to seem to do this.
Since the cheap HT sets don't have this capability, I'm concerned about the legality of operating a repeater that doesn't identify itself. Just another receiver doesn't (that I've heard), doesn't mean it's legal to do things that way.
Is there an inexpensive way to insert an ID generator between the receive and transmit HT units in this kind of setup? It would need to detect activity, wait some period of time, and then send an ID, as well as sending periodically if there's no activity. Either voice or Morse is legal, but presuming this will be a digital playback system of some kind, either one is easy to set up.
united-states legal repeater callsign
united-states legal repeater callsign
asked 17 hours ago
Zeiss IkonZeiss Ikon
681113
asked 17 hours ago
Zeiss IkonZeiss Ikon
681113
edited 5 hours ago
Zeiss Ikon
asked 17 hours ago
Zeiss IkonZeiss Ikon
681113
asked 17 hours ago
Zeiss IkonZeiss Ikon
681113
asked 17 hours ago
Zeiss IkonZeiss Ikon
681113
681113
2
$begingroup$
I've never encountered a repeater that didn't ID — but bear in mind it only has to ID when it's active. Not every 10 minutes, just every 10 minutes in which it's transmitting. And audio or morse ID is sufficient, both aren't needed.
$endgroup$
– hobbs - KC2G
13 hours ago
$begingroup$
Periodic morse ID and timeouts is a task for a cheap MCU, which is the way it's been being done for several decades now. An "Arduino" would work if you plan to DIY without previous familiarity. Ideally you make a little effort to produce somewhat sinusoidal audio.
$endgroup$
– Chris Stratton
12 hours ago
$begingroup$
Given I've seen video of Arduino used as frequency synth for HF WSPR transmitters, I expect it's got plenty of spare cycles to make at least an 8-step audio at 600 Hz.
$endgroup$
– Zeiss Ikon
11 hours ago
add a comment |
2
$begingroup$
I've never encountered a repeater that didn't ID — but bear in mind it only has to ID when it's active. Not every 10 minutes, just every 10 minutes in which it's transmitting. And audio or morse ID is sufficient, both aren't needed.
$endgroup$
– hobbs - KC2G
13 hours ago
$begingroup$
Periodic morse ID and timeouts is a task for a cheap MCU, which is the way it's been being done for several decades now. An "Arduino" would work if you plan to DIY without previous familiarity. Ideally you make a little effort to produce somewhat sinusoidal audio.
$endgroup$
– Chris Stratton
12 hours ago
$begingroup$
Given I've seen video of Arduino used as frequency synth for HF WSPR transmitters, I expect it's got plenty of spare cycles to make at least an 8-step audio at 600 Hz.
$endgroup$
– Zeiss Ikon
11 hours ago
2
2
$begingroup$
I've never encountered a repeater that didn't ID — but bear in mind it only has to ID when it's active. Not every 10 minutes, just every 10 minutes in which it's transmitting. And audio or morse ID is sufficient, both aren't needed.
$endgroup$
– hobbs - KC2G
13 hours ago
$begingroup$
I've never encountered a repeater that didn't ID — but bear in mind it only has to ID when it's active. Not every 10 minutes, just every 10 minutes in which it's transmitting. And audio or morse ID is sufficient, both aren't needed.
$endgroup$
– hobbs - KC2G
13 hours ago
$begingroup$
Periodic morse ID and timeouts is a task for a cheap MCU, which is the way it's been being done for several decades now. An "Arduino" would work if you plan to DIY without previous familiarity. Ideally you make a little effort to produce somewhat sinusoidal audio.
$endgroup$
– Chris Stratton
12 hours ago
$begingroup$
Periodic morse ID and timeouts is a task for a cheap MCU, which is the way it's been being done for several decades now. An "Arduino" would work if you plan to DIY without previous familiarity. Ideally you make a little effort to produce somewhat sinusoidal audio.
$endgroup$
– Chris Stratton
12 hours ago
$begingroup$
Given I've seen video of Arduino used as frequency synth for HF WSPR transmitters, I expect it's got plenty of spare cycles to make at least an 8-step audio at 600 Hz.
$endgroup$
– Zeiss Ikon
11 hours ago
$begingroup$
Given I've seen video of Arduino used as frequency synth for HF WSPR transmitters, I expect it's got plenty of spare cycles to make at least an 8-step audio at 600 Hz.
$endgroup$
– Zeiss Ikon
11 hours ago
add a comment |
2 Answers
2
active
oldest
votes
$begingroup$
Are you up to buying a Raspberry Pi, two USB sound cards, some assorted transistors and such, and making your own interface cable? If so, you can run svxlink. It supports all sorts of fancy things related to internet-linking, remote control, and automation, but you don't need to use any of that; it will also function just fine as a repeater controller for a standalone repeater, and periodic ID is one of the built-in features.
answered 12 hours ago
hobbs - KC2Ghobbs - KC2G
87328
$endgroup$
$begingroup$
I'm not sure how much I'm willing to spend at this point -- and I'd still have to solve the problems of where to put it, how to power it, how to protect it, and how to meet the Part 97 requirements for continuous monitoring and three-minute shutdown if control connection is lost. But a Pi or equivalent and USB accessories isn't likely to cost any more than the proper/legal repeater controllers I've been seeing.
$endgroup$
– Zeiss Ikon
12 hours ago
$begingroup$
A raspberry pi is really not a wise solution to this - fragile (especially the SD card if power is frequently lost), power hungry, expensive, and over complex. This is a task that calls for a small MCU, which is the way it's been being solved since the 1980's. And even if you use a pi, there's no reason to run the user audio through it, just build a trivial mixer.
$endgroup$
– Chris Stratton
12 hours ago
1
$begingroup$
@ChrisStratton that's fair, but there are advantages to doing it this way as well — it's easy to build in a day from readily available parts and you have access to the fancy features if you do want them. A pi zero (which would do fine for this purpose) should pull about a watt and costs $5, and it's entirely possible to run it with a read-only root fs (avoiding data corruption issues), although that isn't done nearly often enough.
$endgroup$
– hobbs - KC2G
12 hours ago
$begingroup$
and in any case, I'm only presenting an option — feel free to present your own, more is better :)
$endgroup$
– hobbs - KC2G
12 hours ago
$begingroup$
It's a common but false misconception that a read-only file system makes an SD card safe for embedded use. In actuality it does not, as the invisible flash translation layer still does housekeeping on its own initiative - modern MLC cells require that it do so. Cards are sold to hold your vacation pictures in a battery powered camera that shuts them down with fair warning, they're really not engineered for embedded use.
$endgroup$
– Chris Stratton
11 hours ago
add a comment |
$begingroup$
Many repeaters are not based on radios with built-in ID or any other repeater functions, but rather an ordinary transmitter and receiver (each possibly a transceiver used only for one function, if that's the most economical option) connected by a repeater controller through which the audio, PTT, etc. signals pass. The repeater controller knows how to ID (and to do so without interrupting usage of the repeater), generates the "courtesy tone" at the end of repeated transmissions, and may have remotely-controllable special functions (e.g. for repeater linking).
As I haven't built a repeater I can't recommend any specific examples, but I hope that you can find suitable products or project plans now that you know what to call them.
answered 14 hours ago
Kevin Reid AG6YO♦Kevin Reid AG6YO
16.3k33170
$endgroup$
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
return StackExchange.using("mathjaxEditing", function ()
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix)
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["$", "$"], ["\\(","\\)"]]);
);
);
, "mathjax-editing");
StackExchange.ifUsing("editor", function ()
return StackExchange.using("schematics", function ()
StackExchange.schematics.init();
);
, "cicuitlab");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "520"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fham.stackexchange.com%2fquestions%2f13146%2fcall-sign-id-for-a-homebrew-or-improvised-repeater%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
$begingroup$
Are you up to buying a Raspberry Pi, two USB sound cards, some assorted transistors and such, and making your own interface cable? If so, you can run svxlink. It supports all sorts of fancy things related to internet-linking, remote control, and automation, but you don't need to use any of that; it will also function just fine as a repeater controller for a standalone repeater, and periodic ID is one of the built-in features.
answered 12 hours ago
hobbs - KC2Ghobbs - KC2G
87328
$endgroup$
$begingroup$
I'm not sure how much I'm willing to spend at this point -- and I'd still have to solve the problems of where to put it, how to power it, how to protect it, and how to meet the Part 97 requirements for continuous monitoring and three-minute shutdown if control connection is lost. But a Pi or equivalent and USB accessories isn't likely to cost any more than the proper/legal repeater controllers I've been seeing.
$endgroup$
– Zeiss Ikon
12 hours ago
$begingroup$
A raspberry pi is really not a wise solution to this - fragile (especially the SD card if power is frequently lost), power hungry, expensive, and over complex. This is a task that calls for a small MCU, which is the way it's been being solved since the 1980's. And even if you use a pi, there's no reason to run the user audio through it, just build a trivial mixer.
$endgroup$
– Chris Stratton
12 hours ago
1
$begingroup$
@ChrisStratton that's fair, but there are advantages to doing it this way as well — it's easy to build in a day from readily available parts and you have access to the fancy features if you do want them. A pi zero (which would do fine for this purpose) should pull about a watt and costs $5, and it's entirely possible to run it with a read-only root fs (avoiding data corruption issues), although that isn't done nearly often enough.
$endgroup$
– hobbs - KC2G
12 hours ago
$begingroup$
and in any case, I'm only presenting an option — feel free to present your own, more is better :)
$endgroup$
– hobbs - KC2G
12 hours ago
$begingroup$
It's a common but false misconception that a read-only file system makes an SD card safe for embedded use. In actuality it does not, as the invisible flash translation layer still does housekeeping on its own initiative - modern MLC cells require that it do so. Cards are sold to hold your vacation pictures in a battery powered camera that shuts them down with fair warning, they're really not engineered for embedded use.
$endgroup$
– Chris Stratton
11 hours ago
add a comment |
$begingroup$
Are you up to buying a Raspberry Pi, two USB sound cards, some assorted transistors and such, and making your own interface cable? If so, you can run svxlink. It supports all sorts of fancy things related to internet-linking, remote control, and automation, but you don't need to use any of that; it will also function just fine as a repeater controller for a standalone repeater, and periodic ID is one of the built-in features.
answered 12 hours ago
hobbs - KC2Ghobbs - KC2G
87328
$endgroup$
$begingroup$
I'm not sure how much I'm willing to spend at this point -- and I'd still have to solve the problems of where to put it, how to power it, how to protect it, and how to meet the Part 97 requirements for continuous monitoring and three-minute shutdown if control connection is lost. But a Pi or equivalent and USB accessories isn't likely to cost any more than the proper/legal repeater controllers I've been seeing.
$endgroup$
– Zeiss Ikon
12 hours ago
$begingroup$
A raspberry pi is really not a wise solution to this - fragile (especially the SD card if power is frequently lost), power hungry, expensive, and over complex. This is a task that calls for a small MCU, which is the way it's been being solved since the 1980's. And even if you use a pi, there's no reason to run the user audio through it, just build a trivial mixer.
$endgroup$
– Chris Stratton
12 hours ago
1
$begingroup$
@ChrisStratton that's fair, but there are advantages to doing it this way as well — it's easy to build in a day from readily available parts and you have access to the fancy features if you do want them. A pi zero (which would do fine for this purpose) should pull about a watt and costs $5, and it's entirely possible to run it with a read-only root fs (avoiding data corruption issues), although that isn't done nearly often enough.
$endgroup$
– hobbs - KC2G
12 hours ago
$begingroup$
and in any case, I'm only presenting an option — feel free to present your own, more is better :)
$endgroup$
– hobbs - KC2G
12 hours ago
$begingroup$
It's a common but false misconception that a read-only file system makes an SD card safe for embedded use. In actuality it does not, as the invisible flash translation layer still does housekeeping on its own initiative - modern MLC cells require that it do so. Cards are sold to hold your vacation pictures in a battery powered camera that shuts them down with fair warning, they're really not engineered for embedded use.
$endgroup$
– Chris Stratton
11 hours ago
add a comment |
$begingroup$
Are you up to buying a Raspberry Pi, two USB sound cards, some assorted transistors and such, and making your own interface cable? If so, you can run svxlink. It supports all sorts of fancy things related to internet-linking, remote control, and automation, but you don't need to use any of that; it will also function just fine as a repeater controller for a standalone repeater, and periodic ID is one of the built-in features.
answered 12 hours ago
hobbs - KC2Ghobbs - KC2G
87328
$endgroup$
Are you up to buying a Raspberry Pi, two USB sound cards, some assorted transistors and such, and making your own interface cable? If so, you can run svxlink. It supports all sorts of fancy things related to internet-linking, remote control, and automation, but you don't need to use any of that; it will also function just fine as a repeater controller for a standalone repeater, and periodic ID is one of the built-in features.
answered 12 hours ago
hobbs - KC2Ghobbs - KC2G
87328
answered 12 hours ago
hobbs - KC2Ghobbs - KC2G
87328
answered 12 hours ago
hobbs - KC2Ghobbs - KC2G
87328
answered 12 hours ago
hobbs - KC2Ghobbs - KC2G
87328
87328
$begingroup$
I'm not sure how much I'm willing to spend at this point -- and I'd still have to solve the problems of where to put it, how to power it, how to protect it, and how to meet the Part 97 requirements for continuous monitoring and three-minute shutdown if control connection is lost. But a Pi or equivalent and USB accessories isn't likely to cost any more than the proper/legal repeater controllers I've been seeing.
$endgroup$
– Zeiss Ikon
12 hours ago
$begingroup$
A raspberry pi is really not a wise solution to this - fragile (especially the SD card if power is frequently lost), power hungry, expensive, and over complex. This is a task that calls for a small MCU, which is the way it's been being solved since the 1980's. And even if you use a pi, there's no reason to run the user audio through it, just build a trivial mixer.
$endgroup$
– Chris Stratton
12 hours ago
1
$begingroup$
@ChrisStratton that's fair, but there are advantages to doing it this way as well — it's easy to build in a day from readily available parts and you have access to the fancy features if you do want them. A pi zero (which would do fine for this purpose) should pull about a watt and costs $5, and it's entirely possible to run it with a read-only root fs (avoiding data corruption issues), although that isn't done nearly often enough.
$endgroup$
– hobbs - KC2G
12 hours ago
$begingroup$
and in any case, I'm only presenting an option — feel free to present your own, more is better :)
$endgroup$
– hobbs - KC2G
12 hours ago
$begingroup$
It's a common but false misconception that a read-only file system makes an SD card safe for embedded use. In actuality it does not, as the invisible flash translation layer still does housekeeping on its own initiative - modern MLC cells require that it do so. Cards are sold to hold your vacation pictures in a battery powered camera that shuts them down with fair warning, they're really not engineered for embedded use.
$endgroup$
– Chris Stratton
11 hours ago
add a comment |
$begingroup$
I'm not sure how much I'm willing to spend at this point -- and I'd still have to solve the problems of where to put it, how to power it, how to protect it, and how to meet the Part 97 requirements for continuous monitoring and three-minute shutdown if control connection is lost. But a Pi or equivalent and USB accessories isn't likely to cost any more than the proper/legal repeater controllers I've been seeing.
$endgroup$
– Zeiss Ikon
12 hours ago
$begingroup$
A raspberry pi is really not a wise solution to this - fragile (especially the SD card if power is frequently lost), power hungry, expensive, and over complex. This is a task that calls for a small MCU, which is the way it's been being solved since the 1980's. And even if you use a pi, there's no reason to run the user audio through it, just build a trivial mixer.
$endgroup$
– Chris Stratton
12 hours ago
1
$begingroup$
@ChrisStratton that's fair, but there are advantages to doing it this way as well — it's easy to build in a day from readily available parts and you have access to the fancy features if you do want them. A pi zero (which would do fine for this purpose) should pull about a watt and costs $5, and it's entirely possible to run it with a read-only root fs (avoiding data corruption issues), although that isn't done nearly often enough.
$endgroup$
– hobbs - KC2G
12 hours ago
$begingroup$
and in any case, I'm only presenting an option — feel free to present your own, more is better :)
$endgroup$
– hobbs - KC2G
12 hours ago
$begingroup$
It's a common but false misconception that a read-only file system makes an SD card safe for embedded use. In actuality it does not, as the invisible flash translation layer still does housekeeping on its own initiative - modern MLC cells require that it do so. Cards are sold to hold your vacation pictures in a battery powered camera that shuts them down with fair warning, they're really not engineered for embedded use.
$endgroup$
– Chris Stratton
11 hours ago
$begingroup$
I'm not sure how much I'm willing to spend at this point -- and I'd still have to solve the problems of where to put it, how to power it, how to protect it, and how to meet the Part 97 requirements for continuous monitoring and three-minute shutdown if control connection is lost. But a Pi or equivalent and USB accessories isn't likely to cost any more than the proper/legal repeater controllers I've been seeing.
$endgroup$
– Zeiss Ikon
12 hours ago
$begingroup$
I'm not sure how much I'm willing to spend at this point -- and I'd still have to solve the problems of where to put it, how to power it, how to protect it, and how to meet the Part 97 requirements for continuous monitoring and three-minute shutdown if control connection is lost. But a Pi or equivalent and USB accessories isn't likely to cost any more than the proper/legal repeater controllers I've been seeing.
$endgroup$
– Zeiss Ikon
12 hours ago
$begingroup$
A raspberry pi is really not a wise solution to this - fragile (especially the SD card if power is frequently lost), power hungry, expensive, and over complex. This is a task that calls for a small MCU, which is the way it's been being solved since the 1980's. And even if you use a pi, there's no reason to run the user audio through it, just build a trivial mixer.
$endgroup$
– Chris Stratton
12 hours ago
$begingroup$
A raspberry pi is really not a wise solution to this - fragile (especially the SD card if power is frequently lost), power hungry, expensive, and over complex. This is a task that calls for a small MCU, which is the way it's been being solved since the 1980's. And even if you use a pi, there's no reason to run the user audio through it, just build a trivial mixer.
$endgroup$
– Chris Stratton
12 hours ago
1
1
$begingroup$
@ChrisStratton that's fair, but there are advantages to doing it this way as well — it's easy to build in a day from readily available parts and you have access to the fancy features if you do want them. A pi zero (which would do fine for this purpose) should pull about a watt and costs $5, and it's entirely possible to run it with a read-only root fs (avoiding data corruption issues), although that isn't done nearly often enough.
$endgroup$
– hobbs - KC2G
12 hours ago
$begingroup$
@ChrisStratton that's fair, but there are advantages to doing it this way as well — it's easy to build in a day from readily available parts and you have access to the fancy features if you do want them. A pi zero (which would do fine for this purpose) should pull about a watt and costs $5, and it's entirely possible to run it with a read-only root fs (avoiding data corruption issues), although that isn't done nearly often enough.
$endgroup$
– hobbs - KC2G
12 hours ago
$begingroup$
and in any case, I'm only presenting an option — feel free to present your own, more is better :)
$endgroup$
– hobbs - KC2G
12 hours ago
$begingroup$
and in any case, I'm only presenting an option — feel free to present your own, more is better :)
$endgroup$
– hobbs - KC2G
12 hours ago
$begingroup$
It's a common but false misconception that a read-only file system makes an SD card safe for embedded use. In actuality it does not, as the invisible flash translation layer still does housekeeping on its own initiative - modern MLC cells require that it do so. Cards are sold to hold your vacation pictures in a battery powered camera that shuts them down with fair warning, they're really not engineered for embedded use.
$endgroup$
– Chris Stratton
11 hours ago
$begingroup$
It's a common but false misconception that a read-only file system makes an SD card safe for embedded use. In actuality it does not, as the invisible flash translation layer still does housekeeping on its own initiative - modern MLC cells require that it do so. Cards are sold to hold your vacation pictures in a battery powered camera that shuts them down with fair warning, they're really not engineered for embedded use.
$endgroup$
– Chris Stratton
11 hours ago
add a comment |
$begingroup$
Many repeaters are not based on radios with built-in ID or any other repeater functions, but rather an ordinary transmitter and receiver (each possibly a transceiver used only for one function, if that's the most economical option) connected by a repeater controller through which the audio, PTT, etc. signals pass. The repeater controller knows how to ID (and to do so without interrupting usage of the repeater), generates the "courtesy tone" at the end of repeated transmissions, and may have remotely-controllable special functions (e.g. for repeater linking).
As I haven't built a repeater I can't recommend any specific examples, but I hope that you can find suitable products or project plans now that you know what to call them.
answered 14 hours ago
Kevin Reid AG6YO♦Kevin Reid AG6YO
16.3k33170
$endgroup$
add a comment |
$begingroup$
Many repeaters are not based on radios with built-in ID or any other repeater functions, but rather an ordinary transmitter and receiver (each possibly a transceiver used only for one function, if that's the most economical option) connected by a repeater controller through which the audio, PTT, etc. signals pass. The repeater controller knows how to ID (and to do so without interrupting usage of the repeater), generates the "courtesy tone" at the end of repeated transmissions, and may have remotely-controllable special functions (e.g. for repeater linking).
As I haven't built a repeater I can't recommend any specific examples, but I hope that you can find suitable products or project plans now that you know what to call them.
answered 14 hours ago
Kevin Reid AG6YO♦Kevin Reid AG6YO
16.3k33170
$endgroup$
add a comment |
$begingroup$
Many repeaters are not based on radios with built-in ID or any other repeater functions, but rather an ordinary transmitter and receiver (each possibly a transceiver used only for one function, if that's the most economical option) connected by a repeater controller through which the audio, PTT, etc. signals pass. The repeater controller knows how to ID (and to do so without interrupting usage of the repeater), generates the "courtesy tone" at the end of repeated transmissions, and may have remotely-controllable special functions (e.g. for repeater linking).
As I haven't built a repeater I can't recommend any specific examples, but I hope that you can find suitable products or project plans now that you know what to call them.
answered 14 hours ago
Kevin Reid AG6YO♦Kevin Reid AG6YO
16.3k33170
$endgroup$
Many repeaters are not based on radios with built-in ID or any other repeater functions, but rather an ordinary transmitter and receiver (each possibly a transceiver used only for one function, if that's the most economical option) connected by a repeater controller through which the audio, PTT, etc. signals pass. The repeater controller knows how to ID (and to do so without interrupting usage of the repeater), generates the "courtesy tone" at the end of repeated transmissions, and may have remotely-controllable special functions (e.g. for repeater linking).
As I haven't built a repeater I can't recommend any specific examples, but I hope that you can find suitable products or project plans now that you know what to call them.
answered 14 hours ago
Kevin Reid AG6YO♦Kevin Reid AG6YO
16.3k33170
answered 14 hours ago
Kevin Reid AG6YO♦Kevin Reid AG6YO
16.3k33170
answered 14 hours ago
Kevin Reid AG6YO♦Kevin Reid AG6YO
16.3k33170
answered 14 hours ago
Kevin Reid AG6YO♦Kevin Reid AG6YO
16.3k33170
16.3k33170
add a comment |
add a comment |
Thanks for contributing an answer to Amateur Radio Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fham.stackexchange.com%2fquestions%2f13146%2fcall-sign-id-for-a-homebrew-or-improvised-repeater%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
$begingroup$
I've never encountered a repeater that didn't ID — but bear in mind it only has to ID when it's active. Not every 10 minutes, just every 10 minutes in which it's transmitting. And audio or morse ID is sufficient, both aren't needed.
$endgroup$
– hobbs - KC2G
13 hours ago
$begingroup$
Periodic morse ID and timeouts is a task for a cheap MCU, which is the way it's been being done for several decades now. An "Arduino" would work if you plan to DIY without previous familiarity. Ideally you make a little effort to produce somewhat sinusoidal audio.
$endgroup$
– Chris Stratton
12 hours ago
$begingroup$
Given I've seen video of Arduino used as frequency synth for HF WSPR transmitters, I expect it's got plenty of spare cycles to make at least an 8-step audio at 600 Hz.
$endgroup$
– Zeiss Ikon
11 hours ago