GXDLMSObject 'invalid' description

3 posts / 0 new
Last post
dvillanueva
GXDLMSObject 'invalid' description

Hi!
I want to read the description of all my GXDLMSObjectCollection objects. I call the function
"(GXDLMSObjectCollection).save(final OutputStream stream, final GXXmlWriterSettings settings)"
and creates the XML correctly but the function (GXDLMSObject).getDescription always return the String "Invalid" in ALL objects. Please, can you help me?

Best regards.

arun

I am also facing same issue , I am reading the DLMS meter and in retrun XML I find "Invalid" in description

See below :
<?xml version="1.0" encoding="utf-8"?>
<Objects>
<GXDLMSClock>
<LN>0.0.1.0.0.255</LN>
<Description>Invalid</Description>
<Access>111111111</Access>
<MethodAccess>000000</MethodAccess>
<Time>03/05/2022 15:18:43-05:30</Time>
<TimeZone>330</TimeZone>
<Status>0</Status>
<Begin>03/05/2022 15:18:43-05:30</Begin>
<End>03/05/2022 15:18:43-05:30</End>
<Deviation>0</Deviation>
<Enabled>0</Enabled>
<ClockBase>1</ClockBase>
</GXDLMSClock>
<GXDLMSIecHdlcSetup>
<LN>0.0.22.0.0.255</LN>
<Description>Invalid</Description>
<Access>111111111</Access>
<MethodAccess />
<Speed>5</Speed>
<WindowSizeTx>1</WindowSizeTx>
<WindowSizeRx>1</WindowSizeRx>
<MaximumInfoLengthTx>128</MaximumInfoLengthTx>
<MaximumInfoLengthRx>128</MaximumInfoLengthRx>
<InterCharachterTimeout>1000</InterCharachterTimeout>
<InactivityTimeout>40</InactivityTimeout>
<DeviceAddress>256</DeviceAddress>
</GXDLMSIecHdlcSetup>
<GXDLMSAssociationLogicalName>
<LN>0.0.40.0.1.255</LN>
<Description>Invalid</Description>
<Access>11111101</Access>
<MethodAccess>0000</MethodAccess>
<ObjectList>
<GXDLMSClock>
<LN>0.0.1.0.0.255</LN>
<Access>111111111</Access>
<MethodAccess>000000</MethodAccess>
</GXDLMSClock>
<GXDLMSIecHdlcSetup>
<LN>0.0.22.0.0.255</LN>
<Access>111111111</Access>
</GXDLMSIecHdlcSetup>
<GXDLMSData>
<LN>0.0.42.0.0.255</LN>
<Access>11</Access>
</GXDLMSData>
<GXDLMSData>
<LN>0.0.96.1.0.255</LN>
<Access>11</Access>
</GXDLMSData>
</ObjectList>
<ClientSAP>16</ClientSAP>
<ServerSAP>1</ServerSAP>
<ApplicationContextName>
<JointIsoCtt>2</JointIsoCtt>
<Country>16</Country>
<CountryName>756</CountryName>
<IdentifiedOrganization>5</IdentifiedOrganization>
<DlmsUA>8</DlmsUA>
<ApplicationContext>1</ApplicationContext>
<ContextId>1</ContextId>
</ApplicationContextName>
<XDLMSContextInfo>
<Conformance>524288</Conformance>
<MaxReceivePduSize>200</MaxReceivePduSize>
<MaxSendPduSize>500</MaxSendPduSize>
<DlmsVersionNumber>6</DlmsVersionNumber>
<QualityOfService>0</QualityOfService>
<CypheringInfo />
</XDLMSContextInfo>
<AuthenticationMechanismName>
<JointIsoCtt>2</JointIsoCtt>
<Country>16</Country>
<CountryName>756</CountryName>
<IdentifiedOrganization>5</IdentifiedOrganization>
<DlmsUA>8</DlmsUA>
<AuthenticationMechanismName>2</AuthenticationMechanismName>
<MechanismId>0</MechanismId>
</AuthenticationMechanismName>
<Secret />
<AssociationStatus>2</AssociationStatus>
<SecuritySetupReference>0.0.0.0.0.0</SecuritySetupReference>
<Users />
<MultipleAssociationViews>0</MultipleAssociationViews>
</GXDLMSAssociationLogicalName>
<GXDLMSData>
<LN>0.0.42.0.0.255</LN>
<Description>Invalid</Description>
<Access>11</Access>
<MethodAccess />
<Value Type="9">48 50 4C 50 50 45 4D 36 58 58 58 30 31 20 20 20</Value>
</GXDLMSData>
<GXDLMSData>
<LN>0.0.96.1.0.255</LN>
<Description>Invalid</Description>
<Access>11</Access>
<MethodAccess />
<Value Type="9">48 30 30 30 30 30 30 30</Value>
</GXDLMSData>
</Objects>

Kurumi
Kurumi's picture

Hi,

What version you are using? Have you modified the source code? This is now tested and it works without problems with several different Android versions and different meters.

Are you reading the association view from the meter or are you adding COSEM objects by yourself?

BR,
Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
http://www.gurux.fi