This approach could also be advantageous to users of Kvaser’s REST API. A program can be written to process the CAN messages locally on the interface, so that just the required information is sent to the host PC. The alternative of transmitting all messages over REST is not that efficient because of the overhead of http and the json coding.
When using a CAN interface to transmit a Diagnostic Protocol command, the program typically expects a message response within a certain period before it ‘timeouts’. Without programming the CAN message flow, the program could timeout most of the time. Programming a Kvaser interface to avoid this situation isn’t as complex as it sounds, thanks to Kvaser’s comprehensive software resources and example files, and it could be much less time-consuming then repeated timeouts. And if you don’t want to create a program for your interface, get in touch with Kvaser to find a Kvaser technical partner that can create one for you.
The Kvaser Ethercan HS (00976-9) is available for sale immediately. For datasheets, user guides, and more, please visit the product page here.