Bytes 0 and 1 of the 5 byte packet returned from the radio will be the contents of memory locations 0圆8 and 0圆9. I keep finding references saying the current vfo can not be read from an 857d so as an example of the eeprom read command set the 5 byte data block to 0x00 0圆8 0x00 0x00 0xbb where 0x0068 is a memory location and 0xbb is the eeprom read command. I did slow down on the writes I was doing. Some have stopped using the eeprom write command because of this but just using the radio or the normal cat commands you are generating writes. I do not know what value of too many is enough to do this. There are warnings around the place about doing too many eeprom writes as that will eventually cause wear killing the memory. I used it as guide but it was still tempting to use the eeprom read cat command to dump every memory location, change a single setting, do another dump then compare to see which bit of which byte was changed with that setting. The 857 has all the settings starting at a different offset that listed for the 817 on that site. If you have a memory map then can read any setting you want. There are read eeprom cat and write eeprom cat commands. The cat on and cat off commands listed for the 817 have never worked with my 857d which is a shame as that would have been very useful. I have not tried the factory defaults command as have not been interested is redoing all the service menu items. There are some undocumented commands listed at for the 817.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |