Ho, yes, correct.
I forgot the dashboard app.
The low-can try to open the socket if the /etc/dev-mapping.conf exists
and correctly set but if your CAN interface doesn't exists then you'll
see error messages:
DEBUG: [API low-can] BCM socket ifr_name is : can0
ERROR: [API low-can] ioctl failed. Error was : No such device
This will not fail the binding which continues to operate. As we might
have several CAN buses, like in a real car, the binding should be able
to process the operational buses even if one is failing. Here, it
doesn't exists at all and the binding lacks some recovery capabilities
which, for example, would retry to connect to a socket if this one failed.
I think that the binding should not fails completely if a bus comes
down. I'm open to discussion about that, binder have also some recovery
capabilities which retries a connection to a failed/disconnected
binding, we could imagine to relaunch the binding until is fine but then
the CAN service would be more degraded than running with errors on one
of its bus. Also, we maybe needs to define priorities or level of
importance on certain buses and not the other which would define which
ones are considerate as mandatory to be up and running, and others with
lower importance would be ignored even if failing.
The binding have some lacks here but will be improved, thanks.
Best regards.
On 16/10/2018 04:55, Jason Reich wrote:
Hi Romain and Giuseppe,
The sample app "dashboard" app also uses the low can service, and will
show the vehicle speed on the UI if the low-can service detects the
correct message. If you setup a vcan interface with low-can, and then
run "cansend vcan0 3e9#22" the speed should change on the UI. Make
sure the vcan interface is up before starting the low-can service and
dashboard app.
Hope that helps,
Jason.
------------------------------------------------------------------------
On 10/10/18 12:29 PM, "Romain Forlot [IoT.bzh]"
<romain.forlot@xxxxxxx> wrote:
> Humm, I don't think that there is an existing apps that use the low-can
> API except the signal-composer for now which is also installed by
> default but the low-can configuration isn't activated by default.
> Anyway, signal-composer is also a service without UI. I suggest you to
> read the usage guide of the low-can service here :
> http://docs.automotivelinux.org/docs/apis_services/en/dev/reference/signaling/low-can-usage-guide.html
> If you haven't already read it. :)
_______________________________________________
automotive-discussions mailing list
automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions
--
Romain Forlot - Embedded Engineer - IoT.bzh
romain.forlot@xxxxxxx - www.iot.bzh - +33675142438
_______________________________________________
automotive-discussions mailing list
automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions
