Download AKD Firmware Release Notes

Issue:
Using FB1.USERBYTEx commands with no feedback with memory leads to a drive crash.
+ General Issues
Version: 01-04-17-000,
September 12, 2011
Solution:
The behaviour is now fixed.
+ General Issues
+ IO Issues
WS.MODE 1 results in incorrect motor phase when DRV.DIR = 1 (4003)
z
Issue:
Wake and Shake Mode 1 does not work properly when the drive direction (DRV.DIR) is set to 1. The value of the commutation
angle is wrong (MOTOR.PHASE) after commutation alignment was succesful terminated.
+ Field Bus Specific Issues
Version: 01-04-15-002, August 29,
2011
Solution:
Eliminated a sign problem that caused the the wrong motor phase.
+ Feedback Issues
+ General Issues
+ Field Bus Specific Issues
Version: 01-04-14-000, August 23,
2011
BASIC Issues
Fixed Bugs
Drive crash when using a camming program. (4027,S-09935)
z
Issue:
When the compiler generates an odd number of data bytes, it could be placed on an odd boundary that would cause a misaligned
access exception.
+ Field Bus Specific Issues
+ General Issues
Solution:
The firmware was modified to avoid the misaligned access exception.
Version: 01-04-13-000, August 15,
2011
+ General Issues
+ Field Bus Specific Issues
Version: 01-04-12-000, August 01,
2011
+ Field Bus Specific Issues
Version: 01-07-00-000 Release Date: July 27, 2012
General Issues
Fixed Bugs
DRV.FAULTHIST reports incorrect time stamps due to bad runtime values. (3619,S-09413)
z
Issue:
The runtime value got stuck at 48days, which led to incorrect fault history values once the runtime hit this limit.
+ General Issues
Solution:
Removed the limiting bug in the code.
Version: 01-04-11-000, July 18, 2011
+ Field Bus Specific Issues
+ General Issues
Version: 01-04-10-000, July 01, 2011
+ General Issues
BASIC Issues
Fixed Bugs
z
Issue:
After MOVE.ABORT the decel rate used is CS.DEC instead of MOVE.DEC.
Version: 01-04-09-000, June 21,
2011
Solution:
Now MOVE.DEC is restored as the decel rate after a MOVE.ABORT.
+ General Issues
+ Service Motion Issues
Drive crash with BASIC telnet console output (3940,S-09703)
z
Issue:
A drive crash can occur when a BASIC program is printing and receiving messages simultaneously.
Version: 01-04-08-000, June 08,
2011
Solution:
The BASIC program can now send and receive messages from Workbench or another client simultaneously. Receiving strings from
the BASIC program still occurs on port 54321. Now when sending string to the BASIC program the Telnet client must use port
54322.
+ General Issues
+ Field Bus Specific Issues
Version: 01-04-07-000, May 23, 2011
Virtual Encoder/Master moving flag (CAMVM.MOVING) not working correctly. (3974,S-09770)
z
+ General Issues
Issue:
Starting a move like CAMVM.GOREL and checking the CAMVM.MOVING flag immeidately afterwards could result in incorrect
value.
Version: 01-04-05-000, May 11, 2011
+ General Issues
Solution:
CAMVM.MOVING is now reporting the correct value.
+ Field Bus Specific Issues
Version: 01-04-03-000, May 09, 2011
EXTENCODER.FREQ, CAMVM.FREQ did not report correct values for large internal values (> 2^32) of these
parameters. (3972)
z
Issue:
ExtEncoder Frequency/Velocity conversion routine does not work correctly for large values.
+ General Issues
+ IO Issues
Solution:
EXTENCODER.FREQ and CAMVM.FREQ is now reporting the correct values.
+ Motion Tasking Issues
+ Field Bus Specific Issues
z
Solution:
Analog position mode is now working correctly.
+ General Issues
+ Homing Issues
z
Solution:
Reading FB1.P, FB2.P, and FB3.P now returns correct values.
+ IO Issues
Version: 01-03-20-001, April 04,
2011
+ General Issues
Incorrect unit conversions for FB1.P, FB2.P, and FB3.P. (3937,S-09657)
Issue:
Reading the values of FB1.P, FB2.P, and FB3.P returns incorrect values.
Version: 01-04-01-000, April 11,
2011
+ General Issues
Analog Position Mode does not work. (3918,S-09667)
Issue:
In Analog Position mode the drive does not respond to analog commands.
Version: 01-04-02-000, April 21,
2011
+ Field Bus Specific Issues
After MOVE.ABORT the decel rate used is CS.DEC instead of MOVE.DEC. (3958)
z
SD.SAVE saves active parameters instead of NV parameters. (3976,S-09800)
Issue:
SD.SAVE saves active parameters instead of NV parameters which may result in incorrect drive state saved in the SD card.
Solution:
Now SD.SAVE performs a DRV.NVLOAD prior to saving away the parameters. Users should be aware that current changes to their
parameters will be overwritten when performing SD.SAVE.