I'm thinking the data update write to EEPROM is going to be (relatively) slower than a mirror copy to RAM.
It seemed logical to pre-calculate all the bytes to change to their new values, checksum the changes and write that to the EEPROM first. Once there, a simple mirror copy would be quick(er) and complete, if the radio got a reset cmd for some reason and executed a re-check of the codeplug integrity.
Also, I'm thinking in terms of permanent freq/PL/NPscanlists etc changes to the codeplug vs a VFO mode of operation which need not be permanant or need a checksum re-calc and store function.
VFO mode from the codeplug side could get tedious.
Your original routine worked with 1/8th the horsepower so this should too. Does the Xcat's VFO lock-step the TX with the RX or is it RX only?
Yeah, loosing feature on next gen designs it always a bad thing. I dont know about the Doug Hall stuff but you had a couple of guys chime it when it was mentioned.
If there are any I/O or an SPI port available that might be a candidate for a serial accessory. I'm guessing since you have the feature worked out, the base code is pretty much boiler plate, if porting it isnt too much of a headache.
If the code is there, accessory design TBD.
I know it violates the KISS philosophy, but you could SPI the data into a ser to par FF/ reg W/ an /OE line (595's I think?) and free up a few I/O if needed.
Yeah, the SyntorX/X9000 squlech syndrome. I had aT74 that hated cold weather, and this is S Texas!
Sometimes it would be so cold in the morning the squelch wouldnt close. Sometimes even the vco drifted in/out of lock until the heater wamed up the back seat floorboard enough for it to behave. I think he just wanted to retire to Aruba or somewhere........
