• If posting about a radio issue: Include the HOST, DSP and UCM/secure firmware versions, flashcode and CPS version you're using along with the operating system info. This is critical information.

TX Interrupt over DCDM not working - configuration error or firmware bug?

Status

motoapx

Contributing Member
Joined
Jul 17, 2012
Messages
59
Looks like I'm running into an issue with TRBO TX interrupt over a Dual Capacity Direct channel. Wondering if anyone else is able to replicate this issue, or if it's just a programming oversight on my part.

Configuration:

- Firmware is R02.60.03 for both units
- Both radios are programmed for a simplex channel in DCDM mode; both radios are Timing Leader Eligible, same Color Code, Slot, etc.
- "Allow Interruption" is unchecked for the supervisor radio; checked for the non-supervisor radio
- "TX Interruptible Frequencies" is checked for both radios
- Admit Criteria is "Color Code Free" for both handhelds
- In Call Criteria for the supervisor radio is "TX Interrupt"; "Follow Admit Criteria" for the non-supervisor radio

Behavior:

When a call is initiated by the supervisor radio and the non-supervisor radio attempts to transmit, a channel busy is heard on the unprivileged radio. This is the expected behavior.

When a call is initiated by the non-supervisor radio and the supervisor radio attempts to transmit, the supervisor radio does the following:
- LED flashes a rapid green during the TX attempt. No tone is heard during this time, and it looks like the radio is beginning the interruption.
- Radio gives a single beep after about two seconds -- not the TRBO talk permit chord, but the same short tone as the Self Test Pass / non-secure TX / MDC short sidetone on an APX.
- Immediately after the sidetone-type beep, the channel busy is heard and "Channel Busy" is indicated on the display
- The unprivileged subscriber continues to transmit without being interrupted -- LED stays solid green throughout the interrupt attempt.


As far as I can tell from the available tutorials, the subscribers are configured correctly to allow the interruption by the supervisor radio. If anyone else could attempt this configuration and try to replicate (or just point out what I did wrong), I'd appreciate the feedback. If this does end up being a firmware bug, I'll be opening a case with Motorola to investigate further.
 
Last edited:
OP
M

motoapx

Contributing Member
Joined
Jul 17, 2012
Messages
59
Nailed this one down. (Spoiler alert, it was my fault.)

Looks like the same radio ID inadvertently got cloned between the two test radios when I was programming the feature in. So the supervisor radio was in fact emitting the interruption, but when it saw its own ID on the channel after the interruption was initiated, that seems to convince the radio that the channel is busy.

If nothing else, hope that the problem description helps someone else out if they end up in this situation. Lesson learned on my part, for sure.
 
Status