WorkBench Release Notes

WorkBench is a Graphical User Interface that allows configuration from different Kollmorgen devices.

Two Installers distributed with each release:

  • Standard Installer: the application with complete help files. The .NET Framework will be downloaded from internet if not already installed.
  • Full Installer: the application with complete help files and the .NET Framework required by the application.
The .NET Framework is a prerequisite for installing WorkBench. The installer will check if the Framework is present, and when not, the Framework will be installed at the same time as the application.

The Installer allows multiple versions of WorkBench to be installed on the same computer and does not remove the older version automatically. You can manually remove older versions of WorkBench using the Windows Control Panel > Add/Remove Programs.

Version 2.14.0.9656 : November 27, 2023

Requirements

Required Components

  • .NET Framework 4.8
  • Visual C++ Redistributable 2010 SP1 (x86)
  • Visual C++ Redistributable 2013 (x86)
  • Visual C++ Redistributable 2015 SP3 (x86)
  • Internet Explorer 10

Supported Operating Systems

  • Windows 7
  • Windows 8
  • Windows 10
  • Windows 11

Action Table

  • Updated Enum Values for Action Sources [S-24504]
  • Issue:

    The safe action sources (200-218) had badly formed texts with redundancy in their terms.

    Solution:

    All safe enum texts were revisited and their terms fixed to avoid redundancy.

    ^ Back to Top ^

    Communication

  • EIP Free Mapping Renaming [S-24515]
  • Issue:

    Naming for the EIP Free Map assembly in WorkBench needed to be updated to match FW.

    Solution:

    EIP Free Map Assembly was renamed to Free Mapping, and the order of the assemblies in the navigation tree was updated to reflect the numerical order of the assemblies.

  • EtherNetIP Assemblies Structure Update [S-24472]
  • Issue:

    The AKD2G firmware keyword structure around EtherNetIP is being updated to support numerous assembly types. WorkBench needs to be updated to support those assemblies.

    Solution:

    The EtherNetIP structure in WorkBench has been refactored to support the new firmware assembly structure, starting with the Standard assembly.

  • EtherNetIP CIP Sync Assembly Mapping [S-24363]
  • Details:

    Added support in WorkBench for EthernetIP CIP Sync Assembly mapping so users can now view and configure the command and response maps for CIP Sync.

  • EtherNetIP CIP Sync Feedback Scaling [S-24550]
  • Details:

    Implemented the new device level feedback scaling tab for EtherNetIP, allowing users to view and edit the feedback EIP position scaling ratios.

  • EtherNetIP Free Map Assembly [S-24362]
  • Details:

    Added mapping and status support for the new EtherNetIP Free Map Assembly.

  • EtherNetIP Synchronized LED [S-24366]
  • Details:

    Added the new Synchronized LED to the EtherNetIP Views to give the user a clear indication of the device's synchronization state.

  • EtherNetIP Update CIP Sync Drive Level Config [S-24365]
  • Details:

    Added a new CIP Sync tab to the EtherNetIP Overview View which allows the user to configure the CIP Sync assembly state and view information about the system.

  • EtherNetIP Defect Reloading Maps After Disconnect is Hanging [D-09596]
  • Issue:

    Attempting to reload the EtherNetIP Map views after disconnecting was resulting in an infinite "loading" for the user.

    Solution:

    Fixed a bug in EtherNetIP controller intialization that was causing the issue after disconnect.

  • User Interface Crashing when Connecting through TwinCAT
  • Issue:

    Connecting to a device through the TwinCAT Ams Net is crashing.

    Solution:

    Problem fixed.

    ^ Back to Top ^

    Fieldbus

  • EtherNetIP Axis Level CIP Sync Config [S-24367]
  • Details:

    Added a new tab in the Axis Level EtherNet IP view that allows the user to configure and monitor CIP Sync.

  • EtherNetIP CIP Sync Assembly Control and Status [S-24364]
  • Details:

    The bitwise indicators and bit descriptions for the CIP Sync Control and Status words were added to the CIP Sync Assembly View.

  • EtherNetIP CIP Sync New Axis Scaling [S-24368]
  • Details:

    Added a new Scaling tab in the AKD2G EtherNet/IP Axis View that allows the user to configure the scaling.

    ^ Back to Top ^

    Functional Safety

  • Updated SdioAdapter
  • Details:

    Using the latest SAFEGRID adapter (1.0.2.149).

    ^ Back to Top ^

    General

  • Added a Message for Firmware Incompatibility While Updating
  • Details:

    In some occasions, the firmware you are trying to download is incompatible with the one currently loaded.

  • Link Text Wrong on Enable Disable View [D-09612]
  • Issue:

    On AKD2G, the link text for controlled stop action configuration was incorrect, showing "Configure Inputs" but linked to the Actions View.

    Solution:

    The link text now shows "Configure Actions" and still links to the Actions View.

    ^ Back to Top ^

    Monitoring

  • Scope view crashing when retrieving recorder channel data from the device. [Req#72223] [D-09617]
  • Issue:

    The application is crashing often when using the Scope view with one type of parameter added to the Watch panel. The crash occurs when collecting the recorded data from the device.

    Solution:

    The problem has been fixed.

    ^ Back to Top ^

    Motor & Power Stage

  • Wrong Descriptions for the Value of Motor Brake Control [Req#71803] [D-09603]
  • Issue:

    The texts for the brake control values are incorrect:

    • 1 - Force Apply - should be 1 - Force Release
    • 2 - Force Release - should be 2 - Force Apply

    Solution:

    Texts have been fixed to match the correct values as per the FW implementation.

    ^ Back to Top ^

    Version 2.13.0.9149 : June 26, 2023

    Requirements

    Required Components

    • .NET Framework 4.8
    • Visual C++ Redistributable 2010 SP1 (x86)
    • Visual C++ Redistributable 2013 (x86)
    • Visual C++ Redistributable 2015 SP3 (x86)
    • Internet Explorer 10

    Supported Operating Systems

    • Windows 7
    • Windows 8
    • Windows 10
    • Windows 11

    General

  • Axis Feedback View Crash
  • Issue:

    When using a localized version of the UI, hovering the Electronic Gearing selection in the Axis Feedback View will cause a crash.

    Solution:

    Improper localization fixed, it will now work properly for all languages.

  • Defect MW Lookup Tables Not Visible with Underscores [D-09522]
  • Issue:

    MW Lookup Tables loaded into the project that contained underscores in the names of the keywords would not load.

    Solution:

    Tables should now load even with underscores in their names. Keywords must still contain a dot ('.') somewhere in the name to load successfully.

  • Description Not Read Properly Form the Device for Negative Values
  • Issue:

    For some device values, the device parameter help will give a description attached to each value. If the value is negative, the description would not be displayed properly, and infer with matching positive values.

    Solution:

    Problem is fixed, negative values are now fully supported with attached descriptions (enum).

    ^ Back to Top ^

    Version 2.12.1.8943 : April 25, 2023

    Requirements

    Required Components

    • .NET Framework 4.8
    • Visual C++ Redistributable 2010 SP1 (x86)
    • Visual C++ Redistributable 2013 (x86)
    • Visual C++ Redistributable 2015 SP3 (x86)
    • Internet Explorer 10

    Supported Operating Systems

    • Windows 7
    • Windows 8
    • Windows 10
    • Windows 11

    Action Table

  • Step Labels and Divider Lines [S-24101]
  • Details:

    On the expanded Action Item view, we have numerically labeled and divided the steps. This will make creating or editing actions less confusing for beginners.

  • Task Parameter Bitmask Editor [S-24083]
  • Details:

    Added support for new action task:

    • 31 - Set user variable bits, Continuous

    ^ Back to Top ^

    Communication

  • Connecting to a Device with Retries [Req#55197] [D-09439]
  • Issue:

    The connect button does not wait until drive is reconnected after reboot.

    Solution:

    WB will keep trying to connect until the drive comes online or until it times out.

    ^ Back to Top ^

    Fieldbus

  • Deleting AKD-C or MKD-C from WorkBench project does not switch to project view [Req#TP#54537] [D-09406]
  • Issue:

    When a drive is deleted from a project, the application automatically switches to the Project view. When a power supply (AKD-C or MKD-C) is deleted, the application stays in the Device view of the no longer existing device instead. There is no node selected in the navigation tree.

    Solution:

    The correct view (Project view) is displayed when a power supply device is deleted.

    ^ Back to Top ^

    Functional Safety

  • Acceleration User Unit Typo for Arcminute
  • Issue:

    Acceleration user unit for Arcminute is wrongly given as a velocity and not an acceleration: Arcminute/s. The problem is only around the displayed string, the calculations are correct.

    Solution:

    The displayed string has been fixed to be an acceleration: Arcminute/s^2. Fixed for SMM 2.x, remains as is for SMM 1.x

  • WorkBench Locked Up when Drive was Power Cycled [Req#55515] [D-09350]
  • Issue:

    When on the Safety Parameters screen in the Safety Group View, when you power cycled a drive that was in that group, it would cause the navigation to be locked up, preventing the user from doing anything.

    Solution:

    Properly handle a disconnecting drive so that it doesn't lock up like that.

    ^ Back to Top ^

    General

  • Cogging Compensation Crash [D-09510]
  • Issue:

    When a minimum range value entered is greater than the maximum range value a crash will occur.

    Solution:

    Prevent crash by sorting the data series. Firmware update in the future will prevent a bad input completely.

  • Cogging Compensation Reload on Teach Move [S-24211]
  • Issue:

    The cogging compensation view lookup table was not reloading when a teach move occurred while outside of the view (ie, if triggered in the terminal).

    Solution:

    Now the cogging compensation view lookup table is reloaded anytime the data is changed, inside or outside of the view.

  • Connecting Issue with Drive with Bad Keyword Block [Req#53868] [D-09352]
  • Issue:

    WorkBench would not connect to a drive that has an activated MechaWare model that contains a bad keyword block with invalid keyword content.

    Solution:

    Updated code that creates the keyword content to properly handle the bad keyword block and set the content to invalid safely.

  • Crash When Adding a Watch Item While Connecting to a Device [D-09309]
  • Issue:

    When adding a watch item while connecting to a physical device or during the launch of a simulated device, the application will crash. It could be recovered by clicking Continue.

    Solution:

    The crash is fixed, the application will prevent the user to select a keyword until the application is fully ready, meaning the initialization is complete.

  • Help Link Indexes Incorrect for Fault Actions [D-09459]
  • Issue:

    Help links being created in WorkBench were incorrect for various Fault Actions keywords.

    Solution:

    Help link creation in WorkBench was updated to fix all Fault Action issues. Along the way, other issues were discovered with help links for safe parameters, some current loop keywords, X1/X2 modes, and more, which have also all been fixed.

  • Missing Horizontal Scrollbar in Faults View [Req#TP#64704] [D-09504]
  • Issue:

    Missing Horizontal Scrollbar in Faults View's History tab.

    Solution:

    Adjusted column definitions to fix overlapping vertical scrollbar and horizontal scrollbar.

  • Position Loop Broken View Layout [D-09435]
  • Issue:

    When using a German user interface, the view layout is broken. Some of the fields are cut and their content is invisible.

    Solution:

    The layout is fixed to self adapt better to the different languages and text lengths.

  • WorkBench Hangs After FW Update During Reboot [Req#63454] [D-09479]
  • Issue:

    WorkBench would get stuck while updating the Firmware of an AKD2G and the user would have to manually close WorkBench and reopen it.

    Solution:

    Fixed code so that it no longer will get stuck there.

  • Warning Popup on Save to Device [S-24219]
  • Issue:

    Users were accidentally overwriting their non-volatile parameters when using the Save to Device buttons.

    Solution:

    A new user option has been added to show a warning before non-volatile parameters are saved so users have the opportunity to cancel if they do not want to overwrite those parameters.

    ^ Back to Top ^

    Motion

  • Service Motion Mode Selector [Req#39540] [D-09367]
  • Issue:

    Required multiple attempts to switch the Service Motion Mode.

    Solution:

    Updated code to properly utilize events to allow switching of Service Motion Mode.

    ^ Back to Top ^

    Motor & Power Stage

  • Added 3 parameters for IPM motors [S-24022]
  • Issue:

    As an IPM User, I want to have all the relevant parameters displayed properly, so I can configure my IPM motor easily.

    Solution:

    Added the 3 missing parameters on the view. Updated behavior to display them properly.

  • Supported Parameters [S-24036]
  • Issue:

    New parameters added to Motor view missing from the corresponding Custom Motor View.

    Solution:

    Max Current (direct) and Phase Advance Gain 1/2 now supported in the Custom Motor view.

    ^ Back to Top ^

    Version 2.12.0.8547 : December 19, 2022

    Requirements

    Required Components

    • .NET Framework 4.8
    • Visual C++ Redistributable 2010 SP1 (x86)
    • Visual C++ Redistributable 2013 (x86)
    • Visual C++ Redistributable 2015 SP3 (x86)
    • Internet Explorer 10

    Supported Operating Systems

    • Windows 7
    • Windows 8
    • Windows 10
    • Windows 11

    Action Table

  • Action Task 29 and 30 Support [S-23694]
  • Details:

    Added support for these 2 new action tasks:

    • 29: Motion task select bit
    • 30: Motion task start selected
    Also added the support for the new configuration conflict related to these new action tasks.

    ^ Back to Top ^

    Communication

  • Application crashes when connecting a second AKD2G device using EoE [Req#TP#60113] [D-09342]
  • Issue:

    When connecting to several devices in one project through EoE,, the first device is connected successfully but subsequent devices fail to connect. The lowered network performance that can be caused by EoE is causing connect handshakes to occur out of order preventing the application from connecting. This could occur in other low performance network scenarios.

    Solution:

    The application is updated to handle the multiple handshake sequences in a more robust way.

    ^ Back to Top ^

    Feedback

    ^ Back to Top ^

    Fieldbus

  • ESI File Format Not Matching ETG Standard
  • Issue:

    ESI file should not have an EOL at the end of the file.

    Solution:

    File format fixed, no EOL at the end of the file.

  • Profinet Scaling - Reference Current Is Not Showing the Correct Value [Req#60016] [D-09341]
  • Issue:

    The referenced keyword is not correct, it is showing Axix Peak Current.

    Solution:

    The referenced keyword is now correct, showing AXIS#.PROFINET.REFCURRENT as the reference current.

  • Unable To Connect to Device with Bad Modbus List [Req#60954] [D-09351]
  • Issue:

    When downloading and activating a MechaWare file that creates some duplicate entries in the modbus list, WorkBench would not properly connect.

    Solution:

    Fixed WorkBench such that it is now able to connect properly, even when there are duplicates.

    ^ Back to Top ^

    Functional Safety

  • New Default Values for SMM 2.x Parameter Set [S-23749]
  • Issue:

    The existing parameter set is configuring the SMM for dual STOs on each axis. In most of the cases, this is not what the user wants and he will have to clean the default configuration before to enter the desired configuration for the safety system.

    Solution:

    The new default values provide a clean default configuration, without anything pre-configured.

  • Safety Parameters 2.x Ranges Changes [D-09343]
  • Issue:

    For the Safety Parameters 2.x, we updated the following ranges:

    • SafeID: max value is now 99 instead of 255.
    • SOS / t_D_SOS: min value is now 0 instead of 1.

    Solution:

  • SMM FW Version Updates Properly [Req#53920] [S-23688]
  • Issue:

    When downgrading the SMM FW from SMM version 3 to SMM version 2, the safety parameters in WorkBench did not reflect the ones in the drive.

    Solution:

    Reboot drive when changing major SMM versions and reset parameters to correct set.

  • Safety - Display Configuration Errors [S-23732]
  • Details:

    When the drive is in safe state 3 or 4, we now show the user some more information coming from the SAFE.CFGERROR keyword in the safety status popup.

    ^ Back to Top ^

    General

  • Add Support for New Keywords [S-23635]
  • Issue:

    WorkBench was not adapting across FW versions for EEO/X#.MODE availability, causing issues in the Hardware Configuration and Encoder Emulation Views

    Solution:

    Added support so WorkBench properly reflects the current feature set of the drive

  • Indicate Blocked Commands in Metadata [S-23873]
  • Issue:

    WorkBench users had no easy way of knowing the reason for a command being blocked. Users had to manually read DRV.BLOCKEDCMDS info to understand the problem.

    Solution:

    Blocked command information is now displayed in the metadata for the associated keyword. When a keyword is blocked, the user can simply open the metadata tag to read the reason.

  • Updated Model Number for Focused Drive
  • Issue:

    Model number change.

    Solution:

    The application has been updated to use the latest product number defined.

  • Configuration Conflict Not Indicated Properly for FB1 and FB2 [Req#54678] [D-09365]
  • Issue:

    When X1 and X2 are not configured for feedback usage, we do get configuration conflicts in the list accessible through the status bar. However, on the FB1 and FB2 feedback selection editor, we do get the configuration conflict indicator but not the explanation.

    Solution:

    Fixed a logic error not recognizing the correct keyword, issue fixed.

  • Firmware Update Failing With Big Files
  • Issue:

    When using a firmware file size bigger than 23MB and doing a factory download (all images), the update procedure will crash with an exception.

    Solution:

    Fixed the code to support larger file sizes.

  • Hardware Configuration View Crash With Incoherent Hardware Information [Req#62264] [D-09396]
  • Issue:

    When for some reason the provided hardware information from the device (HW.INFO) is incoherent with other keywords, the view will crash.

    Solution:

    If we cannot get proper hardware information from the device, we will default to a more generic link and description that still allows the hardware configuration view to work properly.

  • Parameter editor 'reset to default' button enabled when editor is disabled. [D-09255]
  • Issue:

    When the parameter editor is disabled by the application, the 'reset to default' is enabled allowing the value to be changed.

    Solution:

    The 'reset to default' button is now disabled when the parameter editor is disabled.

  • Scope Defect - WorkBench crashes when refreshing scope data. [D-09372]
  • Issue:

    When using the Scope, a crash would occur if the user did a recording, disconnected, reconnected, and refreshed. Also, there was another bug around refreshing recorder channels for array keywords and registered variables, which could become duplicated.

    Solution:

    The crash no longer occurs after disconnecting, reconnecting, and refreshing. Also, the recorder channels now behave correctly when refreshing array keywords or registered variables.

  • EEO Support for New Keywords [S-23642]
  • Details:

    Encoder Emulation View diagrams have been updated to support the recently added EEO#.PIN, EEO#.POUT, EEO#.STATUS, and EEO#.FAULTAXIS keywords. The PIN/POUT keywords are now visible and editable through a new scaling node. The STATUS is now visible through four new LEDs. And the FAULTAXIS value can be edited through a new node/dialog connected to the Faulted status LED.

    ^ Back to Top ^

    Monitoring

  • Saving scope settings with a channel configured with an array type does not save or restore. [Req#TP#58389] [D-09349]
  • Issue:

    When saving Scope setting with a channel configured with an array keyword, the channel cannot be saved.

    Solution:

    Fixed the save routine to support channels configured with array keywords.

    ^ Back to Top ^

    Motion

  • Jog Buttons Not Updated Properly When Changing Op Mode [D-09270]
  • Issue:

    When all conditions are met to allow jog moves, switching the Op Mode will not refresh the buttons state - they will remain as they are. Normally, going from Torque to some other Op Mode and back, should enable/disable the buttons.

    Solution:

    Fixed, the view was not always refreshed when the Op Mode is changing.

  • Motion tasks not being updated when space in unit label text input field. [Req#TP#45806] [D-09353]
  • Issue:

    When the unit label parameter has a space character in it, Motion Tasks cannot be written to the drive.

    Solution:

    The Motion Task parsing is updated to handle space characters.

    ^ Back to Top ^

    Motor & Power Stage

  • Power View Crash When Running Inside a Portuguese Windows OS [Req#11199] [D-09384]
  • Issue:

    When running a Portuguese version of the application within a Portuguese Windows OS version, the Power View will crash upon its opening.

    Solution:

    It was a translation issue that has been solved. We also put in place some translation rules that should avoid a similar problem to occur again in the future.

    ^ Back to Top ^

    Simulation

  • Simulation Not Possible on Customized Models
  • Issue:

    When your device has a customized model number (last 4 digits different from 0000), the simulation won't be available once disconnected.

    Solution:

    Problem fixed, the simulation availability is now computed properly.

    ^ Back to Top ^

    Version 2.11.0.8192 : August 22, 2022

    Requirements

    Required Components

    • .NET Framework 4.8
    • Visual C++ Redistributable 2010 SP1 (x86)
    • Visual C++ Redistributable 2013 (x86)
    • Visual C++ Redistributable 2015 SP3 (x86)
    • Internet Explorer 10

    Supported Operating Systems

    • Windows 7
    • Windows 8
    • Windows 10
    • Windows 11

    Action Table

  • Action Error Support and Run Count [S-23507]
  • Details:

    Added support in WorkBench for action errors. When an error occurs, displays date and time when it occurred along with an error message describing the error. Also added a column for displaying the action run count when available.

  • Action Source and Condition Enumerated Values Updated [S-23453]
  • Issue:

    The Action Source 10 was wrongly named (Move Complete), creating some confusion for the end-users.

    Solution:

    The Source 10 has been renamed 'MT Not Running' instead of 'Move Complete', reflecting better the internal behavior. Some other missing enum values have beend added.

    ^ Back to Top ^

    Analog & Digital IO

  • Support for missing DOUT DIO modes. [S-22839]
  • Issue:

    Mode 26 and 27 were missing from the DOUT/DIO view, and Mode 23 was behaving improperly.

    Solution:

    The missing DOUT Mode 27 (Warning Number) has been added and the missing DIO Mode 26 (PWM Output) has been added with custom Duty Cycle and Period parameters. The broken read/write state for DIO Mode 23 (Compare Output) has been fixed.

    ^ Back to Top ^

    Communication

  • Disconnected View Connect Button Fails to Connect to Drive [Req#45341] [D-09151]
  • Issue:

    Was not able to connect to a drive that was not discoverable by manually entering the IP address.

    Solution:

    Updated code to still attempt to connect to manual IP address, even if it is not discovered. Made connect code consistent across WorkBench buttons.

    ^ Back to Top ^

    Feedback

    ^ Back to Top ^

    Fieldbus

  • EthernetIP and PROFINET wrong naming [Req#43376] [D-09208]
  • Issue:

    2G devices will support all features for 1 fieldbus within 1 model definition, there will be no separate models for the same fieldbus. The features supported will depend from the version of the devices's firmware. The current naming is confusing, indicating some features that are not yet available.

    Solution:

    For 2G devices, the naming of the fieldbus is now generic, not specifying the feature supported for the specific fieldbus.

  • Fieldbus - EtherNetIP and PROFINET - Allow user configurable sorting for mappable items. [S-22941]
  • Issue:

    In the EtherNetIP and PROFINET mapping dialogs it is difficult to find the item (object / telegram) you want to map because the sorting is limited to one column and not configurable.

    Solution:

    For EtherNetIP the mappable objects in the mapping configuration dialog can now be sorted by parameter name or id in ascending or descending order. For PROFINET the mappable telegrams in the mapping configuration dialog can now be sorted by signal name or id in ascending or descending order.

    ^ Back to Top ^

    Functional Safety

  • SAFEGRID Editable State Not Updated When Privilege Level Changed
  • Issue:

    SAFEGRID remains in an editable state after changing the privilege level of the safety project. Editing a parameter will have no effect and a SAFEGRID error message popup is displayed.

    Solution:

    Changing the privilege level of the safety project now forces a refresh of SAFEGRID, showing it in the expected state for the configured privilege level.

  • Safety - Plausibility check for velocity and or deceleration monitoring in SS1, SS2, SOS, SLS, SSR. [S-23456]
  • Details:

    With advanced safety functions and velocity / deceleration monitoring enabled for the functions SS1, SS2, SOS, SLS or SSR, the monitored threshold parameter, e.g. deceleration limit, must be greater than zero. Otherwise, the device will not accept the parameters. A plausibility check is added to prevent that condition.

  • Safety Setup Wizard [S-23236]
  • Details:

    Created new Safety Setup Wizard for initializing Safety. The wizard automatically pops up when a safety-capable device is added to the project and guides the user through configuring Safe Functions, creating/entering a password, and adding the device to a Safety Group. The wizard can be manually opened from a button on the Overview View. An option for disabling the automatic wizard pop-up has been added to the Options window.

  • Simulated Device Creation Supports Safety Firmware Version Configuration [S-23092]
  • Details:

    When creating a new simulated device, the user can configure the safety firmware version to match the expected physical device. It will allow the user to get the proper safety parameter set.

  • Support for Safety 2.x Parameter Set Added [S-23093]
  • Details:

    Parameter set changes for safety 2.x version (according to Data Dictionary v3.0).

  • Support for safety parameter device definition upgrade inside project after SMM firmware update. [S-23403]
  • Details:

    After updating SMM firmware the safety parameters inside the application project file can become incompatible. This change prompt the user and upgrade the parameter device definition if necessary.

  • Support Multiple Safe Description Versions [S-23279]
  • Details:

    The user interface will adapt the used structure of safety parameter based on the device model and the safety firmware version. It will allow to evolve the product, still allowing to work with older versions.

  • SMM Version Format Change [S-23089]
  • Issue:

    The SMM Version scheme changed and the version display format needed to be updated accordingly.

    Solution:

    The SMM Version now displays the full new format including the firmware type, and also major, minor, and revision versions.

  • Upload Safety Parameters from SafeMotion Monitor [S-23359]
  • Issue:

    The button stays enabled when FSoE parameterization is used. As there is no parameter file per say, the upload will fail.

    Solution:

    The button will only be enabled when uploading the safety parameters is possible, disabled otherwise.

    ^ Back to Top ^

    General

  • Add Cursors to Graph [S-22827]
  • Issue:

    Old graphing components did not use new library.

    Solution:

    Updated graphical components to use new SciChart library, added support to display a cursor when valid.

  • Blocked Command Support [S-23404]
  • Issue:

    Users want to have information on why a command is blocked.

    Solution:

    Added informative text and an info icon to blocked commands (buttons) so users can easily see why the command is blocked.

  • Cogging Compensation Finalization - Move Range and Improve Warnings [S-22945]
  • Issue:

    The range editors being above the modulo editors was confusing, because the range editors depended on the modulo editors to be enabled. Also, the motion command warnings were not specific.

    Solution:

    The range editors are moved below the modulo editors for coherence, and the motion command warnings have been updated to include relevant information like start position, end position, and velocity.

  • Cogging Compensation Finalization - Progress Indication and Abort Capability [S-23036]
  • Issue:

    Running the cogging compensation move can take a long time so we need a way to display the current progress and have the ability to abort the move.

    Solution:

    Added a progress bar and position feedback editor to the view. Added an abort button to the adorner.

  • Console Proper Behavior When Connection Is Lost [S-23502]
  • Issue:

    The console was not detecting properly a connection lost, hanging up forever, particularly in the bode measurement process.

    Solution:

    The console is now detecting connection lost and exiting gracefully returning an error message.

  • Lookup Table Editor Visibility when Focus is Lost [S-22869]
  • Issue:

    When analyzing data in the lookup table, having an editor open makes it harder to look at and understand.

    Solution:

    Clicking outside the table will make the editor lose focus and therefore disappear.

  • Spartan 7 - Proper Firmware File Filters for Different Models [S-23189]
  • Issue:

    We no longer want the general multi option card filter for all models, only special models.

    Solution:

    Removed general multi option card filter for all models. Added specific multi-model file filters for AKD-N-DxEC, AKD-N-ExEC, MKD-C-xAEC, MKD-C-xDEC.

  • Added Support for Focused Drives
  • Details:

    Added support for focused drive models with two different size fpgas (SP750 & SP725)

  • Capture - Support New Arming Mode - Continuous Auto-Arm [S-23028]
  • Details:

    Full UI support for this new arming mode.

  • Numerical Memory Editor [S-23376]
  • Details:

    Implemented a numerical text editor that allows a user to edit a numerical value that has the range and units from a related keyword.

  • Single Choice Memory Editor [S-23377]
  • Details:

    Implemented the single choice facade for memory editors, so WorkBench can support memory multi-choices editors linked with keyword values on a view.

  • Support for New Device Model
  • Details:

    Adaptation of the user interface to support the non existence of some features. This new device has less features, more focused on customer needs.

  • Update Config Conflicts to Reflect FW Changes [S-23347]
  • Details:

    Added config conflict support for AXIS#.HWEN.SOURCE, AXIS#.HOME.SWITCHSOURCE, AXIS#.HWLS.NEGSOURCE, and AXIS#.HWLS.POSSOURCE.

    Issue:

    In the Current Loop View, for only AKD1G, there was a permanently broken link to the Cogging Compensation View.

    Solution:

    The link has been fixed and now properly navigates to the AKD1G Cogging Compensation View.

  • Command Source Widget Not Displayed Properly [D-09158]
  • Issue:

    When the UI is integrated in our EtherCAT controller, the command source multi choice widget is dispalying a fixed string instead of the actual value of the command source.

    Solution:

    Fixed, the actual value of the command source is displayed in all the cases.

  • Crash after changing settings in the Setup Wizard and changing the same in main WorkBench window. [D-09218]
  • Issue:

    If the Setup Wizard is run and some parameter values are changed, changing those same values in the main window after dismissing the Wizard will crash WorkBench.

    Solution:

    Properly disposed resources in the Setup Wizard to eliminate the crash scenario.

  • Crash when adding a Watch Item to the new Watch Panel in Windows 7. [Req#TP#58845] [D-09295]
  • Issue:

    Upon adding a Item to the new Watch Panel on Windows 7, the application will crash. This issue is rooted in the keyword picker control and causes problems loading the Scope view and using the Actions view with Recordable Parameters. A visual library used by that control is not supported on Windows 7.

    Solution:

    The keyword picker (used by Watch Panel and other features) is updated to use a visual library that is supported on Windows 7 and greater operating systems.

  • ND models not supported properly
  • Issue:

    The ND models are not recognized properly for firmware update.

    Solution:

    Problem fixed, ND models will be fully recognized and firmware update possible.

  • New Text Editor going in editing mode when copying [D-09087]
  • Issue:

    When copying text from the text editor, the editor would be put into an "edited" state even though no change on the actual value had been done.

    Solution:

    Copying text from the text editor no longer puts it into an "edited" state.

  • Scope Defect - Importing Larger Files [D-09186]
  • Issue:

    In the Scope, there was an crash when importing a CSV which had a greater number of points than the existing dataset while a filter was active.

    Solution:

    Importing a CSV with a greater number of points than the currently existing dataset no longer causes a crash.

  • Scope Defect - Importing Unknown Signals [D-09186]
  • Issue:

    In the Scope, there was an issue when importing a CSV which included signals that were not unknown by the current device. These signals would not be loaded into the channels, and the user would need to manually enter a signal in order to use the channel controls.

    Solution:

    Now, unknown signals are loaded into the channels and shown in error so the user is aware that these signals are not recognized. The filter controls remain enabled so the user does not need to take any further action to manipulate these unknown signals.

  • Setup Wizard Button Remains Disabled [D-09157]
  • Issue:

    When the UI is integrated in our EtherCAT controller, the setup wizard is not enabled properly when it should (online configuration mode).

    Solution:

    Problem fixed, the setup wizard will be enabled when it should.

  • The application crashes with an OutOfMemory exception when downloading firmware. [Req#TP#39562] [S-22993]
  • Issue:

    After using the application for a long time, visiting many views and reconnecting many times, the application could crash, typically when a firmware download is initiated.

    Solution:

    Many memory leaks were fixed in the application.

  • Trigger Type Not Properly Getting Updated [Req#54372] [D-09247]
  • Issue:

    When changing the trigger source in the scope, the trigger type in the more section was not updating to reflect the source.

    Solution:

    Fixed the combo editor to update properly and display the proper trigger type.

  • Underscore Visibility in Watch Panel Signal Picker [D-09066]
  • Issue:

    The first underscore was not being displayed in the watch panel signal picker.

    Solution:

    Updated WorkBench to now properly display the underscore.

  • Watch crashing when adding invalid string [D-09107]
  • Issue:

    Workbench was crashing when adding certain invalid strings (register keywords) to the watch panel text editor.

    Solution:

    Workbench no longer crashes when register keywords are displayed in text editors, and the unsupported register keywords have been removed from the watch panel.

    ^ Back to Top ^

    Monitoring

  • Scope export to Excel failing after multiple attempts. [Req#TP41033] [D-09086]
  • Issue:

    The Excel button in the Scope Save and Print tab fails to open excel after the first time. The file was deleted before Excel could open it.

    Solution:

    The CSV file is kept until the following instance of the process when the Scope view is visited.

  • Scope Signal Export and Import Fixes [Req#39542] [D-09119]
  • Issue:

    The scope has currently different problems around export/import:

    • The exported trace data will be filtered if the filter is selected
    • When imported, the channels are not updated properly (signal, filter activation, filter frequency)
    • When refreshed from drive, the channels are not updated properly (signal)
    • After import or refresh, the filter activation is not working

    Solution:

    The problems have been fixed as follow:

    • The exported trace data are unfiltered (raw recording)
    • When imported, the channels are updated properly (signal, filter activation, filter frequency)
    • When refreshed from drive, the channels are updated properly (signal, filter information are set back to defaults)
    • After import or refresh, the filter activation is working

    ^ Back to Top ^

    Motion

  • Display Command Prefilter Block in position loop diagram [S-22867]
  • Details:

    Added the prefilter block to the position loop diagram allowing the user to interact with the block and the command prefilter tab.

    ^ Back to Top ^

    Simulation

  • PWD protection not working in AKD1G offline simulation. [D-09185]
  • Issue:

    AKD1G offline simulations were not behaving properly around PWD protection. PWD protected keywords were being displayed regardless of the user privilege status.

    Solution:

    AKD1G offline simulations are now handling PWD protected keywords appropriately.

    ^ Back to Top ^

    Tuning

  • Autotuner lockup WorkBench when in Gantry mode [Req#55331] [D-08925]
  • Issue:

    When the axis 2 command source was set to gantry, trying to run an autotune would cause WorkBench to get into an unrecoverable state.

    Solution:

    We now prevent the user from running an autotune or bode from the slave gantry axis. Autotune is also disabled for the master axis because we do not have an algorithm to support that yet, but you can run bode plots still.

  • Cogging Compensation Hanging up During Teach Move
  • Issue:

    Running a teach move in some conditions will hang up the user interface, the user would have to kill the application using the OS.

    Solution:

    Teach move is not hanging up anymore in the same conditions.

  • Frequency Responses Incorrectly Generated and CSV Incomplete [D-09221]
  • Issue:

    The frequency responses were generated improperly for op modes different from position. The CSV file content was incomplete and improper to be read by older applications.

    Solution:

    The frequency responses computation has been fixed to take in account the op mode. CSV files are now compatible with older applications.

  • Bode Measurement Available in the Console
  • Details:

    The bode measurement tool is available from the console. It can be launched using a command line or a script passing all the parameters necessary to the measurement, generating a CSV file with the results.

    ^ Back to Top ^

    Version 2.10.0.7363 : December 08, 2021

    Requirements

    Required Components

    • .NET Framework 4.8
    • Visual C++ Redistributable 2010 SP1 (x86)
    • Visual C++ Redistributable 2013 (x86)
    • Visual C++ Redistributable 2015 SP3 (x86)
    • Internet Explorer 10

    Supported Operating Systems

    • Windows 7
    • Windows 8
    • Windows 10

    Action Table

  • Action Table Recordable Parameter Keyword Picker supports Array Keywords [S-22752]
  • Issue:

    In the Actions View, a Recordable Parameter action that triggers on an array keyword value at a specific index could not be created.

    Solution:

    Now, when an applicable array keyword is selected, an array index can be chosen by typing it into the keyword picker or by selecting it via the combo box which allows to trigger an Action based on the value of a keyword at a specific index.

  • Task Command Buffer - Autocomplete not Working Properly [Req#39702] [D-08963]
  • Issue:

    The autocomplete is not allowing array Action Commands (eg AXIS#.MT.MOVE) - they won't appear in the list even that they are fully supported.

    Solution:

    Fixed - all writable array items, including Action Command, are now supported.

    ^ Back to Top ^

    Analog & Digital IO

  • Analog Motion view crashes when AXIS#.IL.AINSOURCE set to 0 - None. [D-08978]
  • Issue:

    When the Analog Motion view is shown, setting AXIS#.IL/VL/PLSOURCE to 0, None, will cause WorkBench to crash. If AXIS#.IL/VL/PLSOURCE is already set to 0, the Analog Motion view will not show when navigated to.

    Solution:

    The Analog Motion view is fixed to support AXIS#.IL/VL/PLSOURCE with the value 0.

    ^ Back to Top ^

    Communication

  • Usability - Fieldbus - Adding EIP Units [S-22840]
  • Issue:

    For 2G, no units were displayed for the drive value column in the EIP Mapping Tables.

    Solution:

    A new "Units" column displays the units for the drive value, when the value has units. Otherwise, nothing is shown in the units column. 1G units have been updated to match the new 2G units.

    ^ Back to Top ^

    Feedback

    ^ Back to Top ^

    Fieldbus

  • Display EIP Object IDs in Decimal and Hexadecimal. [S-22607]
  • Details:

    EIP Object IDs are now displayed with both decimal and hexadecimal values, instead of just decimal.

  • EIP - Control and Status Word Support [S-22134]
  • Details:

    Added display support for Control and Status word bits.

  • EIP - Feedback Scaling [S-22135]
  • Details:

    Added support for fieldbus feedback scaling in the common area of the EIP views.

  • EtherNet IP Connection Tab Apply Button Enable or Disable [Req#42843] [D-09018]
  • Issue:

    On the EtherNet/IP Connection Tab, the apply button is not enabling/disabling properly when the axes are enabled/disabled.

    Solution:

    Updated the view such that the apply button now updates properly.

  • Modbus - Freeze when Searching in Mapping Configuration [Req#45098] [D-09048]
  • Issue:

    Typing quickly in the Search box when doing Modbus mapping will hang up the application (crash).

    Solution:

    Problem fixed, it will take some time to filter as the list is huge, but it will not crash.

  • Modbus - Message rate displayed improperly with non US locales [Req#43437] [D-09027]
  • Issue:

    When the user has non US locales configured, the Modbus message rate could be read/displayed improperly or eventually crash the application.

    Solution:

    Reading of the Modbus message rate has been fixed to support any locales.

  • Usability - Fieldbus - Adding EIP Units [S-22840]
  • Issue:

    For 2G, no units were displayed for the drive value column in the EIP Mapping Tables.

    Solution:

    A new "Units" column displays the units for the drive value, when the value has units. Otherwise, nothing is shown in the units column. 1G units have been updated to match the new 2G units.

  • Usability - Fieldbus EIP - Add motion tasks info [S-22848]
  • Issue:

    Motion Task information was unclear in the EIP view.

    Solution:

    For AKD1G, a Motion Tasks navigation link has been added to the EIP View motion tab. The motion tab was also updated for AKD2G, adding visibility for several new keywords. For AKD2G, an "In Motion" LED was also added to the EIP View status bar to show when the status word motion bit is set.

    ^ Back to Top ^

    Functional Safety

  • Add new plausibility check for SOUT source configuration [S-22951]
  • Issue:

    There was no warning if SOUT/SOUTDUAL sources were linked to an inactive function.

    Solution:

    Added a new plausibility check for all SOUTs/SOUTDUALs and all possible sources to verify they are not linked to an inactive function.

  • Fix Range for SBT.MAXMOTIONBRAKE [S-22574]
  • Issue:

    The maximum value for SBT.MAXMOTIONBRAKE range was incorrect.

    Solution:

    SBT.MAXMOTIONBRAKE maximum range value has been updated to the correct value of 10800.

  • Revert - Fix Range for SBT.MAXMOTIONBRAKE [S-22574]
  • Issue:

    Changing the range of a parameter in the safety description file is creating incompatibility between files. It is not acceptable for the end users, having an incorrect range is not a safety issue as it will be caught and reported by the SMM.

    Solution:

    SBT.MAXMOTIONBRAKE maximum range value has been reverted to the previous value of 4294967295 for compatibility reason.

  • SAFEGRID incorrect description [Req#42714] [D-09006]
  • Issue:

    The FSoE activation parameter has a wrong description for the value 0, it says Used but it should say Not Used. This is not a major issue as the description is not visible to the end user in SAFEGRID, the display name is visible and its value is correct.

    Solution:

    Fixed the incorrect description to match the value.

  • Safety Navigation Optimization [S-22371]
  • Issue:

    Navigation within SafeGrid was slow and produced a visual flicker.

    Solution:

    Removed redundant SafeGrid updates allowing SafeGrid to update more quickly and without visual flickering.

    ^ Back to Top ^

    General

  • Better Configuration Conflict Support - Explanation on the Editor [S-22812]
  • Details:

    Configuration conflict are signaled to the user with a yellow mark on the top right of the editor. The detailled display will now indicate what is the cause/source of the conflict.

  • Configuration Conflict Better Signaled on Editors [S-22911]
  • Details:

    The small yellow metedata indicator is not very visible for the user. We made that indicator blinking, that should catch the eye of the user more easily.

  • Configuration Conflict Better User Support [E-04000]
  • Details:

    Our 2nd gen drive has a feature indicating when some of the parameters are not properly configured, known as Configuration Conflict. The user interface has some added help to guide the user towards resolution of these problems:

    • Navigation link within WB to the source of the conflict
    • Icon in the status bar indicating if any conflict exist
    • Clicking on the icon will list all the current configuration problems, if any, providing navigation and help links

  • Keyword Picker Array Support [S-22541]
  • Details:

    Added array keyword support to the keyword picker (currently used in the scope) so that the user can select which index to associate with the selected array keyword.

  • Support for new models [S-22682]
  • Details:

    New models would be created in the future, added support in the user interface for when they will appear.

  • Compare Engine - New Comparator Mode [S-22777]
  • Issue:

    There was no support for the new comparator mode for compare engines.

    Solution:

    Added support for the new comparator mode for compare engines.

  • FPGA New Model Support [S-22600]
  • Issue:

    Did not have WorkBench support for new FPGA model.

    Solution:

    Add support for new FPGA model (NC) and new size (LX75)

  • New Watch Panel [E-03932]
  • Issue:

    The existing watch panel had many different problems.

    Solution:

    Implemented a new watch panel with the same functionalities. For now, the legacy watch panel is still accessible with a Right+Click on the Glasses icon.

  • Old Watch Panel Removed [S-22785]
  • Issue:

    The old watch panel had many problems.

    Solution:

    A new watch panel has been implemented to replace the old one. In this story we completely removed the old one, it is no longer accessible.

  • Unknown Model Support [S-22664]
  • Issue:

    When connected to an unknown model, expanding the device status diagram will cause a crash

    Solution:

    Added support for unknown models, and a message to the user.

  • Watch Panel Drag and Drop [S-22951]
  • Issue:

    Watch panel items not able to be reordered by user.

    Solution:

    Add drag and drop functionality to the watch panel, to allow user to reorder items.

  • Defect - Crash at Launch When No Printer Defined [D-08924]
  • Issue:

    WB would crash on launch trying to identify a default paper-size if no printer was defined or if the Windows printer spooler service was disabled.

    Solution:

    Now WB does not crash when no print service is identified. Instead, a default paper size is chosen.

  • Defect - Erasing keyword picker text is not setting empty [D-09009]
  • Issue:

    Erasing the text in the keyword picker does not reset and clear the selection.

    Solution:

    Now, erasing the keyword picker text removes the selection and allows the picker to be set to empty.

  • Disable and Clear Faults button randomly not updated [Req#42711] [D-09003]
  • Issue:

    In some rare occasions, the button will remain disabled even that it should be enabled allowing the user to clear the faults. It would force the user to disconnect/reconnect or use the terminal.

    Solution:

    The refresh of the button state has been fixed, it should be updated properly in all cases.

  • Scope Defect - Export CSV Column Names Too Long [D-08860]
  • Issue:

    When exporting data from the Scope to a CSV file, the parameter column names were very long and contained duplicate information, showing the parameter name and parameter description two times each.

    Solution:

    Now, exported data from the Scope does not contain redundant information, and shows the parameter name and parameter description only once each.

  • Scope Defect - Loss of data when importing and exporting. [D-08922]
  • Issue:

    When a scope file with over 1000 records was imported and then re-exported, the data was cutoff and everything after the first 1000 records was lost.

    Solution:

    WorkBench now updates the number of export records when importing a scope file, so re-exporting that data will preserve the entire data set.

  • Setting the brake usage while axis is enabled is hanging the application [Req#46206] [D-09067]
  • Issue:

    Setting the brake usage in the brake view while the axis is enabled disables navigation with no way to get it back.

    Solution:

    Check the error state of the combo editor to provide a way to get out of the blocked navigation state.

  • Setting the default settings in the scope for AKD2G [Req#42826] [D-09059]
  • Issue:

    When attempting to set the default settings for the scope for AKD2G, a warning would be shown and the settings would not be properly set back to default.

    Solution:

    Updated WorkBench to properly handle information coming from the drive so that the default settings can be set correctly.

  • Signal Picker Defect - Validation is not taking the proper keyword when typing fast. [D-08997]
  • Issue:

    When typing fast in the signal picker (Scope channel selection, Watch Panel parameter selection, etc.) and pressing Enter the incorrect keyword is selected.

    Solution:

    In that scenario the correct keyword is now selected.

  • Slider Tuning Defect [D-08849]
  • Issue:

    When there is no motor attached to the drive, slider tuning view is crashing when changing the bandwidth.

    Solution:

    Protected against a divide by zero exception.

    ^ Back to Top ^

    Monitoring

  • Scope Channel Picker Array Index Out of Sync [D-08976]
  • Issue:

    In some cases the array index displayed in the channel picker is not reflecting the array index configured for the channel. The array index will appear to swap back and forth between two indices.

    Solution:

    The array index displayed in the picker is always synchronized with the channel configuration.

    ^ Back to Top ^

    Motion

  • Analog Motion view crashes when AXIS#.IL.AINSOURCE set to 0 - None. [D-08978]
  • Issue:

    When the Analog Motion view is shown, setting AXIS#.IL/VL/PLSOURCE to 0, None, will cause WorkBench to crash. If AXIS#.IL/VL/PLSOURCE is already set to 0, the Analog Motion view will not show when navigated to.

    Solution:

    The Analog Motion view is fixed to support AXIS#.IL/VL/PLSOURCE with the value 0.

  • Brake View Content Inconsistent
  • Issue:

    Changing the brake configuration (with/without brake) is not always updating the content of the view properly. It may display the content when no brake is present and no content with a brake present.

    Solution:

    Behavior fixed, it will display the content accordingly to the brake presence.

  • Motion Tasks - support within Scope [Req#39522] [S-22589]
  • Issue:

    The UI does not support start/stop of motion tasks from within the scope, forcing the user to switch between views.

    Solution:

    Motion tasks can now be started and stopped from within the scope view, reducing view switching. The configurations has to be done in the Motion Tasks view.

    ^ Back to Top ^

    Project Management

  • Project File Without Watch Items Will not Load [Req#47035] [D-09090]
  • Issue:

    If a project file is saved without any watch items, it could be impossible to load the file for some versions of the application (hang up when opening the project file).

    Solution:

    The application will open project files in all cases.

    ^ Back to Top ^

    Simulation

  • Simulation takes a very long time to start [D-09020]
  • Issue:

    When launching a simulation, it takes a while with a frozen user interface until the views finally appear. It is even worse when the simulation is launched on an existing device from the Disconnected View, it could take up to more than a minute to get everything initialized.

    Solution:

    • User feedback has been added while creating the simulated device (label in the application status bar, label and progress bar in the Disconnected View). Additionally, when restarting an existing device in simulation mode, a special view will appear during the initialization.
    • The creation time and initialization time have also been greatly improved for simulated FW >= 02-07-00-004.

    ^ Back to Top ^

    Tuning

  • Better Integrators Support - Misc Tuning Parameters Added [S-22440]
  • Details:

    Added support in the user interface to configure the interaction between velocity and position loop integrators. Also added some missing parameters to the views (command prefiltering, acceleration feed forward).

  • Cogging Compensation [E-03999]
  • Details:

    Cogging compensation table available with a teach algorithm that would determine the table for the connected motor. Custom table could also be imported directly.

  • Performance Servo Tuner - Importing from CSV [S-22890]
  • Issue:

    The measurement data are currently not loaded when importing a CSV file. This data could be missing for some computation or when you want to redo a measurement whith the same conditions.

    Solution:

    Loading a CSV will now reload all the measurement data. For the values that have units, if they do not match with the current units in the drive, the application will calculate the most suitable value.

  • Slider Tuning Defect [D-08849]
  • Issue:

    When there is no motor attached to the drive, slider tuning view is crashing when changing the bandwidth.

    Solution:

    Protected against a divide by zero exception.

  • Warning occurs after doing a low-pass filter tune using the bode tool [Req#42128] [D-09060]
  • Issue:

    A warning appears in the AR filter tab in the scope view saying the Q value(s) don't match the filter type every time you do a low-pass filter tune using the bode tool.

    Solution:

    Updated value comparisons to allow a tolerance against the default values.

    ^ Back to Top ^

    Version 2.9.0.6662 : June 09, 2021

    Requirements

    Required Components

    • .NET Framework 4.8
    • Visual C++ Redistributable 2010 SP1 (x86)
    • Visual C++ Redistributable 2013 (x86)
    • Visual C++ Redistributable 2015 SP3 (x86)
    • Internet Explorer 10

    Supported Operating Systems

    • Windows 7
    • Windows 8
    • Windows 10

    Communication

  • PROFINET - Service port view is not showing the proper IP details [D-08850]
  • Issue:

    When connected to a 2nd Gen PROFINET device, the TCP/IP view is reporting incorrectly the IP details from the PROFINET connection, not from the service port connection.

    Solution:

    Problem fixed, the TCP/IP view is now reporting the correct IP details on all device types.

    ^ Back to Top ^

    Feedback

    ^ Back to Top ^

    Fieldbus

  • EIP Mapping Configuration [S-22505]
  • Details:

    Added support to allow the user to easily configure the dynamic mapping on AKD2G and AKD1G.

    ^ Back to Top ^

    Functional Safety

  • Safety FW Update - Hex Info Message [S-22533]
  • Issue:

    The format of the FW checksum is not known to the user.

    Solution:

    Added a message to the user that the FW checksum value is expected in hex and needs to be prefixed by 0x.

    ^ Back to Top ^

    General

  • Compare Engine Support - Gen 2 Devices Support [E-03753]
  • Details:

    Added support for compare engine on 2G devices. The user interface supports 1st Gen and 2nd Gen devices.

  • Model Customization - Lookup Table - Graphical Representation [S-22437]
  • Details:

    Added a graphical representation of the lookup table (lookup values vs inputs).

  • Model Customization - Lookup Table - Variable Size [S-22386]
  • Details:

    The user can define the size of the lookup table he needs - not anymore fixed by the model definition.

  • CSV Load - Better error reporting when unable to import data [D-08859]
  • Issue:

    When for some reason a CSV fails to load, the user interface just reports a generic failure, not helping sufficiently the user to fix the offending file.

    Solution:

    The user interface will now report the first error encountered in the file with the offending text including its respective line and column within the loaded file.

  • Parameter Compare Crash [D-08862]
  • Issue:

    Using the Parameter Compare tool with a parameter file as source or target is crashing.

    Solution:

    Problem fixed.

  • Model Customization - Lookup Table - Supports Optional Keywords [S-22385]
  • Issue:

    The lookup table is not displayed properly when the model does not have all the expected keywords defined.

    Solution:

    Some keywords (modulo, output value) are now supported as optional, if they are not defined in the model, the user interface will still display the lookup table properly.

  • Model Customization - Lookup Table - Writing Optimization [S-22435]
  • Issue:

    Writing large arrays to the device may take some significant time as values are written one by one with a lot of overhead.

    Solution:

    Arrays could now be written in chunks, diminishing the amount of communication and overhead for each value.

  • Single choice editor stuck in error [S-22391]
  • Issue:

    The single choice editors (combobox) remain stuck in error when the device is returning an error. The navigation in the user interface is blocked, in many cases the application has to be killed thorugh the Windows Task Manager to recover from that problem.

    Solution:

    The error can now be cleared by pressing the Esc key, the combobox will get out of the error, reloading the current value from the device. The error being recovered, the user can continue to use the user interface for further configuration.

    ^ Back to Top ^

    Motion

  • Error when stopping gantry motion from the scope [D-08871]
  • Issue:

    Pressing the Stop button in scope while running a gantry motion is throwing an error.

    Solution:

    Fixed, Stop will work properly in all modes (individual axes or gantry mode).

  • Gearing Auto Start Configuration [S-22438]
  • Details:

    Visualization and configuration support in the user interface for gear autostart (gearing starts automatically when the drive enables).

    ^ Back to Top ^

    Tuning

  • Gain Scheduling View Hangs [D-00874]
  • Issue:

    When the user changes a value within the gain scheduling view, the user interface will hang up, frozen, requiring the windows task manager to kill the application.

    Solution:

    The application has been fixed for that problem.

    ^ Back to Top ^

    Version 2.8.0.6323 : March 18, 2021

    Requirements

    Required Components

    • .NET Framework 4.8
    • Visual C++ Redistributable 2010 SP1 (x86)
    • Visual C++ Redistributable 2013 (x86)
    • Visual C++ Redistributable 2015 SP3 (x86)
    • Internet Explorer 10

    Supported Operating Systems

    • Windows 7
    • Windows 8
    • Windows 10

    Action Table

  • Action Source 26 - Recordable Parameter [S-21908]
  • Details:

    Added full support in the user interface for this source through a special editor that allows to pickup a device parameter easily.

    ^ Back to Top ^

    Analog & Digital IO

  • Digital IO - Polarity checkbox is not refreshed properly [D-08787]
  • Issue:

    The checkbox indicating the polarity (active high/low) is not refreshed properly, not matching the actual value in the drive.

    Solution:

    Problem fixed by having the refresh working properly.

    ^ Back to Top ^

    Fieldbus

  • PROFINET - Control Status bits highlighting [S-22118]
  • Details:

    When bits are hovered in the bitwise representation or in the detail representation, they are highlighted with a tooltip. The system will now also highlight the bit(s) in the other representation showing clearly the relationships.

  • PROFINET - Control&Status Words [E-03617]
  • Details:

    Full support for bitwise and detailled Control&Status words representation inside the user interface.

  • PROFINET - Force STW1&ZSW1 to be mapped properly in telegrams [S-22235]
  • Details:

    STW1&ZSW1 are only allowed in the main telegram at first IO slot. The user interface is enforcing this and blocking the user to add these signals in the supplementary telegrams.

  • PROFINET - Supplementary Telegram [S-21911]
  • Details:

    Full support to visualize and configure the different possible supplementary telegrams from within the user interface.

  • PROFINET - Detailled bits not refreshed properly [D-08788]
  • Issue:

    If the detailled bits tab is shown and the bit values are changing, the display is not refreshed (LED). The same problem occurs if you are in the PROFINET view but in another tab, coming back to the detailled bits tab will not refresh.

    Solution:

    The refresh problems are fixed. The LEDs should be now always in sync with the drive values.

  • PROFINET - Refresh Issues on Commands in Supp Telegrams [D-08801]
  • Issue:

    The Configure command is not enabled/disabled properly when the PROFINET state machine is changing (in/out of S1).

    Solution:

    Issue is fixed, all commands are updated properly when states are changing.

  • PROFINET - Usability Enhancements [S-22214]
  • Issue:

    1. Supplementary telegrams could not be edited without changing the current configured telegrams.
    2. Configure buttons for the main and supplementary telegrams could be disabled for different reasons, the user may not know why.
    3. Changing the configuration source from Telegram to PROFINET Master will override local values if the Master is not setup properly first.

    Solution:

    1. The edition of supplementary telegrams is now decoupled from the current configured telegram, using a new interface layout.
    2. When configure buttons are disabled, we now indicate why as an information close to the button.
    3. A warning is now displayed close to the configuration source to indicate that switching the source will override the drive data.

    ^ Back to Top ^

    Functional Safety

  • Plausibility Check for Unsupported EnDat Encoders [S-22062]
  • Details:

    EnDat encoders (Encoder 3) are not yet supported by the SafeMotion Monitor. A plausibility check was added to inform the user, future versions of the SafeMotion Monitor will support EnDat encoders.

  • Plausibility check navigation link broken [D-08778]
  • Issue:

    When using the navigation link from a plausibility check outside of the Parameterization view (e.g. Parameter Package), the safety group is not updated properly in the editor. The navigation is, but not the group in the editor, it could be confusig for the user.

    Solution:

    Problem fixed, the correct group is shown in the editor.

  • SafeMotion Monitor Firmware-Hardware Versions Formatting [S-22069]
  • Issue:

    The current formatting is not homogeneous through the different views.

    Solution:

    Firmware version: "M.mm" (M=major, mm=minor padded on 2 digits). Hardware revision: "RM.m" (M=major, m=minor)

    ^ Back to Top ^

    General

  • Documentation - Link to Online Developer Resources [S-22204]
  • Details:

    Direct link to the developer resources added in the documentation section.

  • Documentation - Preferences
  • Details:

    The user can now choose his preferred language and his preferred source (online / offline) for the documentation. The application will try to meet these prefreered settings upon availability. It will first try to meet the language and then the source. When a language is not available, it will defalut to English.

  • Editors - Better In Use Signaling [S-22321]
  • Details:

    Editors have different behaviors when a device parameter is in use or not. Mainly, the editor could be shown as read-only with or without a value. We added a new mode that will colorize the metadata tab in yellow when the parameter is not in use, that should allow to spot problems more easily. Additionally, the In Use value is now showing in the metadata popup, possibly marked in yellow depending on the mode.

  • Editors should be read-only when a parameter is tagged as Blocked [S-22149]
  • Details:

    When a parameter is tagged as Blocked, setting its value will trigger an error. We should disable the editor when the referenced parameter becomes Blocked. This is now implemented and working.

  • Model Customization - Lookup Table [E-03743]
  • Details:

    The models can be customized using lookup tables. The user interface can now visualize, export and import (CSV) these data from/to the device.

  • Model Customization Overview [S-22067]
  • Details:

    Provides an overview about the different models existing in the device, allowing to activate/deactivate and erase them

  • SD Card - Save and Load Parameters [S-21863]
  • Details:

    Added support for saving/loading parameters to/from a SD Memory Card inserted in the drive. Easy acces from the Parameter Load/Save view through buttons, also displaying the status of the SD card.

  • SD Card - Status and Usage [S-22203]
  • Details:

    New view indicating the status of the SD Card and also its usage with the total capacity.

    Issue:

    Until now, the tab selection within a view was not stored and the navigation history was not handling it properly.

    Solution:

    The navigation is now storing the selected tab within the view and restoring it properly when using history navigation.

  • Setup Wizard Crash [S-08834]
  • Issue:

    Running the Setup Wizard connected to a first generation device will crash the user interface.

    Solution:

    Crash is fixed.

  • Using hexadecimal format number in the device is causing parsing problem [D-08820]
  • Issue:

    In some cases, the user interface will fail to connect to the device, in some other occurences, it will just fail to display some values.

    Solution:

    Fixed the parsing in the user interface to support better hexadecimal format.

    ^ Back to Top ^

    Motion

  • Home - Warning displayed for 2G devices when driven by fieldbus [D-08789]
  • Issue:

    2G devices support homing driven by the fieldbus, the warning should not be displayed.

    Solution:

    The warning is not shown anymore for 2G devices.

    ^ Back to Top ^

    Motor & Power Stage

  • Field Weakening - Algorithm Configuration [S-22231]
  • Details:

    Full support for field weakening algorithm configuration from the user interface.

  • Field Weakening - Documentation [S-22230]
  • Details:

    Added a link to the field weakening documentation within the Motor View.

  • Motor View crashes when opened [D-08836]
  • Issue:

    When connected to a first generation device, the motor view will crash when opened.

    Solution:

    Problem fixed, the motor view is opening properly for all types/generations of devices

    ^ Back to Top ^

    Tuning

  • Gantry - Easier Tuning
  • Details:

    Working with the scope adjusting Servo Gains, it is now easy to just copy all the tuning parameters to another axis (slave). The same feature is also available when writing the tuning parameters from within the Performance Servo Tuner. Additionally, the parameter copy dialog highlights rows when the values are different between the source axis and the target axis.

    ^ Back to Top ^

    Version 2.7.0.5821 : November 10, 2020

    Requirements

    Required Components

    • .NET Framework 4.8
    • Visual C++ Redistributable 2010 SP1 (x86)
    • Visual C++ Redistributable 2013 (x86)
    • Visual C++ Redistributable 2015 SP3 (x86)
    • Internet Explorer 10

    Supported Operating Systems

    • Windows 7
    • Windows 8
    • Windows 10

    Feedback

    ^ Back to Top ^

    Fieldbus

  • Applying Modbus mapping configuration is far too slow through slow networks [D-08662]
  • Issue:

    The Modbus configuration dialog is not showing any progress while applying changes and it could take up to 1 minute through a slow network.

    Solution:

    We do have now a progress indicator while applying changes, the speed was also massively improved, particularly through slow networks.

  • Modbus - Mapping a command could create unexpected motion [D-08707]
  • Issue:

    By default, AXIS*.MT.MOVE#0 command(s) is/are part of the map. When showing the mapping list from within the Modbus view, the user interface will wrongly send the move command to the drive, creating unexpected motion if the motion task is properly defined and other conditions met (opmode, axis enabled, ...)

    Solution:

    Problem fixed, mapped commands will never be sent anymore as command to the drive while refreshing a view.

  • Export EtherCAT ESI file from the connected device [S-21743]
  • Details:

    Allows to export the EtherCAT ESI file (xml) for any connected AKD2G EtherCAT device. It will ensure that the ESI file is perfectly matching the device as it is generated by the device itself.

  • Modbus - Mapping Configuration - Clear Current Mapping [S-21644]
  • Details:

    While configuring the Modbus mapping, a new clear functionality has been added to allow the user to start with an empty map.

  • PROFINET - Common information & configuration [S-21898]
  • Details:

    Added a new tab for common information & configuration, like PROFINET identity and telegram source.

  • PROFINET - Custom Telegram Mapping Configuration [S-21646]
  • Details:

    Custom telegram user mapping, allowing user to choose from a possible signal list and map them upon needs.

  • PROFINET - General Configuration [S-21643]
  • Details:

    PROFINET general configuration for common parameters on each axis.

  • PROFINET - Scaling [S-21644]
  • Details:

    Added user interface support for all the PROFINET scaling parameters.

  • PROFINET - Status Bar [S-21852]
  • Details:

    PROFINET status bar displayed on all PROFINET views allowing the user at anytime to monitor the fieldbus general status.

  • PROFINET - Telegram Mapping [S-21645]
  • Details:

    Displays the current main telegram mapping from the drive, including live values exchanged on the fieldbus.

    ^ Back to Top ^

    Functional Safety

  • Remove Upper Lower Limits Plausibility Check for SLS and SCA [S-21882]
  • Issue:

    These two functions should also work when the position is rolling over in the middle of the checked range.

    Solution:

    We do not enforce that the upper should be greater than the lower position - the configurator should know exactly how the system is working around position checking.

  • Safety Parameters Upload [S-21882]
  • Issue:

    The upload only works if the SMM was configured using a parameterization file - it does not allow to upload FSoE parameterization.

    Solution:

    The button will be enabled only if the parameterization was done using a file.

  • Safety - Parameters Viewer should also display the parameters when parameterized through FSoE [S-21824]
  • Issue:

    Parameters are not shown even that the drive is fully operational. The parameters viewer is solely based on parameters downloaded as a file. FSoE CRCs are not shown.

    Solution:

    The parameters viewer is now showing the FSoE CRCs when a fieldbus is available. The parameters are shown in all cases (parameter file / FSoE parameterization).

    ^ Back to Top ^

    General

  • Crash when disconnecting and reconnecting WB using a physical device [D-08669]
  • Issue:

    The scenario to create the crash is about having an AKD2G connected and opening a view (e.g. Modbus), selecting the project node and then moving over to safety. Working in the safety tree, disconnect and reconnect the device, if you then move back to the Motion tree and select the device you were using, WB will crash.

    Solution:

    The issue is fixed.

  • Terminal view not getting the focus when the node is selected [D-08666]
  • Issue:

    In previous versions, when selecting the terminal node, the user could start typing immediately in the terminal as the view was getting the focus. It has stopped working in release 2.5.0.5367.

    Solution:

    The issue is fixed, the focus is properly working again.

  • Flexible restrictions-default value configuration [S-21884]
  • Issue:

    We need to support different restrictions and default values based on the application environment.

    Solution:

    Restrictions/default values adapting:

    • Show All settings default value
    • Project safety features list
    • Minimum offline version supported
    • Feedback type list

  • New Motor Support [S-21884]
  • Issue:

    72R motors missing.

    Solution:

    Added 72R to the WB motor database.

  • Performance improvement - Info keywords grouped [S-21279]
  • Issue:

    The keywords of type Info are currently not grouped for technical reasons. They are consuming bandwidth, particularly because they are also used in the status bar and/or toolbar.

    Solution:

    Info keywords are now also grouped. Some exceptions remain for some keyword causing problems in the firmware - they will be fixed and ten they will appear grouped.

    ^ Back to Top ^

    Motion

  • Basic observer configuration support [S-21954]
  • Details:

    Observer configuration supported for the device of 2nd generation.

    ^ Back to Top ^

    Motor & Power Stage

  • Thermal protection - device and motor [S-03553]
  • Details:

    Graphical and detailed overview of the current state from thermal protection in term of current limits and also in term of thermal capacity usage. Configuration of warning/fault thresholds for the current limits.

    ^ Back to Top ^

    Version 2.6.0.5516 : September 04, 2020

    Requirements

    Required Components

    • .NET Framework 4.8
    • Visual C++ Redistributable 2010 SP1 (x86)
    • Visual C++ Redistributable 2013 (x86)
    • Visual C++ Redistributable 2015 SP3 (x86)
    • Internet Explorer 10

    Supported Operating Systems

    • Windows 7
    • Windows 8
    • Windows 10

    Fieldbus

  • Modbus Mapping - Random crashes when applying mapping [D-08668]
  • Issue:

    Random crash is observed when applying a mapping configuration. After some investigation, we discovered that the problem occurred when faults were present on the drive with a particular mapping configuration. The root of the problem is in the FW, the data returned through the communication channel are corrupted.

    Solution:

    The FW has been fixed for the problem. We also fixed the user interface to ignore the corrupted data, logging the error and avoiding crashing.

  • WB - AKD2G - Modbus: random crash when cancelling a mapping. [D-08650]
  • Issue:

    When you try to map an object to insufficient space in the modbus map and then cancel the mapping, WB could randomly crash based on the speed whith which you clicked Cancel.

    Solution:

    Problem fixed, no more crash.

  • WB - AKD2G - Modbus: additional info about message rate for connected device. [S-21801]
  • Details:

    The device can only respond to a limited number of Modbus requests. If that limit is reached, the device will delay the answers to give back some time to the device processor. The users does not know about that situation.

    Solution:

    To inform the user about the situation, we provide now the message rate and also an indicator if the message rate is too high and therefore the answers are delayed. It will allow the user to adjust the Modbus client to avoid the situation.

  • WB - AKD2G: support for Modbus 32bits alignement
  • Details:

    In some cases, users would want to map parameters always using 32bits, even for 16 bits parameters, to simplify the mapping.

    Solution:

    The configuration dialog offers an option to map all parameters on 32 bits.

    ^ Back to Top ^

    Functional Safety

  • SAFEGRID integration issues [D-08667]
  • Issue:

    • Typos in descriptions (SBT - Max Motion Brake 1, SLS - Time for Velocity in Limits)
    • Advanced parameters user choice was meant to show these parameters, it is in fact the right to display them.
    • STO/SOS restart sources should not include dual inputs

    Solution:

    • Typos are fixed.
    • Changed the UI widget type (checkbox) and label. It is also now invisible for regular users as it is just confusing - the actual advanced parameters are read/only determined by the hardware.
    • STO/SOS restart sources include only single inputs

  • Safety - Missing plausibility check for manual restart
  • Issue:

    When manual start is configured (STO/SOS), we should verify that either a safe input is defined as restart source or that the fieldbus is activated, if not, the drive will remain in safe state forever.

    Solution:

    New plausibility check has been implemented.

  • WB - AKD2G - Safety: SLS/SLA/SLP function activation range has been changed. [S-21783]
  • Details:

    The SafeMotion Monitor does not support yet the Always Activated option for thes safe functions SLS/SLA/SLP.

    Solution:

    The range in WB does not allow this option to avoid problems within the SMM.

    ^ Back to Top ^

    General

  • Toolbar incorrectly disabled when a view is in error [D-08665]
  • Issue:

    When a view is in error for some reason, the navigation is disabled because we want the user to fix the error before navigating away. The toolbar is also disabled, it is incorrect as the user may need to disable its drive to fix the error (or possibly some other toolbar actions).

    Solution:

    The toolbar is now only disabled when switching views, it remains fully enabled when a view is in error.

  • WB - Defect: crash when searching in All Parameters View. [D-08608]
  • Issue:

    Searching for a parameter that is part of the Misc group (not in any other group) is crashing WB.

    Solution:

    Search is not crashing anymore.

    ^ Back to Top ^

    Motor & Power Stage

  • Thermal Protection - Current Limits [S-21831]
  • Details:

    New view added to display the different current limits for the thermal protection of the drive and the motor. The view will give an overview of the current situation and the a associated warning/fault.

    ^ Back to Top ^

    Version 2.5.0.5367 : August 06, 2020

    Requirements

    Required Components

    • .NET Framework 4.8
    • Visual C++ Redistributable 2010 SP1 (x86)
    • Visual C++ Redistributable 2013 (x86)
    • Visual C++ Redistributable 2015 SP3 (x86)
    • Internet Explorer 10

    Supported Operating Systems

    • Windows 7
    • Windows 8
    • Windows 10

    Fieldbus

  • WB - AKD2G: support for Modbus errors.
  • Details:

    Missing support for Modbus errors configuration and visualization.

    Solution:

    Full support implemented in WB.

  • WB - AKD2G: support for Modbus keep alive and watchdog configuration.
  • Details:

    Missing support for these 2 features in WB.

    Solution:

    Full support implemented in WB.

  • WB - AKD2G: support for Modbus logging.
  • Details:

    Missing support for Modbus logging configuration and visualization.

    Solution:

    Full support implemented in WB.

  • WB - AKD2G: support for Modbus mapping
  • Details:

    Missing support in WB for object mapping.

    Solution:

    Added mapping overview and mapping configuration support, including array types.

    ^ Back to Top ^

    Functional Safety

  • WB - AKD2G - Safety: clearing the safety configuration requires a user confirmation.
  • Issue:

    Clearing the Safe ID or the safety parameters is currently asking for the password, but the user is not warned that the operation will clear all the safety configuration. It is required by the specifications.

    Solution:

    The dialog asking for the password has been modified and it is now warning the user about loss of safety configuration, asking for his confirmation before to proceed.

  • WB - AKD2G - Safety: use the term SafeMotion Monitor or SMM.
  • Issue:

    Different terms were used throughout WorkBench to reference the SMM, confusing for the user.

    Solution:

    WorkBench is using everywhere the term SafeMotion Monitor or SMM- these are the official marketing names of the product.

  • WB - Safety: add user Safe ID input for parameter validation.
  • Issue:

    Per specification, there must be an explicit action from the user to identify the device on which parameters are validated. The Safe ID should be entered manually by the user and will be verified by the device.

    Solution:

    Implemented according specs, Safe ID must be entered for parameter validation.

  • WB - Safety: actions displayed during the download process should always be valid.
  • Details:

    After a safety parameter download, the Downoad button will appear enabled again even that this action is invalid at that particular moment. This is confusing for the user.

    Solution:

    The Download button is now disabled or hidden if the operation is invalid.

    ^ Back to Top ^

    General

  • WB: crash when removing a device from a safety group.
  • Issue:

    When using WB > 2.3.1.5012, if a device is removed from a safety group, WB encouters a crash. We also have problems around atcivation/deactivation of links to add devices/groups.

    Solution:

    Problems have been fixed.

    ^ Back to Top ^

    Version 2.4.0.5175 : June 17, 2020

    Requirements

    Required Components

    • .NET Framework 4.8
    • Visual C++ Redistributable 2010 SP1 (x86)
    • Visual C++ Redistributable 2013 (x86)
    • Visual C++ Redistributable 2015 SP3 (x86)
    • Internet Explorer 10

    Supported Operating Systems

    • Windows 7
    • Windows 8
    • Windows 10

    Action Table

  • WB-AKD2G-Support: command buffer autocomplete commands.
  • Details:

    The command buffer editor is not providing any help to the end user about which commands are available.

    Solution:

    Autocomplete has been implemented for the command buffer editor.

    ^ Back to Top ^

    Communication

  • WB-AKD2G: supports connection to AKD2G on slow networks.
  • Details:

    When using a slow connection (VPN) with WB standalone or WB embedded in KAS, the application has difficulties to connect to AKD2G drives, failing at a high percentage rate.

    Solution:

    We removed the watchdog empty commands when not required, it freed up enough bandwidth to allow connection even with slow networks.

    ^ Back to Top ^

    Fieldbus

  • WB - AKD2G: support for Modbus overview and configuration.
  • Details:

    AKD2G supports Modbus, it needs user interface support for easier configuration.

    Solution:

    Added general Modbus configuration support and overview of the connected devices.

    ^ Back to Top ^

    Functional Safety

  • WB - Safety - Defect: validation error reporting broken.
  • Issue:

    Moving a safe device from one safety group to another is breaking the safety report. Running the validation will not report any error once moved to the new safety group.

    Solution:

    Fixed, validation errors are reported properly even after moving safe devices throughout safety groups.

  • WB Console - Safety - Defect: crash when downloading a SMM FW to the device.
  • Issue:

    Downloading a SMM FW to the device will throw a stack overflow - crash of the console app.

    Solution:

    Fixed, the console is downloading properly the SMM FW to the device.

  • WB-AKD2G-Safety: keeping a safety report open in Acrobat casuses problem.
  • Issue:

    When the user opens a safety report or a safety parameters report within Acrobat (PDF reader) from WB and keep it open, subsequent calls to open the download package dialog will fail. The CRC of the package will be shown as 0x00 and the download operation won't work.

    Solution:

    PDFs can stay open in external reader, WB will still be able to perform any other tasks without problem.

  • WB - Safety: *.zip package format should be the default for safety parameters export.
  • Issue:

    The default format was *.bin, the *.zip package will be more helpfull as it contains the PDF publishing all the configured safety parameters.

    Solution:

    Zip package format is now the default for export.

    ^ Back to Top ^

    General

  • WB-Rebranding: supports rebranded drive models.
  • Details:

    Drive models should appear rebranded.

    Solution:

    Implemented support for rebranded drive models.

  • WB-Rebranding: supports rebranded motor series.
  • Details:

    Some motor series should appear rebranded.

    Solution:

    Implemented support for rebranded motors, including filtering based on the brand.

    ^ Back to Top ^

    Motion

  • WB-AKD2G: support new zero velocity thresholds.
  • Details:

    Prior to FW version 02-03-00-00, keywords were AXIS#.DISVTRESH and AXIS#.DISTVTRESH, in the new FWs, they are AXIS#.ZEROV and AXIS#.ZEROT.

    Solution:

    WB modified to use the correct FW according to the FW version.

  • WB-AKD2G-Gantry: new homing mode for gantry
  • Details:

    WB does not support homing mode 19 (Gantry Homing - Use Master Settings).

    Solution:

    Full support for that mode implemented in WB.

  • WB-AKD2G-Support: simplified jog motion full support in user interface.
  • Details:

    Service Motion is a bit complicated to configure for a simple jog motion, particularly when driven using buses (eg Modbus). A new jog simplified feature has been implemented in the drive, WB need to provide support.

    Solution:

    Full jog feature user interface support implemented.

    ^ Back to Top ^

    Project Management

  • WB: Startup page not loaded properly when a project fails to load.
  • Details:

    When a project is already opened, if the user tries to load another project and it fails, WB remains in a bad state (drive eventually still connected, busy cursor still running, ...).

    Solution:

    Current connected devices are disconnected, current project is unloaded and it goes back to the startup page to have a clean empty state.

    ^ Back to Top ^

    Security

  • WB - Security: display in the discovery the protocols supported by the devices
  • Details:

    New devices will provide several ways to connect (tenet/SSH), the user should be able to know what the device supports.

    Solution:

    Icon displayed indicating what protocols are supported.

    ^ Back to Top ^

    Version 2.3.0.4870 : April 17, 2020

    Requirements

    Required Components

    • .NET Framework 4.6.1
    • Visual C++ Redistributable 2010 SP1 (x86)
    • Visual C++ Redistributable 2013 (x86)
    • Visual C++ Redistributable 2015 SP3 (x86)
    • Internet Explorer 10

    Supported Operating Systems

    • Windows 7
    • Windows 8
    • Windows 10

    Action Table

  • WB-AKD2G-Actions: specific editor for CmdSource/OpMode.
  • Details:

    Configuration of the cmd source / op mode used for task 27 is not obvious enough by using a number.

    Solution:

    Special task param editor put in place for task 27.

  • WB-AKD2G-Actions: specific editor for command buffer task.
  • Details:

    Edition of the command buffer content is not easy without having a special editor - commands need to be chained using ';' and the whole entry will be lost if an error occurs.

    Solution:

    Special editor put in place for the command buffer content (autocomplete is not yet implemented).

  • WB-AKD2G-Actions: specific editor for DIN/DIO comparison.
  • Details:

    Configuration of the DIN/DIO comparison used for source 21 is not obvious enough by using a number.

    Solution:

    Special source param & condition value editor put in place for source 21.

    ^ Back to Top ^

    Communication

  • WB-MKD: the program does not handle properly the discovery with MKD-N dual axes.
  • Issue:

    When using a MDK-N dual axes, the axes are going mixed up on the second scan, the 2 axes have the same serial number.

    Solution:

    We are using the MAC address to differentiate these 2 axes when necessary (identical serial number).

    ^ Back to Top ^

    Feedback

    ^ Back to Top ^

    Functional Safety

  • WB-AKD2G Safety - Safe Brake Test view not updated correctly based on the parameterization.
  • Issue:

    When changing from 2 brakes configured on the axis to only 1, the view still shows 2 brakes - it is not refreshed properly.

    Solution:

    Refresh problem fixed - the SBT view is now always matching the current configuration.

  • WB-AKD2G-Safety: adapt WB for new keyword SafeFunctionStatus in drive.
  • Issue:

    SDIp/SDIn active states were not reported properly through AXIS#.SAFE.ACTIVE - a replacement keyword AXIS#.SAFE.FUNCTIONSTATUS was added in FW.

    Solution:

    WB is now using the new keyword to report properly SDIp/SDIn active states.

  • WB-AKD2G-Safety: update SBT states to match the latest FW implementation.
  • Issue:

    The latest SBT FW implementation has some changed and new states that we need to match in WB.

    Solution:

    WB updated to match the latest FW. It is not backward compatible.

  • WB-AKD2G-Safety: added detailled diagram for safety status.
  • Details:

    The status bar contain a safety indicator relating the general SMM status. It is not always easy to understand where the general status comes from (eg. why am I in STO ?).

    Solution:

    Clicking the safety status will popup a detailled diagram of the current safety configuration in the drive, including the status of each safe functions/inputs so the user can understand exactly the source and the path followed to reach the current state.

  • WB-AKD2G-Safety: added plausibility check for absolute position initial value.
  • Details:

    If the absolute position range is defined as unsigned - the initial value cannot be negative and would be rejected by the SMM.

    Solution:

    Plausibility check added in WB to catch the problem early and help the user fixing the problem.

  • WB-AKD2G-Safety: display FSoE state in detailled diagram.
  • Details:

    When safe fieldbus is activated but not running, all safe functions will go in safe state but the user cannot understand why looking at the detailled safety status diagram.

    Solution:

    We have added the value of FSoE state in the detailled status diagram. It will show red when it is not working properly, showing to the user that something is wrong with the fieldbus.

  • WB-AKD2G-Safety: display properly the possible override brake behaviors.
  • Details:

    Brake behavior can be overriden at the drive level, which in turn could be overriden by the safety when SBC is configured. The user interface is not reflecting this, it could be confusing for the user.

    Solution:

    The brake override screen is now reflecting the behavior: when SBC is active, override functionalities are disabled and an information is displayed to the user.

  • WB-AKD2G-Safety: display Safety indicator in the status bar.
  • Details:

    With the current status bar, there is no clear indication about the Safe Motion Monitor and its safe functions configuration and state.

    Solution:

    A Safety indicator has been added to give an immediate idea about the SMM state. To get details a diagram will be popped up by clicking on the indicator.

  • WB-AKD2G-Safety: display Safety indicator in the status bar.
  • Details:

    When an error occured in the SMM, the error code is too generic and we do not know the object concerned by th error (multiple inputs, encoders, ...).

    Solution:

    The error code has been made more specific and an additional info has been added indicating which instance of an object is concerened by the error.

  • WB-AKD2G-Safety: easy access to the parameterization report.
  • Details:

    The parameterization report (SAFEGRID pdf) is not easily available, it could be complicated to get the full parameterization details.

    Solution:

    The parameterization report is now accessible through a split button at the same place the validation report is avaiable.

  • WB-AKD2G-Safety: usability enhancements and advanced parameters support.
  • Details:

    Diagnostic view was difficult to use, no support for advanced parameneters.

    Solution:

    Enhancements:

    • Advanced parameters support
    • Diagnostic view splitted in different views
    • Safety monitoring configuration support

    ^ Back to Top ^

    General

  • WB-Usability: F1 contextual help should work with the new editors.
  • Details:

    Old editors where showing keyword help when F1 was pressed while editing a field, the new editors don't.

    Solution:

    All editors in WB are now showing the keyword help when F1 is pressed while editing.

  • WB-Usability: Property Editor could be closed by clicking outside of it.
  • Details:

    Users complained that it is not obvious that the property editor should be closed by clicking the (x). It is also an additional click to move to the next block to edit.

    Solution:

    Property editor can now be closed by clicking outside of it, the (x) is supported as before.

    ^ Back to Top ^

    Motion

  • AKD2G Encoder Emulation diagram error management.
  • Issue:

    When any of the block in the diagram is in error state, all the blocks are shown in error state confusing the user about which one to fix.

    Solution:

    Each block is now properly individually managed for any error occuring.

    ^ Back to Top ^

    Motor & Power Stage

  • WB: display motor production information.
  • Details:

    Motor production information (prod date / serial number) are not visible within WB.

    Solution:

    This information is now visible at the bottom of the motor view when available.

    ^ Back to Top ^

    Project Management

  • WB: history navigation working across all navigation trees.
  • Details:

    The history navigation has been disabled since the navigation tree was splitted in 2 different trees. When the user uses links to jump from one view to another, it is sometimes difficult to come back easily to the preceding view.

    Solution:

    The history navigation has been fixed and it works now across all the navigation trees and navigation contexts (tabs motion/safety).

  • WB: opening a WorkBench project
  • Issue:

    When trying to open a *.wbp file from the Windows explorer, doing a manual association to WorkBench, the application will crash at startup.

    Solution:

    WorkBench has been fixed and will open properly the project file. The associtaion still has to be done manually for now - not done by the installer.

    ^ Back to Top ^

    Simulation

  • WB-AKD1G: crash when using simulation after being connected to a physical drive.
  • Issue:

    Simulation crashing on AKD1G if you connect first to a physical device and then launch the simulation on the same device.

    Solution:

    Problem fixed.

    ^ Back to Top ^

    Version 2.2.0.4487 : December 10, 2019

    Requirements

    Required Components

    • .NET Framework 4.6.1
    • Visual C++ Redistributable 2010 SP1 (x86)
    • Visual C++ Redistributable 2013 (x86)
    • Visual C++ Redistributable 2015 SP3 (x86)
    • Internet Explorer 10

    Supported Operating Systems

    • Windows 7
    • Windows 8
    • Windows 10

    General

  • WB-Usability: scope is too slow to load.
  • Issue:

    Loading the scope for the first time is taking a long time, about 5s when the drive is idle and the connection is optimal. It can increase to 20s for worse conditions having the drive busy and a slow connection.

    Solution:

    The scope view is much quicker to load, about 2s in optimal conditions. The gain should be even bigger in more difficult conditions.

    ^ Back to Top ^

    Version 2.2.0.4448 : November 28, 2019

    Requirements

    Required Components

    • .NET Framework 4.6.1
    • Visual C++ Redistributable 2010 SP1 (x86)
    • Visual C++ Redistributable 2013 (x86)
    • Visual C++ Redistributable 2015 SP3 (x86)
    • Internet Explorer 10

    Supported Operating Systems

    • Windows 7
    • Windows 8
    • Windows 10

    Analog & Digital IO

  • WB-AKD1G: support for Analog Input Mode 4
  • Details:

    AIN.MODE 4 (Motion Task Feedrate) cannot be configured using WB, it has to be done through the terminal.

    Solution:

    Full support has been added to the UI.

    ^ Back to Top ^

    Communication

  • WB-AKD/MKD: better discovery mechanism and helper view.
  • Details:

    In some cases, the current scan mechanism is failing - particularly when AKD/MKD-N have FW version prior to 1.17. In case of failure, there is no way to know the IP address of the drives to update them.

    Solution:

    The scan process has been fixed to support FWs prior to 1.17. We have added a new Device Discovery dialog that will display all the devices seen on the network without any filtering.

    ^ Back to Top ^

    Functional Safety

  • WB-AKD2G-Safety: Helper control to see the safe encoders configuration.
  • Details:

    Our third party safe component (SAFEGRID) does not allow the usage of user units within the component. It is difficult for the user to keep track of the safe encoders and user units while swithcing through the safe functions.

    Solution:

    We have added an helper control that will give an overview of the selected safe encoders with their respective resolution. This new component will also provide the encoder resolution to the user units helper control displaying the resolution/accuracy for the current configuration.

    ^ Back to Top ^

    General

  • WB: easy help access from within the keyword picker.
  • Details:

    The new keyword picker has a lot of features, end users may not see all of them easily.

    Solution:

    Added help quick access from within the picker (link as an icon and F1 key).

  • WB: New Scope Channel Picker.
  • Details:

    The scope channel picker has become unusable with multi-axis drive, too many signals and no way to search through them.

    Solution:

    New selection mechanism added to select the channel. It allows search in keywords and descriptions filtering a list of potential signals. Keyboard can be used for fast access.

  • WB-MKD: Additional Support
  • Details:

    Missing support in WB:

    • DIN mode 27 not supported for MKD-C
    • VBUS.MAINSCURRENTLIMIT not shown in the power view
    • No scope groups for power and voltage values

    Solution:

    WB support has been added for these items.

  • WB: when All Parameters View is closed, the communication is still running for parameters in the view.
  • Issue:

    If the All Parameters View is open, all subsequent opened views will be slowed down as a lot of unnecessary communication is still running.

    Solution:

    All Parameters View is fixed - communication is properly stopped when exiting.

    ^ Back to Top ^

    Motion

  • AKD2G - Analog Motion: not displaying the proper AIN value in the diagram.
  • Issue:

    Using AIN 2 for analog motion in velocity mode will show the voltage of AIN 1 within the diagram.

    Solution:

    Problem fixed - the correct voltage is shown in all cases.

  • WB-AKD2G: Additional homing modes using creep factor.
  • Issue:

    For AKD2G FW >= 02-02-01-000, homing mode 1 & 2 will also use the creep factor - WB is not displaying it.

    Solution:

    The home view has been adapted to display the creep factor based on the home mode and the FW version.

  • WB-AKD2G: Basic Gantry Support.
  • Details:

    A new command source has been added on the second axis (when available): Gantry. The second axis will serve as slave from axis 1. WB is currently crashing when Gantry is selected and some views that we would want to see are hidden.

    Solution:

    Fixed the crash, made Home View visible on Axis 2 in Gantry mode.

  • WB-AKD2G: Gain Scheduling supported on AKD2G including multi-axes drives.
  • Details:

    Gain scheduling was not supported on AKD2G within WB

    Solution:

    Full Gain Scheduling support added to WB for AKD2G multi-axes devices.

    ^ Back to Top ^

    Motor & Power Stage

  • WB-AKD2G/MKD: Power DC Mode.
  • Details:

    AKD2G/MKD devices have a new parameter allowing them to perfom in DC operation mode, this parameter is not shown in WB.

    Solution:

    WB Power View displays this new parameter and switch related parameters according to the chosen mode.

    ^ Back to Top ^

    Version 2.1.0.3945 : August 08, 2019

    Requirements

    Required Components

    • .NET Framework 4.6.1
    • Visual C++ Redistributable 2010 SP1 (x86)
    • Visual C++ Redistributable 2013 (x86)
    • Visual C++ Redistributable 2015 SP3 (x86)
    • Internet Explorer 10

    Supported Operating Systems

    • Windows 7
    • Windows 8
    • Windows 10

    Action Table

  • WB-AKD2G: actions using a motion task as a source could not specify a particular motion task as a specific source.
  • Details:

    Action sources for motion task can only specify the axis, not a particular task.

    Solution:

    Action sources for motion task can now specify an axis and a particular task if desired.

    ^ Back to Top ^

    Analog & Digital IO

  • WB - MKD-C: proper digital I/O description.
  • Details:

    AKD1G digital I/O screen is always describing DIN 1&2 as high speed inputs. This is not true for all devices, MKD-C inputs are slow inputs, it may confuse the user.

    Solution:

    Digital I/O view is now adapting to the device model, only showing high speed when the inputs effectively supports high speed.

  • WB: multi-axis support for Analog Inputs.
  • Details:

    Analog input view displays the modules using the value but only for Axis 1 - we need to support all axes.

    Solution:

    The view is now displaying all modules using the analog input for all axes. We also added an indication when actions are using the input.

    ^ Back to Top ^

    Anlog & Digital IO

  • WB: Analog Output view support for AKD2G
  • Details:

    Analog output(s) not supported on AKD2G

    Solution:

    Full analog output(s) support on AKD2G, from 0 to n outputs dynamically adjusted based on the drive model.

    ^ Back to Top ^

    Communication

  • WB - AKD/MKD: scanning subdevices when discovery blocked, including using EoE.
  • Details:

    When the discovery (broadcast) is blocked or not routed properly, WB is unable to scan sub-devices. It is particularly problematic if the user can enter manually the power supply IP address, he will then be unable to see sub-devices.

    Solution:

    WB can now discover sub-devices using the power supply provided information about sub-devices, no need of broadcast. WB should scan sub-devices even when the IP address for the power supply was entered manually, including EoE connectivity. It needs recent FWs in the devices (>=1.18.1.0), for older FWs, WB will default to using broadcast discovery.

  • WB - TwinCAT: connection mechanism through TwinCAT API is broken.
  • Issue:

    Using the TwinCAT API, adding a device works, but once disconnected, it is impossible to connect again to the same device (not able to get Physical Information).

    Solution:

    Fixed, reconnection works properly.

  • WB: disconnects when executing FB2.SELECT from the terminal.
  • Issue:

    Unexpected disconnection executing FB2.SELECT.

    Solution:

    Problem fixed, WB is now waiting for the correct timeout value.

  • WB: random crash when connecting to a drive.
  • Issue:

    WB crashing connecting normally to a drive (random, low occurence).

    Solution:

    Fixed in WB.

    ^ Back to Top ^

    Fieldbus

  • WB: Modulo view supported on multiple axes.
  • Details:

    Modulo view works only on axis 1.

    Solution:

    Modulo view is now working on all axes.

    ^ Back to Top ^

    Functional Safety

  • WB - Safety: SMM FW update dialog box cannot be opened.
  • Issue:

    The SMM FW Update dialog cannot be opened for a full configured project with safety devices if none of them are connected.

    Solution:

    Fixed, the dialog can be openend and the devices connected from within the dialog.

  • WB: AKD2G safety drives are not always available to be added to safety groups.
  • Issue:

    The AKD2G safety devices when simulated are not available to be added to a safety group, they should.

    Solution:

    The AKD2G safety devices when connected or simulated are now available to be added to a safety group. When the devices were never connected or simulated, they are not available as we do not know their exact capabilities.

  • WB: localization support for SAFEGRID.
  • Details:

    SAFEGRID interface, parameters with their descriptions and the navigation interface are only available in English for now.

    Solution:

    The safety interface can now be fully localized. We currently have implemented German - other language will come in the future.

  • WB-AKD2G-Safety: User Unit Configuration Helper.
  • Details:

    User unit configuration is complicated, a lot of different parameters to enter. We needed a helper showing to the user the result of all the parameters combined together.

    Solution:

    Helper appearing in the user unit configuration screens.

  • WB-Safety: displays hardware revision and firmware version of the Safe Motion Monitor.
  • Details:

    SMM HW revision and FW version are not easily available, they are useful information for troubleshooting.

    Solution:

    SMM HW revision and FW version are now available in the Safety Diagnostic View under the General tab.

  • WB-Safety: adapt Diagnostic/SBT view to support the new SBT process.
  • Issue:

    The SBT process implementation has been changed to be run at the aixs level. WB should be adapted to show that properly.

    Solution:

    The view has been adapted to the new process. Please note that it does not work anymore with older versions of SBT.

    ^ Back to Top ^

    General

  • WB: display detailled error for any HTTP request problem.
  • Details:

    WB displays a generic HTTP failure for any failed HTTP request.

    Solution:

    WB displays now the detialled error (when available) from the failed HTTP request.

  • WB: support for FW file version 1.5.
  • Details:

    Some of the FW updates, like SFA update, do not require a drive reboot. The FW update in WB always reboot the drive at the end.

    Solution:

    FW files version 1.5 is introducing the possibility to configure the update process. One of the parameter allows to avoid rebooting at the end of the update process.

  • WB: Usability of Diagram's Views.
  • Details:

    Edition possibility from some of the blocks is not obvious and acess using a double-clisk makes it more difficult.

    Solution:

    Icons added close to the editable blocks and linked blocks. The action to perform (edit, jump to target) is now achieved by a single click.

  • WB-AKD2G: Capture support.
  • Details:

    AKD2G Capture is not supported by WB.

    Solution:

    A new view has been added with full AKD2G Capture support.

  • WB-AKD2G: Device Diagnostics View
  • Details:

    Device Diagnsotics is a group node in the tree - it should give an overview and links to other diagnostics views.

    Solution:

    New view implemented with links to major other diagnostics views and an overview of the device status.

  • WB-AKD2G: Device Setting View
  • Details:

    Device Settings is a group node in the tree - it should give links to other important settings views.

    Solution:

    New view implemented with links to major other settinsg view.

  • WB-AKD2G: support for FW versions without AXIS#.ACC/DEC.
  • Details:

    AKD2G will not have anymore a general axis acceleration/deceleration limits as they are redundant with the specific limits (service motion, analog, gearing, ...). It was a point of confusion for many users. It will be removed from the drive, actual WB versions may behave wrongly as they expect these keywords to exist in the drive.

    Solution:

    WB supports drives with or without axis acceleretaion/deceleration limits. The views will adapt automatically.

  • WB-MKD: full documentation support.
  • Details:

    No documentation for MKD devices in current WB.

    Solution:

    MKD documentation has been added to WB.

  • WB: parameters file cannot be read by old WB.
  • Issue:

    New WB (version ≥ 2.0) is using a new file format for parameters, old WB (version < 2.0) cannot read it. It is annoying for AKD1G users as a lot of them are still using 1.x WB versions.

    Solution:

    WB will use the old parameter file format for old drives (AKD1G, MKD), so that it can be read by any version of WB.

  • WB: random crash when WB is disconnected from a drive, user action or loss of connection.
  • Issue:

    WB crashing randomly when dicconnecting, annoyance for the user.

    Solution:

    Fixed in WB.

  • WB: refresh problems after failing FW update or switching from online to simulation.
  • Issue:

    After a FW failing update or when starting a simulation, the refresh of the toolbar and status bars is not done properly, showing old values.

    Solution:

    Refresh problem fixed, the bars will reflect the current staus of the drive.

  • WB: some dialog boxes for user interaction are not modal
  • Issue:

    For some operations, we need to display a dialog box for user interaction (eg. informing about a serial number change). The user has to make a choice before going further, it will chnage the way the process will continue (eg. connecting or canceling because of a serial number change). While this dialog is displayed, any other action should be blocked in WB as they wre not valid until the decision of the user. In the current implementation, it was possible, the dialog box were not modal.

    Solution:

    Fixed, the dialog box are now modal, blocking any other action before a choice is made.

  • WB: unexpected action can be triggered through the toolbar and status bar by the user while updating AKD2G FW.
  • Issue:

    During AKD2G FW update, the toolbar allows to enable/disable and change other motion parameters, this is dangerous as the drive is not in an operational state and will reboot at anytime. All actions should blocked.

    Solution:

    Toolbar and status bars are completetly hidden whil updating the FW.

  • WB: unit custom label lenght is not limited properly in WB.
  • Issue:

    The user can enter too long unit custom labels causing a FW error (no crash, just reported later in the process of editing).

    Solution:

    Fixed, the length is limited to 16 chars as in the FW.

  • WB: using the user interface at the device level to clear faults is doubling the time of the operation.
  • Issue:

    If we measure the time to clear faults for the device (DRV.CLRFAULTS) using the terminal, we can notice that using the button from the UI will take twice the time to perform the operation.

    Solution:

    Fixed, it takes the same time using the terminal or the UI widgets.

  • WB-KAS: crash under high UI load.
  • Issue:

    If a view is immediately selected (Axis Overview or other) after launching AKD integration, it randomly crashes.

    Solution:

    Fixed, it may freeze for some seconds but then move forward.

    ^ Back to Top ^

    Motion

  • WB - AKD2G/Multi-Axis: Electronic Gearing support.
  • Details:

    AKD2G electronic gearing is not supported in WorkBench.

    Solution:

    WB has a new Electronic Gearing View for AKD2G, supporting all axes. AKD1G is using an old view has the keyword scheme is different.

  • WB: axis direction support.
  • Details:

    Axis direction is not easily accessible in WB for AKD1G and not at all for AKD2G - it has to be mainly changed through the terminal.

    Solution:

    Axis direction has been added to the Axis Settings view.

  • WB-AKD2G: Encoder Emulation Output Support.
  • Details:

    No WB support for encoder emulation output.

    Solution:

    Encoder emulation is fully supported within WB.

  • WB-AKD2G: Motion Task Registration Support.
  • Details:

    MT registration is not supported in WB for AKD2G devices.

    Solution:

    Full support in WB through the Motion Task view and a small dialog allowing the user to setup the configuration.

  • WB-AKD2G: Motion Tasks Copy/Paste.
  • Details:

    Motion tasks cannot be copied fr AKD2G devices.

    Solution:

    Copy/Paste is now supported for Motion Tasks on AKD2G - as long as the units are matching perfectly. If the units are not matching, the Paste operation is blocked and throws an error.

  • WB-Safety: displays hardware revision and firmware version of the Safe Motion Monitor.
  • Details:

    SMM HW revision and FW version are not easily available, they are useful information for troubleshooting.

    Solution:

    SMM HW revision and FW version are now available in the Safety Diagnostic View under the General tab.

  • WB - Motion Task individual nodes are not displayed any more for AKD1G.
  • Issue:

    Individual nodes for quick direct access to individual motion tasks is not available anymore.

    Solution:

    Fixed, individual nodes are available again.

  • WB: AKD2G Motion Task cannot start a task with the Start button within the view.
  • Issue:

    On AKD2G, starting a motion task from within the view using the button is crashing.

    Solution:

    Fixed, the button works properly.

    ^ Back to Top ^

    Motor & Power Stage

  • WB - MKD-C: full support in power view.
  • Details:

    The MKD-C hardware architecture allows many more configuration parameters and monitoring points than the AKD-C, they are not shown in the current power view.

    Solution:

    The power view is now supporting all hardware types, including MKD-C with its many parameteres and monitoring points.

  • WB-AKD2G: support for brake power saving.
  • Details:

    Brake power saving not supported in WB.

    Solution:

    The brake power saving feature is now fully configurable from within WB.

  • WB-AKD2G: VBus phases configuration support.
  • Details:

    VBus phases configuration is not supported from within WB.

    Solution:

    Support has been added to the Power View.

  • WB-AKD2G/MKD: support for regen resistors for these device models.
  • Details:

    Regen resistors are not fully supported for AKD2G and MKD devices. The regen view does not propose any regen resistor model.

    Solution:

    Regen resistors are fully supported for these devices.

  • WB: AKM2G not available in KAS IDE-WB.
  • Issue:

    AKM2G are not available in KAD IDE-WB. The series can be selected, but the part number is not displayed and the user cannot choose any AKM2G motor.

    Solution:

    AKMD2G motors are now available within KAS IDE-WB.

  • WB: missing AKM motors.
  • Issue:

    AKM22H-ANB2DB00 is not available in the current WB.

    Solution:

    Updated data from the database.

  • WB: missing AMK2G motors.
  • Issue:

    LD feedbacks are not available.

    Solution:

    WB fixed to allow LD feedbacks selection.

    ^ Back to Top ^

    Project Management

  • WB: navigation tree changed to have only devices in the top tree, no axis.
  • Issue:

    The dual navigation tree having axis in the top tree is forcing the user to do a lot of additional clicks while working on axis configuration when using also common tools/settings like I/Os or scope.

    Solution:

    The top tree is now only allowing the selection of the device, the full device content will be displayed in the bottom tree allowing quick access to any view for that device.

  • WB: the selected view is lost when navigating through different devices.
  • Issue:

    In preceding WBs, when the user switches from one device to another, the latest view selected per device is rememebred and displayed when coming back to the device. In the latest WB, the selectd view is lost if that view is under an Axis section.

    Solution:

    Problem fixed, WB remembers properly the selected view per device.

  • WB: unable to save project
  • Issue:

    Any save operation of the project is failing. It occurs for some specific locales, in that case Dutch.

    Solution:

    The 3rd party ZIP library we are using has encoding problems. We upgraded to a more recent library in which these problems seem to be fixed. We also increased the logging information to help us debug further problems around zipping/unzipping files.

    ^ Back to Top ^

    Simulation

  • WB-AKD2G: Offline Simulation Support.
  • Details:

    AKD2G devices do not have offline simulation support.

    Solution:

    AKD2G offline simulation support is now implemented. It should allow users to prepare configuration without having a real physical device.

    ^ Back to Top ^

    Tuning

  • WB: sine sweep on Bode plot is locking the UI.
  • Issue:

    The user cannot stop the measure - neither with Abort nor with Panic, it could be dangerous.

    Solution:

    Fixed, pressing Abort or Panic (F12) will abort the measure at the end of the current cycle (it may take some seconds).

    ^ Back to Top ^

    Version 2.0.0.3088 : December 21, 2018

    Requirements

    Required Components

    • .NET Framework 4.6.1
    • Visual C++ Redistributable 2010 SP1 (x86)
    • Visual C++ Redistributable 2013 (x86)
    • Visual C++ Redistributable 2015 SP3 (x86)
    • Internet Explorer 10

    Supported Operating Systems

    • Windows 7
    • Windows 8
    • Windows 10

    Communication

  • WB - AKD/MKD: automatic topology scan.
  • Details:

    The user was used with old WB to an automatic scan as soon as the AKD/MKD-C was connected. In the new WB, the scan was manual until now - if not triggered by the user, the underneat AKD/MKD-Ns will not show.

    Solution:

    The scan is automatically triggered as soon as the AKD/MKD-C is connected or when and AKD/MKD-C is added to the topology.

    ^ Back to Top ^

    Feedback

    ^ Back to Top ^

    Functional Safety

  • WB - Safety Diagnostic: Safe Brake Test.
  • Details:

    Safety users cannot easily run & monitor a Safe Brake Test.

    Solution:

    Safety diagnostic view supports SBT fully, allowing the user to launch SBT per axis and monitor its progress and result.

  • WB - Safety Diagnostic: safe I/Os monitoring.
  • Details:

    SMM users cannot see easily the current status of the safe I/Os.

    Solution:

    The new Safety Diagnostic view, tab Safe I/Os, is now publishing the status of all safe inputs and outputs, including their mode and the source configured for the outputs.

  • WB - Safety Diagnostic: Safe Motion Monitor general information.
  • Details:

    SMM users cannot see easily information about the hardware, configuration or status of the module.

    Solution:

    The new Safety Diagnostic view, tab General, is now publishing this information including the FSoE status (if present).

  • WB - Safety: monitoring of the STO inputs.
  • Details:

    The user has currently no possibility to see the input signals on STO inputs.

    Solution:

    A new monitoring view is allowing a detailled view of the different STO inputs.

  • WB - Safety: parameterization file can be saved in i00 format
  • Details:

    FoE and probably other fieldbuses later use i00 format in their file transfer mechanism. There is currently no way to get a safety parameterization file in that format.

    Solution:

    The safety upload mechanism from the drive allows now to save the parameters in i00 format. It has also been added an export mechanism on parameter packages, saving the parameters in i00 to be used by fieldbus masters.

  • WB - Safety: safety parameterization view can display related device parameters for the selected safety function.
  • Details:

    For some functionalities, the motion parameters have to be set properly according to the safety parameters to have the drive performing properly. These parameters are separated in the user interface and it may be difficult to know what you have to do to have them matching. For example, SBC and the device brake parameters have to be in sync to have the brakes acting properly.

    Solution:

    When it is suitable, we can now display Device Related Parameters below SAFEGRID to show the values to the user. The user will be more aware with an easier access to the parameters if the 2 configuration worlds (motion/safety) match together.

  • WB - Safety: user management.
  • Details:

    User management is not supported to protect against unwanted parameterization chnages or parameter download/activation.

    Solution:

    User management is supported with 3 levels: Full Configuration / Commissionning / Maintenance.

  • WB: Safety Description File Changes.
  • Issue:

    The digital output source 67 it not useful, should be removed. The SS1 instance 1 can be triggered by an I/O failure problem, the parameters should always be editable.

    Solution:

    Fixed according requests.

    ^ Back to Top ^

    General

  • WB - AKD 2G - Hardware Configuration: support for connectors configuration.
  • Details:

    Some of the connectors can be used for different purposes. The user has to configure their usage.

    Solution:

    Added a new view supporting the configuraion of the connectors and the brakes. This view includes links toe the configured modules to help the user to understand how the modules are interlinked.

  • WB - AKD 2G: contextual help support.
  • Details:

    AKD 2G has a new structure for help topics, regrouping axis and indexed keywords using single aliases.

    Solution:

    WB supports the new AKD 2G structure along with the old AKD 1G structure.

  • WB - AKD2G support: help for the new device type added, including links from the views
  • Details:

    AKD2G help content was not accessible from within WB and the links from the views were broken using old AKDs aliases.

    Solution:

    AKD2G help integrated in the WB build process. Aliases will work properly depending on the device you are connected to. The content is still in its early draft stage.

  • WB - Faults/Warnings full support for AKD1G and AKD2G.
  • Details:

    AKD2G faults/warnings new scheme is not supported.

    Solution:

    Implementation of a new status bar, faults/warnings popup and view supporting AKD1G and AKD2G schemes homogeneously.

  • WB - KAS Integration: dual navigation tree is supported within KAS.
  • Details:

    WB has a new navigation scheme using a dual tree allowing to navigate to common or axis parameters. It allows WB to support multi-axis drives like AKD2G dual axes. This scheme was not supported in KAS.

    Solution:

    The new navigation schem is supported within KAS.

  • WB - Limits: support for AKD2G HW limits.
  • Details:

    AKD2G as a new scheme for the hardware limits inputs.

    Solution:

    The Limits view has been changed to allow the user to select the digital input for the hardware limit switches.

  • WB - Multi-Axis: Axis Overview.
  • Details:

    Axis overview was not existing after the migration to the new navigation structure (common/axis).

    Solution:

    Implemented a new axis overview that gives a summary about the concerned axis.

  • WB - Multi-Axis: Axis Settings
  • Details:

    The Settings view does not exist on the second axis, the user cannot have an easy overview on the current configuration.

    Solution:

    The Settings view is now fully supported on the second axis when it exists.

  • WB - Multi-Axis support: fixed Overview View at the device level.
  • Details:

    The device Overview View displays the enable state of axis 1 and allows to enable/disable the same axis. This is confusing and incoherent on multi-axis devices.

    Solution:

    Enabling/Disabling information/actions have been removed from the device Overview View, it will be accessible in the axis Overview View.

  • WB - PL.KP multiple units support [Hz,
  • Details:

    Preceding FW had PL.KP in (rev/s)/rev, the new FW will have it in Hz. Different algorithms in WB assume that the unit is (rev/s)/rev, they have to be modified to take the unit in account.

    Solution:

    Algorithms around tuning have been modified to take the unit in account - by first copnverting into the internal unit. Additionally, the import of old parameter files will be blocked as the units are not compatible.

  • WB - Usability enhancements for toolbars
  • Details:

    With the introduction of the contextual toolbars displayed based on the tree selection (common, axis#), users had to switch in the tree to reach some basic functionalities like the Enable/Disable, Save to NV, Disconnect.

    Solution:

    We extended the availability of these functionalities to be present in all toolbars (Enable/Disable available in the common context and the 2 others available within axes contexts). We cannot make all buttons accessible in all cases, it will eat too much space when having multi-axes drives.

  • WB - AKD2G: support of keyword changes.
  • Issue:

    Some keywords have been removed or changed in AKD2G to clarify the user telnet interface, WB has to be changed to behave properly.

    Solution:

    Changes done:

    • AXIS#.CS.VTHRESH changed to AXIS#.DISVTRESH: this velocity threshold is used in all disable modes, not only for controlled stops
    • AXIS#.CS.TO changed to AXIS#.DISTVTRESH: not a timeout, time that the velocity has to be under the velocity threshold to be considered as settled
    • AXIS#.SETTLE.P: new keyword used by all motions that need a position window to consider it setlled
    • AXIS#.SETTLE.V: new keyword used by all motions that need a velocity window to consider it setlled
    • AXIS#.MT.VELOCITYSOURCE: removed, feature not yet supported, the view has been adapted
    • AXIS#.MT.EMERGMT: removed, no used in AKD2G

  • WB: keyword privileges changes
  • Issue:

    AKD2G is changing the keyword privileges scheme, increasing security. WB was unlocking some of the keywords, this is not allowed anymore, WB should use alternative keywords.

    Solution:

    WB has been adapted to support the new scheme and still working properly with 1G drives.

  • WB - KAS: Disconnected view does not show properly.
  • Issue:

    When the AKD integration is launched being offline within KAS, the disconnected view does not show up - the view host appears empty.

    Solution:

    Fixed, the view appers now properly.

    ^ Back to Top ^

    Motion

  • WB - Current Loop: support on the second axis.
  • Details:

    The Current Loop view is not supported on axis 2.

    Solution:

    The Current Loop view is available on all axes.

  • WB - Homing: support on the second axis.
  • Details:

    The Home view is not supported on axis 2. The limit switches and home switch keywords are different under AKD2G, the view has to be adapted.

    Solution:

    The Home view is available on all axes and it has been adapted to support AKD 1G and 2G keyword scheme. The home mode naming and pictures have been edited to me more precise and more coherent.

  • WB - Safety Diagnostic: Safe Motion Monitor general information.
  • Details:

    SMM users cannot see easily information about the hardware, configuration or status of the module.

    Solution:

    The new Safety Diagnostic view, tab General, is now publishing this information including the FSoE status (if present).

    ^ Back to Top ^

    Motor & Power Stage

  • WB - AKD 2G: Brake Configuration Support.
  • Details:

    AKD 2G is supporting several brakes that could be used on one or several axes. WB does not provide any support to configure them.

    Solution:

    WB fully support AKD 2G new brake scheme.

  • WB - AKD 2G: Vbus AC Nominal.
  • Details:

    The configuration for AC Line voltage has changed in AKD 2G.

    Solution:

    WB now supports all different AC Line voltage configurations.

  • WB - Multi-Axis: Motor
  • Details:

    The motor on the second axis has to be configured using the terminal.

    Solution:

    The motor view is now fully supported on the second axis when it exists.

    ^ Back to Top ^

    Project Management

  • WB - Device Management: simplified project view, last saved name displayed for nodes when disconnected.
  • Details:

    The project view is confusing with the included discovery window. The user may have difficulty to identify disconnected devices in the tree, they are showing a generic name with connection information.

    Solution:

    The project view has been simplified, no more discovery, it just contains a button to add new devices. The add new device is only available in the Motion tree, the Safety tree is only grouping existing devices, not adding new ones. The last saved name is now shown for disconnected devices.

  • WB - Device Management: single node for real devices and offline simulations.
  • Details:

    To pass parameters between offline and online devices, the user has currently to save a parameter file and reload it on the other device manually. For safety, it does not work as the parameters are embedded in the project attached to the device node.

    Solution:

    The user can now, using the same node and parameter set, connect to a real device or launch an offline simulation. In both cases, when disconnecting, the user can save the parameters locally within the project. For safety, the user can now easily edit the safety parameters being connected to the device or being simulating offline.

  • WB: Multi-Axis support for the navigation tree, toolbar and status bar.
  • Details:

    The navigation tree, toolbar and status bar only supports single axis drives. The user cannot access the second axis parameters.

    Solution:

    The navigation tree, toolbar and status bar have been adapted to support mulit-axis drives. The second axis may have for now a very limited number of views, they will be added in the future. It is to notice that for single-axis drives, the navigation may be more complex than before, this is for the sake of coherence with multi-axis drives navigation.

  • WB - Start menu structure.
  • Issue:

    In some Win10 OS, only 1 level of folder is allowed in the Start Menu. For that reason under Win10, our installer was adding all shortcuts in the company name folder mixing versions together.

    Solution:

    We have now only 1 level of folder in the Start Menu, using the full product name. Shortcuts are now grouped properly per installed version.

    ^ Back to Top ^

    Simulation

  • WB - Offline: string parameter value with spaces incorrectly saved.
  • Issue:

    The DIN buffer is not saved properly, loosing actions. This is a general problem around string parameters, if they contain spaces, they are only saved until the space.

    Solution:

    Fixed, the parameter string values are saved properly including spaces.

    ^ Back to Top ^

    Tuning

  • WB - Slider Tuning: support on the second axis.
  • Details:

    The Slider Tuning view is not supported on axis 2.

    Solution:

    The Slider Tuning view is available on all axes.

    ^ Back to Top ^