Hello,
I am running Unipi Neuron L403 as home automation controller with about 20 datapoints being stored to MervisDB. I am saving all values every 5 minutes and sending it to DB with the same interval.

My problem with this setup is that I have to change SD card every two months due to it's total failure. I am guessing that this failure is caused by temporary saving values to SD card before it's transfered to DB. In debugging system status window there is a note saying that values are saved to internal storage.

My questions are:

• Is there any way to store values just to operation memory before it's transfered to DB and save card from many unwanted memory writes?
• I am still using MLC cards. Does it mean that if I buy SLC card, this problem will be solved forever or it just 20-times prolongs the card's life?
• Is there any way how to directly create bootable USB drive from Mervis image? I have found solution here, but it seems pretty complicated...

Thank you.
Petr

Problem with activation solved. I have been using virtualised Windows 7 for Mervis programming (and activation) without any trouble until Mervis 2.4 and it seems there is some problem with SSL with current Mervis version and this outdated OS. Everything else works fine, only the activation process fails. With Windows 10 I was able to finish activation as usual.

But there is still problem with MervisDB and Proxy communication. SslHanshakeError persists.

@tomas_hora,
thanks for you answer, now it makes sense, why SD card died so quickly.

One more question. It seems that this feature is called retain configuration in new Mervis IDE. What's going to happen if I disable 'enable periodical saving' option?

@tomas_hora,
My procedure was:

1. flashing neuron-mervis-os_image-2.4.0.4 to SD card and booting it in my Neuron
2. installing merviside-2.4.0-115662
3. uploading RT
4. uploading config
5. trying to licence MervisOS without success

If needed I can create direct access to my Neuron as I have public IP address on site.

Hello @tomas_hora,
ping to db.unipi.technology from the device results like this:

unipi@L403-sn112:~$ ping db.unipi.technology
PING db.mervis.info (77.240.189.131) 56(84) bytes of data.
64 bytes from 77.240.189.131 (77.240.189.131): icmp_seq=1 ttl=52 time=15.1 ms
64 bytes from 77.240.189.131 (77.240.189.131): icmp_seq=2 ttl=52 time=14.1 ms
64 bytes from 77.240.189.131 (77.240.189.131): icmp_seq=3 ttl=52 time=76.0 ms
64 bytes from 77.240.189.131 (77.240.189.131): icmp_seq=4 ttl=52 time=14.9 ms
64 bytes from 77.240.189.131 (77.240.189.131): icmp_seq=5 ttl=52 time=14.8 ms
64 bytes from 77.240.189.131 (77.240.189.131): icmp_seq=6 ttl=52 time=14.8 ms
^C
--- db.mervis.info ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 11ms
rtt min/avg/max/mdev = 14.091/24.956/76.038/22.847 ms

Both logs are available here.
https://drive.google.com/file/d/1fg_V-uB1DLyRYGrT9BApJl4NCFCRvqmD/view?usp=sharing
https://drive.google.com/file/d/1KnJEv3SlOGP7uHzfHUKW5qjiIwgxenmS/view?usp=sharing

Hopefully it helps...

Hello @Martin-Kudláček,
I have direct access to the Internet without proxy server. Only thing I have in my firewall is NAT rule. Activation, MervisDB and SCADA proxy worked like a charm with previous version of Mervis IDE so it seems for me that it's version related issue.

I have also tested db and proxy accesibility. Both are DNS translatable and pingable.

I have also tried to disable certificate validation.

Nothing helps...

There is another issue running IDE 2.4, maybe it's related to licence activation issue. Both MervisDB and Proxy services tells SslHandshakeError

Any solution to fix this?

Hello,
I am having following problem with Mervis 2.4 and it's activation, any suggestions?

Note: Licence number and email is wiped out in screenshot, of course it's properly filled.
Thanks!
Petr

Hello Tomas,
when is this upcoming version od Mervis IDE going to be released? How often is the nvram file written to the storage in current version?
Thank you!

Hello @lionel,
thanks for your reply. I have also considered using this eMMC adapter. After some "google reseach" I didn't found it more reliable than MLC SD card. It seems that eMMC modules are also using MLC memory chips so there is no differrence in memory reliability.

I think that only solution for me is using SSD drive over USB or finding a way how not to store history data on SD but RAM and lower writes to SD to minimum.

As far as I know, this can only be done manually by the support team and they don't want to do it regularly. If you'll find the way to do this, please share your solution. I also have unused data points from testing phase of my project...