-
Notifications
You must be signed in to change notification settings - Fork 365
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
1090 SDR Startup Log error? #413
Comments
Seems like a fairly innocuous error. Looks like we're parsing the string and assuming it is null terminated but it's not. What are those characters? If you "cat -e" the logfile it'll show you character codes. |
I'll take a look at it. On May 13, 2016 10:30:33 AM CDT, cyoung notifications@github.com wrote:
|
FWIW, I got confused by these characters in the logs a few months ago when we were troubleshooting the failure of the Edimax. I saw the characters and posted a snippet for Chris, thinking that was when the failure occured. #267 |
Yeah, I'll just have to add in some extra string handling. It should not affect function. |
@cyoung
I also found this for the 978 device:
|
Update: I cleared my old log and created a new one so you could see the whole log with the interesting character. |
Stratux version:
Stratux config:
SDR
[ ] single
[ X ] dual
GPS
[ X ] yes
[ ] no
type: VK-172
AHRS
[ ] yes
[ X ] no
power source: Ship power via mygoflight USB adaptor
usb cable: N/A
EFB app and version: (e.g., WingX Pro7 8.6.2) N/A
EFB platform: (e.g., iOS 9.2) N/A
EFB hardware: (e.g., iPad Mini 2) N/A
Description of your issue:
The ES Device data as reported in stratux.log appears to be corrupted. This is the snippet from the log:
2016/05/08 21:25:38 ===== ES Device Serial: stx:1090:40������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������ PPM 40 =====
If possible, enable "Replay Logs", reproduce the problem, and provide a copy of the logs in http://192.168.10.1/logs/stratux/ and http://192.168.10.1/logs/stratux.log.
The text was updated successfully, but these errors were encountered: