{"action":"created","issue":{"url":"https://api.github.com/repos/CANopenNode/CANopenNode/issues/11","repository_url":"https://api.github.com/repos/CANopenNode/CANopenNode","labels_url":"https://api.github.com/repos/CANopenNode/CANopenNode/issues/11/labels{/name}","comments_url":"https://api.github.com/repos/CANopenNode/CANopenNode/issues/11/comments","events_url":"https://api.github.com/repos/CANopenNode/CANopenNode/issues/11/events","html_url":"https://github.com/CANopenNode/CANopenNode/issues/11","id":167519559,"number":11,"title":"Dual CAN interfaces","user":{"login":"jhaws1982","id":15879967,"avatar_url":"https://avatars.githubusercontent.com/u/15879967?v=3","gravatar_id":"","url":"https://api.github.com/users/jhaws1982","html_url":"https://github.com/jhaws1982","followers_url":"https://api.github.com/users/jhaws1982/followers","following_url":"https://api.github.com/users/jhaws1982/following{/other_user}","gists_url":"https://api.github.com/users/jhaws1982/gists{/gist_id}","starred_url":"https://api.github.com/users/jhaws1982/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jhaws1982/subscriptions","organizations_url":"https://api.github.com/users/jhaws1982/orgs","repos_url":"https://api.github.com/users/jhaws1982/repos","events_url":"https://api.github.com/users/jhaws1982/events{/privacy}","received_events_url":"https://api.github.com/users/jhaws1982/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-07-26T04:37:05Z","updated_at":"2016-07-29T14:42:49Z","closed_at":null,"body":"My application requires that I independently control two motors via two independent CAN buses (latency concerns on single bus).  I'm using Linux and socketCAN.\r\n\r\nI'm looking at the CANopenNode library and it appears that it provides a nice implementation, however it also appears that I can only use a single CAN interface per application.  Is this correct?  I am guessing I would need to modify the library to support multiple interfaces?  Or is there a cleaner way to approach this?\r\n\r\nFYI - I searched the discussion forums on SourceForge and found a thread from 2014 (https://sourceforge.net/p/canopennode/discussion/387151/thread/04054e35/?limit=25#37dc).  Is this still true?  Best approach would be to modify and implement multiple COO globals?  If so, is this something that may be desirable for the masses, thus would require me submitting a pull request?\r\n\r\nThanks!"},"comment":{"url":"https://api.github.com/repos/CANopenNode/CANopenNode/issues/comments/236199290","html_url":"https://github.com/CANopenNode/CANopenNode/issues/11#issuecomment-236199290","issue_url":"https://api.github.com/repos/CANopenNode/CANopenNode/issues/11","id":236199290,"user":{"login":"CANopenNode","id":13575344,"avatar_url":"https://avatars.githubusercontent.com/u/13575344?v=3","gravatar_id":"","url":"https://api.github.com/users/CANopenNode","html_url":"https://github.com/CANopenNode","followers_url":"https://api.github.com/users/CANopenNode/followers","following_url":"https://api.github.com/users/CANopenNode/following{/other_user}","gists_url":"https://api.github.com/users/CANopenNode/gists{/gist_id}","starred_url":"https://api.github.com/users/CANopenNode/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/CANopenNode/subscriptions","organizations_url":"https://api.github.com/users/CANopenNode/orgs","repos_url":"https://api.github.com/users/CANopenNode/repos","events_url":"https://api.github.com/users/CANopenNode/events{/privacy}","received_events_url":"https://api.github.com/users/CANopenNode/received_events","type":"User","site_admin":false},"created_at":"2016-07-29T14:42:49Z","updated_at":"2016-07-29T14:42:49Z","body":"Hi,\r\n\r\nGlobals are sometimes nice for debugging on some microcontrollers. However, it is possible to have separate CANopenSimple.c, which uses only globals and CANopen.c without them.\r\n\r\nObject dictionary is now implemented with globals only. I plan to change that in future. For now there is a workaround in OD editor. If you use a underscore in the beginning of project name, OD editor can generate globals prefixed with different names."}}
{"actor":{"display_login":"CANopenNode"}}