hollinsky-intrepid
commented
4 years ago Hi @zengli136742681,
We've been waiting to see what Vehicle Spy X requires in terms of API (on the main API, you're looking at the legacy API, which is meant to mimic the icsneo40.dll API), so that we don't have to make breaking changes when we support hardware accelerated ISO15765-2.
It would help to know what you're attempting to do with these functions. The functions are meant to enable hardware acceleration of ISO15765-2, ensuring that there is no USB round trip latency when responding to the flow control. In most cases, this will only make a difference for firmware flashes or very high DAQ throughput, where the added latency of a round trip / OS scheduler / etc can add up over tens of thousands of transactions.
Some devices, such as the ValueCAN 4 line, have low enough USB latency that it doesn't even make a difference.
--Paul
zengli136742681
Hi~ Do you have any plan about the realization of the below ISO15765-2 functions?
//ISO15765-2 Functions int icsneoISO15765_EnableNetworks(void* hObject, unsigned long ulNetworks) { // TODO Implement return false; }
int icsneoISO15765_DisableNetworks(void* hObject) { // TODO Implement return false; }
int icsneoISO15765_TransmitMessage(void hObject, unsigned long ulNetworkID, stCM_ISO157652_TxMessage pMsg, unsigned long ulBlockingTimeout) { // TODO Implement return false; }
int icsneoISO15765_ReceiveMessage(void hObject, int ulNetworkID, stCM_ISO157652_RxMessage pMsg) { // TODO Implement return false; }