You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using 3DR SiK radios. I am noticing weird behavior when using custom dialects. After the program finishes, when I try to close the nodes, the call to node.Close hangs.
I provide an example of what I am talking about. When using the custom dialect (taken from the library examples), after sending 5 messages the program hangs on the close calls. When using the ardupilotmega one, it doesn't.
EDIT: When I first opened the issue I thought this was caused by opening two nodes from a single process, but after further testing I noticed the issue only happened when using a custom dialect.
The text was updated successfully, but these errors were encountered:
JonPichel
changed the title
Closing node hangs when having multiple serial nodes
Use of custom dialect makes node.Close() hang
May 8, 2024
This might be influenced by the quantity of bytes you're feeding into the serial port, and consequently, by messages and dialects, but just in terms of size, not content. Dialects have no effect on routines and are just converters that allow to convert Golang structs to bytes and vice-versa.
In order to further debug this issue, you need to provide a list of all open goroutines during the freeze, that can be generated in this way:
Hi,
I am using 3DR SiK radios. I am noticing weird behavior when using custom dialects. After the program finishes, when I try to close the nodes, the call to node.Close hangs.
I provide an example of what I am talking about. When using the custom dialect (taken from the library examples), after sending 5 messages the program hangs on the close calls. When using the ardupilotmega one, it doesn't.
EDIT: When I first opened the issue I thought this was caused by opening two nodes from a single process, but after further testing I noticed the issue only happened when using a custom dialect.
The text was updated successfully, but these errors were encountered: