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