LogEntry Error while reading position data - LOCO

All discussions related to the Loco Positioning system
Post Reply
aybarskizilay
Beginner
Posts: 11
Joined: Tue Oct 16, 2018 2:03 pm

LogEntry Error while reading position data - LOCO

Post by aybarskizilay » Thu Nov 08, 2018 2:29 pm

Hello everyone,

I am flying with LOCO and Flow Deck together. When I run the "autonomousSequence.py", I sometimes encounter these errors:
Even though, pyhton script keeps running and it completes its flow as expected.

Code: Select all

Error no LogEntry to handle id=1
Error no LogEntry to handle id=12
Error no LogEntry to handle id=13
Error no LogEntry to handle id=1
Error no LogEntry to handle id=2
Error no LogEntry to handle id=3
Error no LogEntry to handle id=5
Error no LogEntry to handle id=7
Error no LogEntry to handle id=8
Error no LogEntry to handle id=9
Error no LogEntry to handle id=10
Error no LogEntry to handle id=11
Error no LogEntry to handle id=12
My CrazyFlie uri: radio://0/6/2M. So I am using high bandwidth.

Furthermore, when I want to read a real-time position data, I somestimes see following errors:

Does anyone know why I am receiving those warning and how to solve it? maybe increasing the memory? How to do it?

Best Regards
Aybars
Attachments
logentry_issue2.PNG

arnaud
Bitcraze
Posts: 1788
Joined: Tue Feb 06, 2007 12:36 pm

Re: LogEntry Error while reading position data - LOCO

Post by arnaud » Mon Nov 12, 2018 12:26 pm

The first error ("Error no LogEntry to handle id=") is not a problem, it is caused by existing log block from a previous connection still sending data. One of the first thing the lib is doing when connecting a Crazyflie is to clear the existing log blocks.

The second error is caused by you creating too many log blocks. There is a fix limit in the firmware there: https://github.com/bitcraze/crazyflie-f ... .c#L76-L77.
  • LOG_MAX_OPS sets the maximum of variables that can be logged (sum of the size of all the log block)
  • LOG_MAX_BLOCKS sets the max number of log blocks, it is currently set at 16
So you can increase LOG_MAX_BLOCKS and it should solve your problem. Be aware that there is also a bandwidth limit: you generally will not be able to get more than ~800 packets per seconds from a Crazyflie.

Post Reply