Difference between revisions of "BoSL Board V0.5 Debug"
| Line 25: | Line 25: | ||
== Debug history == | == Debug history == | ||
=== 6th Feb 2024 === | === 6th Feb 2024 === | ||
| − | Yesterday(cloudy) | + | Yesterday (cloudy) Six BoSL v0.5 boards were tested. Four of these were not able to register to the network.<br> |
| − | Today(clear day) tested the 4 "problematic" boards again, using the same sim card and same code. <br> | + | Today (clear day) tested the 4 "problematic" boards again, using the same sim card and same code. <br> |
2 of them are easy to register to network, no idea why, the weather?<br> | 2 of them are easy to register to network, no idea why, the weather?<br> | ||
1 of them cannot register to network at first, even tried "sendATcmd(F("AT+COPS=0"), "OK", 150000, 1);".<br> | 1 of them cannot register to network at first, even tried "sendATcmd(F("AT+COPS=0"), "OK", 150000, 1);".<br> | ||
Revision as of 22:45, 25 February 2024
This page contains a list of observations from using the BoSL v0.5.x, they may be items which need to be kept in mind when developing and improving code for the BoSL v0.5
Contents
Issue List
ATmega issue
Description:
On the code ported from v0.4.x, there is sometimes no response on the USB serial ports. This may be because the ATmega has crashed. This issue has been observed two times
Test:
This has been observed on both when using the RTC for timed-sleep and when using delay().
SIM7000 issue
Description:
The sim7000 may be unresponsive on power up.
Test:
The sim7000 was powered up and the "AT" command was sent. No response was received, even when the baud rate was adjusted.
This issue was resolved once the BoSLboard reset button was pressed.
Network register issue
Description:
Network registration was not achieved on some boards
Test:
Of 6 new boards tested with the same code, 4 were not able to register to the network. These boards gave "+CREG: 0,2" meaning that they were searching for operators to register to.
This difficulty persisted across resetting the sim7000 and reconnecting the battery.
Debug history
6th Feb 2024
Yesterday (cloudy) Six BoSL v0.5 boards were tested. Four of these were not able to register to the network.
Today (clear day) tested the 4 "problematic" boards again, using the same sim card and same code.
2 of them are easy to register to network, no idea why, the weather?
1 of them cannot register to network at first, even tried "sendATcmd(F("AT+COPS=0"), "OK", 150000, 1);".
but after reconnecting to the battery 2 or 3 times, it was able to register to network.
There is still one board cannot register to network, reconnecting to the battery or await "AT+COPS" for 150s not work.
Adding:
The last board which cannot register to the network started to logging after being connected to battery for about 1 hour,
it looks like the Sim7000 module needs a warm up before work properly.
8th Feb 2024
Stephen got the same network register issue with BoSL 0.5 board today.
He tested sending ATCommand "AT+CEREG=1" and got the network registered.
We can test this ATCommand on more boards that have the same issue.
19 Feb 2024
B5_TurbDepth_3 recovered after stopped logging for 7 days.
20 Feb 2024
B5_DT_SD_2 setup not logging for 3 days. Start to log today when connected to PC USB port.
Looks like a board quality issue.
21 Feb 2024
B5_TurbDepth_3 stopped logging.
Debug showed it keep resetting.
It is a hardware bug, and already fixed on V5.3.0.
For V5.1.0 to V5.2.0, we should avoid boards working at voltage lower than 3.7V.
