The client's address can be anything. It's not defined on the DLMS standard and different manufacturers are using the different values. You need to check that from the documentation.
If you don't find it you can add hex trace from the AEC meter software communication messages and I'll find the correct settings for you.
No, that trace is not useful, but the source address looks like 17 (0x11). There is no disconnect control in your pictures. Are you sure that you can use disconnect control with Low-level authentication? It might that you need to use High-Level authentication to access it.
Below is the similar trace for disconnector control with same LLS authentication
04-Oct-21 9:26:08 AM Open service, IEC62056-46.
04-Oct-21 9:26:08 AM Remote IP: 192.168.10.1 Remote port: 4059.
04-Oct-21 9:26:10 AM Socket opened.
04-Oct-21 9:26:10 AM MeterNo = 60094845.
04-Oct-21 9:26:10 AM Get: Disconnect control - for main Disconnect.
04-Oct-21 9:26:10 AM GetService: GetRequestNormal, {70, 0.0.96.3.10.255, 4}.
04-Oct-21 9:26:10 AM Get service success.
04-Oct-21 9:26:10 AM Release service.
04-Oct-21 9:26:11 AM Socket closed.
04-Oct-21 9:26:25 AM Open service, IEC62056-46.
04-Oct-21 9:26:25 AM Remote IP: 192.168.10.1 Remote port: 4059.
04-Oct-21 9:26:27 AM Socket opened.
04-Oct-21 9:26:27 AM MeterNo = 60094845.
04-Oct-21 9:26:27 AM Set: Disconnect control - for main Disconnect.
04-Oct-21 9:26:27 AM SetService: SetRequestNormal, {70, 0.0.96.3.10.255, 4}.
04-Oct-21 9:26:27 AM Set service success.
04-Oct-21 9:26:28 AM ActionService: ActionRequestNormal, {70, 0.0.96.3.10.255, 1}.
04-Oct-21 9:26:28 AM Action service success.
04-Oct-21 9:26:28 AM Release service.
04-Oct-21 9:26:28 AM Socket closed.
04-Oct-21 9:26:37 AM Open service, IEC62056-46.
04-Oct-21 9:26:37 AM Remote IP: 192.168.10.1 Remote port: 4059.
04-Oct-21 9:26:39 AM Socket opened.
04-Oct-21 9:26:39 AM MeterNo = 60094845.
04-Oct-21 9:26:39 AM Set: Disconnect control - for main Disconnect.
04-Oct-21 9:26:39 AM SetService: SetRequestNormal, {70, 0.0.96.3.10.255, 4}.
04-Oct-21 9:26:39 AM Set service success.
04-Oct-21 9:26:39 AM ActionService: ActionRequestNormal, {70, 0.0.96.3.10.255, 2}.
04-Oct-21 9:26:40 AM Action service success.
04-Oct-21 9:26:40 AM Release service.
04-Oct-21 9:26:40 AM Socket closed.
It might be that Disconnect control is not in the association view. Select "Edit" and "Add Object...". Then select "Disconnect Control" and change Logical Name to 0.0.96.3.10.255.
Establish the connection and try to read the disconnect control object. It might be that the client address is something else, but the trace that you added don't give any information from it.
All objects should be in the association view, so there is an error on the meter.
You need to add objects manually if they are missing from the association view as you have done now.
I'm glad that this is solved, but you should ask if there is a firmware update where this is fixed.
Please, don't add AEC meter software trace. It doesn't tell anything. Meter returns the empty amount of the rows when you use read by range. Is meter returning anything if you read with all or read by entry?
Hello,
Alright, will not add.
meter returns values, when I select "Read" and give the count. "Range" and "Read last" (no.of days) does not return any values.
PC Time zone is UTC+4, and "Use UTC time zone, not standard" is unchecked.
Also the second object which is daily billing profile 0.0.98.2.0.255. I get error (attached).
please advise.
I believe that meter expects that the start and end times are in a specific format.
You can try to select "Ignore Time Zone" and/or "Ignore Time Status" from Advanced tab.
You can also try to check "Use UTC time zone, not standard".
Hello,
Nope, it replies only when I select "Read" with counts, does this option uses any specific formats, compared to other reading options?
Would appreciate if you could assist in the question I asked regarding reading of other profile 0.0.98.2.0.255, screenshot i had shared in previous reply
Just to update, using meter software too, I am able to only read based on read with count.
Now I have a strange issue, I had not saved the older file and now when I add object under profileGeneric, I get a error "capture objects not read", which I was reading earlier.
"Value was either too large or too small for an Int32" is coming because the meter returns data that can't fit Int32. If you add a hex trace from this, I can check what is the problem.
Your meter is returning 4294967295 seconds (FFFFFFFF) as the capture period. If capture is not used it should be Zero.
The capture period is changed from int to UInt32 in the next version so this is not causing problems to you anymore, but you should check if this is the correct value.
I agree with you. If the meter is read once a day the value should be 86400 seconds (0x15180). Now meter returns 0xFFFFFFFF. This is a custom value of AEC and not a standard DLMS value.
Is the meter working correctly if you write 86400 to the capture period?
Here is data converted as hex.
7E A0 18 23 00 02 4A FB 52 14 B9 E6 E7 00 C4 01 C1 00 06 FF FF FF FF E4 EB 7E
<HDLC len="17" >
<TargetAddress Value="11" />
<!-- Logical address:1, Physical address:4861 -->
<SourceAddress Value="52FD" />
<FrameType Value="52" />
<PDU>
<GetResponse>
<GetResponseNormal>
<!-- Priority: High, ServiceClass: Confirmed, Invoke ID: 1 -->
<InvokeIdAndPriority Value="C1" />
<Result>
<Data>
<UInt32 Value="FFFFFFFF" />
</Data>
</Result>
</GetResponseNormal>
</GetResponse>
</PDU>
</HDLC>
No I did not write the capture period, since using the AEC tool meter throws daily EOB values correctly. Maybe the AEC software understands the Uint32 value, this is what I think.
The capture period is changed for UInt32 so this error is not shown anymore.
What I mean is what happens if you try to set 86400 to capture period value with AEC tool? Or is it possible?
Hello,
In AEC tool, it does not give option to enter the capture period, there is this option in the menu to read billing profile, and meter gives back daily EOB. Below is a small log from AEC tool for your ref.
AEC tool trace doesn't help at all. Please, don't add it in the future. I believe that capture period is hard coded and you can't change it for your meter. Capture period is changed for UInt32 in the next version so you can't get an error when you read it.
Hi,
Hi,
Check that your client address and authentication level are the same as AEC meter software.
The authentication level defines what objects you can see.
BR,
Mikko
Hello,
Hello,
Thank-you for your prompt response, I verified the password and authentication level, it is the same.
However the client address, I understand is by default 17 for LLS?.
what else can I re-verify?.
Thank-you!
Hi,
Hi,
The client's address can be anything. It's not defined on the DLMS standard and different manufacturers are using the different values. You need to check that from the documentation.
If you don't find it you can add hex trace from the AEC meter software communication messages and I'll find the correct settings for you.
BR,
Mikko
Hello,
Hello,
Noted, the trace files are not in detail (Hex trace) which comes from AEC software, Below sample trace, will this be useful?
Trace from the AEC software
30-Sep-21 2:32:38 PM Open service, IEC62056-46.
30-Sep-21 2:32:38 PM Remote IP: 192.168.10.1 Remote port: 4059.
30-Sep-21 2:32:39 PM Socket opened.
30-Sep-21 2:32:40 PM MeterNo = 60087274.
30-Sep-21 2:32:40 PM Get: COSEM logical device name.
30-Sep-21 2:32:40 PM GetService: GetRequestNormal, {1, 0.0.42.0.0.255, 2}.
30-Sep-21 2:32:40 PM Get service success.
30-Sep-21 2:32:40 PM Get: Meter serial number.
30-Sep-21 2:32:40 PM GetService: GetRequestNormal, {1, 0.0.96.1.0.255, 2}.
30-Sep-21 2:32:40 PM Get service success.
30-Sep-21 2:32:41 PM Get: Utility Serial Number.
30-Sep-21 2:32:41 PM GetService: GetRequestNormal, {1, 0.0.96.1.1.255, 2}.
30-Sep-21 2:32:41 PM Get service success.
30-Sep-21 2:32:41 PM Get: Account(customer ID).
30-Sep-21 2:32:41 PM GetService: GetRequestNormal, {1, 0.0.96.1.2.255, 2}.
30-Sep-21 2:32:41 PM Get service success.
30-Sep-21 2:32:41 PM Get: Program ID.
30-Sep-21 2:32:41 PM GetService: GetRequestNormal, {1, 0.0.96.1.3.255, 2}.
30-Sep-21 2:32:42 PM Get service success.
30-Sep-21 2:32:42 PM Get: Hardware version.
30-Sep-21 2:32:42 PM GetService: GetRequestNormal, {1, 0.0.96.1.4.255, 2}.
30-Sep-21 2:32:42 PM Get service success.
30-Sep-21 2:32:42 PM Get: Firmware version.
30-Sep-21 2:32:42 PM GetService: GetRequestNormal, {1, 1.0.0.2.0.255, 2}.
30-Sep-21 2:32:42 PM Get service success.
30-Sep-21 2:32:42 PM Get: Factory Module Test Result.
30-Sep-21 2:32:42 PM GetService: GetRequestNormal, {1, 0.0.96.50.15.255, 2}.
30-Sep-21 2:32:43 PM Get service success.
30-Sep-21 2:32:43 PM Release service.
30-Sep-21 2:32:43 PM Socket closed.
Additonal trace
Additonal trace
Hi,
Hi,
No, that trace is not useful, but the source address looks like 17 (0x11). There is no disconnect control in your pictures. Are you sure that you can use disconnect control with Low-level authentication? It might that you need to use High-Level authentication to access it.
BR,
Mikko
Hello,
Hello,
Below is the similar trace for disconnector control with same LLS authentication
04-Oct-21 9:26:08 AM Open service, IEC62056-46.
04-Oct-21 9:26:08 AM Remote IP: 192.168.10.1 Remote port: 4059.
04-Oct-21 9:26:10 AM Socket opened.
04-Oct-21 9:26:10 AM MeterNo = 60094845.
04-Oct-21 9:26:10 AM Get: Disconnect control - for main Disconnect.
04-Oct-21 9:26:10 AM GetService: GetRequestNormal, {70, 0.0.96.3.10.255, 4}.
04-Oct-21 9:26:10 AM Get service success.
04-Oct-21 9:26:10 AM Release service.
04-Oct-21 9:26:11 AM Socket closed.
04-Oct-21 9:26:25 AM Open service, IEC62056-46.
04-Oct-21 9:26:25 AM Remote IP: 192.168.10.1 Remote port: 4059.
04-Oct-21 9:26:27 AM Socket opened.
04-Oct-21 9:26:27 AM MeterNo = 60094845.
04-Oct-21 9:26:27 AM Set: Disconnect control - for main Disconnect.
04-Oct-21 9:26:27 AM SetService: SetRequestNormal, {70, 0.0.96.3.10.255, 4}.
04-Oct-21 9:26:27 AM Set service success.
04-Oct-21 9:26:28 AM ActionService: ActionRequestNormal, {70, 0.0.96.3.10.255, 1}.
04-Oct-21 9:26:28 AM Action service success.
04-Oct-21 9:26:28 AM Release service.
04-Oct-21 9:26:28 AM Socket closed.
04-Oct-21 9:26:37 AM Open service, IEC62056-46.
04-Oct-21 9:26:37 AM Remote IP: 192.168.10.1 Remote port: 4059.
04-Oct-21 9:26:39 AM Socket opened.
04-Oct-21 9:26:39 AM MeterNo = 60094845.
04-Oct-21 9:26:39 AM Set: Disconnect control - for main Disconnect.
04-Oct-21 9:26:39 AM SetService: SetRequestNormal, {70, 0.0.96.3.10.255, 4}.
04-Oct-21 9:26:39 AM Set service success.
04-Oct-21 9:26:39 AM ActionService: ActionRequestNormal, {70, 0.0.96.3.10.255, 2}.
04-Oct-21 9:26:40 AM Action service success.
04-Oct-21 9:26:40 AM Release service.
04-Oct-21 9:26:40 AM Socket closed.
This is SET request (remote
This is SET request (remote disconnect)
This is SET control (remote
This is SET control (remote re-connect)
Hi,
Hi,
It might be that Disconnect control is not in the association view. Select "Edit" and "Add Object...". Then select "Disconnect Control" and change Logical Name to 0.0.96.3.10.255.
Establish the connection and try to read the disconnect control object. It might be that the client address is something else, but the trace that you added don't give any information from it.
BR,
Mikko
Hello,
Hello,
I added manually and read, It worked..!
Log created 11:06:40 AM
11:06:47 AM Read object type DisconnectControl index: 2
7E A0 1C 00 02 4A FB 23 98 AB 92 E6 E6 00 C0 01 C1 00 46 00 00 60 03 0A FF 02 00 2E 65 7E
11:06:47 AM
7E A0 15 23 00 02 4A FB B8 0F DF E6 E7 00 C4 01 C1 00 03 01 B3 FA 7E
11:06:47 AM Read object type DisconnectControl index: 3
7E A0 1C 00 02 4A FB 23 BA BB 90 E6 E6 00 C0 01 C1 00 46 00 00 60 03 0A FF 03 00 F6 7C 7E
11:06:47 AM
7E A0 15 23 00 02 4A FB DA 1B 9F E6 E7 00 C4 01 C1 00 16 01 9A 11 7E
11:06:47 AM Read object type DisconnectControl index: 4
7E A0 1C 00 02 4A FB 23 DC 8B 96 E6 E6 00 C0 01 C1 00 46 00 00 60 03 0A FF 04 00 FE 31 7E
11:06:47 AM
7E A0 15 23 00 02 4A FB FC 2F DB E6 E7 00 C4 01 C1 00 16 04 37 46 7E
Hi,
Hi,
All objects should be in the association view, so there is an error on the meter.
You need to add objects manually if they are missing from the association view as you have done now.
I'm glad that this is solved, but you should ask if there is a firmware update where this is fixed.
BR,
Mikko
Sure, I will check this..
Sure, I will check this..
Thank-you for your support...!
Hello,
Hello,
I was adding the profileGeneric objects, and when I read the below object it reads, but where do I see the values?
Log created 1:06:34 PM
1:06:43 PM Read object type ProfileGeneric index: 1
7E A0 1C 00 02 4A FB 23 FE 9B 94 E6 E6 00 C0 01 C1 00 07 01 00 63 01 01 FF 01 00 87 BF 7E
1:06:43 PM
7E A0 1B 23 00 02 4A FB 1E 12 99 E6 E7 00 C4 01 C1 00 09 06 01 00 63 01 01 FF 3B FF 7E
1:06:43 PM Read object type ProfileGeneric index: 4
7E A0 1C 00 02 4A FB 23 10 EB 9A E6 E6 00 C0 01 C1 00 07 01 00 63 01 01 FF 04 00 3F C1 7E
1:06:43 PM
7E A0 18 23 00 02 4A FB 30 00 F9 E6 E7 00 C4 01 C1 00 06 00 00 07 08 3D D9 7E
1:06:43 PM Read object type ProfileGeneric index: 5
7E A0 1C 00 02 4A FB 23 32 FB 98 E6 E6 00 C0 01 C1 00 07 01 00 63 01 01 FF 05 00 E7 D8 7E
1:06:43 PM
7E A0 15 23 00 02 4A FB 52 5B 97 E6 E7 00 C4 01 C1 00 16 01 9A 11 7E
1:06:44 PM Read object type ProfileGeneric index: 6
7E A0 1C 00 02 4A FB 23 54 CB 9E E6 E6 00 C0 01 C1 00 07 01 00 63 01 01 FF 06 00 8F F2 7E
1:06:44 PM
7E A0 25 23 00 02 4A FB 74 25 05 E6 E7 00 C4 01 C1 00 02 04 12 00 08 09 06 00 00 01 00 00 FF 0F 02 12 00 00 BE 7F 7E
1:06:44 PM Reading profile generic data
7E A0 4F 00 02 4A FB 23 76 7A 46 E6 E6 00 C0 01 C1 00 07 01 00 63 01 01 FF 02 01 01 02 04 02 04 12 00 08 09 06 00 00 01 00 00 FF 0F 02 12 00 00 09 0C 07 E5 0A 01 FF 00 00 00 FF FF 10 00 09 0C 07 E5 0A 06 FF 00 00 00 FF FF 10 00 01 00 89 16 7E
1:06:44 PM
7E A0 15 23 00 02 4A FB 96 73 17 E6 E7 00 C4 01 C1 00 01 00 8A D8 7E
1:06:44 PM Read object type ProfileGeneric index: 7
7E A0 1C 00 02 4A FB 23 98 AB 92 E6 E6 00 C0 01 C1 00 07 01 00 63 01 01 FF 07 00 57 EB 7E
1:06:44 PM
7E A0 18 23 00 02 4A FB B8 40 F1 E6 E7 00 C4 01 C1 00 06 00 00 25 80 FE C1 7E
1:06:44 PM Read object type ProfileGeneric index: 8
7E A0 1C 00 02 4A FB 23 BA BB 90 E6 E6 00 C0 01 C1 00 07 01 00 63 01 01 FF 08 00 9F 68 7E
1:06:44 PM
7E A0 18 23 00 02 4A FB DA 54 B1 E6 E7 00 C4 01 C1 00 06 00 00 25 80 FE C1 7E
Hello,
Hello,
Further to my query, I was adding below objects under "ProfileGeneric", is this the correct way..?
Profile values 30 mins
05-Oct-21 1:05:12 PM Open service, IEC62056-46.
05-Oct-21 1:05:12 PM Remote IP: 192.168.10.1 Remote port: 4059.
05-Oct-21 1:05:13 PM Socket opened.
05-Oct-21 1:05:14 PM MeterNo = 60094845.
05-Oct-21 1:05:14 PM Get: Load Profile–cumulative.
05-Oct-21 1:05:14 PM GetService: GetRequestNormal, {7, 1.0.99.1.1.255, 3}.
05-Oct-21 1:05:14 PM Get service success.
05-Oct-21 1:05:14 PM Get: Load Profile–cumulative.
05-Oct-21 1:05:14 PM GetService: GetRequestNormal, {7, 1.0.99.1.1.255, 4}.
05-Oct-21 1:05:14 PM Get service success.
05-Oct-21 1:05:14 PM Release service.
05-Oct-21 1:05:14 PM Socket closed.
Daily billing profile
05-Oct-21 1:06:36 PM Open service, IEC62056-46.
05-Oct-21 1:06:36 PM Remote IP: 192.168.10.1 Remote port: 4059.
05-Oct-21 1:06:38 PM Socket opened.
05-Oct-21 1:06:38 PM MeterNo = 60094845.
05-Oct-21 1:06:38 PM Get: Billing Profile(Daily).
05-Oct-21 1:06:38 PM GetService: GetRequestNormal, {7, 0.0.98.2.0.255, 3}.
05-Oct-21 1:06:39 PM GetService: GetRequestNext(BlockNumber = 00000001).
05-Oct-21 1:06:39 PM Get service success.
05-Oct-21 1:06:39 PM Get: Active energy import (+A) [kWh].
05-Oct-21 1:06:39 PM GetService: GetRequestNormal, {3, 1.0.1.8.0.255, 3}.
05-Oct-21 1:06:39 PM Get service success.
05-Oct-21 1:06:39 PM Get: Active energy import (+A) rate 1 [kWh].
05-Oct-21 1:06:39 PM GetService: GetRequestNormal, {3, 1.0.1.8.1.255, 3}.
05-Oct-21 1:06:40 PM Get service success.
05-Oct-21 1:06:40 PM Get: Active energy import (+A) rate 2 [kWh].
05-Oct-21 1:06:40 PM GetService: GetRequestNormal, {3, 1.0.1.8.2.255, 3}.
05-Oct-21 1:06:40 PM Get service success.
05-Oct-21 1:06:40 PM Get: Active energy import (+A) rate 3 [kWh].
05-Oct-21 1:06:40 PM GetService: GetRequestNormal, {3, 1.0.1.8.3.255, 3}.
05-Oct-21 1:06:40 PM Get service success.
05-Oct-21 1:06:40 PM Get: Active energy import (+A) rate 4 [kWh].
05-Oct-21 1:06:40 PM GetService: GetRequestNormal, {3, 1.0.1.8.4.255, 3}.
05-Oct-21 1:06:40 PM Get service success.
05-Oct-21 1:06:40 PM Get: Active energy export (-A) [kWh].
05-Oct-21 1:06:40 PM GetService: GetRequestNormal, {3, 1.0.2.8.0.255, 3}.
05-Oct-21 1:06:40 PM Get service success.
05-Oct-21 1:06:40 PM Get: Active energy export (-A) rate 1 [kWh].
05-Oct-21 1:06:40 PM GetService: GetRequestNormal, {3, 1.0.2.8.1.255, 3}.
05-Oct-21 1:06:40 PM Get service success.
05-Oct-21 1:06:40 PM Get: Active energy export (-A) rate 2 [kWh].
05-Oct-21 1:06:40 PM GetService: GetRequestNormal, {3, 1.0.2.8.2.255, 3}.
05-Oct-21 1:06:41 PM Get service success.
05-Oct-21 1:06:41 PM Get: Active energy export (-A) rate 3 [kWh].
05-Oct-21 1:06:41 PM GetService: GetRequestNormal, {3, 1.0.2.8.3.255, 3}.
05-Oct-21 1:06:41 PM Get service success.
05-Oct-21 1:06:41 PM Get: Active energy export (-A) rate 4 [kWh].
05-Oct-21 1:06:41 PM GetService: GetRequestNormal, {3, 1.0.2.8.4.255, 3}.
05-Oct-21 1:06:41 PM Get service success.
05-Oct-21 1:06:41 PM Get: Reactive energy import (+R) [kvarh].
05-Oct-21 1:06:41 PM GetService: GetRequestNormal, {3, 1.0.3.8.0.255, 3}.
05-Oct-21 1:06:41 PM Get service success.
05-Oct-21 1:06:41 PM Get: Reactive energy import (+R) rate 1 [kvarh].
05-Oct-21 1:06:41 PM GetService: GetRequestNormal, {3, 1.0.3.8.1.255, 3}.
05-Oct-21 1:06:41 PM Get service success.
05-Oct-21 1:06:41 PM Get: Reactive energy import (+R) rate 2 [kvarh].
05-Oct-21 1:06:41 PM GetService: GetRequestNormal, {3, 1.0.3.8.2.255, 3}.
05-Oct-21 1:06:41 PM Get service success.
05-Oct-21 1:06:42 PM Get: Reactive energy import (+R) rate 3 [kvarh].
05-Oct-21 1:06:42 PM GetService: GetRequestNormal, {3, 1.0.3.8.3.255, 3}.
05-Oct-21 1:06:42 PM Get service success.
05-Oct-21 1:06:42 PM Get: Reactive energy import (+R) rate 4 [kvarh].
05-Oct-21 1:06:42 PM GetService: GetRequestNormal, {3, 1.0.3.8.4.255, 3}.
05-Oct-21 1:06:42 PM Get service success.
05-Oct-21 1:06:42 PM Get: Reactive energy export (-R) [kvarh].
05-Oct-21 1:06:42 PM GetService: GetRequestNormal, {3, 1.0.4.8.0.255, 3}.
05-Oct-21 1:06:42 PM Get service success.
05-Oct-21 1:06:42 PM Get: Reactive energy export (-R) rate 1 [kvarh].
05-Oct-21 1:06:42 PM GetService: GetRequestNormal, {3, 1.0.4.8.1.255, 3}.
05-Oct-21 1:06:42 PM Get service success.
05-Oct-21 1:06:42 PM Get: Reactive energy export (-R) rate 2 [kvarh].
05-Oct-21 1:06:42 PM GetService: GetRequestNormal, {3, 1.0.4.8.2.255, 3}.
05-Oct-21 1:06:42 PM Get service success.
05-Oct-21 1:06:42 PM Get: Reactive energy export (-R) rate 3 [kvarh].
05-Oct-21 1:06:42 PM GetService: GetRequestNormal, {3, 1.0.4.8.3.255, 3}.
05-Oct-21 1:06:42 PM Get service success.
05-Oct-21 1:06:43 PM Get: Reactive energy export (-R) rate 4 [kvarh].
05-Oct-21 1:06:43 PM GetService: GetRequestNormal, {3, 1.0.4.8.4.255, 3}.
05-Oct-21 1:06:43 PM Get service success.
05-Oct-21 1:06:43 PM Release service.
05-Oct-21 1:06:43 PM Socket closed.
Hi,
Hi,
Please, don't add AEC meter software trace. It doesn't tell anything. Meter returns the empty amount of the rows when you use read by range. Is meter returning anything if you read with all or read by entry?
What is time zone of your PC? It looks like you have selected "Use UTC time zone, not standard". Is this the case?
https://www.gurux.fi/GXDLMSDirector.DeviceProperties#UseUTC
BR,
Mikko
Hello,
Hello,
Alright, will not add.
meter returns values, when I select "Read" and give the count. "Range" and "Read last" (no.of days) does not return any values.
PC Time zone is UTC+4, and "Use UTC time zone, not standard" is unchecked.
Also the second object which is daily billing profile 0.0.98.2.0.255. I get error (attached).
please advise.
Hi,
Hi,
I believe that meter expects that the start and end times are in a specific format.
You can try to select "Ignore Time Zone" and/or "Ignore Time Status" from Advanced tab.
You can also try to check "Use UTC time zone, not standard".
BR,
Mikko
Hello,
Hello,
Nope, it replies only when I select "Read" with counts, does this option uses any specific formats, compared to other reading options?
Would appreciate if you could assist in the question I asked regarding reading of other profile 0.0.98.2.0.255, screenshot i had shared in previous reply
Just to update, using meter
Just to update, using meter software too, I am able to only read based on read with count.
Now I have a strange issue, I had not saved the older file and now when I add object under profileGeneric, I get a error "capture objects not read", which I was reading earlier.
Hi,
Hi,
It might be possible that read by range is not implemented for the meter if you can't read this with the manufacturer application.
Try to read the capture object again. Select Profile generic object and select "File" and "Refresh".
BR,
Mikko
Hello,
Hello,
Yes, refresh works..!
Could you assist in below error
"Value was either too large or too small for an Int32"
Hi,
Hi,
"Value was either too large or too small for an Int32" is coming because the meter returns data that can't fit Int32. If you add a hex trace from this, I can check what is the problem.
BR,
Mikko
Hello,
Hello,
GXDLMSDirector 8.1.2104.0801
Log created 9:10:24 AM
9:10:32 AM Read object type ProfileGeneric index: 1
7E A0 1C 00 02 4A FB 23 10 EB 9A E6 E6 00 C0 01 C1 00 07 00 00 62 02 00 FF 01 00 64 3B 7E
9:10:32 AM
7E A0 1B 23 00 02 4A FB 30 6E 51 E6 E7 00 C4 01 C1 00 09 06 00 00 62 02 00 FF 17 11 7E
9:10:32 AM Read object type ProfileGeneric index: 4
7E A0 1C 00 02 4A FB 23 32 FB 98 E6 E6 00 C0 01 C1 00 07 00 00 62 02 00 FF 04 00 DC 45 7E
9:10:32 AM
7E A0 18 23 00 02 4A FB 52 14 B9 E6 E7 00 C4 01 C1 00 06 FF FF FF FF E4 EB 7E
System.OverflowException: Value was either too large or too small for an Int32.
at System.Convert.ToInt32(UInt32 value)
at Gurux.DLMS.Objects.GXDLMSProfileGeneric.Gurux.DLMS.Objects.IGXDLMSBase.SetValue(GXDLMSSettings settings, ValueEventArgs e)
at Gurux.DLMS.GXDLMSClient.UpdateValue(GXDLMSObject target, Int32 attributeIndex, Object value, List`1 columns)
at Gurux.DLMS.GXDLMSClient.UpdateValue(GXDLMSObject target, Int32 attributeIndex, Object value)
at GXDLMSDirector.GXDLMSCommunicator.Read(Object sender, GXDLMSObject obj, Boolean forceRead)
at GXDLMSDirector.MainForm.Read(Object sender, GXAsyncWork work, Object[] parameters)
Hi,
Hi,
Your meter is returning 4294967295 seconds (FFFFFFFF) as the capture period. If capture is not used it should be Zero.
The capture period is changed from int to UInt32 in the next version so this is not causing problems to you anymore, but you should check if this is the correct value.
BR,
Mikko
Hello,
Hello,
The capture period should be 86,400 seconds (daily, EOB). I am able to retrieve this in the AEC tool..
Noted..
Hi,
Hi,
I agree with you. If the meter is read once a day the value should be 86400 seconds (0x15180). Now meter returns 0xFFFFFFFF. This is a custom value of AEC and not a standard DLMS value.
Is the meter working correctly if you write 86400 to the capture period?
Here is data converted as hex.
7E A0 18 23 00 02 4A FB 52 14 B9 E6 E7 00 C4 01 C1 00 06 FF FF FF FF E4 EB 7E
<HDLC len="17" >
<TargetAddress Value="11" />
<!-- Logical address:1, Physical address:4861 -->
<SourceAddress Value="52FD" />
<FrameType Value="52" />
<PDU>
<GetResponse>
<GetResponseNormal>
<!-- Priority: High, ServiceClass: Confirmed, Invoke ID: 1 -->
<InvokeIdAndPriority Value="C1" />
<Result>
<Data>
<UInt32 Value="FFFFFFFF" />
</Data>
</Result>
</GetResponseNormal>
</GetResponse>
</PDU>
</HDLC>
BR,
Mikko
Hello,
Hello,
No I did not write the capture period, since using the AEC tool meter throws daily EOB values correctly. Maybe the AEC software understands the Uint32 value, this is what I think.
Thank you for the HEX conversion..
Hi,
Hi,
The capture period is changed for UInt32 so this error is not shown anymore.
What I mean is what happens if you try to set 86400 to capture period value with AEC tool? Or is it possible?
BR,
Mikko
Hello,
Hello,
In AEC tool, it does not give option to enter the capture period, there is this option in the menu to read billing profile, and meter gives back daily EOB. Below is a small log from AEC tool for your ref.
Daily billing profile
05-Oct-21 1:06:36 PM Open service, IEC62056-46.
05-Oct-21 1:06:36 PM Remote IP: 192.168.10.1 Remote port: 4059.
05-Oct-21 1:06:38 PM Socket opened.
05-Oct-21 1:06:38 PM MeterNo = 60094845.
05-Oct-21 1:06:38 PM Get: Billing Profile(Daily).
05-Oct-21 1:06:38 PM GetService: GetRequestNormal, {7, 0.0.98.2.0.255, 3}.
05-Oct-21 1:06:39 PM GetService: GetRequestNext(BlockNumber = 00000001).
05-Oct-21 1:06:39 PM Get service success.
Hi,
Hi,
AEC tool trace doesn't help at all. Please, don't add it in the future. I believe that capture period is hard coded and you can't change it for your meter. Capture period is changed for UInt32 in the next version so you can't get an error when you read it.
BR,
Mikko
Hello,
Hello,
Noted, when is the new version available.?
Hi,
Hi,
It's released during this week.
BR,
Mikko
Hello,
Hello,
I am using below version, is this the one..?
Hi,
Hi,
It's not released yet. You need to wait a few days.
BR,
Mikko
Hello, Noted, thank-you!
Hello,
Noted, thank-you!
Hello,
Hello,
Is the new version now available..?
Regards,
Swaroop
Hi,
Hi,
Yes, you should be notified of it. Update to the latest version.
BR,
Mikko
Hello,
Hello,
When I check for updates, it says no update available and the version is still same.
Do I have to do it manually, could you please assist.
Thank-you!
Regards,
Swaroop
Hi,
Hi,
The version should be 8.2.2111.1801. Download the latest version from the download page if you are using the old version for 3.5.
BR,
Mikko
Hello,
Hello,
Noted, Thank-you!
Regards,
Swaroop