This is something that needs to be discussed fairly early on as it won't be long and I'll need to watch parameters on a PC while developing.
I have a few ideas about how this should all work, but they are by no means a thorough well thought out set of ideas.
I'll try to present them here, and change and update them as your suggestions and critical discussions ensue.
- All "burn to flash" and "store in memory" commands and data should be fully checksummed such that no bad data ever gets in.
- An error should be sent back to the tuning software providing information if an corrupt packet is received or a framing error etc occurs.
- There should be some facility for a datalogging mask to be set such that small subsets can be datalogged with much higher frequency
- Data logged should have a weak checksum included in it for later processing (don't care at the time)
- Config for external hardware actuation should be supported by "chosen port" config sends
This is quite likely full of holes right now, be merciless, rip it apart :-) no offense will be taken!
Admin