On Tue, Aug 30, 2022 at 12:16 PM, Skip Hansen wrote:
"interested in dynamically configuring anything else
except perhaps the squelch"
Unless you intend to do that via a sigital pot, a macro of a couple of SB9600 command packets should do it.
I dont think the v1 of the calc was ever posted here, only linked to by Dennis near the beginning of the discussions.
"I'm thinking that the initial code plug contents will be generated by
RSS and loaded into the Xcat. CI-V, or Doug Hall can be used to
change the basics of mode 1 which would be used as the "VFO" mode.
Copying modified mode 1 data into other modes and saving them to flash
should be easy."
I was thinking that the initial flash programming to the Pico should be more native to it
ie: using the Pico programming tools via the onboard USB port. Should be a lot less transform/convert coding needed to get the data in it's memory.
I know for "maximim usability" that means bringing the USB? lines outside the case.
If the ESP32 or whatever future 2.4ghz link can be operated over the USB that could be dual purpose and justify the modification to the case.?
If any VFO/PL parameters changed are RAM only, then checksum routines shouldnt be needed either. Otherwise that will need consideration as well.
There is still the issue (so far) of a codeplug with modified/non RSS compliant PL configuration being "re-educated" if imported back into RSS.
