kopia lustrzana https://github.com/Hamlib/Hamlib
ccab50a7df
When the settings are saved via the front panel on the MD-01, the
following debug messages are printed on COM 0:
thread_motionController: settings changed!\r\n
thread_protocols: settings changed!\r\n
Notably, because these aren't timestamped the way the other debug
messages are, they were missing the our debug message sieve and causing
protocol errors. Address this by treating anything that doesn't start
with the ROT2PROG start byte ('W') as a log frame.
|
||
|---|---|---|
| .. | ||
| amsat | ||
| androidsensor | ||
| apex | ||
| ars | ||
| celestron | ||
| cnctrk | ||
| easycomm | ||
| ether6 | ||
| flir | ||
| fodtrack | ||
| grbltrk | ||
| gs232a | ||
| heathkit | ||
| indi | ||
| ioptron | ||
| m2 | ||
| meade | ||
| prosistel | ||
| radant | ||
| rotorez | ||
| saebrtrack | ||
| sartek | ||
| satel | ||
| spid | ||
| ts7400 | ||