Startseite >
Knowledge Base >
FAQs nach Themen >
Downloads >The following flowchart will guide you to help determine whether you are affected by the Backup FPGA firmware. If you are, please download the new files and instructions.
Questions & Answers
The below represents frequent questions our support, engineering and sales teams have been asked over the years. If you have a question, please submit our contact us form to reach our application engineering team.
Can you help me determine if I am affected by this Backup FPGA firmware?
What is the sequence of events leading to possible brake disengagement?
The sequence of events leading to possible brake disengagement is described in this flow chart. The box marked in red shows the wrong behavior due the fault condition.
If I update the Backup FPGA firmware, can the problem occur that the brake disengages after updating?
No. The updated Backup FPGA firmware (FB0xx_0602_00_01) will behave as expected.
Can the brake disengage unexpectedly when a firmware download was successful?
No.
Can a firmware download with a standard beta or production release fix the issue?
No. The Backup FPGA firmware is not part of the standard beta or production release of operational firmware. The Backup FPGA firmware is programmed separately, and requires special files and process. The files and process are listed in this article.
Where was this problem found?
It was found in a Kollmorgen laboratory during product development. There are no known incidents in the field.
Will my firmware be tainted when updating the Backup FPGA firmware?
No. The Backup FPGA firmware is not part of the main AKD firmware and is not used under normal operating conditions.
If I upgrade the Backup FPGA firmware, will this influence the AKD’s behavior?
No. The Backup FPGA firmware is not used under normal operating conditions. It is not loaded and therefore not part of the main AKD functionality.
How can I figure out the current version of my Backup FPGA firmware?
Connect to the AKD. Go to terminal view. Enter the command “DRV.INFO”. In the section "FPGA", you can read the Backup FPGA firmware version.
For example:
FPGA Version : FP0006_0602_00_00 Operational image : FP0006_0602_00_00 Resident image : FPB006_0602_00_01 Size : 45
The version for the Backup FPGA firmware can be found under "Resident image".
The coding is a follows: FPB00x_yyyy_yy_yy, where “x” represents a certain type, and “y” represents the version number. In this example the version is 0602_00_01.
What versions will this Backup FPGA upgrade apply to?
All Backup FPGA firmware versions FPB0xx_0300_00_00 through FPB0xx_0602_00_01.
0300_00_00 was released in March 2012; 0602_00_01 was released 10 April 2017.
The next question, How can I figure out the current version of my Backup FPGA firmware?, explains how to discover what version you have.
How do I update the Backup FPGA firmware on my AKD? Is this something I can do myself?
Yes, you can update the Backup FPGA firmware yourself. Instructions to upgrade the Backup FPGA firmware can be found on this page or downloaded. The downloadable file may also be found as an attachment at the bottom of this page.
Does the brake disengage while a firmware download is running?
No. The brake will not disengage during a firmware download.
The brake may disengage during a reboot if the download fails and the user firmware has been corrupted.
Which serial numbers are affected?
The following serial numbers are affected by the bug:
- B-0901-00001 – B-1714-00255
- P-0901-00001 – P-1715-00004
- R-0901-00001 – R-1714-00221
- T-0901-00001 – T-1715-00000
What AKDs are affected?
The following model numbers are affected by the bug:
- AKD-P; AKD-B; AKD-T; AKD-M
- KC1-B; KC1-M
NOT affected are models beginning with AKD-N, AKD-C.
What are possible ways to prevent this issue?
One of the following countermeasures can prevent this issue:
- Secure the load during firmware download
- Remove the motor connector from the AKD before starting firmware download (remove power from the AKD before disconnecting any cables!)
- Upgrade the Backup FPGA firmware on the AKD to version FPB0xx_0602_00_01 or higher.
If my system is always in a safe position during a firmware download, do I need to apply further countermeasures?
If you have properly secured your system such that no motion will occur if the brake disengages during the above sequence, then you do not need to apply further countermeasures.
If my system does not have a brake, am I affected by this issue?
No.
When is the Backup FPGA firmware used?
The Backup FPGA firmware is used only when the operational FPGA firmware is corrupted. It is NOT used under normal operating conditions including firmware download and boot up.
Why is there a Backup FPGA firmware?
The Backup FPGA’s purpose is to provide a fallback mechanism to download firmware when the user firmware is corrupted. This Backup FPGA firmware supports only the minimal functionality necessary to for the FPGA (field-programmable gate array) to communicate so the user can flash the AKD with a new user firmware.
Is there a relationship between PL and SIL?
With the use of PFH (Probability of Dangerous Failure per Hour) value you can build a relation between PL (Performance Level) and SIL (Safety Integrity Level). See page Safety.