!!!! IMPORTANT NOTICE !!!!!! In addition to the notice below we have to announce an issue of interoperability with very old CAN-PCI/405 boards that comes up since the version 3.10.1 of the driver. The main CPU of the board had to be migrated from PPC405GP to PPC405GPr. This has an impact on the firmware of the board. Unfortunately older drivers would try to "update" the firmware on the board if they find a board from the current production batch which would turn into a downgrade for boards with 405GPr making these boards non functional. To avoid this situation the boards from current production lots (with 405GPr) get a new PCI-ID assigned. Therefore all drivers before 3.10.1 won't talk to CAN-PCI/405 boards with PPC405GPr because the older drivers don't know the new PCI-ID. The driver (since 3.10.1) knows both old and new PCI-IDs and can handle both kind of boards. But it never tries to update any firmware on the CAN-PCI/405. But if you still have a very old CAN-PCI/405 board that has NEVER been used with a driver since 3.7.3 (compare IMPORTANT NOTICE below) the board still has the original first firmware and the current driver won't work with it out of the box. In this case you have to use a driver with update capability (3.7.3 till 3.9.x) to update the firmware as described below. After that this old board will work as expected with a current driver release. esd electronic system design gmbh September 03, 2015 !!!! IMPORTANT NOTICE !!!!!! In some applications it may become necessary to correlate the current hardware timestamp of the CAN-PCI/405 with the system time of the host computer. With this new driver revision the jitter of requesting the hardware timestamp is reduced drastically. In order to achieve this and to address another issue that some (real-time) operating systems (e.g RTX) show a non-deterministic timing during CAN communication because of a performance constraint in the communication between host computer and the CAN-PCI/405 target hardware it becomes necessary to update the CAN-PCI/405 firmware and bootloader. Starting with driver revision 3.7.3 this update is performed implicitly on the first start of the new driver. IMPORTANT: After the bootloader update the driver startup fails and the host computer has to be rebooted !! The update of the bootloader is irreversible. PLEASE NOTICE: After the bootloader update using any driver revision prior to 3.7.3 will fail, because the necessary change couldn't be implemented backward compatible !! If the use of drivers prior 3.7.3 is necessary, sending the device back to esd is required for a bootloader downgrade. esd electronic system design gmbh January 16, 2007