Skip to content
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

[BUG] Gateway change Port to /dev/ttyUSB0 and Baudrate 115200 #279

Open
schnitzlein opened this issue Sep 17, 2024 · 2 comments
Open

[BUG] Gateway change Port to /dev/ttyUSB0 and Baudrate 115200 #279

schnitzlein opened this issue Sep 17, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@schnitzlein
Copy link

schnitzlein commented Sep 17, 2024

Describe the bug
After changeging from default setup to /dev/ttyUSB0 the gateway sink service is in a reset/restart loop and wont start proberly.

To Reproduce
Steps to reproduce the behavior:

  1. docker-compose --env-file gateway.env up -d

  2. sleep 2

  3. docker-compose ps

  4. the sink_service is in restarting loop

  5. docker-compose logs sink_service shows the error description below

Expected behavior
the sink_service should run normally, but it restarts continously

Platform details:

  • default wirepas gateway only with changes in port from /dev/ttyACM0 to /dev/ttyUSB0

Transport service settings:
....

Sink service settings:


# Select the version of wirepas Gateway to use:

#   - "latest" (default if  not set): the gateway will use the latest official release,
#     and at each reboot, the gateway will check if there is a new release to upgrade
#   - "edge":  the gateway will use the top of gateway master branbch. At each reboot,
#     the gateway will check if there is a new release to updgrade
#   - "v1.4.0", "v1.5.0"...: any tag available from docker hub
#
GATEWAY_TAG=latest
# Gateway unique id (used also as mqtt client name)
# If left blank, id will be automatically generated as a uuid based on your hardware
# Id can be any string as long as it is unique in your network. 
WM_GW_ID=my_first_5G_mesh_gw

# Sink service configuration
# On which port the sink is attached (ex: /dev/ttyACM0 or /dev/ttyAMA0 if using a rpi hat)
# Default Nordic development kit
#WM_GW_SINK_UART_PORT=/dev/ttyACM0
# Custom_pcb
WM_GW_SINK_UART_PORT=/dev/ttyUSB0
# Uart bitrate of the sink. It depends on the build configuration of dualmcu_app (ex: 115200, 125000, 1000000)
WM_GW_SINK_BITRATE=115200
#WM_GW_SINK_BITRATE=125000

# Transport service configuration
# If you need more Mqtt settings; please check https://github.com/wirepas/gateway/blob/master/python_transport/wirepas_gateway/utils/argument_tools.py for additional parameters.
# Address of the broker to connect
WM_SERVICES_MQTT_HOSTNAME=localhost
# MQTT port (usually 8883 for secure access, or 1883 for unsecure)
WM_SERVICES_MQTT_PORT=1883
# Username to connect to broker
WM_SERVICES_MQTT_USERNAME=
# Password to connect to broker
WM_SERVICES_MQTT_PASSWORD=

# Uncomment following line to skip TLS check on brocker (uncomment it for local brocker)
WM_SERVICES_MQTT_FORCE_UNSECURE=true

Screenshots
wirepas@wirepasgw:~ $ docker-compose logs sink-service
Attaching to sink-service
wirepas@wirepasgw:~ $ docker-compose logs sink-service
Attaching to sink-service
sink-service | 2024-09-18 09:29:03,250 | [INFO] Main:WM_GW_SINK_BAUDRATE: 125000
sink-service | 2024-09-18 09:29:03,250 | [INFO] Main:WM_GW_SINK_ID: 1
sink-service | 2024-09-18 09:29:03,250 | [INFO] Main:WM_GW_SINK_UART_PORT: /dev/mysink
sink-service | 2024-09-18 09:29:03,250 | [INFO] Main:Starting Sink service:
sink-service | -Port is /dev/mysink
sink-service | -Baudrate is 125000
sink-service | -Dbus Service name is com.wirepas.sink.sink1
sink-service | 2024-09-18 09:29:03,262 | [DEBUG] SERIAL:Custom bitrate set: 125000
sink-service | 2024-09-18 09:29:03,263 | [INFO] wpc_int:WPC initialized
sink-service | 2024-09-18 09:29:03,266 | [ERROR] SLIP:Wrong CRC from host to node detected: 2 (208)
sink-service | 2024-09-18 09:29:03,266 | [WARNING] wpc_int:Wrong CRC for request 0x0e, send it again 1/3
sink-service | 2024-09-18 09:29:03,270 | [WARNING] wpc_int:Waiting confirm for frame_id 0x01 but received 0x00
sink-service | 2024-09-18 09:29:03,271 | [INFO] Main:Node is running mesh API version 19 (uart baudrate is 125000 bps)
sink-service | 2024-09-18 09:29:03,309 | [INFO] Config:Stack version is: 5.7.0.30
sink-service | 2024-09-18 09:29:03,313 | [INFO] Config:Stack is stopped
sink-service | 2024-09-18 09:29:03,767 | [INFO] msap:Status is 0x0f
sink-service | 2024-09-18 09:29:03,801 | [INFO] Config:Stack version is: 5.7.0.30
sink-service | 2024-09-18 09:29:05,206 | [INFO] msap:No App config Set
sink-service | 2024-09-18 09:29:05,754 | [ERROR] wpc_int:Didn't receive answer to the request 0x27 error is: -2
sink-service | 2024-09-18 09:29:05,754 | [ERROR] Otap:Cannot read target scratchpad
sink-service | 2024-09-18 09:29:05,804 | [INFO] msap:No App config Set
sink-service | 2024-09-18 09:29:06,342 | [ERROR] wpc_int:Didn't receive answer to the request 0x27 error is: -2
sink-service | 2024-09-18 09:29:06,342 | [ERROR] Otap:Cannot read target scratchpad
sink-service | 2024-09-18 09:29:06,369 | [INFO] msap:No App config Set
sink-service | 2024-09-18 09:29:06,918 | [ERROR] wpc_int:Didn't receive answer to the request 0x27 error is: -2
sink-service | 2024-09-18 09:29:06,918 | [ERROR] Otap:Cannot read target scratchpad
sink-service | 2024-09-18 09:29:06,968 | [INFO] msap:No App config Set
sink-service | 2024-09-18 09:29:07,506 | [ERROR] wpc_int:Didn't receive answer to the request 0x27 error is: -2
sink-service | 2024-09-18 09:29:07,506 | [ERROR] Otap:Cannot read target scratchpad
sink-service | 2024-09-18 09:29:07,527 | [INFO] msap:No App config Set
sink-service | 2024-09-18 09:29:08,078 | [ERROR] wpc_int:Didn't receive answer to the request 0x27 error is: -2
sink-service | 2024-09-18 09:29:08,078 | [ERROR] Otap:Cannot read target scratchpad
sink-service | 2024-09-18 09:29:08,140 | [INFO] msap:No App config Set
sink-service | 2024-09-18 09:29:08,169 | [INFO] msap:No App config Set
sink-service | 2024-09-18 09:29:08,694 | [ERROR] wpc_int:Didn't receive answer to the request 0x27 error is: -2
sink-service | 2024-09-18 09:29:08,694 | [ERROR] Otap:Cannot read target scratchpad
sink-service | 2024-09-18 09:29:09,246 | [ERROR] wpc_int:Didn't receive answer to the request 0x27 error is: -2
sink-service | 2024-09-18 09:29:09,246 | [ERROR] Otap:Cannot read target scratchpad
sink-service | 2024-09-18 09:29:09,343 | [INFO] msap:No App config Set
sink-service | 2024-09-18 09:29:09,366 | [INFO] msap:No App config Set
sink-service | 2024-09-18 09:29:09,898 | [ERROR] wpc_int:Didn't receive answer to the request 0x27 error is: -2
sink-service | 2024-09-18 09:29:09,898 | [ERROR] Otap:Cannot read target scratchpad
sink-service | 2024-09-18 09:29:10,426 | [ERROR] wpc_int:Didn't receive answer to the request 0x27 error is: -2
sink-service | 2024-09-18 09:29:10,426 | [ERROR] Otap:Cannot read target scratchpad
sink-service | 2024-09-18 09:29:10,540 | [INFO] msap:No App config Set
sink-service | 2024-09-18 09:29:10,567 | [INFO] msap:No App config Set
sink-service | 2024-09-18 09:29:11,094 | [ERROR] wpc_int:Didn't receive answer to the request 0x27 error is: -2
sink-service | 2024-09-18 09:29:11,094 | [ERROR] Otap:Cannot read target scratchpad
sink-service | 2024-09-18 09:29:11,638 | [ERROR] wpc_int:Didn't receive answer to the request 0x27 error is: -2
sink-service | 2024-09-18 09:29:11,638 | [ERROR] Otap:Cannot read target scratchpad
sink-service | 2024-09-18 09:29:11,716 | [INFO] msap:No App config Set
sink-service | 2024-09-18 09:29:11,749 | [INFO] msap:No App config Set

Additional context
Before with the /dev/ttyACM0 and baudrate set to 125000 it works fine.
After manually or complete reboot of the system, debugging shows this reset loop.

@schnitzlein schnitzlein added the bug Something isn't working label Sep 17, 2024
@GwendalRaoul
Copy link
Contributor

Hello,

But have you rebuild your dualmcu at 125000 baudrate?

Do you confirm that a device running the dulamcu app at 125000kb is connected to /dev/ttyUSB0?

Because the log seems to say the opposite.

Thanks,
Gwendal

@amolizm
Copy link

amolizm commented Sep 24, 2024

Hello,

I believe this part

WM_GW_SINK_UART_PORT=/dev/ttyUSB0

is device mapping from host to container device, and /dev/mysink is a placeholder within the docker container environment, please correct me if I'm wrong.

I'm having the similar problem, sink service is restarting in a loop when its up. The docker-compose.yml, I have pulled from github/wirepas/gw.

Has this issue been resolved?

I have a transport service, using the sink0 which I have declared within the sink container by,

WM_GW_SINK_ID: sink0

I get the following error, when I try to initialize/get sink from sink_manager.get_sink("sink0") method.

ERROR:root:Unknown` sink sink0 from sink list

Thanks in advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants