<< Click to Display Table of Contents >> Navigation:  Diagnostics with CanEasy > Execute diagnostics projects

 

BSKD7 projects can be executed in two different ways:
 

•starting the diagnostics with the corresponding batch file itself

•adding the diagnostics project to the workspace and starting the project via the tree entry

 

 

 
Executing the diagnostics project via batch file

 

A diagnostics project can be executed directly via its batch file. An already configured and running CanEasy is not needed. BSKD7 is starting automatically with CanEasy and enables the communication to the bus. It is only necessary to have a corresponding workspace file at the same folder as the batch file. The diagnostics project is automatically added to list of available diagnostics projects in the workspace. The diagnostics project can be used with the terminal window.
To close the diagnostics project, use the corresponding commands (q,x,e) or select "Close diagnostics project" via the tree entry BSK Diagnose 7.

 
 
Executing the diagnostics project from workspace

 

If BSKD7 projects were added to a workspace, they can be started with a double click or by using their context menu. A started diagnostics project is displayed bold in the tree view. To close the diagnostics project, use the corresponding commands (q,x,e), select "Close diagnostics project" via the tree entry BSK Diagnose 7 or via the context menu of the project itself.

 

 

 

Automatic Start of simulation on start of diagnostics

 

The automatic start of the simulation can be configured via the context menu of the tree entry BSK Diagnose 7. If the menu entry "Auto-Start simulation" is hooked, the simulation will be started directly if a diagnostics project is executed. If the menu entry is not hooked, the simulation must be started manually.

 

 

Terminal visible/invisible

 

It is possible to suppress the terminal window of an active diagnostics project via context menu of the BSKD7 root node. For this the command Terminal visible is used, also to display the actual state. This function is also available via COM interface and could be set and retrieved with the following property:

 

 

BSKD7 can be remote controlled via the COM interface. So it could be possible to suppress the terminal window by using e.g. a corresponding VBA application which makes the terminal window unneeded. So the terminal window can be suppressed with the named property. The terminal windows can be displayed at all times via the context menu of the root node. The "visible property" is saved during runtime. That means: If a diagnostics project is closed with an invisible terminal window and it is started again, the terminal is still invisible (if CanEasy was not closed).