Batboard

Batlabbers - maybe you can figure this one out, I can't. Situation is an XTS 3000 Series 3 with 591008-4F1E00-9 Flash, DSP of 8.02.08 and Firmware of 7.12.0.

Touching the first Zone assignment, or having any Astro signalling enabled on Conventional personalities (yes, someone actually uses this as a fallback, cute ..) causes MODAT and Secure Config to show errors in CPS which then can't be cleared by changing the settings of those fields back to the original, ie once you modify them, you can't rectify the error,even though you reset the field back to it's original data value. Darn strange.

The error is always in the same areas: MODAT (Revert), Secure Config, Scan Config(main). Since these all go to a reversion or selected keying channel, it makes sense (really?). But how to fix it ? None of these options are enabled, for pitys' sake!

I have seen the posts on MODAT revert needing to be pointed to a conventional personality, done that, also turned off Emergency signalling for MODAT, for example. Using that as a prototype, tests revealed the same behaviour.

It seems that the data associated with Zone 1 in the codeplug hoovered from the radio is the key issue. Any modification to that and bang, unrecoverable errors.

The work around was to leave Zone 1 with it's old/bogus personalities and just dump all the valid Zones in after that and never refer to Zone 1. But I hate leaving dirty code around. But why does Astro signalling , even if pointed to personalities not in that zone, still torch the validity ?

Tried using a Flashport u/g to whack it to a "known good" state and it would not load with "Unknown capabilty", as the Flashport s/w was for a Series I and this was a Series III, I thought you *could* go down. Oh well.

Anyone else seen this ? Wonder if this radio came from Nick ?

I can hear it now "cruddy flash". Moto Depot service for a lobotomy the only solution ?

thanks all

singletone

Is the Modat revert pointing to a conventional analog non-secure channel (zone/channel screen)? Is the personality associated with that channel set to analog/non-secure?

George

Very common questions with using the newer CPS stuff.

Thanks for posting your radio config... It helps us "helpers" a lot.

Modat Revert error:
You MUST have one channel, somewhere that has MODAT enabled as the signalling option. Even if you have no intention of EVER using that channel, you must have that present to clear that error. I suggest removing MODAT from your radio's flash / options if you have no intention of ever using it. It's one less headache.

Scan Error:
If you have your list built, and ANY of the scan list members is a trunking talkgroup, the list type must show "Talkgroup."

Secure Error:
Since you have multikey, you must enable ONE of the multi-keys in the multikey menu. You may never have to use it, but one must be set active.

If you have the means, I would suggest correcting your flash to a more current / valid one.

Good Luck.. the future of radios rests in your hands...
tpg

The answers to your troubles were already given by others, but I'll add a few more bits in:

Singletone wrote:
Tried using a Flashport u/g to whack it to a "known good" state and it would not load with "Unknown capabilty", as the Flashport s/w was for a Series I and this was a Series III, I thought you *could* go down. Oh well.

singletone

Absolutely not. FLASHport upgrades will only work if:

1) The Model # is correct. This means you cannot flash a III into a I, or vice versa. You also cannot use a Flash designed for instance UHF on a 800MHz radio. The model# is defined in the FLASHport software package at the factory.

2) The current FLASHcode is correct. This means the flashcode currently residing in the target radio has to match what was defined in the FLASHport software package at the factory.

Basically, your radio has to be identical in every way to the intended target radio the FLASHport package was created for.

Singletone wrote:
Anyone else seen this ? Wonder if this radio came from Nick ?

singletone

Yes, you have the Nick 'whored out' flashcode. Cruddy flashcode with incompatible options, that's why there are so many weird problems with them.

Todd

Thanks, I did see the post of 3 days ago, but didn't connect the dots on the Secure Options, Scan List etc being affected. All is well now, thanks folks. I DO feel dumb !

singletone