search

gilestrolab / ethoscope

a platform from monitoring animal behaviour in real time from a raspberry pi
http://lab.gilest.ro/ethoscope/
GNU General Public License v3.0
17 stars 25 forks source link

async database writer has stopped unexpectedly #183

Open FENGZHENGHFUT opened 1 year ago

FENGZHENGHFUT commented 1 year ago

When I run ethoscope, it often got the following error after 8-9 hours and then stopped. IMG_20230912_173245 This maked it hard to continue my experiments, because when I restarted the ethoscope and restarted tracking, the data will save the new .db file but has the same date. Like 2023-09-11_01-35 and 2023-09-11_09-35. so i don‘ know how to write my metadata.csv's 'date'. I'd appreciate it if you have any ideas on how to solve it !

ggilestro commented 1 year ago

This is normally a sign of a faulty or low quality SD card.

FENGZHENGHFUT commented 11 months ago

Hi，ggilestro I had replaced the different SD cards and it was stable for 3 months. As shown in the image below： NY({R}2WQQS@F($LN3F65Y1 I've recently encountered a new problem. I burned and replaced the SD card with a new one, and the first few times my node found the corresponding ethocope number normally, but after that the node couldn't find the ethoscope after powering up the device. However,my router showed the ethoscope device connected to the wifi. Is it the problem of quality of the SD card? Because when I burn a new card again and load the device the node can find the new ethoscope 000. Would there be any other factors that would cause this, as it would be too expensive to replace the SD card frequently? The node log shows the following： IMG_20231228_091501 This situation did not affect my node to find other ethoscope devices. Looking forward to for your reply. Thanks you.