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. Wasion IM300 Default Settings

Wasion IM300 default settings

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 flagr97 , 30 April, 2021
Forums
General discussion

Hello! I visited the page with the default values from different meters and unfortunately I haven't found the default parameters for the Wasion Group Co.Ltd meter, I have a "IM300" in my hands and I can't establish a DLMS connection via GXDLMSDirector, which always return me an "Failed to receive reply from the device in given time" error

Profile picture for user Kurumi

Kurumi

5 years 1 month ago

Hi,

Hi,

Are you using an optical probe or serial port connection? If your serial port settings are correct (baud rate, etc.) you can try to find correct addresses with GXDLMSDirector's HDLC address resolver. Select "HDLC address resolver" from the "Tool" menu and set correct media settings. Then select "Scan".

BR,
Mikko

flagr97

5 years 1 month ago

Hey,

Hey,

Answering your question, I'm using a serial connection.

The good news is that the method worked! The bad news is that another error appeared haha

When I try to connect, it returns an "Unacceptable frame" error, as seen on the image below:

Image
Profile picture for user Kurumi

Kurumi

5 years 1 month ago

Hi,

Hi,

This looks good. :-)

Can you add the hex byte log here so I can check what meter is returning?

BR,
Mikko

flagr97

5 years 1 month ago

In reply to Hi, by Kurumi

Well, again I bring good news

Well, again I bring good news and bad news :)

The "bad" is the log:
GXDLMSDirector 8.2.2104.2901
Log created 14:06:27
14:06:29 Initializing serial connection.
14:06:29 02:06:29.715 Info Opening
14:06:29 02:06:29.715 Info Serial Port Settings: Port Name: COM3 Baud Rate: 9600 Data Bits: 8 Parity: None Stop Bits: One Flow Control: None Eop: None
14:06:29 02:06:29.716 Info Open
14:06:30 Send SNRM request.
7E A0 08 FE FF 21 93 0E AE 7E
14:06:30 02:06:30.725 Sent 7E A0 08 FE FF 21 93 0E AE 7E
14:06:30 02:06:30.789 Received 7E A0 21 21 FE FF 73 83 AD 81 80 14 05 02 01 30 06 02 01 40 07 04 00 00 00 01 08 04 00 00 00 01
14:06:30 02:06:30.816 Received 01 1B 17
14:06:30
7E A0 21 21 FE FF 73 83 AD 81 80 14 05 02 01 30 06 02 01 40 07 04 00 00 00 01 08 04 00 00 00 01 1B 17 7E
14:06:30 Parsing UA reply succeeded.
14:06:30 Send AARQ request.
7E A0 2C FE FF 21 10 1C 55 E6 E6 00 60 1D A1 09 06 07 60 85 74 05 08 01 01 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1E 5D FF FF B3 E2 7E
14:06:30 02:06:30.816 Sent 7E A0 2C FE FF 21 10 1C 55 E6 E6 00 60 1D A1 09 06 07 60 85 74 05 08 01 01 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1E 5D FF FF B3 E2 7E
14:06:35 Data send failed. Try to resend 1/3
14:06:35 02:06:35.828 Sent 7E A0 2C FE FF 21 10 1C 55 E6 E6 00 60 1D A1 09 06 07 60 85 74 05 08 01 01 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1E 5D FF FF B3 E2 7E
14:06:35 02:06:35.933 Received 7E A0 08 21 FE FF 97 5C 3D 7E
14:06:35
7E A0 08 21 FE FF 97 5C 3D 7E
14:06:35 02:06:35.933 Sent 01 42 30 03 0D 0A
14:06:40 02:06:40.939 Info Closing
14:06:40 02:06:40.939 Info Closed
Gurux.DLMS.GXDLMSException: Unacceptable frame.
em GXDLMSDirector.GXDLMSCommunicator.ReadDLMSPacket(Byte[] data, Int32 tryCount, GXReplyData reply)
em GXDLMSDirector.GXDLMSCommunicator.ReadDataBlock(Byte[] data, String text, Int32 multiplier, Int32 tryCount, GXReplyData reply)
em GXDLMSDirector.GXDLMSCommunicator.ReadDataBlock(Byte[] data, String text, Int32 multiplier, GXReplyData reply)
em GXDLMSDirector.GXDLMSCommunicator.ReadDataBlock(Byte[] data, String text, GXReplyData reply)
em GXDLMSDirector.GXDLMSCommunicator.ReadDataBlock(Byte[][] data, String text, GXReplyData reply)
em GXDLMSDirector.GXDLMSCommunicator.InitializeConnection(Boolean force)
em GXDLMSDirector.GXDLMSDevice.InitializeConnection()
em GXDLMSDirector.MainForm.Connect(Object sender, GXAsyncWork work, Object[] parameters)

The good news is that I managed to establish communication, with the WRAPPER interface, instead of HDLC, but there are only 2 options (print below), how can I add more OBIS codes to read the measurements?

Image
Profile picture for user Kurumi

Kurumi

5 years 1 month ago

Hi,

Hi,

Meter is not accepting AARQ message. It's a strange because it accepts SNRM message.
You need to change the authentication level. There is four authentications in your meter.
If you read example #2 you can see what client and server address you need to use (ClientSAP and serverSAP) and what authentication level you need to use (Machanism ID in Authentication Machanism Name tab).

BR,
Mikko

flagr97

5 years 1 month ago

Hey, sorry, but where can I

Hey, sorry, but where can I find this example #2?

Profile picture for user Kurumi

Kurumi

5 years 1 month ago

Hi,

Hi,

From your picture. Read association #2 and then select "General" -tab. You can see client and server SAP (address). Use them.

BR,
Mikko

flagr97

5 years ago

Hey! After some time I got it

Hey! After some time I got it working better, I had to change the server address size to 4 to get it working, but now it's responding an "Invalid OBIS codes" error when I try to get the Association View, here is the log:

[Log removed by kurumi]

Profile picture for user Kurumi

Kurumi

5 years ago

Hi,

Hi,

The logical name is missing for TcpUdpSetup object. You need to ask the meter manufacturer if there is a firmware update available that fixes this.

I'll remove the trace and add only bad data.
<Structure Qty="04" >
<UInt16 Value="0029" />
<UInt8 Value="00" />
<Structure Qty="02" >
<Array Qty="06" >
<Structure Qty="03" >
<Int8 Value="01" />
<Enum Value="00" />
<None />
</Structure>
<Structure Qty="03" >
<Int8 Value="02" />
<Enum Value="00" />
<None />
</Structure>
<Structure Qty="03" >
<Int8 Value="03" />
<Enum Value="00" />
<None />
</Structure>
<Structure Qty="03" >
<Int8 Value="04" />
<Enum Value="00" />
<None />
</Structure>
<Structure Qty="03" >
<Int8 Value="05" />
<Enum Value="00" />
<None />
</Structure>
<Structure Qty="03" >
<Int8 Value="06" />
<Enum Value="00" />
<None />
</Structure>
</Array>
<Array Qty="00" >
</Array>
</Structure>
BR,
Mikko

  • Create new account
  • Reset your password

Hire Us!

Latest Releases

  • Tue, 06/09/2026 - 11:16
    gurux.dlms.java 4.0.95
  • Tue, 06/09/2026 - 10:03
    Gurux.DLMS.Python 1.0.199
  • Mon, 06/08/2026 - 13:39
    gurux.dlms.cpp 9.0.2606.0801
  • Mon, 06/01/2026 - 10:15
    gurux.dlms.cpp 9.0.2606.0101
  • Thu, 05/28/2026 - 16:06
    gurux.dlms.java 4.0.94

New forum topics

  • Error reading L&G Meter
  • Pass a TCP Client to GXNet
  • Australian EDMI Mk10D (Essential Energy area)
  • Strange mix of data notificiation vs get response
  • DLMS Connection
More

Who's new

  • Tuanhgg
  • Adel
  • charnon
  • Paddles
  • Miguel Ángel
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin