[App_rpt-users] node issues..

[Tony]

well we discovered the problem.

a broken wire.

so it now works, now trying to figure out how to change the
connect/disconnect messages from node # to callsign and how to lower
the announcement levels without bothering the rx/tx levels

On Sat, 27 Jun 2015 19:30:26 -0400
Doug Crompton <doug at crompton.com> wrote:

> If you have carrierfrom=usb then you should see the hungup status in
> the client when you ground pin 8. If you are not you possibly could
> possibly have a bad DMK-URI. Make sure you are using pin 8 on the
> DMK-URI NOT pin 7. Also make sure you have ctcssfrom=no 73 Doug
> WA3DSP http://www.crompton.com/hamradio
> 
> 
> > Date: Sat, 27 Jun 2015 11:20:54 -0400
> > From: w2ibc435 at gmail.com
> > To: doug at crompton.com
> > Subject: Re: [App_rpt-users] node issues..
> > 
> > it don't seem to matter what I do on this thing. COR is +5 on
> > signal. the thing floats at .7 with no signal. I can force it to a
> > ground and the TX still stays locked no messages
> > 
> > carrierfrom=usb is what I am using. 
> > 
> > its getting very close to meeting mr 20 pound sledge then going to
> > the dump.
> > 
> > On Fri, 26 Jun 2015 23:11:00 -0400
> > Doug Crompton <doug at crompton.com> wrote:
> > 
> > > Go into the Asterisk client. Type -  asterisk -rvvv   - at the
> > > Linux prompt. You should see the 'hungup' status when you release
> > > the carrier - COR untrue - not when you key.  If you are not
> > > seeing the hungup command with COS change then there is either
> > > something setup wrong or a hardware problem.  At least in
> > > simpleusb.conf you either set  carrierfrom= usb   or
> > > usbinvert     - usb is high +5 COS on signal and usbinvert is low
> > > (0V) on signal.  It has to be a good low!!!  Less than .5 volts
> > > and preferably close to 0V in that direction.
> > > 
> > > If you can isolate the COS line and connect it to +5 and ground
> > > alternately you should see the hungup status in the client. If the
> > > logic is backwards the system thinks it is always keyed and will
> > > hold all output messages. When you are in that state it can be
> > > very confusing because nothing seems to work right. 73 Doug WA3DSP
> > > http://www.crompton.com/hamradio
> > > 
> > > 
> > > > Date: Fri, 26 Jun 2015 22:34:23 -0400
> > > > From: w2ibc435 at gmail.com
> > > > To: app_rpt-users at ohnosec.org
> > > > Subject: Re: [App_rpt-users] node issues..
> > > > 
> > > > its new install, and yes it is the DMK URI. and yes repeater is
> > > > hooked up.
> > > > 
> > > > receiver COR is active high (+5V when signal is detected) but
> > > > it is doing this without any signal from the receiver cor and
> > > > with signal from cor. 
> > > > 
> > > > in usbradio.conf for COR detect I have tried DSP,USB,USBINVERTED
> > > > nothing changes with the output.
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > On Fri, 26 Jun 2015 22:17:31 -0400
> > > > Robert Newberry <N1XBM at amsat.org> wrote:
> > > > 
> > > > > Is this a brand new install? Is there a radio hooked to your
> > > > > sound card? I've run into this once where the COR pin was
> > > > > active high, thus disconnecting the DB25 caused it to think
> > > > > there was a signal on the input thus causing PTT. Are you
> > > > > using a DMK  URI? Are you getting ptt indication?
> > > > > 
> > > > > N1XBM
> > > > > Apparare Scientor
> > > > > Paratus Communicare
> > > > > Allstar Node # 27086, 41540, 41812
> > > > 
> > > > _______________________________________________
> > > > 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. 
> > > > 
> > >  		 	   		  
> > 
>