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

Log files in solo vs controller #224

Open
hamishwillee opened this Issue Nov 30, 2015 · 4 comments

Comments

Projects
None yet
3 participants
@hamishwillee
Contributor

hamishwillee commented Nov 30, 2015

Solo/controller both have lots of logs. There seems to be quite a lot of similarity between some of the files and in other cases there appears to be a similar file type/extension but different filename. Check out the pdf file comparison - report1.pdf

  • Does the controller copy and rename some files/is there an overlap
  • Do you need both controller and solo logs. @nick3dr your PDFs only explain how to get the controller logs, does that mean you think only the controller logs are useful?
  • If a controller and solo both have a log of the same type, what is the difference?

I've created a single example of each log in both controller/drone below.

  • What are each of these types
  • Are any completely useless to anyone - ie temps that should be ignored
  • Are any duplicates on controller/drone
  • Are any useful only to 3dr

Note: assuming anything ending in [.]\d+ is a rotated log file (.1 being the most recent previous incarnation of the bare filename).

controller

  • 3dr-pairing.conf
  • 3dr-solo.log.n - Catch-all log for thing that don't go elsewhere (PeterB). dataflash_logger's stuff ends up here because SoloLink's syslog configuration hasn't said to put them elsewhere.
  • 3dr-stm32.log.n -
  • 3dr-temp.log.n -
  • 3dr-top.log.n - cpu usage statistics
  • 3dr-video.log.n -
  • 3dr-wifi.log.n -
  • boot.n -
  • dmesg.n -
  • messages.n -
  • solo.tlog.n - telem logs that the controller has received (eliao). Controller only. Created by a process called "tlog" (IIRC) from the telemtry stream coming from Solo.
  • wtmp.n -

drone

  • 3dr-rc.log.n -
  • 3dr-solo.log.n - dataflash_logger's stuff ends up here because SoloLink's syslog configuration hasn't said to put them elsewhere.
  • 3dr-telem.log.n - contains some logging on bidirectional telem bandwidth (eliao). Created on Solo and contains information from telem_forwarder; telem_forwarder is the process that talks on the serial port to PixHawk and relays the telemetry to clients (Controller as a special case and other "clients" that connect - e.g. dataflash_logger).
  • 3dr-temp.log.1
  • 3dr-top.log.n - Cpu usage statistics (eliao)
  • 3dr-wifi.log.n -
  • boot.n -
  • dmesg.n -
  • messages.n -
  • shotlog.nnn.log - symlinks to these files for backwards compatibility (we don't need those).
  • shotlog.log.n - shot manager logs (eliao). shotlog.n.log are
  • wtmp..n -
@eliao

This comment has been minimized.

Show comment
Hide comment
@eliao

eliao Nov 30, 2015

Contributor

shotlog.log.n are shot manager logs. shotlog.n.log are symlinks to these files for backwards compatibility, so we don't need those.

3dr-telem.log.n contains some logging on bidirectional telem bandwidth.

3dr-top.log.n contains cpu usage statistics.

On the controller:
solo.tlog.n are the telem logs that the controller has received.

@johnfinley may be able to add some more details.

Contributor

eliao commented Nov 30, 2015

shotlog.log.n are shot manager logs. shotlog.n.log are symlinks to these files for backwards compatibility, so we don't need those.

3dr-telem.log.n contains some logging on bidirectional telem bandwidth.

3dr-top.log.n contains cpu usage statistics.

On the controller:
solo.tlog.n are the telem logs that the controller has received.

@johnfinley may be able to add some more details.

@hamishwillee

This comment has been minimized.

Show comment
Hide comment
@hamishwillee

hamishwillee Nov 30, 2015

Contributor

Thanks @eliao - I copied your information above to make it clear which ones we still don't know about:

  • when you say we don't need the symlinks, should we arrange these be deleted?
  • Are there any documents around on interpreting the logs you have identified above (other than the tlogs of course)
  • When you say "solo.tlog.n are the telem logs that the controller has received." - are you suggesting that all tlogs get copied from the Solo, and are these the SAME as 3dr-solo.log.n ? (and is the mapping 1:1 for the number - I presume not, since the controller might not have the latest, so would be one number lower)
Contributor

hamishwillee commented Nov 30, 2015

Thanks @eliao - I copied your information above to make it clear which ones we still don't know about:

  • when you say we don't need the symlinks, should we arrange these be deleted?
  • Are there any documents around on interpreting the logs you have identified above (other than the tlogs of course)
  • When you say "solo.tlog.n are the telem logs that the controller has received." - are you suggesting that all tlogs get copied from the Solo, and are these the SAME as 3dr-solo.log.n ? (and is the mapping 1:1 for the number - I presume not, since the controller might not have the latest, so would be one number lower)
@eliao

This comment has been minimized.

Show comment
Hide comment
@eliao

eliao Dec 1, 2015

Contributor
  • symlinks can be deleted from any archives of the logs. But we should keep them on vehicle for backwards compatibility.
  • I don't know of any docs on interpreting these logs. They were mainly developer facing and as such used to log data for debugging.
  • I don't think we store tlogs on Solo. Only on the controller. The difference would be that the controller logs would only log telem that it received, so it would skip drops.
Contributor

eliao commented Dec 1, 2015

  • symlinks can be deleted from any archives of the logs. But we should keep them on vehicle for backwards compatibility.
  • I don't know of any docs on interpreting these logs. They were mainly developer facing and as such used to log data for debugging.
  • I don't think we store tlogs on Solo. Only on the controller. The difference would be that the controller logs would only log telem that it received, so it would skip drops.

@hamishwillee hamishwillee referenced this issue Dec 2, 2015

Merged

Fixes #202 #210

@tarazansafak

This comment has been minimized.

Show comment
Hide comment
@tarazansafak

tarazansafak Mar 16, 2017

Hey guys,

Is real time IMU logs available on Solo? Can I display them via command line? Or any hints? I need to get them programatically.

Hey guys,

Is real time IMU logs available on Solo? Can I display them via command line? Or any hints? I need to get them programatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment