p2p -no response

[SH_Lee]

I am currently running an example of p2p.
I went through make clean/make/make loading process using terminal.
Each of the two crezyflies went through the same process.
But I couldn't get what I thought.
The result window is as follows.

I experimented with the same address value, different channels in 2 crazyflies.

Is there any part that I need to set differently?

[kimberly]

Hi!

Just for reference for the other users, you are referring to this example: https://github.com/bitcraze/crazyflie-f ... er_to_peer

Seems that the right firmware has been flashed. Are you seeing the m4 LED flash very briefly every 2 seconds? Then it is sending the packet, but the other one is not receiving it.

Both crazyflies need to be in the same channel (both on 60 or both on 80). The address should be different.

[SH_Lee]

Thank you for the information.
Is crazyradio PA essential in this process?

[kimberly]

Not necessarily. You can also connect an USB cable to one of the crazyflies to read out the debugprints from the code in the console tab.

[SH_Lee]

As you say, we are experimenting with different addresses on the same channel. But there's still no response.
The led m4 works just like you said.
But one crazyflie not only blinks m4 but also m1 with a red one second cycle.
The program seems to have been properly flashed, but it doesn't seem to be able to communicate with each other.
Are there any expected problems?

[kimberly]

The m1 is an indication of the battery. M4 is sending one quick red for sending and gives 1 small yellow when it receives. So if you are only seeing red flashes of m4, it is still not receiving.

Not sure if it helps but it might help to update the NRF chip? Have you ever flashed the latest release before on the crazyflie before you started all of this like in here.

I used addresses 0xE7E7E7E701 and 0xE7E7E7E702 myself.

[SH_Lee]

I updated nrf before, but I updated it again, and I tried using the same address as you.
I've tried switching from ch.80 to ch60 and still can't accept it.
Could it be a hardware issue that doesn't work without modifying the example file?
(All other communications are normal except for the example of p2p.)

[kimberly]

Then I wouldn't know why it does not work for you. I tried it again with my two crazyflie 2.1s and I get the following:

Code: Select all

---
SYS: Crazyflie 2.1 is up and running!
SYS: Build 90:5ab968148e48 (2020.04 +90) MODIFIED
SYS: I am 0x20373357594B5007002D0042 and I have 1024KB of flash!
CFGBLK: v1, verification [OK]
DECK_CORE: 0 deck(s) found
IMU: BMI088 Gyro I2C connection [OK].
IMU: BMI088 Accel I2C connection [OK]
IMU: BMP388 I2C connection [OK]
ESTIMATOR: Using Complementary (1) estimator
CONTROLLER: Using PID (1) controller
MTR-DRV: Using brushed motor driver
EEPROM: I2C connection [OK].
IMU: BMI088 gyro self-test [OK]
STAB: Wait for sensor calibration...
SYS: Free heap: 13216 bytes
Waiting for activation ...
STAB: Ready to fly.
[RSSI: -35 dBm] Message from CF nr. 2, Hello 
[RSSI: -35 dBm] Message from CF nr. 2, Hello 
[RSSI: -35 dBm] Message from CF nr. 2, Hello 

You can try to make the NRF without bluetooth support, although that is not necessary for the latest release. Also I noticed that if you communicate with one of the crazyflies of with the CR PA, there is more packet loss, so if you want to see the debugmessages it is good to connect one crazyflie through usb instead.

You can put debug messages in the code yourself to try to figure to understand what the code is doing.

[SH_Lee]

How do I turn off the Bluetooth?

Actually, I'm experimenting with bolts.
Is p2p communication not possible in the bolt?

I'm trying many things based on what you said.
If there are any other possible problems, please keep them updated.

[SH_Lee]

I changed the ble ?= 1 to 0 in the makefile of nrf.
The bolt is not detected on the cell phone and other devices, is it correct that the ble is turned off properly?
Or is there a way to check the change in the led light?