Skip to main content
Home
for DLMS smart meters
Open source solutions for DLMS smart metering

Main navigation

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

Breadcrumb

  1. Home
  2. Forums
  3. * Access Rights Depending On Client Connection *

* Access Rights depending on client connection *

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 amfragal , 5 May, 2016
Forums
Gurux.DLMS

Hi!

Is there any way to specify access rigths to Attributes in an GXDLMSObject, depending on the client connection (public, management,..) used from the client side?

We are analyzing Gurux.DLMS.Server.Example in C# and we don“t see an inmediate way to get that goal.

Thaks in advance!

Profile picture for user Kurumi

Kurumi

10 years 2 months ago

Access Rights depending on client connection

Hi,

We have updated new version. We have added two methods.
Connected and Disconnected. You can update access rights on Connected.

We have also improved server side functionality for large data amounts.

BR,

Mikko

amfragal

10 years 2 months ago

In reply to Access Rights depending on client connection by Kurumi

* Access Rights depending on client connection *

Thanks so much Mikko!
You answer helped us a lot.

After download last version of server code, we have checked that method Connected() in class GXDLMSBase() can help us to get the goal, but we are not able to get it yet.

An example:

- We are trying to set 'NoAccess' mode for attribute "ClockBase" in object "GXDLMSClock" when public client (16) is connected to the server.

- According with Blue_Book, attribute 'clock_base' for the object 'clock' corresponds to attribute 9.
So, in method Connected(), when we detect that client connected corresponds to public client (16), we try to set 'NoAccess' for that attribute like this :

SetAccess(9,AccessMode.NoAccess)

- After that, if we ask from public client for attribute 'clock_base' to server (Obis: 0.0.1.0.0.255, class: 8, attribute:9), the server is still offering the value of the attribute to the client, despite we set its right as NoAccess mode.

Is there another way to set access rigths in server, or any step left in server side?

Thanks in advance!

Profile picture for user Kurumi

Kurumi

10 years 2 months ago

Access Rights depending on client connection

Hi,

This is an issue. We are checking Access level on Write and Set, but not on Read or Get messages.
I added issue from this:
http://www.gurux.fi/node/5372

We will fix this ASAP.

BR,

Mikko

Profile picture for user Administrator

Administrator

10 years 2 months ago

Access Rights depending on client connection

Hi,

New versions from GXDLMSDirector and DLMS component are available where this is fixed.

  • Create new account
  • Reset your password

Hire Us!

Latest Releases

  • Mon, 07/27/2026 - 12:37
    gurux.dlms.cpp 9.0.2607.2701
  • Thu, 07/23/2026 - 16:19
    gurux.dlms.java 4.0.96
  • Thu, 07/09/2026 - 14:34
    Gurux.DLMS.Python 1.0.201
  • Fri, 06/26/2026 - 16:32
    Gurux.Service 3.0.2606.2601
  • Wed, 06/24/2026 - 08:36
    Gurux.DLMS.Python 1.0.200

New forum topics

  • T_APPL_DATA_LN_N1 subtest 3 fails on an LN-only server regardless of the response to a non-existing-object GET
  • Version mismatch between Gurux.DLMS 9.x and Gurux.Common/Gurux.Serial 8.x
  • Service not known error on gprs communication
  • Help Needed: Interfacing Saral 100 Energy Meter with Microcontroller via RS232
  • Connecting Meter to Agent via serial
More

Who's new

  • software_P
  • eloisedc16
  • OlegVoiva
  • Martaepili
  • Vegazone-Alini
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin