Log into the RTCM and select “d” for diagnostics and pres “1” for set initial tone level then set for 3khz deviation. That’s what I do at least. They match my Acid nodes.
k0jsc
···
On Wed, May 11, 2016 at 10:00 AM, app_rpt-users-request@ohnosec.org wrote:
Send App_rpt-users mailing list submissions to
app_rpt-users@ohnosec.orgTo subscribe or unsubscribe via the World Wide Web, visit
[http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users)or, via email, send a message with subject or body ‘help’ to
app_rpt-users-request@ohnosec.orgYou can reach the person managing the list at
app_rpt-users-owner@ohnosec.orgWhen replying, please edit your Subject line so it is more specific
than “Re: Contents of App_rpt-users digest…”
Today’s Topics:
RTCM transmit adjustment (James Cizek)
Re: RTCM transmit adjustment (Tim Sawyer)
Re: Help Tuning Stats Server (Tim Sawyer)
more XIPPR XIPAR or whatever it’s called (Steve Wright)
Re: RTCM transmit adjustment (Jesse Lloyd)
Message: 1
Date: Tue, 10 May 2016 11:00:55 -0600
From: James Cizek james.m.cizek@gmail.com
To: app_rpt mailing list app_rpt-users@ohnosec.org
Subject: [App_rpt-users] RTCM transmit adjustment
Message-ID:
<CAEhYShKfZHZTB-mnzjB3+V3-xNou4WheU7_yuQroeH678m_=ag@mail.gmail.com>Content-Type: text/plain; charset=“utf-8”
Hi all,
For those of you using RTCMs on your repeaters… I was wondering what
procedure you use to set the TX level on your RTCM. There are great tools
built into the RTCM/Allstar for setting squelch and RX levels, but TX is
left pretty much to your imagination.
Curious how folks are going about this. On the hardware-only path
controllers (SCOM, Arcomm, etc…) it’s very clearly documented about how
they’d like you to set levels throughout the audio path. There is even
reasonably good documentation for setting TX levels with a URIx. The RTCM,
not so much.
I’ve got a few of the RTCMs deployed now and things sound really good, but
I am following my own made-up procedure based on what I think it should
be. Got to wondering how others are doing it and if I could improve my
methods any.
Thanks for sharing!
James
KI0KN
-------------- next part --------------
An HTML attachment was scrubbed…
URL: <http://ohnosec.org/pipermail/app_rpt-users/attachments/20160510/c60a0ff3/attachment-0001.html>
Message: 2
Date: Tue, 10 May 2016 16:17:54 -0700
From: Tim Sawyer tisawyer@gmail.com
To: James Cizek james.m.cizek@gmail.com
Cc: app_rpt mailing list app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] RTCM transmit adjustment
Message-ID:
<CAG3ht9tPzXH726A58REQ0AC10bV6cpK2RGJoYST7ENy5wwjSHA@mail.gmail.com>Content-Type: text/plain; charset=“utf-8”
Set 'em the same way as any other device. Send a tone with cop,4 and adjust
(with the RTCM pot) for 3KHz (no P/L) on your service monitor.
for example:
*CLI> rpt cmd cop 4
where = any string or number (command parser is kinda dumb)
Repeat above command (type up arrow) to stop tone.
On Tue, May 10, 2016 at 10:00 AM, James Cizek james.m.cizek@gmail.com
wrote:
Hi all,
For those of you using RTCMs on your repeaters… I was wondering what
procedure you use to set the TX level on your RTCM. There are great tools
built into the RTCM/Allstar for setting squelch and RX levels, but TX is
left pretty much to your imagination.
Curious how folks are going about this. On the hardware-only path
controllers (SCOM, Arcomm, etc…) it’s very clearly documented about how
they’d like you to set levels throughout the audio path. There is even
reasonably good documentation for setting TX levels with a URIx. The RTCM,
not so much.
I’ve got a few of the RTCMs deployed now and things sound really good, but
I am following my own made-up procedure based on what I think it should
be. Got to wondering how others are doing it and if I could improve my
methods any.
Thanks for sharing!
James
KI0KN
App_rpt-users mailing list
To unsubscribe from this list please visit
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down
to the bottom of the page. Enter your email address and press the
“Unsubscribe or edit options button”
You do not need a password to unsubscribe, you can do it via email
confirmation. If you have trouble unsubscribing, please send a message to
the list detailing the problem.
–
–
Tim
-------------- next part --------------
An HTML attachment was scrubbed…
URL: <http://ohnosec.org/pipermail/app_rpt-users/attachments/20160510/4186f1d3/attachment-0001.html>
Message: 3
Date: Tue, 10 May 2016 16:52:44 -0700
From: Tim Sawyer tisawyer@gmail.com
To: app_rpt mailing list app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] Help Tuning Stats Server
Message-ID:
<CAG3ht9t-kK8xzxozzKwqVdHfL9h8XbQD_J1rbuG3bSJVwKufTQ@mail.gmail.com>Content-Type: text/plain; charset=“utf-8”
Hey Folks,
Check out the new stats server. It’s working much, much better. Very fast
now. Be sure to check out bubble chart’s new look. Good examples are
http://stats.allstarlink.org/getstatus.cgi?2135 and
http://stats.allstarlink.org/getstatus.cgi?2560
It’s still a work in progress and it would be great if everybody banged on
it to <http://stats.allstarlink.org> see how it does under load. We know
the PTT time isn’t always updated properly. If you see any other bugs
please let us know. A post here is good.
A big thank you to David KB4FXC for his work getting Apache tuned and
tweaking the db and programs, to Jim WB6NIL for providing the new server
and restored backups and to all of you for your patience during the outage.
There’s more work yet to be done but were real close to wrapping up this
project.
BTW, Jim is out of the hospital
On Thu, May 5, 2016 at 8:08 PM, Tim Sawyer tisawyer@gmail.com wrote:
While Jim is in the hospital I’m attempting to get the new stats server
working. But I’m out of my element here and need help.
The new server is getting killed by all the status updates and requests.
I’m not sure if Apache is to blame or if the server can’t provide enough
threads or just what the problem is. It looks like there is plenty of free
memory.
If you have experience with high volume CGI applications on Debian/Ubuntu
please email me.
–
Tim
–
–
Tim
-------------- next part --------------
An HTML attachment was scrubbed…
URL: <http://ohnosec.org/pipermail/app_rpt-users/attachments/20160510/2d98824e/attachment-0001.html>
Message: 4
Date: Wed, 11 May 2016 13:42:21 +1200
From: Steve Wright info@meshnetworks.co.nz
To: app_rpt mailing list app_rpt-users@ohnosec.org
Subject: [App_rpt-users] more XIPPR XIPAR or whatever it’s called
Message-ID: 57328DFD.1010803@meshnetworks.co.nz
Content-Type: text/plain; charset=utf-8; format=flowed
Righto, I got most of it running.
NOT for the inexperienced as the passwords are hidden deep in www conf
dirs, and it exercised my find and grep skillz to the max! But therein
is enough information for most l33t hax0rs to find it. Email me if you
want to WORK on it and I’ll be more concise.
Now to add some usbaudio and serialPTT goodness and see if the voter
will fly!
What fun!
S
Message: 5
Date: Tue, 10 May 2016 18:58:58 -0700
From: Jesse Lloyd ve7lyd@gmail.com
To: James Cizek james.m.cizek@gmail.com
Cc: app_rpt mailing list app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] RTCM transmit adjustment
Message-ID: D073AFE9-538D-42FA-8DDF-0AE2B5E8B7E2@gmail.com
Content-Type: text/plain; charset=us-ascii
I set the rx up so it reads 3 Khz deviation on the RTCM’s built in console meter, then set the tx level so I get 3Khz out of my transmitter. (No PL)
I then change from 1khz tone to 800hz followed by 1.8 Khz and verify that the levels dont move as tone frequency changes. Changing levels indicates a pre/de emphasis issue.
If using PL you have to account for that deviation, unless you filter if you with your IFR.
Cheers,
Jesse
On May 10, 2016, at 10:00 AM, James Cizek james.m.cizek@gmail.com wrote:
Hi all,
For those of you using RTCMs on your repeaters… I was wondering what procedure you use to set the TX level on your RTCM. There are great tools built into the RTCM/Allstar for setting squelch and RX levels, but TX is left pretty much to your imagination.
Curious how folks are going about this. On the hardware-only path controllers (SCOM, Arcomm, etc…) it’s very clearly documented about how they’d like you to set levels throughout the audio path. There is even reasonably good documentation for setting TX levels with a URIx. The RTCM, not so much.
I’ve got a few of the RTCMs deployed now and things sound really good, but I am following my own made-up procedure based on what I think it should be. Got to wondering how others are doing it and if I could improve my methods any.
Thanks for sharing!
James
KI0KN
App_rpt-users mailing list
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
App_rpt-users mailing list
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
End of App_rpt-users Digest, Vol 87, Issue 23
