Batboard

Hi all!

I have bought such Astro Saber Model III:

Model Number H04KDH9PW7AN
Internal Hardware version 000A
Firmware Version 04.01.00.00
DSP Version I06.02.00
System Package H35
FLASHCode 140001-000000-3
External Codeplug Size 2188

I tried to program it with CPS ver. R05.00.02.

Radio has started to be read normally, but when CPS begins "unpacking" codeplug, eror message has appears:



I have pressed NO, but it in what has not resulted - radio data not become accessible.

After that I have tried read radio again and pressed YES, but CPS has informed that I should use latest version CPS. I have followed to advice and have updated CPS to ver. R05.02.00.

After that I have repeated attempt, but received the same error message (Filed "Designated Data Member"...). In the next attempt I pressed YES - in this time radio data were successfully displayed in CPS and became available for reading/changing & etc. After that I have written down data in radio and now it is successfully read without any error messages. That is now all works normally.

My questions:

1. What happens?
2. Whether somebody else faced such message (Filed "Designated Data Member"...)?
3. Than occurrence of this message is caused?

As best I could figure, it's a combination of old HOST firmware and being written with DOS RSS. I used to get a similar error when writing an old VSELP Astro saber with RSS 08.06; something like "You are writing an invalid TX Designated Data Member. If this is not corrected, data scan capabilities may be lost, We strongly recommend correcting this before proceeding." and an OK option. I hit OK, radio wrote fine, no problems thereafter. It was more a nuisance than anything.

Now, in RSS 9.05 (and probably in Astro Portable CPS, which I don't use), under your screen for scanlist configuration and entry there is an actual setting for "Designated Data Member." Set this to "None" and the error will go away. I have no idea what it was used for.. maybe as some sort of VSELP data priority channel when in scan mode.

Having found "Designated Data Member" in CPS I have thought as well as you

I was excited with that CPS R05.00.02 could not eliminate such problem and for this reason could not open codeplug at all. It is IMHO very strange, because Windows CPS for Astro Saber exists for a long time and it should be able work correctly with transceivers programmed in DOS RSS.

motorola_otaku wrote:As best I could figure, it's a combination of old HOST firmware and being written with DOS RSS. I used to get a similar error when writing an old VSELP Astro saber with RSS 08.06; something like "You are writing an invalid TX Designated Data Member. If this is not corrected, data scan capabilities may be lost, We strongly recommend correcting this before proceeding." and an OK option. I hit OK, radio wrote fine, no problems thereafter. It was more a nuisance than anything. Now, in RSS 9.05 (and probably in Astro Portable CPS, which I don't use), under your screen for scanlist configuration and entry there is an actual setting for "Designated Data Member." Set this to "None" and the error will go away. I have no idea what it was used for.. maybe as some sort of VSELP data priority channel when in scan mode.

I've gotten this every now and then with my old Vselp A/S using DOS. The only option I see under the Scan config is "Designated Tx Mem...." but I can only select any channel within the scan list that is not Rx-only, Selected channel, or Talkback. I can't set it to "none". I would also get this with CPS but went back to DOS because I like it more. I think this is just a quirk of old A/S firmware.