I’m trying to interface a Schneider Electric / L&T DLMS Category C3 bi-directional energy meter using its RS232 port, which is exposed using an RJ11 4-pin connector. I’m stuck at a few points and would really appreciate guidance.
1. RJ11 RS232 Pinout (4-pin) for L&T / Schneider meter
The meter manual is not clear on the RS232 pinout.
Does anyone know the exact mapping for:
Pin 1 – ?
Pin 2 – ?
Pin 3 – ? (ground?)
Pin 4 – ?
A confirmed TX, RX, GND assignment would help a lot.
Honeywell / Elster AS3500 and AS3000 are very common in Portugal for renewable energy metering.
I have a AS3500 W12B-743-OSE-0037S-DD000 meter which I'm trying to read with DLMSDirector but so far without any success.
The only thing I managed to do was use the HDLC Address Resolver and find out that the meter manufacturer is ELS. Then I cloned the settings for Elster and changed just the flag from ELE to ELS.
I use Gurux.c library and when i tested it with gxdlmsdirector ctt test
The Communication is ok between this two (Device and Software)
But when software was sent only this :
7e a0 2f 00 02 0e d3 03 10 5e 66 e6 e6 00 c8 1e
30 00 00 00 0c 63 a9 c6 fe 56 8e 96 a8 9f fe ed
1b c9 a9 a3 15 20 64 85 be 96 2f 07 00 c8 b8 6e
7e
I’ve encountered an issue where the meter can send an incorrect response to the request for first attribute and after that local LN is changed.
Current Behavior:
When parsing the response for the first attribute, the Logical Name of a local object is being updated based on the meter’s response. This can cause problems if the response is incorrect. I’ve observed cases where the LN becomes null or changes to a different one entirely. (I've seen a meter to respond with two PDUs in one TCP message, or meter closed the TCP connection before responding.)
Once this happens, further communication with that object is impossible. The only way to recover is to refresh the association or manually correct the Logical Name.
Example:
In one instance, the meter responded to the current security setup 0.0.43.0.0.255 with the real instance of currently connected security setup: 0.0.43.0.5.255. That changed the local object from 0.0.43.0.0.255 to 0.0.43.0.5.255.
Suggested Solution:
The Logical Name should never be modified based on responses from the meter.
A possible solution would be to maintain an internal copy of the LN that remains immutable and is used for all requests, while a secondary copy could reflect any changes reported by the meter.
Currently it should be handled by this method. But the check can be skipped, if the value is not a byte[]. If it is a null, it will return a null. This check needs some work and also the setLogicalName in each object can be adjusted, to not to change the LN. But the LN needs to be changed when loading the object from xml or i think when reading the associacion list, it uses this method also.
