Error ServiceNotSupported for some Actaris ACE6000 and SL7000

Forum Rules

Before commenting read Forum rules

Don't comment the topic if you have a new question.

You can create a new topic selecting correct category from Gurux Forum and then create a new topic selecting "New Topic" from the top left.

By Davenzo , 22 February, 2021
Forums
Gurux.DLMS

Hello,

I have a problem with some Actaris but not all of them,
when I read the clock with the following commands:

7EA01C0002002307327C5FE6E600C0011200080000010000FF0800F8377E

or

7EA01C0002002307544C59E6E600C0012200080000010000FF03009F407E

or

7EA01C0002002307765C5BE6E600C0013200080000010000FF020002287E

I get the following error:

7EA0120700020023527821E6E700D80102A7717E

which translated is:

<ExceptionResponse>
<StateError Value="ServiceNotAllowed" />
<ServiceError Value="ServiceNotSupported" />
</ExceptionResponse>

I do not understand if the clock is not readable for some specific meters and why I can read it in others.

Is there a way for me to get through this specific request without getting an exception?

Thank you very much

Kurumi

5 years 3 months ago

Hi,

Is this the only command that you are sending? Are all the meters using the same firmware version?

BR,
Mikko

Davenzo

5 years 3 months ago

Hi,

This is the first GetRequest I am sending, before that I send the association request in order to connect to the meter but nothing else. This works for most of the Actaris I am reading.

The firmware is not the same,
4.73 is the firmware of a meter I can read
6.11 is the firmware of a meter I cannot read

Thank you very much

Kurumi

5 years 3 months ago

Hi,

What programming language library you are using?
Make sure that you have selected "Get" -proposed conformance.

BR,
Mikko

Davenzo

5 years 3 months ago

Hi,

I am using a library based on iCube on Java.

I asked for a working call of the same command:

My command (not working)

7EA01C0002002307365819E6E600C0011200080000010000FF020088CA7E

<HDLC len="27" >
<TargetAddress Value="16401" />
<SourceAddress Value="3" />
<!--I frame.-->
<FrameType Value="36" />
<PDU>
<GetRequest>
<GetRequestNormal>
<!--Priority: NORMAL ServiceClass: UN_CONFIRMED invokeID: 2-->
<InvokeIdAndPriority Value="18" />
<AttributeDescriptor>
<!--CLOCK-->
<ClassId Value="8" />
<!--0.0.1.0.0.255-->
<InstanceId Value="0000010000FF" />
<AttributeId Value="2" />
</AttributeDescriptor>
</GetRequestNormal>
</GetRequest>
</PDU>
</HDLC>

Working command:

7EA01C000200230F769C95E6E600C0018100080000010000FF020065D77E

<HDLC len="27" >
<TargetAddress Value="16401" />
<SourceAddress Value="7" />
<!--I frame.-->
<FrameType Value="76" />
<PDU>
<GetRequest>
<GetRequestNormal>
<!--Priority: HIGH ServiceClass: UN_CONFIRMED invokeID: 1-->
<InvokeIdAndPriority Value="129" />
<AttributeDescriptor>
<!--CLOCK-->
<ClassId Value="8" />
<!--0.0.1.0.0.255-->
<InstanceId Value="0000010000FF" />
<AttributeId Value="2" />
</AttributeDescriptor>
</GetRequestNormal>
</GetRequest>
</PDU>
</HDLC>

Here I can notice a few differences,

SourceAddress Value
FrameType Value
InvokeAndPriority

Could any of these fields be causing the issue for these specific Actaris but not for the others?

Thank you ver much

Kurumi

5 years 3 months ago

Hi,

Change the library for Gurux java version. Support is better. :-)
In the beginning, you can try to change ServiceClass to Confirmed.

Data is correct. One of the settings is wrong and that is causing the problem.
I believe that Itron has improved or changed some functionality for the newer firmware.

BR,
Mikko