The name ConfigItem means, they provide a configuration dialog to the user and they can be configured to communicate together. All ConfigItems together in one ConfigViewer, their settings and the connections between them, are called "project".

ConfigItems are the items inside the ConfigViewer. They must be connected together with ConfigLines (communication arrows) to enable the data exchange between them.

There are different types of ConfigItems and each has a special job to do.

The ComObjects are general purpose communication objects (device drivers). In this version of kbLogger, these types are available: CAN devices, Files, RS232 and Sockets. These items can communicate with the outer world (outside of kbLogger). They does not change the messages between the driver and the communication target.

List of general purpose ComObjects:

There are also special communication objects which uses internally general purpose ComObjects to communicate to the real hardware. In addition to that, they has a build in communication layer to handle a device specific protocol and to provide an API to ConfigItems with kbScript capability.

List of special ComObjects:

The simulation objects are able the change the messages, ignore them or to generate new ones.

List of SimulationObjects:

The ViewerObjects are used to show the simulation output to the user.

List of ViewerObjects:

Activation state of ConfigItems:
Every ConfigItem can be set into inactive state or back to active state. In the inactive state, the ConfigItem can be configured, but not communicate with its communication partners (the ConfigItems connected with it). Switch the activation state of an ConfigItem, do a right-click on it and choose "Active". An inactive ConfigItem is shown in translucent style.