On Fri, 15 May 2009 23:28:54 -0400, Woodrick, Ed
ewoodr...@ed-com.com said:
Easy solution, stop callsign routing. Use repeater linking instead.
Problem solved.
Ed WA4YIH
That'd be silly. If I want to KNOW for sure the call made it to the
other side, and get a RESPONSE from the network
On Sun, 17 May 2009 09:33:33 +1000, Tony Langdon vk3...@gmail.com
said:
At 01:16 AM 5/17/2009, you wrote:
John is right on the money here.
-
Tactical Call Sign SOP:
A tactical call sign is entered in the 4 digit comment field after a
station's legal call sign:
This would seem
At 05:22 PM 5/17/2009, you wrote:
That'd be silly. If I want to KNOW for sure the call made it to the
other side, and get a RESPONSE from the network that says so, the ONLY
option for that is callsign routing.
This is true, DPlus does not give any concrete indications that
you're getting
At 05:31 PM 5/17/2009, you wrote:
And how does that work when attempting to use callsign squelch?
Hmm, I'd have thought that callsign squelch would be generally an
impediment to emergency operations. I know that if I was an operator
on duty, I'd much rather an open channel, so I could be
I have a icom ID-800H and the programming software. Is there anyone who might
know the appropriate sequence to download data? It seems the data downloads ok
but then after turning the radio back on the memory channel number and the
letter M blink alternately. Is there a process I need to
We've had the discussion many times before.
Last year at Dayton, everyone was having to source route to the local repeater
to talk. No one was able to have a conversation because people kept barging in
because they could not hear the activity on the local repeater.
This year there were a
Source routing to an individual callsign (native D-STAR) has its purpose
as well. If the station (callsign) that I want to talk to is attached
to a traveler, say a long haul truck driver or a road warrior, then
simply calling the station using callsign routing makes more sense.
Callsign
There is no question Dplus makes contacts possible for more people, in
large due to the obtuse nature of setting up radios that you likened to
MSDOS vs Windows as a user interface in an earlier post. Many average
hams find setting up a radio and using the features of say, and IC91,
far too
--- In dstar_digital@yahoogroups.com, john_ke5c k...@... wrote:
Callsign routing to a long haul truck driver who is in range of a DStar
repeater say 5% of the time, and whose whereabouts even then would be known
only if he remembered to key up?
Well, that is like making the argument that
Steve is correct. It has more to do with the user interface than with
the protocol(s) involved. One of the problems with D-STAR (and amateur
radio design in general) is that radios are designed by engineers,
usually without any benefit of a user interaction designer. The
popularity of the
John,
What a coincidence! I talked exactly about this subject with Ray Novak from
Icom in 2006 here in Brazil. The radio amateur should have access to an open
language to deal with the radio interface and the radios will never more be
like this.
73's
PY2JF
De:
At 09:33 PM 5/17/2009, you wrote:
We've had the discussion many times before.
Last year at Dayton, everyone was having to source route to the
local repeater to talk. No one was able to have a conversation
because people kept barging in because they could not hear the
activity on the local
At 05:43 AM 5/18/2009, you wrote:
DSTAR continues to emerge. That said, I believe the long range solution
to more fully utilize DSTAR lies in a sensible user interface that
integrates all of the features of DSTAR (G2 and Dplus) in a user
friendly format. Also making system statue available on
At 09:23 AM 5/18/2009, you wrote:
You said multiple country/repeater conversations aren't possible with
callsign routing -- False.
OK, that's one trick I would like to know, and without using
multicast - because of the administrator intervention required, I
consider this feature to have
Your argument about having to program your radio driving 70mph down the road
sure bolsters my case that icom oughtta be putting a voice module in both
their hts, and mobile rigs.
_
From: dstar_digital@yahoogroups.com [mailto:dstar_digi...@yahoogroups.com]
On Behalf Of Tony Langdon
I absolutely stand by my statements.
Embedded...
From: dstar_digital@yahoogroups.com [mailto:dstar_digi...@yahoogroups.com] On
Behalf Of Nate Duehr
Sent: Sunday, May 17, 2009 7:23 PM
To: dstar_digital@yahoogroups.com
Subject: Re: 880 vs 800 (was: Re: [DSTAR_DIGITAL] Signal Distance)
Ed,
There's a little bit of reality that's being left out of this discussion that
definitely needs to be interjected.
When the conversation is using voice, there is absolutely no issues with the
tactical callsigns being used on voice. Actually D-STAR makes it much more
effective as you don't have
Tony Langdon wrote:
At 09:23 AM 5/18/2009, you wrote:
You said multiple country/repeater conversations aren't possible with
callsign routing -- False.
OK, that's one trick I would like to know, and without using
multicast - because of the administrator intervention required, I
your comment suggests that yet again Icomm missed the boat as far as
accessibility of the new
radios.
- Original Message -
From: justin Mann w9...@cox.net
To: dstar_digital@yahoogroups.com
Sent: Monday, May 18, 2009 00:13
Subject: RE: 880 vs 800 (was: Re: [DSTAR_DIGITAL] Signal
Why not simply put the tactical call in the short message. Then it will
scroll by every time you transmit.
73, Tom n4zpt
Dennis Griffin wrote:
I have worked many public service events disaster preparedness
exercises. One would have to be very creative to get meaningful
tactical calls
I bought an ICOM 880 at Dayton, with Ed, and others help I put the right
parameters in the first time and got on the air with the Dayton DSTAR
repeater. This is a whole new world to learn.
Downloaded the ICOM free software and was able to load all the settings
from the radio, make some changes
21 matches
Mail list logo
