[App_rpt-users] App_rpt-users Digest, Vol 80, Issue 104

Mark DuMoulin @ WB2ERS wb2ers at metcom.com
Fri Oct 30 12:13:39 UTC 2015


Yes please sign me up.

User: wb2ers
Password: wb2ers

I assume I can change the password once I have a login


Mark DuMoulin
WB2ERS
Wb2ers at metcom.com
C 800-410-3130



-----Original Message-----
From: app_rpt-users-bounces at ohnosec.org [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of app_rpt-users-request at ohnosec.org
Sent: Thursday, October 29, 2015 8:38 PM
To: app_rpt-users at ohnosec.org
Subject: App_rpt-users Digest, Vol 80, Issue 104

Send App_rpt-users mailing list submissions to
	app_rpt-users at ohnosec.org

To subscribe or unsubscribe via the World Wide Web, visit
	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 at ohnosec.org

You can reach the person managing the list at
	app_rpt-users-owner at ohnosec.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of App_rpt-users digest..."


Today's Topics:

   1. Re: DIAL Question (Corey Dean)
   2. Re: DIAL simpleusb (Tim Sawyer)
   3. Re: UIR Startup (Mark DuMoulin @ WB2ERS)
   4. Re: UIR Startup (Steve N4IRS)
   5. Re: AMBE question (Bryan Fields)
   6. Re: AMBE question (ronald simpson)


----------------------------------------------------------------------

Message: 1
Date: Thu, 29 Oct 2015 12:18:58 -0400
From: Corey Dean <n3fe at repeater.net>
To: David McGough <kb4fxc at inttek.net>
Cc: app_rpt-users at ohnosec.org
Subject: Re: [App_rpt-users] DIAL Question
Message-ID: <D3C84F7B-CF9A-4B21-A85C-E92319C8BEB3 at repeater.net>
Content-Type: text/plain;	charset=us-ascii

Yes!  I ran it that way with an r100 for a few weeks before moving it over to the msf5000.  I had no issues running simpleusb and usbradio.  I don't have any of the cracks or pops anywhere that you are referring to running usbradio.  I do know what you are talking about but I have never experienced that on any of my equipment.

Sent from my iPhone

> On Oct 29, 2015, at 10:14 AM, David McGough <kb4fxc at inttek.net> wrote:
> 
> 
> Has anyone tested the simpleusb driver with the RPi2 version of DIAL?
> 
> 
>> On Thu, 29 Oct 2015, Corey Dean wrote:
>> 
>> I thought I had replied to everyone and I noticed I only replied to Neil.  I have been running the Debian rpi2 image for quite a while.  Way back when Steve first created it.  I run it in full duplex mode using usbradio on an msf5000 with no issues at all.  
>> 
>> I know what you are talking about with the echo issue.  That seems to just be a problem on the arch image on the hamvoip site as that is the only place I have heard it.  I did try that image long and and having audio delays at almost 10 seconds and time just made it unusable.  That was even using simpleusb.  No problems running usbradio and dsp on the Debian image.
>> 
>> To make a long story short, the Debian image just works! No have had zero issues with it.
>> 
>> Corey N3FE
>> 
>> Sent from my iPhone
>> 
>>> On Oct 29, 2015, at 8:46 AM, Jon Rorke <jrorke at cogeco.ca> wrote:
>>> 
>>> I have been playing with the full duplex mode using DSP decode (PL, carrier squelch) in and out on the RPI2 with DIAL and so far it seems to be on par with what Acid does on a PC. 
>>> 
>>> There is some latency due to audio processing but its about 200 to 250 ms and seems to be stable. I have never seen an acid box with 0 latency on the full duplex audio. 
>>> 
>>> In may opinion it woks just as well as an ACID set up on a pc  for a single full duplex repeater node.
>>> 
>>> Can;t speak to the other questions though.
>>> 
>>> Jon VA3RQ
>>> 
>>>> On 10/28/2015 5:48 PM, Neil k8it wrote:
>>>> I have been waiting a bit before I start playing with DIAL on a RPI2.
>>>> I still have two questions
>>>> 1. Does the RPI2 DIAL  version solve the tx echo buffer issue that the current version of Asterisk RPI2 code has. The fix to this issue seems to be taking a long           time.
>>>> 2. Some users have reorted that a lot of modules have been disabled, such as the Echolink channel driver and others.
>>>> 3. With the new Mini-DV4  dongle $125  and the amount of 
>>>> capability, has anybody wrote a channel driver to tie the Yaesu 
>>>> Fusion Wires-X network into DIAL. It appears that most of the 
>>>> documentation is out there, we just need someone to write the 
>>>> channel driver
>>>> 
>>>> 
>>>> Thanks
>>>> 73 Neil Sablatzky  K8IT
>>>> Allstar Node 41838 KITLINK
>>>> Allstar Node 42087 KITLINK HUB
>>>> IRLP Node exp0068
>>>> Echolink K8IT-L
>>>> WIRES-X K8IT 11479 Room 21479
>>>> 
>>>> From: Steve N4IRS
>>>> Sent: Tuesday, October 27, 2015 10:35 AM
>>>> To: N7MTC . ; app_rpt-users at ohnosec.org
>>>> Subject: Re: [App_rpt-users] Procedure for loading DIAL on a R-Pi2 
>>>> or a PC
>>>> 
>>>> Mac,
>>>> The RPi2 install is pretty much download the image, burn it to SD card,.
>>>> Once the Pi boots, you can login on the HDMI / USB console, or SSH into the board on port 222.
>>>> The board is setup for DHCP so check your DHCP (router) server for address.
>>>> If you want, you can login via the built in serial port at 115,200 
>>>> System will walk you through setup.
>>>> 
>>>> FAQ for DIAL is at:
>>>> <http://docs.allstarlink.org/drupal/node/170>
>>>> 
>>>> 73, Steve N4IRS
>>>> 
>>>> 
>>>>> On 10/27/2015 10:20 AM, N7MTC . wrote:
>>>>> Is there a procedure for loading the "new" DIAL version of asterisk for Raspberry pi2?  
>>>>> 
>>>>> I am looking to connect either a Pi2 or an intel NUC to a Yaesu Dr-1x using the Arcom RC-210 and  the Arcom ADR.  I noticed DIAL has replaced ACID as the latest flavor of asterisk for both PC and PI2.  I have not found any install write-ups or YouTubes showing a DIAL install.
>>>>> 
>>>>> Regardless of which platform I will need to use an USB to Serial adapter to connect the ALLSTAR node to the repeater controller.  It will be of the FTDI chipset either a trendnet Tu-s9 or a GearMo USB RS-232.
>>>>> 
>>>>> 
>>>>> /73
>>>>> Mac, N7MTC
>>>>> 
>>>>> 
>>>>> Benjamin Franklin - "Those who surrender freedom for security will not have, nor do they deserve, either one."
>>>>> 
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> App_rpt-users mailing list
>>>>> App_rpt-users at 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 at 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.
>>>> No virus found in this message.
>>>> Checked by AVG - www.avg.com
>>>> Version: 2015.0.6173 / Virus Database: 4455/10900 - Release Date: 
>>>> 10/27/15
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> App_rpt-users mailing list
>>>> App_rpt-users at 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 at 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.
> 


------------------------------

Message: 2
Date: Thu, 29 Oct 2015 10:25:28 -0700
From: Tim Sawyer <tisawyer at gmail.com>
To: Steve N4IRS <szingman at msgstor.com>
Cc: "app_rpt-users at ohnosec.org" <app_rpt-users at ohnosec.org>
Subject: Re: [App_rpt-users] DIAL simpleusb
Message-ID:
	<CAG3ht9uW80TNGu9BGZghqGg3FozagJ_dmrwJFA3Ygo5XjzmhAg at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Working fine including GPIO.

On Thursday, October 29, 2015, Steve N4IRS <szingman at msgstor.com> wrote:

> Yes,
> No errors reported.
>
> > Has anyone tested the simpleusb driver with the RPi2 version of DIAL?
>
> --
>          ,,,
>         (o o)
> -----ooO-(_)-Ooo------
> --- N4IRS was Here ---
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at 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.



--
--
Tim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ohnosec.org/pipermail/app_rpt-users/attachments/20151029/50ce6e1d/attachment-0001.html>

------------------------------

Message: 3
Date: Thu, 29 Oct 2015 17:46:39 +0000
From: "Mark DuMoulin @ WB2ERS" <wb2ers at metcom.com>
To: 'Ken' <ke2n at cs.com>, "app_rpt-users at ohnosec.org"
	<app_rpt-users at ohnosec.org>, "Mark DuMoulin @ WB2ERS"
	<wb2ers at metcom.com>
Subject: Re: [App_rpt-users] UIR Startup
Message-ID: <da574ffa2fe54879aae2b807a84a2545 at MAIL2.metcom.com>
Content-Type: text/plain; charset="us-ascii"

Ken,

Sorry, typo on my side about pin 21 and I just rang out the cable anyway.
I have an IAX client connected to Asterisk where I currently have the signaling and audio path IAX - Asterisk - Radio functioning properly.

The opposite path Radio - Asterisk - IAX is not functioning.
CTCSS (URI pin 7) goes from the pulled up 5 volts to 0 when the radio is receiving signal.
I'm assuming that signaling is present through Asterisk as I get a brief upscale indication on the IAX SPK bargraph and I get a caller ID from the URI node when the receiver receives a properly tone coded signal.
There is no audio being routed through to IAX. This is the issue.

Note: IAX works fine with other node types such as radio-gui, radio-gui-cell and radio-phone.


URI DB-25 pin

1. goes to the Radio PTT
7. goes to the CTCSS Detect from the radio and I have a 18k pullup attached to +5 at 14 20. goes to radio Gnd 21. goes to Radio Receive Audio out. This is no greater than 0 dbm.
22. goes to the radio flat Transmit Audio in.

We have flashing green indicating app_rpt application is running.

Any ideas?

Mark DuMoulin
WB2ERS
Wb2ers at metcom.com
C 800-410-3130



-----Original Message-----
From: Ken [mailto:ke2n at cs.com]
Sent: Thursday, October 29, 2015 11:01 AM
To: app_rpt-users at ohnosec.org; Mark DuMoulin @ WB2ERS <wb2ers at metcom.com>
Cc: 'Steve Zingman' <szingman at msgstor.com>
Subject: UIR Startup

>>> Also noticed "I have the receiver audio connected to pin 22 Left_Out."
>>> Receive audio goes to mic in pin 9.

Actually - it should normally go to pin 21 "mic AC".
This has an attenuator in line.  
It is possible to burn out the chip if you go direct to pin 9 and overdrive it.

GL
Ken




------------------------------

Message: 4
Date: Thu, 29 Oct 2015 13:47:00 -0400
From: Steve N4IRS <szingman at msgstor.com>
To: "\"Mark DuMoulin\"@WB2ERS" <wb2ers at metcom.com>, 'Ken'
	<ke2n at cs.com>,	"app_rpt-users at ohnosec.org" <app_rpt-users at ohnosec.org>
Subject: Re: [App_rpt-users] UIR Startup
Message-ID: <56325B94.8070204 at msgstor.com>
Content-Type: text/plain; charset=windows-1252; format=flowed

Comment out the rxctcssfreqs line. in usbradio.conf

On 10/29/2015 1:46 PM, Mark DuMoulin @ WB2ERS wrote:
> Ken,
>
> Sorry, typo on my side about pin 21 and I just rang out the cable anyway.
> I have an IAX client connected to Asterisk where I currently have the 
> signaling and audio path IAX - Asterisk - Radio functioning properly.
>
> The opposite path Radio - Asterisk - IAX is not functioning.
> CTCSS (URI pin 7) goes from the pulled up 5 volts to 0 when the radio is receiving signal.
> I'm assuming that signaling is present through Asterisk as I get a brief upscale indication on the IAX SPK bargraph and I get a caller ID from the URI node when the receiver receives a properly tone coded signal.
> There is no audio being routed through to IAX. This is the issue.
>
> Note: IAX works fine with other node types such as radio-gui, radio-gui-cell and radio-phone.
>
>
> URI DB-25 pin
>
> 1. goes to the Radio PTT
> 7. goes to the CTCSS Detect from the radio and I have a 18k pullup 
> attached to +5 at 14 20. goes to radio Gnd 21. goes to Radio Receive 
> Audio out. This is no greater than 0 dbm.
> 22. goes to the radio flat Transmit Audio in.
>
> We have flashing green indicating app_rpt application is running.
>
> Any ideas?
>
> Mark DuMoulin
> WB2ERS
> Wb2ers at metcom.com
> C 800-410-3130
>
>
>
> -----Original Message-----
> From: Ken [mailto:ke2n at cs.com]
> Sent: Thursday, October 29, 2015 11:01 AM
> To: app_rpt-users at ohnosec.org; Mark DuMoulin @ WB2ERS 
> <wb2ers at metcom.com>
> Cc: 'Steve Zingman' <szingman at msgstor.com>
> Subject: UIR Startup
>
>>>> Also noticed "I have the receiver audio connected to pin 22 Left_Out."
>>>> Receive audio goes to mic in pin 9.
> Actually - it should normally go to pin 21 "mic AC".
> This has an attenuator in line.
> It is possible to burn out the chip if you go direct to pin 9 and overdrive it.
>
> GL
> Ken
>
>



------------------------------

Message: 5
Date: Thu, 29 Oct 2015 14:41:16 -0400
From: Bryan Fields <Bryan at bryanfields.net>
To: APP RPT <app_rpt-users at ohnosec.org>
Subject: Re: [App_rpt-users] AMBE question
Message-ID: <5632684C.8080706 at bryanfields.net>
Content-Type: text/plain; charset=windows-1252

On 10/29/15 11:25 AM, Robert Newberry wrote:
> This topic could be another e-mail list. 
Why?

> This is where allstar has it nailed
> being able to link multiple audio paths. We have someone using dstar 
> on our system it sounds pretty decent. I'd like to see p25 and DMR 
> included. I'll stop posting on this as well and keep it last for this list.

I would like to see asterisk being the common platform used for internet linking of any radio systems.  It decouples the network from the technology.
Course this does remove the network operators from the god like status they have and the ensuing circle-jerk :)

--
Bryan Fields

727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net


------------------------------

Message: 6
Date: Thu, 29 Oct 2015 17:37:49 -0700
From: ronald simpson <n6gkj1 at gmail.com>
To: Steve Zingman <szingman at msgstor.com>
Cc: App RPT Users <app_rpt-users at ohnosec.org>
Subject: Re: [App_rpt-users] AMBE question
Message-ID:
	<CANr-_9rhZ9EXMOFaXZ9XX2Hk8CtmqcRd6=yncKqpdV9Xa4+x+g at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I have a considerable investment into Fusion. I will support this effort in any way I can. I ordered one of the dongles that does Fusion, Dstar and DMR. I saw the YouTube video of the demonstration about this dongle in the Fusion mode.

I see alot of potential here in this group

Ron
N6GKJ
On Oct 29, 2015 6:47 AM, "Steve N4IRS" <szingman at msgstor.com> wrote:

> When we did the DMR to AllStar testing, we used the NW Digital Radio 
> DV3000. It was mounted on a RPi2 running asterisk.
> The DV3000 uses AMBE-3000 vocoder chip from DVSI. We tested with 
> Mototrbo and D-Star. Did not have a Fusion or P25 radios.
>
> 73, Steve N4IRS
>
> On 10/29/2015 8:03 AM, David McGough wrote:
>
>> Guys,
>>
>> I haven't looked carefully as to which variants of AMBE are in use by 
>> D-STAR, Fusion, etc...Doesn't the original AMBE patent expire fairly soon?
>>
>> The reason I'm asking is that I know there are some fledgling 
>> open-source AMBE implementations out there.  A couple years ago I 
>> hacked CODEC2 into Asterisk for experimentation, thinking about 
>> directly linking to HF via the FreeDV project--and, not wanting to 
>> transcode from one low-bandwidth CODEC to another, making truly awful audio!
>>
>> After playing with it a few weeks, I didn't do much more...(I've 
>> still got that code and it still works, if anyone wants to play with 
>> it?)
>>
>> ...Just wondering.
>>
>> 73, David KB4FXC
>>
>>
>> On Thu, 29 Oct 2015, Matthew Pitts wrote:
>>
>> Mike,
>>>
>>> You are correct in the statement that the DV4mini needs additional
>>>
>> hardware to handle the transcoding from a digital radio. Once I get 
>> my nodes back up on my Raspberry Pi, I will work on an updated 
>> version of the D-STAR channel driver that supports DMR and Fusion 
>> AMBE encoding and decoding as well as radio control functionality for the DV4mini.
>>
>>> Matthew Pitts
>>> N8OHU
>>>
>>> On October 28, 2015 6:18:34 PM EDT, Mike Zingman 
>>> <mike.zingman at gmail.com>
>>> wrote:
>>>
>>>> Actually the DV4Mini alone does not help tie Allstar into Wires-X.  
>>>> In order to do that one must:
>>>>
>>>> 1) Have an interface to the YSF network protocol
>>>> 2) Decode and extract the AMBE frames from the streamed protocol
>>>> 3) Transcode the frames to PCM at the proper sample rate using the 
>>>> DVSI
>>>> AMBE3000 chipset
>>>> 4) Send those frames to something like the already created USRP 
>>>> channel driver
>>>>
>>>> In reverse, 4, 3, 2, 1 to send data back to the YSF network.  In 
>>>> addition to the simple outline above, you would want to
>>>> a) Add audio filtering/shaping to make the AMBE audio more 
>>>> acceptable to what we are used to on Allstar (one of the single 
>>>> greatest aspects of Allstar is the audio quality)
>>>> b) Transfer of as much metadata between the networks as possible
>>>>
>>>> The DV4Mini is a radio module + digital modulator (DStar/DMR/YSF).  
>>>> It has no AMBE encode/decode hardware so there is no way to 
>>>> transcode the audio content.  For that a "ThumbDV" or a DV3000 
>>>> would be the hardware of choice.  The DV4Mini could be used as a 
>>>> user radio on an existing RF network, but one would still need the 
>>>> AMBE3K to do the transcode.
>>>>
>>>> Mike
>>>>
>>>>
>>>> On Wed, Oct 28, 2015 at 5:48 PM, Neil k8it <k8it at cac.net> wrote:
>>>>
>>>> I have been waiting a bit before I start playing with DIAL on a RPI2.
>>>>> I still have two questions
>>>>> 1. Does the RPI2 DIAL  version solve the tx echo buffer issue that
>>>>>
>>>> the
>>>>
>>>>> current version of Asterisk RPI2 code has. The fix to this issue
>>>>>
>>>> seems to
>>>>
>>>>> be taking a long time.
>>>>> 2. Some users have reorted that a lot of modules have been 
>>>>> disabled,
>>>>>
>>>> such
>>>>
>>>>> as the Echolink channel driver and others.
>>>>> 3. With the new Mini-DV4  dongle $125  and the amount of 
>>>>> capability,
>>>>>
>>>> has
>>>>
>>>>> anybody wrote a channel driver to tie the Yaesu Fusion Wires-X
>>>>>
>>>> network into
>>>>
>>>>> DIAL. It appears that most of the documentation is out there, we 
>>>>> just
>>>>>
>>>> need
>>>>
>>>>> someone to write the channel driver
>>>>>
>>>>>
>>>>> Thanks
>>>>> 73 Neil Sablatzky  K8IT
>>>>> Allstar Node 41838 KITLINK
>>>>> Allstar Node 42087 KITLINK HUB
>>>>> IRLP Node exp0068
>>>>> Echolink K8IT-L
>>>>> WIRES-X K8IT 11479 Room 21479
>>>>>
>>>>> *From:* Steve N4IRS <szingman at msgstor.com>
>>>>> *Sent:* Tuesday, October 27, 2015 10:35 AM
>>>>> *To:* N7MTC . <n7mtc at outlook.com> ; app_rpt-users at ohnosec.org
>>>>> *Subject:* Re: [App_rpt-users] Procedure for loading DIAL on a 
>>>>> R-Pi2
>>>>>
>>>> or a
>>>>
>>>>> PC
>>>>>
>>>>> Mac,
>>>>> The RPi2 install is pretty much download the image, burn it to SD
>>>>>
>>>> card,.
>>>>
>>>>> Once the Pi boots, you can login on the HDMI / USB console, or SSH
>>>>>
>>>> into
>>>>
>>>>> the board on port 222.
>>>>> The board is setup for DHCP so check your DHCP (router) server for
>>>>>
>>>> address.
>>>>
>>>>> If you want, you can login via the built in serial port at 115,200 
>>>>> System will walk you through setup.
>>>>>
>>>>> FAQ for DIAL is at:
>>>>> <http://docs.allstarlink.org/drupal/node/170>
>>>>> <http://docs.allstarlink.org/drupal/node/170%3E>
>>>>>
>>>>> 73, Steve N4IRS
>>>>>
>>>>>
>>>>> On 10/27/2015 10:20 AM, N7MTC . wrote:
>>>>>
>>>>> Is there a procedure for loading the "new" DIAL version of 
>>>>> asterisk
>>>>>
>>>> for
>>>>
>>>>> Raspberry pi2?
>>>>>
>>>>>
>>>>>
>>>>> I am looking to connect either a Pi2 or an intel NUC to a Yaesu 
>>>>> Dr-1x using the Arcom RC-210 and  the Arcom ADR.  I noticed DIAL 
>>>>> has
>>>>>
>>>> replaced
>>>>
>>>>> ACID as the latest flavor of asterisk for both PC and PI2.  I have
>>>>>
>>>> not
>>>>
>>>>> found any install write-ups or YouTubes showing a DIAL install.
>>>>>
>>>>>
>>>>>
>>>>> Regardless of which platform I will need to use an USB to Serial
>>>>>
>>>> adapter
>>>>
>>>>> to connect the ALLSTAR node to the repeater controller.  It will 
>>>>> be
>>>>>
>>>> of
>>>>
>>>>> the FTDI chipset either a trendnet Tu-s9 or a GearMo USB RS-232.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> /73
>>>>>
>>>>> Mac, N7MTC
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Benjamin Franklin - "Those who surrender freedom for security will
>>>>>
>>>> not
>>>>
>>>>> have, nor do they deserve, either one."
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> App_rpt-users mailing
>>>>>
>>>> listApp_rpt-users at ohnosec.orghttp://
>>>> 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 at 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.
>>>>>
>>>>> ------------------------------
>>>>>
>>>>> No virus found in this message.
>>>>> Checked by AVG - www.avg.com
>>>>> Version: 2015.0.6173 / Virus Database: 4455/10900 - Release Date:
>>>>>
>>>> 10/27/15
>>>>
>>>>>
>>>>> _______________________________________________
>>>>> App_rpt-users mailing list
>>>>> App_rpt-users at 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 at 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 at 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 at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ohnosec.org/pipermail/app_rpt-users/attachments/20151029/1df294a8/attachment.html>

------------------------------

_______________________________________________
App_rpt-users mailing list
App_rpt-users at ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users


End of App_rpt-users Digest, Vol 80, Issue 104
**********************************************



More information about the App_rpt-users mailing list