After testing OpenMUC jDLMS, we are testing a meter simulator prototype, we try to use the library gurux.dlms.java to implement the DLMS server part . We have seen in the examples that communication between client and server is based on DLMS TCP / HDLC protocols, but in our case the communication is based on MQTT Messaging.
Question :
What is the good practice to add a custom protocol without having to fundamentally change the existing code of Gurux ?
(communication is made via an MQTT broker between client and DLMS server instances)
Hello, I am testing the compatibility of the gurux client with the openmuc server and I can not make it go. I have also tried actaris ace6000 with the openmuc client and it has not worked for me, I think it's a configuration problem, have not you had any problems using openmuc?
Thank you
Please, make own topic if you have a new question. Check client and server addresses. They are usually causing problems if you are not receiving an answer from the server.
Communication between DLMS client/server other than TCP/HDLC
Hi,
I believe that you have PLC modem or PLC serial port converter. What meter and converter you are using?
BR,
Mikko
Communication between DLMS client/server other than TCP/HDLC
Hi,
Yes we have a PLC Modem ON Semiconductor (NCN49597) and for the meters we try to simulate different manufacturers.
Mansour
Communication between DLMS client/server other than TCP/HDLC
Hello, I am testing the compatibility of the gurux client with the openmuc server and I can not make it go. I have also tried actaris ace6000 with the openmuc client and it has not worked for me, I think it's a configuration problem, have not you had any problems using openmuc?
Thank you
Communication between DLMS client/server other than TCP/HDLC
Hi frato,
Please, make own topic if you have a new question. Check client and server addresses. They are usually causing problems if you are not receiving an answer from the server.
BR,
Mikko