- App_rpt-users - lists.keekles.org

Re: [App_rpt-users] DIAL Raspberry Pi 2 Delay
by ronald simpson 09 Apr '16

09 Apr '16

Hi guys, Take a look at how the RasPi operates. You have USB2 ports on a USB2 hub. There is only so much data you can push across that bridge. RasPi weak link is the USB2. I am not going to rewrite all the work done by the many masses. I have a similar arrangement, however I use a RasPi for each radio, a small Netgear SW and put in linking shortcuts. This method ALWAYS works... It does not add that much cost or footprint. I have a small compact system in a 50cal ammo can Especially when there is the will there is a way Ron, N6GKJ http://n6gkj.lodiarc.org On Apr 8, 2016 4:03 PM, "Steve Zingman" <szingman(a)msgstor.com> wrote: Matt, The 3 is supported check the download link. 73, Steve N4IRS Sent via smoke signal (AT&T 4G LTE) -------- Original message -------- From: Matt Brennan <brennanma(a)gmail.com> Date: 04/08/2016 3:33 PM (GMT-05:00) To: Kevin Custer <kuggie(a)kuggie.com> Cc: app_rpt-users(a)ohnosec.org Subject: Re: [App_rpt-users] DIAL Raspberry Pi 2 Delay This is a portable crossband repeater setup in a Pelican case. It is intended to be deployed during public service events. Raspberry Pi's were used to keep the form factor small (and the cost down, since it's all out of pocket). We tried to use a Raspberry Pi 3, but unfortunately it doesn't seem to be supported yet. We aren't really doing any processing. It's two radios on simplex channels, with a third that transmits on both. The largest number of audio paths enabled at any given time is 2. A Raspberry Pi 2 should be able to handle that. In fact, the CPU never goes above 30%. I have another one running Asterisk that can handle managing 10 active SIP calls without an issue. -Matt On Fri, Apr 8, 2016 at 11:16 AM, Kevin Custer <kuggie(a)kuggie.com> wrote: > 3 radios on one Raspberry Pi 2? I guess my next question would be why? > > If you are running SimpleUSB now, switching to USBradio will likely make > the situation worse as there is generally more DSP going on in USBradio > than SimpleUSB - depending on exact configuration. > > Raspberry Pi's are inexpensive as compared to some PC's which could have > enough horsepower to properly operate 3 or 4 radio interfaces, even in full > DSP. If you really want to run multiple radio adapters on a single > appliance, consider choosing a hardware platform powerful enough to do it > properly. > > Kevin > > > On 4/8/2016 9:52 AM, Matt Brennan wrote: > >> Sorry - 3. 3 separate simplex radios. >> >> Someone else individually replied to me and said it's likely an issue >> with SimpleUSB and I should try using usbradio instead. I will be trying >> that tomorrow, but still open to other suggestions. >> >> Thanks again, >> Matt, NM1B >> > > _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users 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 App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users 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.

1 0

Re: [App_rpt-users] DIAL Raspberry Pi 2 Delay
by Steve Zingman 08 Apr '16

08 Apr '16

Matt, The 3 is supported check the download link. 73, Steve N4IRS Sent via smoke signal (AT&T 4G LTE) -------- Original message -------- From: Matt Brennan <brennanma(a)gmail.com> Date: 04/08/2016 3:33 PM (GMT-05:00) To: Kevin Custer <kuggie(a)kuggie.com> Cc: app_rpt-users(a)ohnosec.org Subject: Re: [App_rpt-users] DIAL Raspberry Pi 2 Delay This is a portable crossband repeater setup in a Pelican case. It is intended to be deployed during public service events. Raspberry Pi's were used to keep the form factor small (and the cost down, since it's all out of pocket). We tried to use a Raspberry Pi 3, but unfortunately it doesn't seem to be supported yet. We aren't really doing any processing. It's two radios on simplex channels, with a third that transmits on both. The largest number of audio paths enabled at any given time is 2. A Raspberry Pi 2 should be able to handle that. In fact, the CPU never goes above 30%. I have another one running Asterisk that can handle managing 10 active SIP calls without an issue. -Matt On Fri, Apr 8, 2016 at 11:16 AM, Kevin Custer <kuggie(a)kuggie.com> wrote: > 3 radios on one Raspberry Pi 2? I guess my next question would be why? > > If you are running SimpleUSB now, switching to USBradio will likely make > the situation worse as there is generally more DSP going on in USBradio > than SimpleUSB - depending on exact configuration. > > Raspberry Pi's are inexpensive as compared to some PC's which could have > enough horsepower to properly operate 3 or 4 radio interfaces, even in full > DSP. If you really want to run multiple radio adapters on a single > appliance, consider choosing a hardware platform powerful enough to do it > properly. > > Kevin > > > On 4/8/2016 9:52 AM, Matt Brennan wrote: > >> Sorry - 3. 3 separate simplex radios. >> >> Someone else individually replied to me and said it's likely an issue >> with SimpleUSB and I should try using usbradio instead. I will be trying >> that tomorrow, but still open to other suggestions. >> >> Thanks again, >> Matt, NM1B >> > > _______________________________________________ App_rpt-users mailing list App_rpt-users(a)ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users 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.

1 0

DIAL Raspberry Pi 2 Delay
by Matt Brennan 08 Apr '16

08 Apr '16

Hello, I am running into a fun issue with DIAL using multiple URIx's on a RasPi 2. The issue is that we have a variable delay between the radios. Sometimes the delay is virtually non-existent. Other times, the delay is almost 2 seconds. There is nothing else running on the RasPi. I have a number of theories, including that this is a USB delay issue. Anyone run into this? Or have an idea how to work around it? Thanks and 73, Matt, NM1B

2 5

Port 4569 forwarding
by Richard Ames 07 Apr '16

07 Apr '16

Port forwarding for 4569 does not appear to work on node 43153. May need to be forced. Thanks, Dick Ames KI6NOX Lincoln, CA. Sent from Mail for Windows 10

1 0

DIAL trunk
by Ken 07 Apr '16

07 Apr '16

I think I found a bug in my DIAL distribution. It only affects trunk lines as far as I can tell. When I added "trunk=yes" to iax.conf file I got an warning message in the CLI: WARNING[19228]: chan_iax2.c:11128 build_user: Unable to support trunking on user 'iaxclient' without timing Where 'iaxclient' was the context name I was using. Looking into chan-iax.c I found this: /* WB6NIL backport stuff */ #define DAHDI_FILE_TIMER "/dev/zap/timer" #define DAHDI_FILE_PSEUDO "/dev/zap/pseudo" Since the DIAL distribution does not have "zap" and uses "dahdi" instead, this creates a problem, ultimately resulting in the warning message. There is also a related message in the asterisk log when you start or restart asterisk: WARNING[2334] chan_dahdi.c: Unable to open '/dev/dahdi/pseudo': No such file or directory I changed the source to read "/dev/dahdi/timer" "/dev/dahdi/pseudo" and recompiled asterisk. Now it accepts the trunk parameter without issuing the warning message and the message in the log file is gone (next step - actually getting the trunk to work). 73 Ken

1 0

Re: [App_rpt-users] RTCM voter problem - try 2
by James Cizek 07 Apr '16

07 Apr '16

Thanks Sam, that was a good catch. I have tried so many different things I didn't see that I missed putting that back in. It did not help anything. I restarted asterisk, and rebooted the RTCM. It just sits there saying the GPS receiver is active and that it sees 9 satellites. The yellow light blinks forever and it never logs into the asterisk server. With the "master" setting in voter.conf, it's apparent that the RTCM is talking to the server as when the menu item 10 is set to "2"(none), the asterisk log spools by with many "voter client trying to authenticate as a mix client" error. This stops happening immediately when menu item 10 is set to either 0 or 1 (as would be expected). Any other ideas on where to look? Thanks for the help! James KI0KN On Tue, Apr 5, 2016 at 1:27 PM, Sam Skolfield <kj6qfs(a)gmail.com> wrote: > try this: you need to specify a "master" timing source. > > > [general] > port = 667 > buflen = 200 > password = blah > > [1115] > Horsetooth = blah,*master*,transmit > plfilter = y > txtoctype = none > > On Tue, Apr 5, 2016 at 11:56 AM, James Cizek <james.m.cizek(a)gmail.com> > wrote: > >> Hi all, >> >> I posted this problem many months ago and I came to the conclusion at >> that time that it was my 1PPS signal from the GPS into the RTCM that was >> the problem. I have changed hardware now to fix that and I still have the >> problem so I am suspecting a config issue and hope someone will have an >> idea. >> This is on a stock DIAL box. >> >> RTCM is setup and working great as a standard node. >> Everything is working great on the repeater as long as RTCM is in >> non-voter mode. >> >> I have the chan_voter module loading in modules.conf. >> >> Here is my voter.conf: >> >> [general] >> port = 667 >> buflen = 200 >> password = blah >> >> [1115] >> Horsetooth = blah,transmit >> plfilter = y >> txtoctype = none >> >> >> I am happy to share any other config if requested. >> >> In the RTCM menus, I have a static IP, I have the voter server IP, all >> the approriate IP fields filled out. As mentioned, the RTCM works fine with >> the asterisk server when it's in non-voter mode. >> >> Here's the way I am testing: >> Verify RTCM menu item 10 is set to (2) None. >> >> Boot server, then boot RTCM. RTCM console says: >> >> GPS Receiver Active, waiting for aquisition >> GPS signal acquired, number of satellites in view = 9 >> 04/05/2016 17:58:17.560 Time now syncronized to GPS >> 04/05/2016 18:13:18.580 Host Connection established (Pri) (10.16.1.240) >> >> I have a very nice, clean, 5Volt 1PPS signal going to pin 7 on the >> DB15. Verfied with o-scope. >> >> as soon as I change menu item 10 on the RTCM to either a (1) or a (0) >> instead of (2), I *instantly* get this on the RTCM console: >> >> 04/05/2016 18:44:13.660 Lost GPS Time synchronization >> 04/05/2016 18:44:13.660 Host Connection Lost (Pri) (10.16.1.240) >> >> and it sits there forever and never re-establishes connection to the host. >> >> Here is a snippet of the GPS output: >> >> $PFEC,GPtps,160405181603,1,0,1,150701000000,00,17,160405165607,1891,238580 >> $GPGGA,181603,4020.9810,N,10506.4515,W,0,07,00.00,001566.7,M,-020.0,M,, >> $GPGSV,2,1,08,03,53,215,46,07,09,253,37,09,28,305,39,16,63,126,43 >> $GPGSV,2,2,08,22,26,178,44,23,60,316,43,26,52,066,41,31,17,061,34 >> $GPRMC,181603,V,4020.9810,N,10506.4515,W,,,050416,008.9,E,N*1A >> $PFEC,GPtps,160405181603,3,0,1,150701000000,00,17,160405165607,1891,238580 >> $GPGGA,181604,4020.9810,N,10506.4515,W,0,03,00.00,001566.7,M,-020.0,M,, >> $GPRMC,181604,V,4020.9810,N,10506.4515,W,,,050416,008.9,E,N*1D >> $PFEC,GPtps,160405181604,3,0,1,150701000000,00,17,160405165607,1891,238581 >> $GPGGA,181605,4020.9812,N,10506.4495,W,1,07,01.73,001573.3,M,-020.0,M,, >> $GPRMC,181605,A,4020.9812,N,10506.4495,W,,,050416,008.9,E,A*0F >> $PFEC,GPtps,160405181605,3,0,1,150701000000,00,17,160405165607,1891,238582 >> $GPGGA,181606,4020.9812,N,10506.4494,W,1,07,01.73,001573.2,M,-020.0,M,, >> $GPRMC,181606,A,4020.9812,N,10506.4494,W,000.0,283.2,050416,008.9,E,A*06 >> >> >> I am just not sure where to go from here. I can't seem to find anyone >> that's had any problem like this or what might be causing it. >> >> I have tried 5 different RTCMs and 5 different GPSs from 3 different >> manufacturers. >> >> Any suggestions on what I might be missing? >> >> Many thanks for any help anyone can offer! >> >> James >> KI0KN >> >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> 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. >> > > > > -- > KJ6QFS > Sam Skolfield >

3 2

Re: [App_rpt-users] Files listed, zero bytes...
by Steve Wright 06 Apr '16

06 Apr '16

On 07/04/16 06:57, Jim Aspinwall wrote: > ... if only I had room on the volume to support the local copy method. > I think I'm going to have to simply rebuild the node, and have the custom function work re-applied. Sad. Rats. Can you leave a USB disk attached for some scratch storage? Is there a machine on its' local network that you can NFS mount or iSCSI to? Linux networking is absurdly flexible once you get used to it. Steve

1 0

Disabling ID functions
by Stephen - K1LNX 06 Apr '16

06 Apr '16

This is not glaringly obvious to me... so I'm wondering if it's possible or supported. I have my URI tied into a port of my repeater controller specifically for Allstar access and a few other things, and my ID requirement is being handled by the controller itself. How do I disable the ID coming from app_rpt? I saw these options in the rpt.conf file, but I wasn't sure if commenting them out or setting the time to "0" would effectively disable it? idrecording = |iK1LNX ; id recording or morse string see http://ohnosec.org/drupal/node/87 idtalkover = |iK1LNX ; Talkover ID (optional) default is none see http://ohnosec.org/drupal/node/129 idtime = 540000 ; id interval time (in ms) (optional) Default 5 minutes (300000 ms) politeid = 30000 ; time in milliseconds before ID timer expires to try and ID in the tail. (optional, default 30000) tnx Stephen K1LNX

3 5

Re: [App_rpt-users] Files listed, zero bytes...
by Jim Aspinwall 06 Apr '16

06 Apr '16

Interesting potential solution... if only I had room on the volume to support the local copy method. I think I'm going to have to simply rebuild the node, and have the custom function work re-applied. Sad. 4. Files listed, zero bytes... (Steve Wright) ------------------------------ Message: 4 Date: Tue, 5 Apr 2016 11:36:31 +1200 From: Steve Wright <info(a)meshnetworks.co.nz> To: app_rpt-users(a)ohnosec.org Subject: [App_rpt-users] Files listed, zero bytes... Message-ID: <5702FA7F.4050109(a)meshnetworks.co.nz> Content-Type: text/plain; charset=windows-1252; format=flowed On 05/04/16 10:18, Jim Aspinwall <no1pc(a)yahoo.com> wrote: > I tried to SFTP a couple of the files back into the node and while I see what appears to be a successful copy status, the file still shows zero bytes.? > Sounds like you've lost connectivity at some point and its retried the transfer, and not known what to do about the 'existing' (empty) files. Delete the whole tree structure and try the transfer again. It's not really safe to SFTP (or any tenuous-remote copying) over an existing production directory tree. SFTP first to a temp dir, and then login and cp -a Steve

1 0

RTCM voter problem - try 2
by James Cizek 06 Apr '16

06 Apr '16

Hi all, I posted this problem many months ago and I came to the conclusion at that time that it was my 1PPS signal from the GPS into the RTCM that was the problem. I have changed hardware now to fix that and I still have the problem so I am suspecting a config issue and hope someone will have an idea. This is on a stock DIAL box. RTCM is setup and working great as a standard node. Everything is working great on the repeater as long as RTCM is in non-voter mode. I have the chan_voter module loading in modules.conf. Here is my voter.conf: [general] port = 667 buflen = 200 password = blah [1115] Horsetooth = blah,transmit plfilter = y txtoctype = none I am happy to share any other config if requested. In the RTCM menus, I have a static IP, I have the voter server IP, all the approriate IP fields filled out. As mentioned, the RTCM works fine with the asterisk server when it's in non-voter mode. Here's the way I am testing: Verify RTCM menu item 10 is set to (2) None. Boot server, then boot RTCM. RTCM console says: GPS Receiver Active, waiting for aquisition GPS signal acquired, number of satellites in view = 9 04/05/2016 17:58:17.560 Time now syncronized to GPS 04/05/2016 18:13:18.580 Host Connection established (Pri) (10.16.1.240) I have a very nice, clean, 5Volt 1PPS signal going to pin 7 on the DB15. Verfied with o-scope. as soon as I change menu item 10 on the RTCM to either a (1) or a (0) instead of (2), I *instantly* get this on the RTCM console: 04/05/2016 18:44:13.660 Lost GPS Time synchronization 04/05/2016 18:44:13.660 Host Connection Lost (Pri) (10.16.1.240) and it sits there forever and never re-establishes connection to the host. Here is a snippet of the GPS output: $PFEC,GPtps,160405181603,1,0,1,150701000000,00,17,160405165607,1891,238580 $GPGGA,181603,4020.9810,N,10506.4515,W,0,07,00.00,001566.7,M,-020.0,M,, $GPGSV,2,1,08,03,53,215,46,07,09,253,37,09,28,305,39,16,63,126,43 $GPGSV,2,2,08,22,26,178,44,23,60,316,43,26,52,066,41,31,17,061,34 $GPRMC,181603,V,4020.9810,N,10506.4515,W,,,050416,008.9,E,N*1A $PFEC,GPtps,160405181603,3,0,1,150701000000,00,17,160405165607,1891,238580 $GPGGA,181604,4020.9810,N,10506.4515,W,0,03,00.00,001566.7,M,-020.0,M,, $GPRMC,181604,V,4020.9810,N,10506.4515,W,,,050416,008.9,E,N*1D $PFEC,GPtps,160405181604,3,0,1,150701000000,00,17,160405165607,1891,238581 $GPGGA,181605,4020.9812,N,10506.4495,W,1,07,01.73,001573.3,M,-020.0,M,, $GPRMC,181605,A,4020.9812,N,10506.4495,W,,,050416,008.9,E,A*0F $PFEC,GPtps,160405181605,3,0,1,150701000000,00,17,160405165607,1891,238582 $GPGGA,181606,4020.9812,N,10506.4494,W,1,07,01.73,001573.2,M,-020.0,M,, $GPRMC,181606,A,4020.9812,N,10506.4494,W,000.0,283.2,050416,008.9,E,A*06 I am just not sure where to go from here. I can't seem to find anyone that's had any problem like this or what might be causing it. I have tried 5 different RTCMs and 5 different GPSs from 3 different manufacturers. Any suggestions on what I might be missing? Many thanks for any help anyone can offer! James KI0KN

4 10