It is initialized in my case t 0xC1(Priority.HIGH+ServiceClass.CONFIRMED), which is fine.
However, I find that the behaviour may not be correct since:
- a Zero (InvokeId+Priority) is, I think, legitimate -> but it will be forced to another value
- Priority calculation behaviour depends on the InvokeID value - although their not related
What do you think ?
- Should the Priority be calculated if it is Zero in the request ?
- If so, should this initialization be done independently of the invokeID value (look only at the Priority part of the uint8) ?
Idea of this is that you can change invoke ID or priority for each message if needed.
This can be used for Priority management.
If value is zero Invoke ID and Priority is get from server settings. This is normal case.
I change comment so that it's describes that invoke ID and priority are both added.
InvokeID and Priority
Hi,
Idea of this is that you can change invoke ID or priority for each message if needed.
This can be used for Priority management.
If value is zero Invoke ID and Priority is get from server settings. This is normal case.
I change comment so that it's describes that invoke ID and priority are both added.
BR,
Mikko
setting InvokeIdAndPriority, ClassId, InstanceId and AttributeId
Sir,
When I try to read Wisdom meter configured for Indian standard, the meter responds for the following request.
<InvokeIdAndPriority Value="129" />
<AttributeDescriptor>
<!--PROFILE_GENERIC-->
<ClassId Value="7" />
<!--1.0.99.1.0.255-->
<InstanceId Value="0100630100FF" />
<AttributeId Value="3" />
But, when I use Gurux, the request sent is as follows:
<InvokeIdAndPriority Value="193" />
<AttributeDescriptor>
<!--ASSOCIATION_LOGICAL_NAME-->
<ClassId Value="15" />
<!--0.0.40.0.0.255-->
<InstanceId Value="0000280000FF" />
<AttributeId Value="2" />
Hence meter could not be associated and reporting as undefined object.
Pl. help me to set InvokeIdAndPriority, ClassId, InstanceId and AttributeId
Thank you
Invoke id and priority id
It is understood that the device does not provide object table and we have to enter manually. Hence the above
Dear Sir,
Dear Sir,
Please, if you have a new question, create a new topic.
Change CONFIRMED ServiceClass to UN_CONFIRMED.
cl.setServiceClass(ServiceClass.UN_CONFIRMED);
BR,
Mikko
Thank you, Sir
Thank you, Sir