
25 Chapter 4
4.3 Specific Requirements
4.3.1 Device Driver Functionality
The AdsCAN.dll driver needs to decide which driver should be called
depending on different hardware.
The AdsCAN.dll driver should properly translate the function parameters
to a lower layer driver.
4.3.2 The CAN Driver Framework
All user-mode functionality is implemented through Win32 communica-
tion API Functions.
The AdsCan.dll unified driver interface for all CAN cards is shown in fig-
ure 4.1.
Figure 4.1: AdsCan.dll architecture
With the new driver architecture, you don’t need to recompile your CAN
applications when you switch one CAN card with another.
User's Application
AdsCAN.dll
Ads841.dl l Ads1680.dll Other CAN card dll
Ads841s.sys
Ads841s.vxd
Ads1680s.sys
Ads1680s.vxd
Other CAN card sys
Other CAN card vxd
PCL841 card PCI1680 card Other CAN cards
Cal l CAN wi n32 API
Dynami c deci de whi ch
dll should be loaded
Kommentare zu diesen Handbüchern