I checked high binding source, and found out high-can can only connected with low-can. afb_daemon_require_api("low-can", 1);
Please help me with it. Should high viwi support mutli low level bindings.
Environment
None
Activity
Walt Miner
May 23, 2019 at 10:14 PM
Is this still open or can it be closed?
Romain Forlot
September 11, 2017 at 7:27 AM
Got it.
Xin Zhou
September 11, 2017 at 12:02 AM
Hi,
Thanks a lot.
Now we are focus on other project for a while, so don't hurry for this.
Romain Forlot
September 9, 2017 at 2:46 PM
Some investigation has been done in branch "claneys-dev" following that but nothing finalized yet. This feature has been moved to afb-signal-composer then I will make high-viwi compatible with it.
Idea is to make a binding that can connect to several signals sources and still flexible, using configuration file and dynamics virtual signal definitions.
In a first time, if you are in hurry, I could make a dirty patch but this will be temporary and regression will happens once the signal composer is finished.
Jose Bollo
September 6, 2017 at 8:27 AM
I assigned the file to Romain that is actively focused on that particular topic
Major
Right now I'm creating a new binding to connect usb wheel, and give data to application. I want use the High-Low-Can model like this.
<vehicle can> — <low binding>
--- <high viwi binding> — <application>
<usb wheel> — <wheel binding>
I checked high binding source, and found out high-can can only connected with low-can.
afb_daemon_require_api("low-can", 1);
Please help me with it. Should high viwi support mutli low level bindings.