我正在执行ble_app_uart_c例程的功率测量,并且已经关闭了串行端口,这与打开串行端口时测量的波形不同。我猜封闭的串口会影响扫描。
This is the waveform without closing the serial port

This is the waveform without serial port initialization

我正在执行ble_app_uart_c例程的功率测量,并且已经关闭了串行端口,这与打开串行端口时测量的波形不同。我猜封闭的串口会影响扫描。
This is the waveform without closing the serial port

This is the waveform without serial port initialization

Why the current without UART initialization is lower than normal?
請問兄台為何串口沒初始情況下,電流出現平時工作以下的數值?
I wonder that the difference just UART is working or not.But the time period of scope is different. The main current consumpion may not be cause by the scan ble event.
個人認為差異只是剛好串口有無作動而已,但實際脈衝周期似乎也有明顯差距,可能的原因也許變動的電流脈衝並非主要是scan ble的工作電流造成。
Is the ble_app_uart_c example without uart driver normal or not during advertising/scan / discovery /connection period?
在範例略過初始化下廣播,掃描,發現跟裝置連接的事件處理程序都正常作動嗎?
No serial port initialization.The slave machine could not connect.
Finally, how can I check if the power I measured is normal? Scan.
This viewBut the results I got were a lot different from what I had measured.
The peripheral is not connected.It may be some reasons. Is it the service UUID matched and the scan filter suitable? And you can trace the central side without UART initialization scan_evt_handler();ble_nus_c_evt_handler();db_disc_handler(); is okay or not.
If the event handler is not working, you can't expect the power consumption is follow the power profile.
I initialize the UART, and then close the serial port app_uart_close() after the scan start. It seems that if uART is not initialized before scanning initialization, it will lead to no scanning. I don't know what UART has to do with scan initialization.I'm normal now.
Best regards
I don't think that the UART driver closed will be made the scan event abnormal. Because I have done the other BLE project without UART driver case in SDK17.0.2 central.(Refer ble_app_gatts example). It must be some reasons And when you close the UART , it's there any error code happened or not? In your current timig, I think the system reset happened in the low spike. You may trace that timing.
ok, 我試試看
ok, 我試試看