On Friday, 29 October 2021 10:46:43 CET Sven Eckelmann wrote: > If you just read the mvm->radio_stats.on_time_rf (in usec) then you see following: [...] > channel active time: 8560 us > channel active time: 4295006989 us > channel active time: 4295020943 us > channel active time: 4295051766 us > channel active time: 4295086037 us > channel active time: 4295119851 us > channel active time: 4295157051 us > channel active time: 4295193488 us > channel active time: 4295247769 us > channel active time: 4295302615 us > channel active time: 4295315627 us > channel active time: 4295352876 us > channel active time: 45385 us > channel active time: 121871 us > channel active time: 142972 us > channel active time: 262344 us > channel active time: 418666 us > > So it also jumps all over the place. This could be investigated further but I > just wanted to mention it here. Sorry, wanted to write more about it last week but forgot about it. If I basically filter out the upper 32 bit in mvm->radio_stats.on_time_rf then it didn't look that bad on a AX210. It seems like the upper bits is sometimes 0x00000001 for unknown reasons. Like it would be some kind of flag which should indicate some kind of change/event. So maybe the firmware team could check what this means. It is not really urgent - I just got interested in the problem :) Thanks, Sven
Attachment:
signature.asc
Description: This is a digitally signed message part.
