If communication is suddenly stopped while communicating using a thread, a dead lock occurs in the lock in Gurux DLMS. Is there a good way to solve this?
If you want to read concurrently multiple meters using RS-485 you need to create your own client for each thread. There is a frame sequence counter for each connection and this causes you can't share one GXDLMSClient instance for multiple threads.
During 1:1 communication, when DLMS disconnect is transmitted to stop communication with the meter, a dead lock often occurs in the lock of Guux DLMS. Is there any good way to solve this?
Hi,
Hi,
If you are using DLMS and RS-485 then it (daisy chaining) should be possible. You can't read multiple meters with RS-232.
BR,
Mikko
I can't understand what a
I can't understand what a daisy chaining
Is it a multi-drop function?
Hi,
Hi,
Daisy chaining is the same thing as multi-drop in terms of RS-485.
BR,
Mikko
If communication is suddenly
If communication is suddenly stopped while communicating using a thread, a dead lock occurs in the lock in Gurux DLMS. Is there a good way to solve this?
HI,
HI,
If you want to read concurrently multiple meters using RS-485 you need to create your own client for each thread. There is a frame sequence counter for each connection and this causes you can't share one GXDLMSClient instance for multiple threads.
BR,
Mikko
During 1:1 communication,
During 1:1 communication, when DLMS disconnect is transmitted to stop communication with the meter, a dead lock often occurs in the lock of Guux DLMS. Is there any good way to solve this?
Hi,
Hi,
There shouldn't be any deadlocks. Can you describe when this occurs or tell more?
BR,
Mikko