Possible firmware bug in R12.00.13

This forum is dedicated to discussions pertaining specifically to the Motorola ASTRO line of radios (those that use VSELP/IMBE/AMBE), including using digital modulation, digital programming, FlashPort upgrades, etc. If you have general questions please use the General or Programming forums.

Moderator: Queue Moderator

Post Reply
motoman30
New User
Posts: 11
Joined: Sun May 10, 2009 3:49 pm

Possible firmware bug in R12.00.13

Post by motoman30 »

I might have come across a firmware bug here. Not really a bug, just the radio doing something which doesn't make any sense.

Radio details:

XTS5000 Model III
700/800 MHz
Host: R12.00.13
DSP: R12.00.04
Secure: R05.03.00 DES-OFB/DES-XL/AES-256
589088-401687-7 (Engineering radio)
BRAVO122

System type is 3600 SmartZone Omnilink. 800 MHz; no rebanding channels.

Condition:

- Sitting on digital talkgroup
- Secure enabled
- Key strapped to DES-OFB (Radio shows Ø on the screen when TX or RX.)
- Dispatcher, using a console, is multi-selecting the digital dispatch talkgroup, and a legacy analog dispatch talkgroup.
- AES icon appears on the screen next to the Ø symbol. Both the Ø and AES icon DO NOT flash (clear tx from dispatch)
- AES icon only appears on multi-select transmissions
- We do not use AES-256 on this talkgroup. AES-256 keys are not loaded into the DIU3000.
- When dispatch unkeys, AES icon disappears.
- AES icon not present on subscriber RX if dispatcher disables the multiselect at the console.

Just to make it clear, our dispatch is intentionally transmitting digital/clear. This how we wanted it.

This "bug" doesn't negatively affect anything, but I don't think the AES icon is supposed to appear during reception of a multiselect transmission. Can anyone else replicate this? Not a critical bug by any means, just a quirk.

And for what it's worth, we do have talkgroups which are strapped secure with AES-256, but dispatch does not have access to them. The codeplug is configured properly and the AES-256 keys are not strapped to the dispatch talkgroup. (AES normally will appear on the screen when you're strapped to an AES-256 key.)
akardam
Posts: 2251
Joined: Thu Mar 04, 2004 10:53 am

Re: Possible firmware bug in R12.00.13

Post by akardam »

Don't know if you can claim it as a bug in 12.00.13 without having an identically provisioned prior-firmware radio to test with. Has this radio always done this, or just started after a firmware refresh?
motoman30
New User
Posts: 11
Joined: Sun May 10, 2009 3:49 pm

Re: Possible firmware bug in R12.00.13

Post by motoman30 »

Hi akardam. I don't have any other radios to test with. All radios have the same firmware version. This was a recent analog-->digital upgrade, hence the multiselect to the old analog talkgroup for the time being. All brand new stuff.

I spotted this "bug" as I'm familiar with the way the radio behaves on other talkgroups.
motoman30
New User
Posts: 11
Joined: Sun May 10, 2009 3:49 pm

Re: Possible firmware bug in R12.00.13

Post by motoman30 »

This thread may be closed. I found the cause for this "bug", which in fact, is NOT a bug.

Under the Trunking System/Multikey tab, there's a pulldown box for "Patch Key". Supposedly you can specify a key to be used during patched talkgroup communications. Very interested.

Our selection was defaulted to Key 1, which happens to be the AES-256 key.

My error.
Post Reply

Return to “Legacy Batboard Motorola ASTRO (VSELP/IMBE/AMBE) Equipment Forum”