Open ethpi opened 3 years ago
As far as I know, the inverter gets the time by requesting it from semonitor.py when it first connects. If the RPi has received the time from a network time server then the time in the inverter should be correctly set when semonitor.py starts. I don’t know how the time would get set otherwise unless your inverter also has a network connection. I don’t know anything about the PROT_CMD_COMBI_SET_TIME_STAMP command or how to use it.
On Jun 9, 2021, at 2:26 AM, Jan @.***> wrote:
Hi,
I use your software since a few years and it works great. Many thanks. But there is a little problem.
I connected my converter via RS485 to a RPI with RS485-USB-adapter. I noticed, that sometimes my converter gets the wrong time from the RPI, when the RPI reboots. I thought I can solve this problem if I wait starting semonitor.py until the time of the RPI is correctly set while booting. But this plan doesn't work.
The problem is, that I switch of my RPI in the night due to energy saving and hacking protection. If I restart it in the morning, it seems that the time of the converter is set by the RS485 connection without the OS of the RPI is fully started and without semonitor.py ist started.
Today I switched on my RPI at about 7:30 and forgot to enter the decryption key for the SSD, so the OS wasn't booted for about 60min. During this 60min period the time of the converter changed anyway. Otherwise if I disconnect the RS485-USB-adpater and reconnect it not until the OS of the RPI is fully booted, I never noticed this behaviour.
First question: Is the time of the converter set by the RS485-USB-adapter without a fully started OS and without semonitor.py?
Second question: Is there a command to set the time of the converter manually? In the file seCommand.py I read "PROT_CMD_COMBI_SET_TIME_STAMP". Is this a suitable command with the "-c" option of semonitor.py? How can I use it?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jbuehl/solaredge/issues/159, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZLQ3ZPD72IVQQOCAE44ITTR4XT7ANCNFSM46LUP7IA.
Hi,
I use your software since a few years and it works great. Many thanks. But there is a little problem.
I connected my converter via RS485 to a RPI with RS485-USB-adapter. I noticed, that sometimes my converter gets the wrong time from the RPI, when the RPI reboots. I thought I can solve this problem if I wait starting semonitor.py until the time of the RPI is correctly set while booting. But this plan doesn't work.
The problem is, that I switch of my RPI in the night due to energy saving and hacking protection. If I restart it in the morning, it seems that the time of the converter is set by the RS485 connection without the OS of the RPI is fully started and without semonitor.py ist started.
Today I switched on my RPI at about 7:30 and forgot to enter the decryption key for the SSD, so the OS wasn't booted for about 60min. During this 60min period the time of the converter changed anyway. Otherwise if I disconnect the RS485-USB-adpater and reconnect it not until the OS of the RPI is fully booted, I never noticed this behaviour.
First question: Is the time of the converter set by the RS485-USB-adapter without a fully started OS and without semonitor.py?
Second question: Is there a command to set the time of the converter manually? In the file seCommand.py I read "PROT_CMD_COMBI_SET_TIME_STAMP". Is this a suitable command with the "-c" option of semonitor.py? How can I use it?