[jira] [Commented] (PLC4X-355) Unsuported transport javacan/socketcan/virtualcan/

["Łukasz Dywicki (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/PLC4X-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615912#comment-17615912 ] 

Łukasz Dywicki commented on PLC4X-355:
--------------------------------------

Hello [~466787806], thank you for reporting issue. With regard to failure of drivers - you need to add plc4j-transport-socketcan to list of your dependencies. Currently CAN drivers do depend on can transport api alone. It is a bit unfortunate, cause a fair default is socketcan which is then not included in classpath.

Can you please confirm if adding mentioned dependency helps?

> Unsuported transport javacan/socketcan/virtualcan/
> --------------------------------------------------
>
>                 Key: PLC4X-355
>                 URL: https://issues.apache.org/jira/browse/PLC4X-355
>             Project: Apache PLC4X
>          Issue Type: Bug
>          Components: Driver-CANopen
>    Affects Versions: 0.9.1
>            Reporter: yayask
>            Assignee: Łukasz Dywicki
>            Priority: Major
>         Attachments: image-2022-10-11-10-14-06-970.png, image-2022-10-11-10-15-00-405.png, image-2022-10-11-10-15-43-100.png, image-2022-10-11-10-16-25-869.png
>
>
> (Linux) When I try to connect the can device, the default javacan, socketcan, and can transmissions all prompt that they are not supported. But I can use the example of s7 normally. I don't know where the problem makes unsupported transport socketscan.
> !image-2022-10-11-10-15-00-405.png!
> !image-2022-10-11-10-15-43-100.png!
> !image-2022-10-11-10-16-25-869.png!
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)