The problem comes from the fact that this doc is very outdated and should not be followed. I am going to look at it to update or remove it.

Nowaday, you should setup the LPS system following the documentation on the bitcraze website, and then you can connect and control the Crazyflie using the standard crazyflie_ros driver without needing to do anything special about the LPS: the Crazyflie receives the anchor position from the anchors over radio, will estimates its position, and has onboard position control loops.

If you are looking at flying a swarm of Crazyflies in ROS, the LPS is supported by Crazyswarm by setting "motion_capture_type: none".

Thaks a lot for your response Arnaud, I have been trying the way you mention and it's working quite well (I was using 6 anchors in TWR, and one Crazyflie).
Right now I would like to do the same using 10 anchors in TWR, but the way the lps-ros package is built it doesn't accept to extend log to have more than 6 anchors (modifying launch log_range and log_range node). Is this caused because of the crazyflie_ros implementation or is this because of crazyflie log package limits in the hardware?
In case is caused by the second, would be possible to create two log blocks and feed them to log_range node from 2 separate topics? Is there another way to get the ranging values into ROS?