Search Result

0 results found on Nordicsemi

All results

3 results found on DevZone

NordicSemi

DevZone - first 10 hits

nPM1300 getting TRICKLETIMEOUT error

Hi, I have an issue I can't understand. I'm getting the TRICKLETIMEOUT (Trickle timer timeout) ERROR 64 from my nPM1300. If I understand correctly: 1. Trickle charging happens when the battery voltage is below 2.9 (or 2.5V). 2. If the battery voltage is >2.9V, it should leave the Trickle charging state quite fast after "Battery detected state" in the Product Specification 6.2.1 Charging cycle 3. TRICKLETIMEOUT happens IF the battery voltage does not exceed 2.9 (or 2.5V) after 10 minutes (tOUTTRICKLE Trickle charging timeout - 10min). The problem is that my battery is at about 4V, and nPM1300 is never leaving the Trickle charging state. Here is a log after a hard reset of nPM1300 (you don't see the error 64 it's not yet generated), but if I wait eventually I'll get the log ERROR 64, which means TRICKLETIMEOUT ERROR. You can also see in the log at one point

forum

7/15/2024

Matter sleepy end device: Not able to commission to network

What I'm trying to do is set a matter device as a sleepy end device, my device as in I'm using a nrf52840dk as my matter device. Also, I am using nrf connect sdk v2.1.1, visual studio IDE I choose the template sample and followed the steps in the documentation to make the device work as a temperature sensor which send random data. I edited the prj file to set my device as a sleepy end device " CONFIG_OPENTHREAD_MTD_SED =y ". I was able to see that my device was configured as a sleepy end device from the device log upon boot up. But I was not able to commission the device. I changed the device type to minimal end device type and was able to commission the device. And again to sleepy end device, I couldn't commission it. I am using a google nest hub as border router and

forum

3/13/2023

regrading sniffer trace and data transfering

hello, i have used and got the d devzone.nordicsemi.com/.../audio_5F00_csv_5F00_09_2D00_02_2D00_2023.xlsx devzone.nordicsemi.com/.../audio_5F00_file.pcapng ata using sniffer.. trying to send 486 kb in 2035 packets total time taking is 190 seconds in that data time taken for each read and time is 56ms ( average) waiting time before the next write happens is 33 ms (average) that 56 ms average is connection interval right?the one we are setting with slave latency.. in code that value is 7.5 to 12 ms then why it is taking 56ms for every packet? while transmitting master sends write command for every transmission is there any way to send data continuosly because right now time taking for one packet is 80ms we want to reduce this as low as possible.. note: attaching excel where we calculated intervals and wireshark file kindly check and get back to me thanks and regards manikandan v

forum

2/15/2023