-
Notifications
You must be signed in to change notification settings - Fork 243
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
Control message request over UDP(unicast/multicast) not working #523
Comments
Sending control messages is only supported for TCP connections. Sending UDP messages to ECUs is not allowed in our cars. I do not know how other OEMs are handling this. |
DLT Daemon also does not support this, because of the same reason. |
Hi @tejaswinijoshi89 / @vifactor , @alexmucde , I am facing the same issue. The UDP connection is not happening to ECU. It remains in yellow. Due to this, the DLT messages from ECU are not seen on the dlt-viewer. Do you have any workaround for this? |
Hello together,
|
Hi @alexmucde ,
|
@Samuel-John Please check if it is a firewall issue. Can you also try older versions of DLT Viewer? |
I tried multiple versions of the dlt-viewer. In particular 2.21, 2.26 and the one built from master. Never could connect to dlt-daemon (built from scratch and running directly on my machine) even if I configure it to use UDP as I described above. I use ubuntu. Qt 5.15.x and 6.4.x Firewall can be indeed the reason, but I am not sure how to check it. |
I am connecting dltviewer (tried with v2.26.0, v2.27.0, v2.18.0) with dltdaemon (https://github.com/COVESA/dlt-daemon/tree/master) over UDP. I am able to receive log messages from dltdaemon over both UDP unicast and multicast interface. But when I try to send control message from dltviewer (GetLogInfo,GetDefaultLoginfo,etc) i get error as "ECU Not Connected ". I even checked on wireshark. UDP signal transmission traces from dltviewer to dltdaemon over UDP are not present.
Does dltviewer supports control message request over UDP. If so then how to enable it.
The text was updated successfully, but these errors were encountered: