Skip to main content
Home
for DLMS smart meters

Main navigation

  • Home
  • Products
  • About us
  • Open Source
  • Community
  • Forum
  • Downloads
User account menu
  • Log in

Breadcrumb

  1. Home
  2. Access Error: Device Reports Unmatched Type.

Access Error: Device Reports unmatched type.

By Mikael.Hild, 30 September, 2023
Forums
Gurux.Net

Hi Mikko,

I've been using the GXDlmsClient, where I would like to read the configuration and then save it, and then read the profiles.

Short explanation:

1. Read Association Views
2. Read Register and Extended Register attributes and values.
3. Read Data attributes and values
4. Read Clock attributes and values
5. Read Profile attributes (all but buffer)
6. Read one row from buffer for last read.
7. Save GXDLMSObjectCollection.

The reason I wanted to read all scalars and units was to have them applied on the buffer values. (I noted that it was not applied if you only read attribute 3, I also had to read the value from attribute 2 for this to work on the register).

Later when I want to read profiles (by date-range) where I have stripped seconds, milliseconds and tested with all possible skips, I get "Access Error: Device reports unmatched type".

At first I read many posts on the forum that suggested that it could be something wrong with the Clock, I tested many variations.

Now I did some tests where I compared my XML with XML saved by GXDLMSDirector and could see that the clock object values have "Cell Type="10" (string?), while using GXDLMSClient saving the ObjectCollection have "Cell Type="25" (DateTime).

Could the loaded data types, from the configuration file, cause the Unmatched Type error because it specified as DateTime instead of string? I do not get this error with DLMSDirector, only when loading my XML Configuration after reading all objects with all attributes.

I will try to catch the actual trace for it.

Profile picture for user Kurumi

Kurumi

1 year 9 months ago

Hi, When you are reading…

Hi,

When you are reading profile generic profiles it doesn't use the clock object.

Can you add the hex trace so I can check from the bytes what might be the reason for this?

BR,
Mikko

  • Log in or register to post comments
  • Create new account
  • Reset your password

Hire Us!

Latest Releases

  • Wed, 07/09/2025 - 16:41
    Gurux.Serial.Android 2.0.13
  • Wed, 07/09/2025 - 12:07
    gurux.dlms.c 9.0.2507.0901
  • Sat, 07/05/2025 - 15:04
    Gurux.DLMS.Python 1.0.188
  • Tue, 07/01/2025 - 10:09
    Gurux.DLMS.Python 1.0.187
  • Tue, 07/01/2025 - 09:54
    gurux.dlms.c 9.0.2507.0101

New forum topics

  • Authentication issues (AARQ) with WASION IM300
  • Regarding the dlms android project
  • Unable to read attribute =3 (1.0.94.91.0.255) IC=7 for Indian Metering, while I'm able to read attribute 3 for other Profile generic class
  • Register Activation class (class_id = 9) attribute index 3 data is not visible
  • Load profile
More
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin