Back to top

Debugging interaction problem between WorkBench and drives may be facilitated by using the built-in logging mechanism.

Where are the application and the log files in your system:

The easiest way to access the application or the log files is to open the About box in WB, it will give you the full path to the application and log folder:

image

WB has 2 log files:

O arquivo em anexo mostra como calcular a inércia da carga movimentada pelo servo motor.

Conhecer a inércia da carga permite determninar se o sistema está bem dimensionado e qual a resposta máxima que este sistema pode dar.

The Load On Startup listbox on the Scope Settings screen in Workbench is by default disabled ( greyed out ).

Under the Tools->Options pull-down menu in Workbench there is a box that can be checked to enable this feature.

The checkbox is called "Reload Scope Settings when Scope page is Opened.

The fault history in Workbench shows a number of days, hours, minutes, and seconds for each fault occurrence.  This is the runtime of the drive.  It is the ammount of time that the drive has been in a booted-up state, whether enabled or disabled.

If a fault occurs while Workbench is connected to the drive, then Workbench shows the computer's time and date of when the fault occurred and also shows the elapsed time from when the fault occurred (after pressing the Refresh button). 

From the Fault History page:

In late 2013, Workbench was tested to be compatible with Windows 8.

 

Cloud for Workbench on KDN

I had an idea related to having an online storage location (cloud) that Workbench could connect to and store a customer’s parameter file and/or program file.  I approached the Workbench development team about this, but left it as a “nice to have someday in the future” kind of thing.  But with KDN having a login profile available to every customer, maybe it could be used to developed this.  Part of my idea for a cloud was to have multiple login layers for each login profile.  A customer can create the profile an