Solution:

1) Be sure the firmware chip (29EE010) match the protocol (DeviceNet or CANopen). "DnetROM.IMG" for DeviceNet, "CANROM.IMG" for CANopen. 2) Be sure to Adjust the DIP switch to OFF (Address : 0), and using another pin-to-pin cable between serial port of your computer and ADAM-5000/CAN RS-232 port when you want to update the firmware. 3) Only 6 modules supported for ADAM-5000/CAN. They are ADAM-5017, ADAM-5018, ADAM-5024, ADAM-5051, ADAM-5056 and ADAM-5060. 4) The MACID can't the same as ADAM-5000/CAN's ID, and the RTR (Remote Transmission Request-bit) should always be '0'. 5) You have to use the utility MONITOR.EXE or DNU.EXE in pure MS-DOS mode. As you know the CAN port is memory map I/O structure. 6) For DeviceNet protocol, you have to "Open Connection" before issue any command, and remember to "Close Connection" before terminate your application. However, CANopen protocol don't need such procedure. 7) Only DeviceNet protocol supported for VisiDAQ and 32-bit DLL drivers. 8) The DIP switch setting of baud rate is different for DeviceNet and CANopen. Bit 7 Bit 8 DeviceNet CANopen OFF OFF 125K 20K ON OFF 250K 125K OFF ON 500K 500K ON ON Not Used 1M 9) It's recommended to use FIXED IRQ when Event_Handle function is used. 10) Termination resistors are factory installed to allow for impedance matching. A resistor can be enabled by utilizing jumper 9. Basically, the PCL-841 and default ADAM-5000/CAN were terminal. So you have to remove jumper 9 when you have more then one ADAM-5000/CAN in a project. For example, you have 3 ADAM-5000/CAN for your project. You have to remove the jumper 9 of ADAM-5000/CAN #1 and ADAM-5000/CAN #2. PCL-841 <---> ADAM-5000/CAN #1 (remove JP9) <---> ADAM-5000/CAN #2 (remove JP9) <---> ADAM-5000/CAN #3. 11) DRAIN is the ground of CAN bus interface. V- and DRAIN are isolated. Kindly refer to the attached file for the further information.