From: "Ralf Reiterer" <ralfreit@...>
Where in the data field returned by the 1a 00 command does
the ProII return repeater offset? It returns tones and
whether tones are in use. It rather ignores the concept of
offset as far as I can find.
Yeah, it seems so since it also does provides split operation only by
command 0F but no shift state (DUP-, DUP+). Unfortunately I have not
found any documentation about the contents sent by the IC-756PROII and
III for command 1A 00 . As I'm currently writing a
IC-756/PRO/PROII/PROIII driver for my software (www.radioctl.com) any
documentation for that command would be helpful.
You pretty much have to play around to document it. This is what I
get for the 00 command:
typedef struct
{
BYTE subcommand;
BYTE memoryNumber[ 2 ];
BYTE sel; //Sel- Scan Select flag (1 byte) $01
BYTE frequency[ 5 ];
BYTE mode;
BYTE filterbw;
BYTE flags; // Flags: &01 - when set, Tx Subtone on
// &02 - when set, Rx Subtone on
// &10 - when set, Mode LSB, USB,
// AM, FM is modified to data mode
BYTE unk1;
BYTE txtone[ 2 ]; // ? Really three bytes with unk1
BYTE unk2;
BYTE rxtone[ 2 ]; // ? really three bytes with unk1.
BYTE name[ 10 ]; // 10 bytes ascii name (Fill in end tag first)
} ICOM_memory;
And this is what I get for the three P registers, the 1a 01 contents.
Alas, there is no command to transfer the Px registers to the VFO. (Ah,
if you do know one I overlooked please pass it along.) I've not looked
too hard into the Px memories because I see little utility to it. (I am
using memory 99 as a utility memory for jam setting the transceiver when
I change bands and the like. It also allows me to play with data mode
filter selections and bandwidths.
typedef struct
{
BYTE band;
BYTE bandregister;
BYTE frequency[ 5 ];
BYTE mode;
BYTE filterbw;
BYTE unk1; // maybe subtone flags.
BYTE unk2;
BYTE txtone[ 2 ];
BYTE unk3;
BYTE rxtone[ 2 ];
} ICOM_px_memory;
I wonder if the 7000's firmware
will be updateable.
I really hope that it will be. Man each modern computer allows the BIOS
to be updated, so shouldn't it be standard for all modern radio devices
too!?
If they do it I do have experience with the "safe way" that we used
in the Motorola Inmarsat terminals. Always run from RAM. For an update
transfer to a never written to chunk of EEPROM or an actual PROM with
the necessary bootloader code. Once new code is in memory and the set
is running from that code it can be written to the EEPROM in one
relatively fast operation. If it gets interrupted the untouched part of
memory still allows you to update your radio. Otherwise those SatCom
terminals could become VERY expensive boatanchors. It was well thought
out in advance to prevent the boatanchor phenomenon. They learned from
seeing what happened with the first Intel motherboards/boatanchors that
had the EEPROM feature.
{^_-} W6MKU
