Nice idea, but unworkable in D-Star due to the fact that it's a single carrier
system.
If you take a real trunked system like MPT1327, trunked P25 or TETRA, then
there multiple carriers per site (or timeslots in the case of TETRA) to allow
multiple calls.
In D-Star, there can only be one
Comments in-line
73 G4ULF
--- In dstar_digital@yahoogroups.com, Barry barrym...@... wrote:
Darren wrote:
To access MB6AM, users should configure their radios in simplex mode
on
144.8625 MHz, with no RPT settings required. If RPT settings are
used, then
the following settings must be
Not quite true.
If you have a small number of synced gateways talking to a Trust Server (which
is actually the standard gateway software running in a Trust Server mode), when
a station moves repeaters, the update is virtually instantaneous across all
repeaters.
In fact, after the initial
There are other reasons why the radio may generate a beep.
The main one is loss of bit-sync.
Every 21st frame has 0x55 0x2d 0x16 at the end - if you generate these at 20 or
22 frame intervals, sure enough, you get a beep.
If you miss several, you get a beep.
So, under weak conditions, you can
Ah - that would be much like the terse response I got to ask to join the rtpDir
group then ?
I was told that my access attempt was being logged, and I would be reported to
the FBI...
--- In dstar_digital@yahoogroups.com, Tony Langdon vk3...@... wrote:
At 03:22 AM 10/5/2009, you wrote:
Scott
European G2 TRUST server at: xtrust2.xreflector.net
There is no European Trust Server.
There are a group of German D-Star users that have declared UDI from the
one-and-only worldwide G2 Trust Server and hence partitioned the network.
As people have been working hard to fix the routing
, dlake02 wrote:
I completely agree that DNS is inappropriate for instantaneous moves.
73 David - G4ULF
No offense intended David, but anyone who says this hasn't done it.
DNS can EASILY handle virtually instantaneous updates, when configured
and used correctly. It is NOT used
: dstar_digital@yahoogroups.com [mailto:dstar_digi...@yahoogroups.com] On
Behalf Of Stewart Bryant
Sent: Monday, July 27, 2009 4:31 PM
To: dstar_digital@yahoogroups.com
Subject: Re: [DSTAR_DIGITAL] Re: First home-made dstar G2 gateway went live
today.
dlake02 wrote:
I completely agree
Scott
Sorry to bust your bubble, but I did this over 2 weeks ago now on the real G2
system, not the German one that house a handful of repeaters.
As I am fed up with you not listening to what people are saying, may I just
repeat for the last time:
There is NO European Trust Server. Please
also use the address
space that makes sense, e.g. 10.x.x.x, 44.x.x.x, 192.168.x.x,
172.x.x.x, or x.x.x.x in the IP world.
John
On Jul 24, 2009, at 1:40 PM, dlake02 wrote:
John
The whole use of the 10.X.X.X addresses seems like a real mess, but
in fact, it could be put to very
Hello All
I've had several emails over the weekend asking very similar questions on my
software, so I'm going to make some comments and observations here.
Why ? Quite simple - I already have a very busy day (and evening) job, and the
time I have to reply/work on the code is very limited.
1)
Scott
I think I explained this already.
It can take a VERY long time to receive the database sync from the Trust
Server. In some instances, up to 2 hours after requesting it.
What you are seeing is pretty quick - but I would expect that as you are on a
very small system.
David
--- In
Bryant wrote:
dlake02 wrote:
John
Yes, but my thoughts are why use a relational database to do the
job of
a Routing Protocol ?
Let me clarify. I could be wrong, but don't think I ever mentioned a
relational database in my discussion. I use
Who are We please ?
David
--- In dstar_digital@yahoogroups.com, ham44865 ham44...@... wrote:
We have not decided on the host name yet.
Details will follow in the next couple of weeks.
It will be open to testing and experimentation.
73
Scott/KI4LKF
Hi Jochen
First, you sent me an email asking if I would like to test my software on your
system several weeks ago - I apologise that I have been so busy, that I haven't
gotten round to it yet !
Second. I have some questions about your X-Trust system:
1) Each user requires a unique /28 IP
There is a certain expectation among D-STAR RF users that if they are
in range of a D-STAR repeater, that provides gateway services, that
they should be able to do callsign routing to any other D-STAR RF user
that is in range of a gateway equipped D-STAR repeater. This means
that they all
Scott
Some comments on your code logic please (all meant in the spirit of
co-operation, NOT criticism):
1) dstar_register_rptr. You use the call strcpy(ip, inet_ntoa(ia));
However ia has already been set to the IP Address of the Trust Server.
If this is a registration, the IP address sent in
Scott
This is the source downloaded today:
dstar_gwy.zipi386 17.5 KiBSun Jul 19 2009 10:44
David
Scott
Do not twist my words please.
I didn't say that a Trust Server didn't work.
What I said was that whilst Icom have designed the G2 Trust Server to be
able to be run as a devolved system, that piece of code doesn't work.
You cannot build the Icom system as a cascade of units.
IF the Icom
@yahoogroups.com, ham44865 ham44...@... wrote:
It has changed 10 times since then. OLD stuff.
The one I am running now, it is flawless.
I will post another copy after I define it to run as a
Linux service.
Scott
--- In dstar_digital@yahoogroups.com, dlake02 dlake@ wrote:
Scott
registrations to us trust
and 3 to European trusts.
No 10.x.x.x anywhere in any registration packet
for a NEW repeater.
Scott
--- In dstar_digital@yahoogroups.com, dlake02 dlake@ wrote:
Scott
If this is a registration, the IP address sent in the initial sequence
should be a subnet
--- In dstar_digital@yahoogroups.com, John Hays j...@... wrote:
On Jul 24, 2009, at 12:33 PM, dlake02 wrote:
Scott
In the initial packet, the IP address is set to a 10.X.X.X/28
address. You won't see that in the database, because it is only sent
until the Zone RP is authorized
went live with the European TRUST server a couple of weeks ago.
Scott/KI4LKF
--- In dstar_digital@yahoogroups.com, dlake02 dlake@ wrote:
Scott
Congratulations on your progress.
Last night, I had a conversation via the GB7NM with G3SMU from GB7MH -
totally G2 routed
At the end of last week, GB7MH, currently awaiting installation at our repeater
site, was connected to the live Icom G2 Trust Network.
The repeater uses my Linux-based G2 compatible code, Robin Cutshaw's DPlus code
(unmodified) and Pete Loveall's D-Star Monitor code (unmodified).
The repeater
24 matches
Mail list logo
