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.
Forums
Hi
I am facing problems when trying to connect my device to GXDLMSDirector ("no device found in time")
The device is a Sagemcom S211 meter, which is DLMS-ready according to the cover (specs of the protocol and port in appendix).
The meter is connected to my pc through a serial port USB connection.
I am not certain about what baud rate to select, since it's not explicitly reported in the documentation. Also, I get no result from the HDLC Adress Resolver so I don't know what adresses to select when adding the device.
In the documentation is specifically stated that the meter will not allow communication to be passed back to the meter. I understand that it means only communication from the meter to the computer is to be transmitted? Not sure if this is relevant but I like to mention it to be sure.
I am not sure what to try next, any help is more than welcome. Thanks in advance!
Kind regards
Victor
Image
Hi,
Hi,
I believe that your meter is sending push messages and you can't communicate with your meter.
This means that you can listen to the serial port and read data from the push messages that the meter sends, but you can't establish the connection for the meter.
Select "Tools" and "Serial monitor". Select the correct serial port and try to change the baud rate to higher.
Check "hex" and then select "open" and after a few seconds, you should see the data in the output.
If the data is DLMS you can use Gurux components to parse and visualize it.
BR,
Mikko
Hi Mikko
Hi Mikko
Thank you for your response! I'm glad that has been cleared up.
I have followed your suggestions, and I am now able to read out and visualize data from the meter.
However, compared to the documentation sheet I provided the data still doesn't make sense. The baud rate I ended up using is 2,000,000 baud (2Mbps) since the telegrams are the right size if set like that.
I do receive telegrams with a length of 45 bytes (what it should be) but the flag bytes (7E) and other constant bytes do not appear. Also, there should be a lot of 0x00's in the data (because of unused 3-phase inputs), instead there are many 0xFF's, where the 0's should be. Here are three examples of the telegrams I receive (complete output below):
A0 52 01 F2 9D 59 7D 71 9D 9D 9F 9F 99 93 8F 91 8D 97 EB 97 79 7F 66 7C C4 02 1E 14 FE FF FF FF FF FF FF FF FF FF FF FF FF 59 5F 03 00
A0 52 01 F2 9D 59 7D 71 9D 9D 9F 9F 99 93 8F 91 8D 97 EB 97 79 7E 62 8E A4 02 1C 44 F9 FF FF FF FF FF FF FF FF FF FF FF FF 33 02 06 01 00
A0 52 01 FB 9D 59 7D 71 9D 9D 9F 9F 99 93 8F 91 8D 97 EB 97 79 FF 5E 8C 24 01 0E 56 FE FF FF FF FF FF FF FF FF FF FF FF FF AF C3 03 00
Do you know what could cause this problem? Is this a parsing problem? Or maybe a hardware problem?
Thanks in advance!
Kind regards
Victor
Hi,
Hi,
I believe that your serial port settings are invalid. Are your other settings 8None1?
If they are, try with different baud rates. I hope it'll help.
I'll remove your hex trace because it makes this harder to read and it doesn't give any new information.
BR,
Mikko