I can connect Sanxing DCU from GXDLMSDirector with these settings in screenshot.
However i cannot read object list. It throws "GetObjects failed. Access Error : Device reports Read-Write denied" error (Error is also in screenshot).
Is there any other ways to read object list of that device or am i missing something.
You need to verify from Sanxing that you have the correct client and server address. That is usually the problem. Sanxing support is usually quite good, so just ask if they know the reason.
Client and server address is already true, its already in the first post photo.
I also made connections with other dlms solutions, but our company is used to work with gurux.
Is there any other things to be done in program or is there any topic related to this device?
Here is the log file from gxdlmsdirector when i try to get object list from dcu:
You have an older meter from the Sanxing meter and the association view is not implemented for this association. Now I can't remember was there a meter update for this, but you need to add items manually.
Can you read the meter with authentication None (Public association)?
If you can, you can see all the objects that a meter can offer.
Then select "Edit" and "Add object". Then add objects that you want to read. You can start by adding clock object. Then try to read it. If you can read it, then add other objects that you want to read.
We can get all objects that meter gives, but we dont need meter objects. We need DCU objects, the way that you advise is didnt work. We cannot read meter as Public. Than we added clock object, we can read DCU clock but it gives an error, error is in below screenshot. Also we tried like 0.0.40.0.0.255 object (Current association), it also fails. We tried adding object by hand and copying from an SANXING THREE PHASE METER. Can you help us creating .gxc file for DCU?
Actually we do not read meters directly. We read meters from Sanxing Data Concentrating Unit (DCU).
An exp. of reading is below. We send an ActionRequest to DCU with using "0000603200FF" method.
The request that meter receives is in "MethodInvocationParameters" section, below code is for Load Profile of the meter.
And the response from DCU is below. Dcu asks the meter, gets result from meter and returns us the result as "ActionResponse".
This example is from an other DLMS library. We'd like to create an .gxc object for that job, and try this on GXDLMSDirector
HEX OF RECEIVED RESPONSE: 00010001000100B9C701440001000202090831313736393631350981A4C402430000000001008200980119020F090C07E6040B01000000FFFF4C0011000600000006060000000006000000000600000000060000000006000000001200001200001259021203E8060000000006000000000600000000020F090C07E6040B01010000FFFF4C0011000600000006060000000006000000000600000000060000000006000000001200001200001258731203E8060000000006000000000600000000
Hi,
Hi,
You need to verify from Sanxing that you have the correct client and server address. That is usually the problem. Sanxing support is usually quite good, so just ask if they know the reason.
BR,
Mikko
Hi Kurumi, thanks for the
Hi Kurumi, thanks for the reply.
Client and server address is already true, its already in the first post photo.
I also made connections with other dlms solutions, but our company is used to work with gurux.
Is there any other things to be done in program or is there any topic related to this device?
Here is the log file from gxdlmsdirector when i try to get object list from dcu:
GXDLMSDirector 8.2.2202.0901
Log created 15:14:53
15:14:54 Initializing Network connection.
15:14:55 Send AARQ request.
00 01 00 01 00 01 00 38 60 36 A1 09 06 07 60 85 74 05 08 01 01 8A 02 07 80 8B 07 60 85 74 05 08 02 01 AC 0A 80 08 41 61 31 32 33 34 35 2E BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 20 1E 5D FF FF
15:14:55
00 01 00 01 00 01 00 44 61 42 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 88 02 07 80 89 07 60 85 74 05 08 02 01 AA 0A 80 08 31 32 33 34 35 36 37 38 BE 10 04 0E 08 00 06 5F 1F 04 00 00 18 1F 02 00 00 07
15:14:55 Parsing AARE reply succeeded.
15:14:57 --- Collecting objects. ---
15:14:57 Collecting objects
00 01 00 01 00 01 00 0D C0 01 C1 00 0F 00 00 28 00 00 FF 02 00
15:14:57
00 01 00 01 00 01 00 05 C4 01 C1 01 03
System.Exception: GetObjects failed. Access Error : Device reports Read-Write denied.
path: GXDLMSDirector.MainForm.RefreshDevice(GXDLMSMeter dev, Boolean bRefresh)
path: GXDLMSDirector.MainForm.Refresh(Object sender, GXAsyncWork work, Object[] parameters)
Hi,
Hi,
You have an older meter from the Sanxing meter and the association view is not implemented for this association. Now I can't remember was there a meter update for this, but you need to add items manually.
Can you read the meter with authentication None (Public association)?
If you can, you can see all the objects that a meter can offer.
Then select "Edit" and "Add object". Then add objects that you want to read. You can start by adding clock object. Then try to read it. If you can read it, then add other objects that you want to read.
BR,
Mikko
Hi Kurumi,
Hi Kurumi,
We can get all objects that meter gives, but we dont need meter objects. We need DCU objects, the way that you advise is didnt work. We cannot read meter as Public. Than we added clock object, we can read DCU clock but it gives an error, error is in below screenshot. Also we tried like 0.0.40.0.0.255 object (Current association), it also fails. We tried adding object by hand and copying from an SANXING THREE PHASE METER. Can you help us creating .gxc file for DCU?
Actually we do not read meters directly. We read meters from Sanxing Data Concentrating Unit (DCU).
An exp. of reading is below. We send an ActionRequest to DCU with using "0000603200FF" method.
The request that meter receives is in "MethodInvocationParameters" section, below code is for Load Profile of the meter.
And the response from DCU is below. Dcu asks the meter, gets result from meter and returns us the result as "ActionResponse".
This example is from an other DLMS library. We'd like to create an .gxc object for that job, and try this on GXDLMSDirector
Best regars, have a nice day.
REQUESTS:
<ActionRequest>
<ActionRequestNormal>
<InvokeIdAndPriority Value="44" />
<MethodDescriptor>
<ClassId Value="0001" />
<InstanceId Value="0000603200FF" />
<MethodId Value="87" />
</MethodDescriptor>
<MethodInvocationParameters>
<Structure Qty="0002" >
<OctetString Value="\11769615" />
<OctetString Value="C0014300070100630100FF0201010204020412000809060000010000FF0F02120000090C07E6040B01000000FF800000090C07E6040C02000000FF8000000100" />
</Structure>
</MethodInvocationParameters>
</ActionRequestNormal>
</ActionRequest>
HEX OF SENDED REQUEST : 000100010001005BC3014400010000603200FF87010202090831313736393631350940C0014300070100630100FF0201010204020412000809060000010000FF0F02120000090C07E6040B01000000FF800000090C07E6040C02000000FF8000000100
RESPONSE:
<ActionResponse>
<ActionResponseNormal>
<InvokeIdAndPriority Value="44" />
<Result Value="Success" />
<ReturnParameters>
<Data>
<Structure Qty="0002" >
<OctetString Value="\11769615" />
<OctetString Value="C402430000000001008200980119020F090C07E6040B01000000FFFF4C0011000600000006060000000006000000000600000000060000000006000000001200001200001259021203E8060000000006000000000600000000020F090C07E6040B01010000FFFF4C0011000600000006060000000006000000000600000000060000000006000000001200001200001258731203E8060000000006000000000600000000" />
</Structure>
</Data>
</ReturnParameters>
</ActionResponseNormal>
</ActionResponse>
HEX OF RECEIVED RESPONSE: 00010001000100B9C701440001000202090831313736393631350981A4C402430000000001008200980119020F090C07E6040B01000000FFFF4C0011000600000006060000000006000000000600000000060000000006000000001200001200001259021203E8060000000006000000000600000000020F090C07E6040B01010000FFFF4C0011000600000006060000000006000000000600000000060000000006000000001200001200001258731203E8060000000006000000000600000000