[new node] m-bus frame parser

[Aaqu]

Hi,
I don't understand why it works so slowly, a lot of time passes before the first and next address is read (4-8s).

I use an ethernet converter, it works very well with the tcp node.
Consider providing an m-bus parser node into which the m-bus frame will be inserted from tcp node.

I carried the tests on the desk (m-bus ~1m of wire) and asking every 2 seconds my device responded in about 612ms

[robertsLando]

@Aaqu You could try to increese the baud rate

[Aaqu]

@Aaqu You could try to increese the baud rate

on m-bus library is not ok (Host Reconnect Timeout 1000ms, second Reconnect Timeout 0ms, auto scan off) sometimes first request 20s
I don't understand why it works so slowly, a lot of time passes before the first and next address is read (4-8s).

on TCP node is ok
I carried the tests on the desk (m-bus ~1m of wire) and asking every 2 seconds my device responded in about 612ms

In my opinion it doesn't look like a baud rate problem, is 2400 set in eth <-> rs232 converter. Both have the same speed.

[robertsLando]

Baud rate is just a serial thing, not TCP, that's why TCP doesn't have that issue... 2400 is slow but it also depends on how far your device is, the far it is the smaller should be the baud rate to limit communication errors

[Aaqu]

Both work on TCP, the converter I use has 2400 defined.
TCP from the second test is the native node-red block (I wrote hex frame to ask device id 2)

*M-Bus Controller use TCP - I planned two address request on 10:00:00 receive first on ~10:00:04 and second ~10:00:09

[Aaqu]

Maybe thinking wrong, but when something enters the queue, it should be queried immediately and should move on to the next query in the queue. Should only define the timeout.