

18:50, EET

June 27, 2012

Where does UserAccessLevel come from? I’m suddenly seeing a problem where UserAccessLevel is Readable on my tags, instead of Readable, Writeable.
I have a custom node manager, and I never get calls to readNonValue asking for UserAccessLevel.
After I first start my server, the tags that should be writable appear as Readable, Writable for both AccessLevel and UserAccessLevel. If I click on a node in the tree that is not supposed to be Writeable I see Readable for both attributes, but every node I look at after that shows Readable, Writeable for AccessLevel, but only Readable for UserAccessLevel.
I’m using UAExpert as a client, but I don’t think the problem is in the client – restarting the client doesn’t help, but restarting the server does.
19:43, EET

December 21, 2011

9:01, EET

December 21, 2011

14:02, EET

June 27, 2012

Okay, that took care of my problem. I think it may point to a bug in the SDK, though.
I had not overridden the method, so the default behavior was causing the problem.
I think it was related to AccessLevel being read-only. Maybe the UserAccessLevel gets masked to read-only, but then doesn’t change back when the client asks for a different node?
Anyway, thanks for the help!
Most Users Ever Online: 1919
Currently Online:
37 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Heikki Tahvanainen: 402
hbrackel: 144
rocket science: 88
pramanj: 86
Francesco Zambon: 83
Ibrahim: 78
Sabari: 62
kapsl: 57
gjevremovic: 49
Xavier: 43
Member Stats:
Guest Posters: 0
Members: 796
Moderators: 7
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1538
Posts: 6493
Newest Members:
rubinramsbotham, SandraVen, lisa40301214436, AndrewLed, georgianaweis51, sophiadavis, Waynegalse, Phillipbus, Oscarsat, WilliamJerModerators: Jouni Aro: 1027, Pyry: 1, Petri: 0, Bjarne Boström: 1037, Jimmy Ni: 26, Matti Siponen: 353, Lusetti: 0
Administrators: admin: 1