Re: [App_rpt-users] stuck transmitting/timedout, can't get it to unkey
Did it ever work correctly? Have you checked the COR line or COR settings? Neil
The URI and modified fobs need to see a hardware signal that goes to ground on an active hi or low state. If one is using hardware cor from a radio, then it needs to pull to ground if active low or active hi. It does not need to have a voltage output. It just needs to pull to ground. If your radio is sourcing a voltage but doesn't pull to ground then the URI or fob may not see a signal change and think the cor is open. App_ Rpt may think the receiver is open depending on your settings in usbradio.conf in the "COR from" line. This is because any sourced voltage from the radio is blocked by the diode going to one of the input lines. The CM108 chip has internal pullup resistors on its cor input lines so it doesnt need external voltage, hence the diode in line. In all may systems I modify the radios to have open collector that pulls to ground on a signal. All my systems are "active low" this way. If you have a radio that doesn't pull to ground then you can use the cor signal to drive an NPN transistor. connect the collector to the fob/ URI and invert your setting in usbradio.conf. One other thing, On simplex nodes I have seen some radios where the cor goes active on transmit when connected through the Packet interface to fobs/URIs. In this case you might want to use DSP squelch instead of external hardware for cor. Just some thoughts. Jon VA3RQ On 11/5/2010 8:23 AM, Neil Addis (WA5JXY) wrote:
Did it ever work correctly? Have you checked the COR line or COR settings?
Neil _______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
It does work correctly. It is currently working correctly but the strange thing is that intermittently (sometimes many hours apart), it will go into a state where it thinks there is a reason to be keyed, even though as far as I can tell there is nothing telling it to key. While it is not in this bad state, everything seems to work. Id timers, time out timers, hang time, cor, ptt, repeat audio, telemetry, linking, unlinking, etc. But once in a while the transmitter comes on the air and stays on the air until timeout, then drops off the air and then nothing that I do will allow it to come on the air again until I reboot. From the dump it looks like it is some mysterious link 0 that is the reason for it keying. I have been tweaking audio levels today and have been rebooting every few hours because of making hardware changes related to audio coupling with the radios and the USB-fob, so it has not done the mysterious timeout today. I plan to leave it alone tonight and see how it is tomorrow after running all night without any configuration changes. By the way, my radio outputs 5 volts with no signal and outputs 0 volts with received signal, I use that 5 volts to drive the base of a transistor through a 10k series resister, the emitter grounded, and the collector to the USB-fob cor (cm108 pin 48 voldn). This is just temporary as I intend to use the DSP PL decode in the future. For now this is working, except when it looses its mind and needs a reboot. Chuck On Fri, Nov 5, 2010 at 7:23 AM, Neil Addis (WA5JXY) <wa5jxy@gmail.com>wrote:
Did it ever work correctly? Have you checked the COR line or COR settings?
Neil _______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
participants (3)
-
Chuck Henderson -
Jon Rorke -
Neil Addis (WA5JXY)