Tool is not having configuration support for the values in 'day of week' and 'hundredth of second'
For single action schedule command to set Attribute10 "Activate_passive_calendar_time" meter expect valid values in the all fields of time (also for 'day of week' and 'hundredth of seconds') but tool send the 0xff in both fields. It is better that field configurable and user can define the what value will be send to the meter.
09 0C 07 E7 0A 18 FF 00 2A 37 FF 01 4A 00
Also specified in Blue book "activate_ passive_ calendar_time" :
Defines the time when the object itself calls the specific method activate_passive_calendar. A definition with "not specified" notation in all
fields of the attribute will deactivate this automatism. Partial "not specified" notation in just some fields of date and time are not allowed."
If the fields for 'day of…
If the fields for 'day of week' and 'hundredth of seconds' configurable in the tool then user can configure the valid values.
Hi, The "not specified"…
Hi,
The "not specified" means that the meter should ignore that field and that is widely used.
Some meters can't handle the time-zone or time status and those fields can be ignored in GXDLMSDirector if you select "Advanced" tab.
Are you sure that time zone or time status is not the reason why this fails?
BR,
Mikko
Thanks for the response. I…
Thanks for the response.
I am sure time zone or time status is not that failure reason.
I am unable to set only attribute10 "Activate_passive_calendar_time" using GuruX tool but that is working with other tool, I have tried with other tool and working fine but that will send the 0x00 in both fields "Hundredth of second and day of week". Other attributes working fine.
Hi, Setting the date-time…
Hi,
Setting the date-time can be a real pain with some meters because they are expecting that data is coming in a specific format as it's with your meter.
If your other tool is sending Zero for the day of the week it's working wrong because according to DLMS standard possible values are 1-7 or 0xFF. This is wrong implemented for your meter and it's breaking the DLMS standard.
This seems more like a meter issue and because this is working with lots of different meters there is no need to change this.
BR,
Mikko
Yes possible values are…
Yes possible values are correct but for this particular case (Attribute 10 of Activity calendar) it is not allowed to use partial not specified (0xFF) fields.
For your reference wordings of Blue Book is copied as below:
activate_ passive_ calendar_time: Defines the time when the object itself calls the specific method activate_passive_calendar. A definition with "not specified" notation in all
fields of the attribute will deactivate this automatism. Partial "not specified" notation in just some fields of date and time are not allowed. octet-string, formatted as specified in 4.1.6.1 for date-time.
Hi, The values are not…
Hi,
The values are not correct. In your previous post, you said that the day of the week is zero. That is not possible because value zero is invalid value. Possible values are defined in Blue Book 4.1.6.1 Date and time formats.
dayOfWeek: interpreted as unsigned range 1…7, 0xFF
1 is Monday
0xFF = not specified
If your meter actually uses a value of Zero, it is something the meter manufacturer needs to fix.
BR,
Mikko
Meter not allow to set…
Meter not allow to set partial unspecified values in some fields of date-time of attr10 "activate_ passive_ calendar_time"? Also that is not allowed in Blue book.
Meter can be set successfully only the valid values in day of week 1-7 and hundredth of second 0-100.