New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SD card config.txt full comment line parsing #915
Comments
Just for context, the SD card issue is being discussed on this forum thread. |
This issue turned out to be the "# IMU" line comment which the parser interprets as there are no variables to log. Removing that line fixes the fixed frequency logging. I will mark this as an enhancement and either the parser should be improved or the documentation should be clearer. |
I would vote parsing myself, which would require an addition to the driver in the
But let's discuss it during the triage meeting. |
Fixed by #1004 |
Hi everyone,
I'm currently trying to ramp up logging via the SD deck. I get to the point where log files are created on the SD card using cfclient to start and end the logging. However, when analyzing the log files using your tools (cfusdlog.py) it seems like only timestamps are being logged. We use a slightly individually adapted firmware, but those changes should mainly regard the UWB code. I've already removed all the other decks to avoid interference via the SPI. Here is the config.txt file, the console output, and the resulting log file:
config.txt
console output (... replaces some irrelevant output from our own firmware):
log file (I had to add .txt in order to upload it on GitHub, but it's a binary without file extension):
sd_log08.txt
Interestingly, logging works when I don't rely on the fixedfrequency part of the config.txt file. I.e., if I use your standard example config_kalman.txt. This will for now be my current way forward, but it'd be interesting to find the problem nonetheless.
Best,
Dominik
The text was updated successfully, but these errors were encountered: