Below you find a list of known issues and how to resolve or work around the problem. If this is a confirmed bug, we are working on fixing it as soon as possible.
I: fullmo USB2drive: I cannot connect to a CAN network with 20 kbit/s
A: fullmo USB2drive currently does not support 20 kbit/s. Supported baud rates are: 50K, 125K, 250K, 500K, 1MBit.
I: The fullmo USB2drive has two flashing red LEDs
A: fullmo Kickdrive always checks and updates the fullmo USB2drive firmware, according to the application requirements, or in case the USB2drive did not respond with the current firmware version. Two flashing red LEDs indicate that the USB2drive was switched to bootloader / firmware update mode. Please wait until the firmware update has been completed. If the update was interrupted or the USB2drive remains in bootloader mode for other reasons, please open a standard project file in fullmo Kickdrive, start communication in the CAN Interface module and wait until the update completes.
I: How do I prevent fullmo Kickdrive from automatically updating the fullmo USB2drive firmware?
A: The automatic update and software management in fullmo Kickdrive makes sure that for every project and application a suitable USB2drive firmware is used. E.g. the ebmpapst K4 drive support requires a different firmware than the standard CAN interface operation. If you want to prevent such automatic update operations, you can use the Communication Port setting "fullmo:noupdate" in your Kickdrive project.
I: fullmo USB-CAN: After repeated attempts to connect to my CAN equipment, the device does not respond any more.
A: This is a problem due to the single-CAN-channel design of the USB-CAN and its firmware: When the USB-CAN's CAN transceiver enters a "bus off" state, e.g. due to mismatching baud rates, the USB-CAN stops communication on the USB side, too.
The only known solution for this is to remove the USB connection and replug it, so the USB-CAN device is completely reset. The "fullmo USB2drive" device does not show this behavior.
I: fullmo USB-CAN: After repeated attempts to connect to my CAN equipment, the device does not respond any more.
A: This is a problem due to the single-CAN-channel design of the USB-CAN and its firmware: When the USB-CAN's CAN transceiver enters a "bus off" state, e.g. due to mismatching baud rates, the USB-CAN stops communication on the USB side, too.
The only known solution for this is to remove the USB connection and replug it, so the USB-CAN device is completely reset. The "fullmo USB2drive" device does not show this behavior.
I: fullmo USB2drive: The device is not found or Kickdrive reports "Device Update" in the CAN Interface module status.
A: Wait and try again. Especially when connecting the fullmo USB2drive for the first time, or to a different USB port, Windows can take up to one minute until the device is fully recognized and ready to use.
I: I tried to start my drive using the "CANopen Drive - Setup" Module, but it did not respond. When I press "Stop", nothing happens, the Setup panel does not return to "Idle" state.
A: This can happen with the current Kickdrive software version in the following situation: Your drive is not accessible (CAN bus problem? Power supply? Wrong baud rate?, ...). After choosing "Start" in the "CANopen Drive - Setup" panel, Kickdrive is blocked with the repeated tries to address the drive. Solution: Close the Kickdrive project and reopen it. If you are using the fullmo USB-CAN, power cycle it (see above). Then try again.
I: When I control my drive using the "CANopen Drive - Setup" Module, sporadic Timeout messages appear (yellow status indicator)
A: This is a known problem in fullmo Kickdrive versions V1.9.77 or earlier. The timeout problem has been observed when the Scope module is active, or other Kickdrive modules produce considerable extra CAN bus traffic. Please try with the current Kickdrive release available for download.
Q: I didn't find the answer to my question here. Can you help me?
A: Please check our Release Notes and make sure this is not a problem that has been fixed in a recent update. If this did not help, please contact support@kickdrive.de for assistance.
