• To anyone looking to acquire commercial radio programming software:

    Please do not make requests for copies of radio programming software which is sold (or was sold) by the manufacturer for any monetary value. All requests will be deleted and a forum infraction issued. Making a request such as this is attempting to engage in software piracy and this forum cannot be involved or associated with this activity. The same goes for any private transaction via Private Message. Even if you attempt to engage in this activity in PM's we will still enforce the forum rules. Your PM's are not private and the administration has the right to read them if there's a hint to criminal activity.

    If you are having trouble legally obtaining software please state so. We do not want any hurt feelings when your vague post is mistaken for a free request. It is YOUR responsibility to properly word your request.

    To obtain Motorola software see the Sticky in the Motorola forum.

    The various other vendors often permit their dealers to sell the software online (i.e., Kenwood). Please use Google or some other search engine to find a dealer that sells the software. Typically each series or individual radio requires its own software package. Often the Kenwood software is less than $100 so don't be a cheapskate; just purchase it.

    For M/A Com/Harris/GE, etc: there are two software packages that program all current and past radios. One package is for conventional programming and the other for trunked programming. The trunked package is in upwards of $2,500. The conventional package is more reasonable though is still several hundred dollars. The benefit is you do not need multiple versions for each radio (unlike Motorola).

    This is a large and very visible forum. We cannot jeopardize the ability to provide the RadioReference services by allowing this activity to occur. Please respect this.

Smart PTT

billy2047

📶 🕨 Ø T₁ ÆS Ⱬ ⬜ ᴴ L |→| 𝅘𝅥 💾 🛰️ 🔋
Joined
Aug 12, 2016
Messages
142
Location
SYS REG RFSD
Hi all,

Could someone tell the difference between "Inhibit on correct NAC" and "Inhibit on Status Symbols" under Smart PTT?

We're operating on conventional P25 (both simplex and repeated) with different NACs. We're having issue with units walking over each other. We don't have this problem on trunking because radio would bonk the other who is trying to talk when someone is already talking.

Thanks all!
 

hitechRadio

Member
Joined
Dec 23, 2010
Messages
556
Strait from the CPS Help, CPS Help is your friend.

Inhibit on Correct NAC
Prevents transmission while the radio is receiving a digital (ASTRO) voice call that has a matching Network Access Code (NAC) for the current channel (see Rx Network ID).

Inhibit on Status Symbols
Prevents transmission while receiving a digital (ASTRO) voice call and when the 'last-received' signal status bit recorded was either inbound busy or unknown.

Either one would solve your issue, I would use Correct NAC inhibit, as Inhibit on status seems to inhibit on any invalid (unknown) signal, even interference.

There is also a new feature for Conv. P25 called Talk Permit Tone under TX Options, it does not have anything to do with your issue above but i thought i would mention it.
It gives a similar experience to trunking, the radio must receive an ACK to transmit, thus be in range of the repeater. Since there is no squelch tail on digital like an analog repeater. the plus side, It gives the user and idea they infact did hit the repeater.
It is a new feature, so your results may very. But our testing so far has been good. It also gives the user a TPT tone they are use to on trunking.
 
Last edited:

billy2047

📶 🕨 Ø T₁ ÆS Ⱬ ⬜ ᴴ L |→| 𝅘𝅥 💾 🛰️ 🔋
Joined
Aug 12, 2016
Messages
142
Location
SYS REG RFSD
I wasn't sure what inbound busy or unknown mean and how would a radio know a channel is busy or unknown when it is operating on simplex P25?
 

dickie757

Wired
Joined
Apr 25, 2017
Messages
479
Location
Out of range
The channel contains information that is kind of like logic. If the frequency in the channel has activity, is it the correct emission? This could be analog, NXDN, DMR, P25, M17, etc. If the emission type is recognized as a valid type by the variables in the channel, then the next step is to check out NAC, then talkgroup. If any of those variables do NOT match up to channel info, the light is illuminated, but no audio is passed to the speaker.

While most channel programs include logic to inhibit transmissions while the light is on, programming can allow tx during a busy channel situation, as is your case. It could be intentional or oversight.
 
Top