-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mbus-tcp-request-data / mbus-tcp-request-data-multi-reply #97
Comments
Do you have the same behavior on requesting the secondary address of the B23 212-100? |
Yes, same story |
The multi-reply fails on Debian@armv7, Freebsd@intel. However it succeeds on Debian@intel/virtualbox. On all tested platforms mbus-tcp-request-data succeeds |
@t006 Could you please try the following patch? https://gist.github.com/lategoodbye/79f8b487d78522cdaaeb0de8c857d2a7 |
Although on page 210 the manual at https://library.e.abb.com/public/94eba55dce8048e6b6e6fcff264a3163/2CMC484001M0201.pdf mentions the meter can be stateful in the M-Bus answers and should be properly reset (where #95 would come in) I don't think this applies here as according to the debug output both applications send out "10 7B 01 7C 16" as the last command and the meter answers to one but not the other. Lets see if the timing helps or if the request just doesn't make it all the way to the reader and needs to be repeated. Cheers, |
Here I have a ABB CEM 05100 reading a B23 212-100 meter.
mbus-tcp-request-data is working perfectly, however mbus-tcp-request-data-multi-reply failed to receive any data.
When I login into the web interface of the CEM I can see a lot more frames. Any idea?
mbus-tcp-request-data-multi-reply -d 192.168.2.43 6021 1 int init_slaves(mbus_handle *): debug: sending init frame #1 [2016-03-28 06:55:01] SEND (005): 10 40 FD 3D 16 int init_slaves(mbus_handle *): debug: sending init frame #2 [2016-03-28 06:55:06] SEND (005): 10 40 FD 3D 16 [2016-03-28 06:55:06] SEND (005): 10 7B 01 7C 16 int mbus_sendrecv_request(mbus_handle *, int, mbus_frame *, int): Failed to receive M-Bus response frame. Failed to send/receive M-Bus request.
`mbus-tcp-request-data -d 192.168.2.43 6021 1 [2016-03-28 06:55:19] SEND (005): 10 7B 01 7C 16
[2016-03-28 06:55:20] RECV (149): 68 8F 8F 68 08 01 72 83 52 07 00 42 04 20 02 36 20 00 00 0E 84 00 03 00 00 00 00 00 8E 40 84 00 00 00 00 00 00 00 04 FF A0 15 00 00 00 00 04 FF A1 15 00 00 00 00 04 FF A2 15 00 00 00 00 04 FF A3 15 00 00 00 00 07 FF A6 00 00 00 00 00 00 00 00 00 07 FF A7 00 06 00 00 00 00 00 00 00 07 FF A8 00 00 00 B6 21 1B 00 00 00 07 FF A9 00 B0 0D D9 00 00 00 00 00 0D FD 8E 00 07 30 2E 37 31 2E 31 42 0D FF AA 00 0B 30 30 31 2D 32 31 32 20 33 32 42 1F 26 16
int mbus_frame_print(mbus_frame *): Dumping M-Bus frame [type 4, 149 bytes]: 68 8F 8F 68 08 01 72 83 52 07 00 42 04 20 02 36 20 00 00 0E 84 00 03 00 00 00 00 00 8E 40 84 00 00 00 00 00 00 00 04 FF A0 15 00 00 00 00 04 FF A1 15 00 00 00 00 04 FF A2 15 00 00 00 00 04 FF A3 15 00 00 00 00 07 FF A6 00 00 00 00 00 00 00 00 00 07 FF A7 00 06 00 00 00 00 00 00 00 07 FF A8 00 00 00 B6 21 1B 00 00 00 07 FF A9 00 B0 0D D9 00 00 00 00 00 0D FD 8E 00 07 30 2E 37 31 2E 31 42 0D FF AA 00 0B 30 30 31 2D 32 31 32 20 33 32 42 1F 26 16
`
The text was updated successfully, but these errors were encountered: