Hi,
I am using exactly 3.1.16 version (3.0.1 same behavior) of the Gurux java library. I am making a call to get data from the meter in a time transition period = 27th October 2019 (transition summer to winter)
My problem is that in the Prometer meter I am not receiving summertime readings from 2:00, 2:15, 2:30, and 2:45 a.m. Obviously all other readings before and after that hour are present for the given scope.
I have made exactly the same invocation, with the same arguments, but for L+G meter. There was no gap like that. All readings from 2 a.m. for summer and winter time (4 summertime + 4 wintertime) are present.
Did anyone was facing a similar problem?
Maybe, my invocation is wrong?
I would like also to add that I have tried also similar tests:
- with different timezones (UTC +, CEST)
- with different periods
- different implementations of readRowsByRange (Date, Calendar, GXDateTime types as date arguments)
I will be very grateful for any help. Thank you very much.
DST is implemented differently to the meters. Some meters doesn't support it at all.
I believe that your problem with Prometer is when your meter is moving from wintertime to summertime?
Can you see are there summertime readings at 2:00 in Prometer?
If the meter is saving values using current date-time and not UTC time, it might be possible that there are no readings in that time.
L+G Meters that we are reading doesn't support summertime.
You can check this selecting clock object and reading it. Check is Daylight Savings enabled checked.
Hi, thanks for the reply.
No, I am talking about the transition between summer and wintertime, the moment when we have got two "2:00" hours :).
L+G, as you mention does not support summertime, but sends daylight saving status. That is cool because it helped me a lot to handle readings from L+G meters. I do not have any problems with that anymore :)
My big pain is related to the Promoter where there are missing readings. In other words, I noticed that there is a 1-hour gap in the Promoter - Situation on 27th October 2019
LG - PROMETER
1:30 1:30
1:45 1:45
2:00 GAP - summertime
2:15 GAP - summertime
2:30 GAP - summertime
2:45 GAP - summertime
2:00 2:00 - wintertime
2:15 2:15 - wintertime
2:30 2:30 - wintertime
......
Later on, I will attach some logs to prove it (but it will take some time)
Thanks
I promised to post some logs (image) from both L+G and the Prometer for the same scope, which is:
start = 2019:9:27 0:0:0 end = 2019:9:27: 4:0:0 - no tampering in timezones, default for my location is Europe/Copenhagen.
Please, don't post images. You can see them fine, but they are compressed and from other PCs they are fuzzy. I can't read the first image at all.
It seems that your Prometer is using UTC time zone, is that correct? Did your read attribute 3?
Can you read your clock with GXDLMSDirector? It'll read all the attributes automatically.
Hi,
Sorry, about these pictures. Indeed, I noticed that the one attached is useless.
GXDLMSDirector told me:
time - 05.05.2020 15:06:24 - which is 1hr back to my zone time.
time Zone = 0
In other words exactly as you said.
This was my first time with GXDLMSDirector (sorry to say that, I am a newbie), but I have also made a read from the profile, which I am interested in, for a given scope and there were following results (copy-paste of clock column from GXDLMSDirector ). They are aligned with the results I posted in my previous comments.
But, UTC is a standard, not a timezone, which is a key to the solution. Logs from my program were a little bit misleading for me and the ignorance the Prometer works in UTC were the reason for my problems.
Thanks a lot for your patience and your time I think I will be able to handle that in my program.
Hi,
Hi,
DST is implemented differently to the meters. Some meters doesn't support it at all.
I believe that your problem with Prometer is when your meter is moving from wintertime to summertime?
Can you see are there summertime readings at 2:00 in Prometer?
If the meter is saving values using current date-time and not UTC time, it might be possible that there are no readings in that time.
L+G Meters that we are reading doesn't support summertime.
You can check this selecting clock object and reading it. Check is Daylight Savings enabled checked.
BR,
Mikko
Hi, thanks for the reply.
Hi, thanks for the reply.
No, I am talking about the transition between summer and wintertime, the moment when we have got two "2:00" hours :).
L+G, as you mention does not support summertime, but sends daylight saving status. That is cool because it helped me a lot to handle readings from L+G meters. I do not have any problems with that anymore :)
My big pain is related to the Promoter where there are missing readings. In other words, I noticed that there is a 1-hour gap in the Promoter - Situation on 27th October 2019
LG - PROMETER
1:30 1:30
1:45 1:45
2:00 GAP - summertime
2:15 GAP - summertime
2:30 GAP - summertime
2:45 GAP - summertime
2:00 2:00 - wintertime
2:15 2:15 - wintertime
2:30 2:30 - wintertime
......
Later on, I will attach some logs to prove it (but it will take some time)
Thanks
Hi blady,
Hi blady,
Can you read your clock and check what is your time zone. https://www.gurux.fi/Gurux.DLMS.Objects.GXDLMSClock
L+G is using DLMS standard way with time zone as a default. If I remember right Promoter is using UTC time, not DLMS standard way.
BR,
Mikko
I promised to post some logs
I promised to post some logs (image) from both L+G and the Prometer for the same scope, which is:
start = 2019:9:27 0:0:0 end = 2019:9:27: 4:0:0 - no tampering in timezones, default for my location is Europe/Copenhagen.
In attachment (image) could
In attachment (image) could be found a clock and result of reading time from the Promoter meter as you requested.
Still, I do not have any idea how to proceed :)
Hi,
Hi,
Please, don't post images. You can see them fine, but they are compressed and from other PCs they are fuzzy. I can't read the first image at all.
It seems that your Prometer is using UTC time zone, is that correct? Did your read attribute 3?
Can you read your clock with GXDLMSDirector? It'll read all the attributes automatically.
BR,
Mikko
Hi,
Hi,
Sorry, about these pictures. Indeed, I noticed that the one attached is useless.
GXDLMSDirector told me:
time - 05.05.2020 15:06:24 - which is 1hr back to my zone time.
time Zone = 0
In other words exactly as you said.
This was my first time with GXDLMSDirector (sorry to say that, I am a newbie), but I have also made a read from the profile, which I am interested in, for a given scope and there were following results (copy-paste of clock column from GXDLMSDirector ). They are aligned with the results I posted in my previous comments.
But, UTC is a standard, not a timezone, which is a key to the solution. Logs from my program were a little bit misleading for me and the ignorance the Prometer works in UTC were the reason for my problems.
Thanks a lot for your patience and your time I think I will be able to handle that in my program.
Hi,
Hi,
I improved the time zone documentation. I hope it makes this more clear.
https://www.gurux.fi/Gurux.DLMS.Objects.GXDLMSClock
BR,
Mikko