Multiple CULs #988

dkadioglu · 2023-06-30T15:44:22Z

dkadioglu
Jun 30, 2023

Hi,

I have one question: When I have two CULs (one regular nanoCUL, one nanoCUL based on a Arduino Nano Every) connected, does wmbusmeters use them both at the same time? I have currently configured device=auto:c1. According to the logs, both devices are recognized.

Thanks and best

BIBOLV · 2023-07-03T19:57:16Z

BIBOLV
Jul 3, 2023
Collaborator

Hi,
For one device definition it will listen to one dongle - first that is found. If you want to listen to multiple dongles then provide device definition in config for each dongle. device=/dev/ttyUSB0:cul for example.

0 replies

dkadioglu · 2023-07-04T10:58:16Z

dkadioglu
Jul 4, 2023
Author

Thabk you very much. I have it working now, I think. However, it only works if I specify one dongle explicitely and the other one with auto:
device=/dev/ttyACM0:cul:c1 device=/dev/ttyUSB0:cul:c1
doesn't work,
device=/dev/ttyACM0:cul:c1 device=auto:c1
works.
In the first case, the first named CUL is recognized, the other one seems to not answer and the recognition fails. If I change the order, the same happens, so the first one is recognized, the second one not. When I specify the second one with auto, both are recognized. Is there maybe some bug?

Another proposal I would have is, if in debug output the info could be added, which of the devices received the telegram.

1 reply

weetmuts Jul 4, 2023
Maintainer

This sounds like a bug. Can you run with loglevel=debug and post the log here.

dkadioglu · 2023-07-04T20:58:23Z

dkadioglu
Jul 4, 2023
Author

When I tried to reproduce it, to get the log output, I found out, that it works sometimes and sometimes not. I could not identify any systematology so far. Sometimes both devices work, sometimes only one of them. Interestingly, if I define device=auto:c1 two times, it seems to work more reliable.

Here is one log output:

(wmbusmeters) version: 1.14.0-RC1
(config) store meter files in: "/wmbusmeters_data/logs/meter_readings"
(config) using device: /dev/ttyUSB0:cul:c1 
(config) using device: /dev/ttyACM0:cul:c1 
(config) number of meters: 5
(lookup) with file/hex "/dev/ttyUSB0" cul
(serial) check if /dev/ttyUSB0 can be accessed
(serial) tty /dev/ttyUSB0 can be accessed
(serial) EVENT thread interrupted
(serial) before config: /dev/ttyUSB0 speed(B9600) input(ICRNL|IXON) output(ONLCR|OPOST) control(CLOCAL|CREAD|CSIZE|HUPCL) local(ECHO|ECHOCTL|ECHOE|ECHOK|ECHOKE|ICANON|IEXTEN|ISIG) special_chars(3,28,127,21,4,1,17,19,26,18,15,23,22,2,9,48,195,242,118,150,2) modem(DTR|RTS)
(serial) after config:  /dev/ttyUSB0 speed(B38400) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(3,48,195,242,118,150,1) modem(DTR|RTS)
(serialtty) opened /dev/ttyUSB0 fd 3 (detect cul)
(serial /dev/ttyUSB0) sent "560D0A"
(serial) EVENT thread interrupted
(serial) received binary ""
(cul) probe response ""
(serial /dev/ttyUSB0) sent "560D0A"
(serial) EVENT thread interrupted
(serial) received binary ""
(cul) probe response ""
(serial /dev/ttyUSB0) sent "560D0A"
(serial) EVENT thread interrupted
(serial) received binary ""
(cul) probe response ""
(serial) EVENT thread interrupted
(serialtty) closed /dev/ttyUSB0 (detect cul)
(cul) are you there? no
Expected cul on /dev/ttyUSB0 but did not find it! Ignoring tty!
(verbose) ignoring device c1
(lookup) with file/hex "/dev/ttyACM0" cul
(serial) check if /dev/ttyACM0 can be accessed
(serial) tty /dev/ttyACM0 can be accessed
(serial) EVENT thread interrupted
(serial) before config: /dev/ttyACM0 speed(B9600) input(ICRNL|IXON) output(ONLCR|OPOST) control(CLOCAL|CREAD|CSIZE|HUPCL) local(ECHO|ECHOCTL|ECHOE|ECHOK|ECHOKE|ICANON|IEXTEN|ISIG) special_chars(3,28,127,21,4,1,17,19,26,18,15,23,22,2,9,48,195,242,118,150,2) modem(DTR|RTS|CTS)
(serial) after config:  /dev/ttyACM0 speed(B38400) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(3,48,195,242,118,150,1) modem(DTR|RTS|CTS)
(serialtty) opened /dev/ttyACM0 fd 3 (detect cul)
(serial /dev/ttyACM0) sent "560D0A"
(serial) EVENT thread interrupted
(serial) received binary "F8"
(cul) probe response "<F8>"
(serial /dev/ttyACM0) sent "560D0A"
(serial) EVENT thread interrupted
(serial) received binary "5620312E3637206E616E6F43554C3836385F723536380D0A"
(cul) probe response "V 1.67 nanoCUL868_r568<0D><0A>"
(serial) EVENT thread interrupted
(serialtty) closed /dev/ttyACM0 (detect cul)
(cul) are you there? yes
(main) opening /dev/ttyACM0:cul:c1
Started config cul on /dev/ttyACM0 listening on c1
(cul) on /dev/ttyACM0
(serial) EVENT thread interrupted
(serial) before config: /dev/ttyACM0 speed(B38400) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(2,9,48,195,242,118,150,2) modem(DTR|RTS|CTS)
(serial) after config:  /dev/ttyACM0 speed(B38400) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(3,48,195,242,118,150,1) modem(DTR|RTS|CTS)
(serialtty) opened /dev/ttyACM0 fd 3 (cul)
(main) regular reset of cul  on /dev/ttyACM0 will happen every 82800 seconds
(cul) set link mode c
(serial /dev/ttyACM0) sent "6272630D0A"
(serial) EVENT thread interrupted
(serial) received binary "434D4F"
(cul) checkCULFrame "CMO"
(cul) no eol found yet, partial frame
(serial) received binary "4445"
(cul) checkCULFrame "CMODE"
(cul) no eol found yet, partial frame
(serial) received binary "0D0A"
(cul) checkCULFrame "CMODE<0D><0A>"
(cul) no leading 'b' so it is text and no frame
(cul) received "CMODE"(serial /dev/ttyACM0) sent "5832310D0A"
(serial) EVENT thread interrupted
(wmbus) no alarm (expected activity) for cul

A restart of the host (Rpi 3+) and therefor also of the Docker container did not help. Then I changed the config to two lines of device=auto:c1, restarted only the Docker container and both CULs were recognized.

Does that output help already, or do you need anything else?

Another proposal I would have is, if in debug output the info could be added, which of the devices received the telegram.

What do you think about that? This would help to see, if both devices are really receiving telegrams.

2 replies

BIBOLV Jul 4, 2023
Collaborator

Can you post log with both devices on auto and when both are recognized? There is nothing on USB0, so maybe ACM0 and ACM1?

dkadioglu Jul 5, 2023
Author

Can you post log with both devices on auto and when both are recognized? There is nothing on USB0, so maybe ACM0 and ACM1?

The devices are definitely on USB0 and ACM0, as shown in dmesg. So far, they never had different dev paths. Following the output with config

device=auto:c1
device=auto:c1

(wmbusmeters) version: 1.14.0-RC1
(config) store meter files in: "/wmbusmeters_data/logs/meter_readings"
(config) number of meters: 5
(main) device /dev/ttyACM0 not currently used, detect contents...
(serial) check if /dev/ttyACM0 can be accessed
(serial) tty /dev/ttyACM0 can be accessed
(serial) EVENT thread interrupted
(serial) before config: /dev/ttyACM0 speed(B38400) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(2,9,48,147,248,118,128,37,2) modem(DTR|RTS|CTS)
(serial) after config:  /dev/ttyACM0 speed(B9600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(3,48,147,248,118,128,37,1) modem(DTR|RTS|CTS)
(serialtty) opened /dev/ttyACM0 fd 3 (detect amb8465/amb3665)
(serial) received binary ""
(amb8465/3665) sending 6 bytes attempt 0
(serial /dev/ttyACM0) sent "FF0A02008077"
(amb8465/3665) sent 6 bytes OK
(serial) EVENT thread interrupted
(amb8465/3665) reading response... 1
(serial) received binary "FF"
(amb8465/3665) reading response... 2
(serial) received binary ""
(amb8465/3665) reading response... 3
(serial) received binary ""
(amb8465/3665) are you there? no.
(serialtty) closed /dev/ttyACM0 (detect amb8465/amb3665)
(serial) EVENT thread interrupted
(serial) before config: /dev/ttyACM0 speed(B9600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(2,9,32,48,211,118,225,2) modem(DTR|RTS|CTS)
(serial) after config:  /dev/ttyACM0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(3,32,48,211,118,225,1) modem(DTR|RTS|CTS)
(serialtty) opened /dev/ttyACM0 fd 3 (detect im871a)
(serial) received binary ""
(serial /dev/ttyACM0) sent "A5010F00"
(serial) EVENT thread interrupted
(serial) received binary "E0"
(im871a) checkIM871AFrame "E0"
(im871a) frame does not start with a5 "E0"
(im871a) no a5 found at all, drop frame packet.
(im871a/im170a) are you there? no.
(serialtty) closed /dev/ttyACM0 (detect im871a)
(serial) EVENT thread interrupted
(serial) before config: /dev/ttyACM0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(2,9,224,48,211,118,75,2) modem(DTR|RTS|CTS)
(serial) after config:  /dev/ttyACM0 speed(B19200) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(3,224,48,211,118,75,1) modem(DTR|RTS|CTS)
(serialtty) opened /dev/ttyACM0 fd 3 (detect rc1180)
(serial /dev/ttyACM0) sent "00"
(serial) EVENT thread interrupted
(serial) received binary "FE"
(serialtty) closed /dev/ttyACM0 (detect rc1180)
(serial) EVENT thread interrupted
(rc1180) are you there? no.
(serial) EVENT thread interrupted
(serial) before config: /dev/ttyACM0 speed(B19200) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(2,9,48,147,248,118,150,2) modem(DTR|RTS|CTS)
(serial) after config:  /dev/ttyACM0 speed(B38400) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(3,48,147,248,118,150,1) modem(DTR|RTS|CTS)
(serialtty) opened /dev/ttyACM0 fd 3 (detect cul)
(serial /dev/ttyACM0) sent "560D0A"
(serial) EVENT thread interrupted
(serial) received binary "F8"
(cul) probe response "<F8>"
(serial /dev/ttyACM0) sent "560D0A"
(serial) EVENT thread interrupted
(serial) received binary "5620312E3637206E616E6F43554C3836385F723536380D0A"
(cul) probe response "V 1.67 nanoCUL868_r568<0D><0A>"
(serialtty) closed /dev/ttyACM0 (detect cul)
(serial) EVENT thread interrupted
(cul) are you there? yes
(main) opening c1
Started auto cul on /dev/ttyACM0 listening on c1
(cul) on /dev/ttyACM0
(serial) EVENT thread interrupted
(serial) before config: /dev/ttyACM0 speed(B38400) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(2,9,48,147,248,118,150,2) modem(DTR|RTS|CTS)
(serial) after config:  /dev/ttyACM0 speed(B38400) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(4,48,147,248,118,150,1) modem(DTR|RTS|CTS)
(serialtty) opened /dev/ttyACM0 fd 4 (cul)
(main) regular reset of cul  on /dev/ttyACM0 will happen every 82800 seconds
(cul) set link mode c
(serial /dev/ttyACM0) sent "6272630D0A"
(serial) EVENT thread interrupted
(serial) received binary "434D4F"
(cul) checkCULFrame "CMO"
(cul) no eol found yet, partial frame
(serial) received binary "4445"
(cul) checkCULFrame "CMODE"
(cul) no eol found yet, partial frame
(serial) received binary "0D0A"
(cul) checkCULFrame "CMODE<0D><0A>"
(cul) no leading 'b' so it is text and no frame
(cul) received "CMODE"(serial /dev/ttyACM0) sent "5832310D0A"
(wmbus) no alarm (expected activity) for cul
(serial) EVENT thread interrupted
(main) device /dev/ttyUSB0 not currently used, detect contents...
(serial) check if /dev/ttyUSB0 can be accessed
(serial) tty /dev/ttyUSB0 can be accessed
(serial) EVENT thread interrupted
(serial) before config: /dev/ttyUSB0 speed(B38400) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(2,9,16,84,211,118,128,37,2) modem(DTR|RTS)
(serial) after config:  /dev/ttyUSB0 speed(B9600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(3,16,84,211,118,128,37,1) modem(DTR|RTS)
(serialtty) opened /dev/ttyUSB0 fd 3 (detect amb8465/amb3665)
(serial) received binary ""
(amb8465/3665) sending 6 bytes attempt 0
(serial /dev/ttyUSB0) sent "FF0A02008077"
(serial) EVENT thread interrupted
(amb8465/3665) sent 6 bytes OK
(amb8465/3665) reading response... 1
(serial) received binary ""
(amb8465/3665) reading response... 2
(serial) received binary ""
(amb8465/3665) reading response... 3
(serial) received binary ""
(amb8465/3665) are you there? no.
(serialtty) closed /dev/ttyUSB0 (detect amb8465/amb3665)
(serial) EVENT thread interrupted
(serial) EVENT thread interrupted
(serial) before config: /dev/ttyUSB0 speed(B9600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(2,9,88,211,118,225,2) modem(DTR|RTS)
(serial) after config:  /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(3,88,211,118,225,1) modem(DTR|RTS)
(serialtty) opened /dev/ttyUSB0 fd 3 (detect im871a)
(serial) received binary ""
(serial /dev/ttyUSB0) sent "A5010F00"
(serial) EVENT thread interrupted
(serial) received binary ""
(im871a/im170a) are you there? no.
(serialtty) closed /dev/ttyUSB0 (detect im871a)
(serial) EVENT thread interrupted
(serial) before config: /dev/ttyUSB0 speed(B57600) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(2,9,192,88,211,118,75,2) modem(DTR|RTS)
(serial) after config:  /dev/ttyUSB0 speed(B19200) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(3,192,88,211,118,75,1) modem(DTR|RTS)
(serialtty) opened /dev/ttyUSB0 fd 3 (detect rc1180)
(serial /dev/ttyUSB0) sent "00"
(serial) EVENT thread interrupted
(serial) received binary ""
(serial /dev/ttyUSB0) sent "30"
(serial) EVENT thread interrupted
(serial) received binary ""
(serialtty) closed /dev/ttyUSB0 (detect rc1180)
(serial) EVENT thread interrupted
(rc1180) are you there? no.
(serial) EVENT thread interrupted
(serial) before config: /dev/ttyUSB0 speed(B19200) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(2,9,240,91,211,118,150,2) modem(DTR|RTS)
(serial) after config:  /dev/ttyUSB0 speed(B38400) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(3,240,91,211,118,150,1) modem(DTR|RTS)
(serialtty) opened /dev/ttyUSB0 fd 3 (detect cul)
(serial /dev/ttyUSB0) sent "560D0A"
(serial) EVENT thread interrupted
(serial) received binary "3F2028F8807820697320756E6B6E6F776E2920557365206F6E65206F6620422062204320652046206C20522054207420562057205820780D0A"
(cul) probe response "? (<F8><80>x is unknown) Use one of B b C e F l R T t V W X x<0D><0A>"
(serial /dev/ttyUSB0) sent "560D0A"
(serial) EVENT thread interrupted
(serial) received binary "5620312E32362E303920612D63756C6677204275696C643A2070726976617465206275696C642028756E6B6E6F776E29206E616E6F43554C3836382D3333372028462D42616E643A203836384D487A290D0A"
(cul) probe response "V 1.26.09 a-culfw Build: private build (unknown) nanoCUL868-337 (F-Band: 868MHz)<0D><0A>"
(serialtty) closed /dev/ttyUSB0 (detect cul)
(serial) EVENT thread interrupted
(cul) are you there? yes
(main) opening c1
Started auto cul on /dev/ttyUSB0 listening on c1
(cul) on /dev/ttyUSB0
(serial) EVENT thread interrupted
(serial) before config: /dev/ttyUSB0 speed(B38400) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(2,9,16,84,211,118,150,2) modem(DTR|RTS)
(serial) after config:  /dev/ttyUSB0 speed(B38400) input() output() control(CLOCAL|CREAD|CSIZE) local() special_chars(3,16,84,211,118,150,1) modem(DTR|RTS)
(serialtty) opened /dev/ttyUSB0 fd 3 (cul)
(main) regular reset of cul  on /dev/ttyUSB0 will happen every 82800 seconds
(cul) set link mode c
(serial /dev/ttyUSB0) sent "6272630D0A"
(serial) EVENT thread interrupted
(serial) received binary "434D4F44450D"
(cul) checkCULFrame "CMODE<0D>"
(cul) no eol found yet, partial frame
(serial) received binary "0A"
(cul) checkCULFrame "CMODE<0D><0A>"
(cul) no leading 'b' so it is text and no frame
(cul) received "CMODE"(serial /dev/ttyUSB0) sent "5832310D0A"
(wmbus) no alarm (expected activity) for cul
(serial) EVENT thread interrupted
(serial) registered regular callback HOT_PLUG_DETECTOR(0) every 2 seconds
(serial) waiting for stop
(serial) received binary "62354534"

dkadioglu · 2023-07-26T22:08:38Z

dkadioglu
Jul 26, 2023
Author

I hope, my last logs are helpful. Do you have any idea, if and what could go wrong here, that both devices are only working if loaded by auto?

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

wmbusmeters

Multiple CULs #988

{{title}}

Replies: 4 comments 3 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

wmbusmeters

Multiple CULs #988

dkadioglu Jun 30, 2023

Replies: 4 comments · 3 replies

BIBOLV Jul 3, 2023 Collaborator

dkadioglu Jul 4, 2023 Author

weetmuts Jul 4, 2023 Maintainer

dkadioglu Jul 4, 2023 Author

BIBOLV Jul 4, 2023 Collaborator

dkadioglu Jul 5, 2023 Author

dkadioglu Jul 26, 2023 Author

dkadioglu
Jun 30, 2023

Replies: 4 comments 3 replies

BIBOLV
Jul 3, 2023
Collaborator

dkadioglu
Jul 4, 2023
Author

weetmuts Jul 4, 2023
Maintainer

dkadioglu
Jul 4, 2023
Author

BIBOLV Jul 4, 2023
Collaborator

dkadioglu Jul 5, 2023
Author

dkadioglu
Jul 26, 2023
Author