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.
Q: 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.
Q: The fullmo USB2drive shows two flashing red LEDs
A: 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, perform the following operation: Open the project template Templates/template_usb2drive.kicktpl that can be found in your Kickdrive software folder, and reset the firmware to the default CAN interface according to the USB2Drive_reset_and_firmware_update.pdf document.
Q: How do I prevent Kickdrive from automatically updating the fullmo USB2drive firmware?
A: The automatic update and software management in 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.
Q: Obsolete "fullmo USB-CAN" interface: 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 newer fullmo USB2drive accessory does not show this behavior.
Q: 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.
NOTE: Please also note the information on "USB2Drive shows two flashing red LEDs" above.
Q: 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 obsolete fullmo USB-CAN, power cycle it (see above). Then try again.
Q: I have started the Scope module and now I cannot perform a firmware update or download a Python script to a MovingCap drive.
A: This restriction is "by design". Firmware or Python script downloads to the drive cannot be run in parallel with Scope data acquisition, because they make use of the same CANopen SDO mechanisms. SDO segmented downloads or SDO block transfers are disturbed by the scope's Expedited SDO frames. This also applies to string object readouts using the Object Editor - reading a software version while the Scope is started might fail. But since these strings are short, a second readout usually succeeds.
Solution: Stop the Scope before performing any of these operations: CANopen Firmware Update , MovingCap Python script download, string object read or write.
Q: IXXAT CAN Interface: I try to use Kickdrive with the "ixxat:" setting, but it does not work.
A: Kickdrive currently only supports the (now outdated) VCI 3 API. We are planning a related update, but currently this is not available yet.
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.
