Hello,
first of all, thanks for all the work, this project is pure gold!
We are using GXDLMSDirector to connect to an MT382 meter via optical interface. Connecting to the meter works. However, when trying to read the association view, we receive the error "GetObjects failed. Failed to receive reply from the device in given time".
Increasing the timeout does not fix it.
DLMSDirector Logs:
GXDLMSDirector 9.0.2508.2701
Log created 09:29:05
09:29:10 Initializing serial connection.
09:29:10 09:29:10.580 Info Opening
09:29:10 09:29:10.580 Info Einstellungen für die serielle Schnittstelle: Portname: COM3 Baudrate: 300 Daten Bits: 7 Parität: Even Stopp-Bits: One Ablaufsteuerung: None Eop: None
09:29:10 09:29:10.595 Info Open
09:29:13 --- Collecting objects. ---
09:29:13 Collecting objects
00 01 00 64 00 01 00 29 DC 08 49 53 4B 67 74 AC D0 F5 1E 11 00 00 00 00 C0 01 81 00 0F 00 00 28 00 00 FF 02 00 B3 00 1A 57 A2 B0 AD 76 93 2F 68 DD
09:29:13 09:29:13.117 Sent 00 01 00 64 00 01 00 29 DC 08 49 53 4B 67 74 AC D0 F5 1E 11 00 00 00 00 C0 01 81 00 0F 00 00 28 00 00 FF 02 00 B3 00 1A 57 A2 B0 AD 76 93 2F 68 DD
09:29:28 Failed to receive reply from the device in given time.
System.Exception: GetObjects failed. Failed to receive reply from the device in given time.
bei GXDLMSDirector.MainForm.RefreshDevice(GXDLMSMeter dev, Boolean bRefresh)
bei GXDLMSDirector.MainForm.Refresh(Object sender, GXAsyncWork work, Object[] parameters)
--------------------------------------------------
--------------------------------------------------
Device Properties:
<?xml version="1.0" encoding="utf-8"?>
<GXDLMSDevice xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="Gurux1">
<WaitTime>15</WaitTime>
<MaximumBaudRate>300</MaximumBaudRate>
<Standard>4</Standard>
<Password />
<Security>Authentication</Security>
<SecuritySuite>1</SecuritySuite>
<KeyAgreementScheme>0</KeyAgreementScheme>
<SystemTitle>49534B6774ACD0F5</SystemTitle>
<ServerSystemTitle>49534B6774ACD0F5</ServerSystemTitle>
<DedicatedKey>00112233445566778899AABBCCDDEEFF</DedicatedKey>
<PreEstablished>true</PreEstablished>
<IgnoreSNRMWithPreEstablished>true</IgnoreSNRMWithPreEstablished>
<BlockCipherKey>00112233445566778899AABBCCDDEEFF</BlockCipherKey>
<AuthenticationKey>00112233445566778899AABBCCDDEEFF</AuthenticationKey>
<BroadcastKey />
<Challenge />
<Signing>0</Signing>
<LogicalAddress>1</LogicalAddress>
<ClientAddress>100</ClientAddress>
<InterfaceType>1</InterfaceType>
<UseFrameSize>true</UseFrameSize>
<MACSourceAddress>8</MACSourceAddress>
<MacDestinationAddress>8</MacDestinationAddress>
<InactivityTimeout>110</InactivityTimeout>
<FrameDelay>0</FrameDelay>
<ObjectDelay>0</ObjectDelay>
<ServiceClass>UnConfirmed</ServiceClass>
<IncreaseInvocationCounterForGMacAuthentication>true</IncreaseInvocationCounterForGMacAuthentication>
<SignCipherOrder>0</SignCipherOrder>
<Name>MT382</Name>
<Verbose>true</Verbose>
<Conformance>12220486</Conformance>
<Manufacturer>ISK</Manufacturer>
<HDLCAddressing>0</HDLCAddressing>
<UseProtectedRelease>false</UseProtectedRelease>
<SecurityChangeCheck>false</SecurityChangeCheck>
<MediaType>Gurux.Serial.GXSerial</MediaType>
<MediaSettings><Port>COM3</Port><Bps>300</Bps><Parity>2</Parity><ByteSize>7</ByteSize></MediaSettings>
<UseLN>true</UseLN>
<Objects2 />
</GXDLMSDevice>
Thanks.
Hi, Select the Secured…
Hi,
Select the Secured connections tab and uncheck the pre-established system title. Iskraemeco MT382 doesn't use it. After that you should be able to establish the connection to the meter and read it.
BR,
Mikko
Hello, thanks for the reply…
Hello,
thanks for the reply.
Now when reading the clock, we get "Object reference not set to an instance of an object".
We were once connected with the meter and were able to read/write registers. However, by mistake, the register 0-0:43.0.0*255 was set to "All messages must be authenticated". After that, we were not able to connect to the meter again.
BR,
Yanik
Hi, That error seems a bit…
Hi,
That error seems a bit unusual. There is no object reference with the clock object that might cause this.
If you set All messages must be authenticated to the client side, just read the association view again. If you set that to the meter side, you need to ask meter vendor how to reset that.
BR,
Mikko