Following https://en.eeworld.com/bbs/forum.php?mod=viewthread&tid=1065192&extra= and 【NXP Rapid IoT Review】+ NXP Rapid IoT Unboxing Surprise, we continued on the road. This time, we used the mobile app to connect to Rapid IoT for testing. First, let's take a look at the charging view. Under normal charging conditions, the charging voltage is 5.25V and the current is about 0.2A. . But if the screen is always on, it will only reach 97% after two hours of charging. It will never be fully charged. . Another thing is that there is no shutdown button, so it means that if you want to shut down, you can only wait until the battery is completely dead. Such batteries are easily damaged by over-discharge. It is recommended that Rapid IoT can add a shutdown function later.
Second,then use the app to connect. I will not describe the process of downloading the APP. I guess many netizens who have reviewed it have shared the process. Here I will share some situations encountered in the app connection.
If a novice cannot connect for the first time and the following error message appears, he will definitely suspect that the phone is not working or the app installation failed. I also suspect this. After communicating in the group, I found that many netizens have similar situations.
The only solution is to persevere and log in several times so that you can always log in. In addition, it is best to use a wifi network when the network conditions are good, such as late at night. The reason for this is that the server is abroad, so it takes a certain amount of time to connect.
Third, after logging into the app, I found that there were more things to come. There were also some problems that occurred during the Bluetooth connection with Rapid IoT. After searching for Rapid IoT, there were certain hardware requirements to connect to it. Let me share my experience: 1. Using Redmi Note 2 (may be criticized for being too old: sexy
, I could search for Rapid IoT by approaching it, but the signal strength was only -48, and then an error message appeared as soon as it was connected, as shown below, saying that an unreliable connection occurred, and that was the end of it. 2. Even if it was connected, IOT would restart, and then the Bluetooth icon on the bottom of the phone interface kept jumping, and the data could not be updated. .
2. Finally, I used a fruit machine (I am not a cent, and I basically don’t use an Apple machine), and I could connect to it in one go, and then the data could be updated in about ten seconds.
Find a bug: Maybe because the development board was charging while the screen was on, the temperature displayed was quite different from the ambient temperature (the indoor temperature was less than 15°, and there was no heating indoors in Shenzhen in the south), but the displayed temperature was 27.99°, so there is still room for later optimization. . . .
Fourth, Next, test the app to control the RBG LED light operation
By clicking on the app screen, you can control the red, blue, and green lights on Rapid IoT, and you can also turn them all off (the first light that shows white is all turned off)
Upload a video, which is a video of the test of the RGB three-color light. . .
5. Data update delay When using the app to view data, I found that the data update is a bit slow, especially in the six-axis data update. This should also be related to the situation of the server being overseas and the network. In the future, NXP can improve a lot by deploying more domestic servers. This does not have much impact. . . Let's take a look at how long the delay is through a test video. . .
Finally, to sum up, when using Rapid IoT, you still need more patience to try more and try different methods. This content was originally created by EEWORLD forum user 飞扬自己. If you need to reprint or use it for commercial purposes, you must obtain the author's consent and indicate the source