I should further clarify the "duplex=1 mode" settings. This is the mode when in rpt.conf has duplex set to 1 and usbradio has duplex=0. This config is a half duplex mode but gives a courtesy beep and tail after RX activity. The duplex=1 mode in rpt.conf tells the node it is in half duplex mode but sends a courtesy beep and a tail after it receives a signal from the node receiver. The duplex=0 in usbradio tells the URI hardware that your radio is only half duplex and cannot transmit while receiving. The setup for half duplex nodes is kinda nice as it tells the user that they are making the sinplex node. A setting of duplex =0 in rpt conf and duplex =0 in usbradio is the same as above with no courtesy tone and no tail. It works just as well as above but there is no local feedback to let you know if you are hitting the simplex node or not. Jon VA3RQ On 9/27/2014 12:11 PM, REDBUTTON_CTRL wrote:
Ok In a bid to understand what it is you think is wrong let me clarify from what you are saying below. Your node is set up for duplex=1 (half duplex with courtesy beep and tail) right? And the problem you are seeing is the node will not receive a signal when it is transmitting the courtesy beep or tail - right?
If the above is correct, then this configuration cannot receive a signal while it is transmitting. This is normal for this configuration. If your radio is portable or mobile radio, then your radio can only receive or transmit but not both simultaneously. So in duplex =1 mode the URI assumes your receiver is active if the node isnt transmitting. So the node ignores all receiver activity while its transmitting. Once the tail is gone then it will listen to thereceiver cor line.
For some reason from you explanation below you are expecting the node to receive in full duplex. Unless the radio you have connected is capable of full duplex, this wont work. If the radio connected to the URI is a pair of radios or a duplexed base station and if you set the duplex setting to duplex=2 in rpt conf and duplex =1 in usbradio then it will receive while its transmitting.
Hope I understand this right and this helps.
Jon VA3RQ
On 9/27/2014 11:47 AM, Mike M wrote:
I'm starting to think its the URI.
First, I got rid of all the components (transistor and RC) because they made little difference and don't want the added complexity. I went back to usbinvert. I brought the radio and URI to the 1620 node on the VM (basically a stock install of ACID) and connected Zoiper directly to the node. This left the BBB and its configuration completely out of the loop and I still got the same behavior.
Next I reconnected the URI and radio to the BBB and connected directly to it via Zioper (I didn't do this before because I was having trouble connecting Zoiper to the BBB, but I got that figured out) and it's still the same behavior.
And just to eliminate the radio, I disconnected it completely, connected the COR input to a pullup, and grounded it by hand. When I ground the COR line (usbinvert), I can hear slight background noise through Zoiper and when I unground it, the courtesy tone is triggered (URI PTT active as well) and then the background noise goes away when the CT is done. But if I ground the COR line while the courtesy tone is playing, it ignores the COR and does not pass audio to zioper until I cycle the COR line again.
And finally I tried using the CTCSS input, same exact behavior.
I know there is a URI test program from DMK, but I didn't really see a way to simply read out the status of the inputs, just automated tests requiring a loopback.
-Mike
sage to the list detailing the problem.
App_rpt-users mailing list App_rpt-users@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.