Changes by last author:
Changed:
|
While we developed the CRC-protected triggerlog, we found that the number of pulses is relatively high (eg. for 60-2 above idle RPM) and not known in advance. Therefor low-overhead, but CRC protected protocol was developed that supports variable frames: |
|
While we developed the CRC-protected triggerlog, we found that the number of pulses is relatively high (eg. for 60-2 above idle RPM) and not known in advance.
Therefore low-overhead, but CRC protected protocol was developed that supports variable frames: For info about the actually implemented protocol see SerialComm/TriggerFrameFormat - this page remains for ideas / brainstorming (read: ideas here might not reflect actual implementation). |
| It seems likely that this will be the standard for all communications (except bootloader and AIM of course), the primtrig + sectrig triggerlog, some internal events and runtime data (command 126) was already implemented (as of 1.1.85). |
|
This is going to be the standard for all communications (except bootloader and AIM of course), the primtrig + sectrig triggerlog, some internal events and runtime data was already implemented (as of 1.1.85). |