mitaux8030
Silent Key
I love to tinker. For me, its the best way to learn. To that end, I got my hands on a 'sacraficial' MR-K to experiment and learn with.
It appears as if its a conventional only M-RK2. 344A3937P235. Looking at the LBIs, it would appear as if there's no circuit hardware differences between the conventional and EDACS variants, even down to the flash .bin file.
So it appears as if it would only be the features enabled (with the Feature Encryption string) that determines if a particular M-RK is EDACS or conventional - would that be an accurate statement?
As received (no label, just a test personality programmed, out of the factory box) the radio powered up with a FEAT ERR 0552. Reading some of the advice here, I took copies of the .bin file, saved the tracking data, the 'as delivered' feature encryption string, and noted the ESN - then proceeded to update the flash from M2G28400 to M2G46402. This didn't help, so doing a recovery on the radio (first without erasing the EEPROM, and then with erasing it) still didn't help with this particular problem. I assume that the problem is the feature encryption string was corrupt (or doesn't match up with the ESN) to begin with when I got it?
If it helps any, it shows the following in Features:
Ch# 0
SG# 0
SY# 0
and shows NO features at all.
Wonder how MA-Com USA would react to someone from the other side of the world calling up to confirm if my FE string and ESN match? Do they have an email address that such queries can be directed to?
Not that it matters a lot, as it works fine in conventional mode anyway.
My education continues.
It appears as if its a conventional only M-RK2. 344A3937P235. Looking at the LBIs, it would appear as if there's no circuit hardware differences between the conventional and EDACS variants, even down to the flash .bin file.
So it appears as if it would only be the features enabled (with the Feature Encryption string) that determines if a particular M-RK is EDACS or conventional - would that be an accurate statement?
As received (no label, just a test personality programmed, out of the factory box) the radio powered up with a FEAT ERR 0552. Reading some of the advice here, I took copies of the .bin file, saved the tracking data, the 'as delivered' feature encryption string, and noted the ESN - then proceeded to update the flash from M2G28400 to M2G46402. This didn't help, so doing a recovery on the radio (first without erasing the EEPROM, and then with erasing it) still didn't help with this particular problem. I assume that the problem is the feature encryption string was corrupt (or doesn't match up with the ESN) to begin with when I got it?
If it helps any, it shows the following in Features:
Ch# 0
SG# 0
SY# 0
and shows NO features at all.
Wonder how MA-Com USA would react to someone from the other side of the world calling up to confirm if my FE string and ESN match? Do they have an email address that such queries can be directed to?
Not that it matters a lot, as it works fine in conventional mode anyway.
My education continues.