CPU Temperature Logging

Jetson Nano

Hey,

I designing a chasis for my custom airframe including the ideal components from a Starling 2 Drone. I'm designing a heatsink on the design. For that I would like to do a graphical performance analysis of CPU's temperatures, utils.

In the web-portal, I am able to see the live feed and plots of the various crtical parameters including CPU temperatures, utils etc. Is there a way, I can get to access these data and retireve them from VOXL2 for further analysis?

tom

@Jetson-Nano You can use voxl-logger in order to capture the voxl-cpu-monitor output

Jetson Nano

Thanks for reverting @tom. I'm able to download the logs. But here can I see the CPU temperature readings and utils data? I ran the VOXL2 for a shorter instance and observed that only logging of critical data available.

-- Logs begin at Tue 2024-10-29 10:07:40 UTC, end at Tue 2024-10-29 10:19:04 UTC. --
Oct 29 10:07:40 m0054 systemd[1]: Started voxl-cpu-monitor.
Oct 29 10:07:42 m0054 voxl-cpu-monitor[1447]: loading our config file
Oct 29 10:07:42 m0054 voxl-cpu-monitor[1447]: =================================================================
Oct 29 10:07:42 m0054 voxl-cpu-monitor[1447]: en_auto_standby:  0
Oct 29 10:07:42 m0054 voxl-cpu-monitor[1447]: normal_cpu_mode:  auto
Oct 29 10:07:42 m0054 voxl-cpu-monitor[1447]: standby_cpu_mode: powersave
Oct 29 10:07:42 m0054 voxl-cpu-monitor[1447]: fan_mode:         auto
Oct 29 10:07:42 m0054 voxl-cpu-monitor[1447]: =================================================================
Oct 29 10:07:42 m0054 voxl-cpu-monitor[1447]: Init complete, entering main loop
Oct 29 10:07:42 m0054 voxl-cpu-monitor[1447]: client "voxl-camera-server21297388" connected to channel 0  with client id 0
Oct 29 10:07:43 m0054 voxl-cpu-monitor[1447]: client "qvio-server53044883" connected to channel 0  with client id 1
-- Reboot --
Oct 29 10:18:37 m0054 voxl-cpu-monitor[1492]: client "voxl-camera-server20186581" with id 1 has disconnected from channel 0
Oct 29 10:18:38 m0054 voxl-cpu-monitor[1492]: client "voxl-camera-server09386053" connected to channel 0  with client id 1

tom

@Jetson-Nano Have you looked at voxl-inspect-cpu?