InvkeID and Priority

By Nico , 12 June, 2017

Forums

Hello,

I have a question regarding the Invoke_ID and Priority usage in latest Gurux version.

In the GXDLMS.java / getLNPdu(), the following code suggests that a zero (InvokeId+Priority) must be initialized:

if (p.getInvokeId() != 0) {
reply.setUInt8((byte) p.getInvokeId());
} else {
reply.setUInt8(getInvokeIDPriority(p.getSettings()));
}

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) ?

Thanks

Nico

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>

<ClassId Value="7" />

<InstanceId Value="0100630100FF" />
<AttributeId Value="3" />
But, when I use Gurux, the request sent is as follows:
<InvokeIdAndPriority Value="193" />
<AttributeDescriptor>

<ClassId Value="15" />

<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