Users can define which log Sections are enabled. Sections can be subdivided into modules, so users can enable each module separately. Each module contains a configuration item with a question Enable log section/module?.
If items are not modified, the system automatically assumes that logs are not created. If items are modified, a No answer disables log creation (except for IOData Section, please check Notes), and an Yes answer enables Section log. Modifying a Section value implies in changing all Module values inside that Section.
Enable log sections option
•IOData Section is an exception to this case. Its corresponding item is Disable IOData section. Not changing this item is the same as enabling this Section. Changing it by answering No to question Enable log section/module? disables this Section •Changing these variables can be performed while E3 is executing, and it is applied up to 30 seconds after execution |
Available log Sections are described on the next table.
Log Sections and their modules
Section |
Description |
|---|---|
DB |
Shows errors on database or data discard operations, as well as results of operations executed on acquisition and execution threads |
EdbSync |
Log with informative messages about the process of importing and syncing external electrical models |
ImportExport |
Log generated by E3 Studio on data importing or exporting processes |
IOData |
Shows data read and written by E3Run |
Playback |
Log generated by E3Playback |
RECRaw |
Detailed log of REC communications. Available modules on this section are the following: •Client: Records request packages •Server: Records response packages |
Storage |
Allows tracking Storage operations. Available modules on this Section are the following: •Dropped: Lists all values discarded by a Storage •Input: Lists all variations of Tag values linked to a Storage •Stored: Displays all values sent by a Storage to a Database |
Sync |
Allows monitoring information synced between E3 Server and E3Run (and among E3 Servers in Hot-Standby mode). Available modules on this section are the following: •Alarm: Shows alarm messages generated by E3Run, which are passed to an alarm summary kept by E3 Server •Vars: Shows changes made on E3 Server's persistent Tags database |
Undo |
Records system activities of E3 Studio's Undo menu |
There are special log sections that record operations executed on a specific thread, as well as their duration. Only operations that last more than a certain time (default value is 100 ms) are logged. These logs allow checking when E3 processing becomes slow, almost stopped. Available special log sessions are described next.
•Full: Main log gathering general information about E3 Server, E3Run, E3 Studio, and E3 Viewer execution. Available modules are described on the next table.
Available modules for Full logs
Module |
Description |
|---|---|
AccessChecker |
Thread responsible for checking Domain's permissions or access in E3 Server (E3Run) |
AlarmCallbackManager |
Thread responsible for receiving alarm events from Remote Domains (E3Run) |
AlarmQueue |
Threads responsible for sending alarm events |
AlarmServer |
E3Run's thread responsible for asynchronously sending Alarm events |
DBCallbackManager |
Thread responsible for receiving and storing in cache the statistics sent by the E3DBEngine process |
DefragDlg |
Thread responsible for the defragmentation of project and library files (Studio) |
DomainManager |
E3 Server Domain's state manager thread (opens or closes the active Domain, updating a Domain based on changes on .dom files) |
E3Admin |
E3 Admin's main thread |
E3Runtime |
E3Run's main thread, allows identifying locks or slowdowns during E3's execution |
E3Server |
E3 Server's main thread |
EdbSync |
Thread responsible for the process of importing and syncing external electrical models |
EventQueue |
E3 Server's threads responsible for sending asynchronous Link events |
IOManager |
E3Run's thread responsible for receiving data generated by IOServers |
LicenseManager |
E3 Server's license check thread |
LinePrinter |
Thread responsible for sending asynchronous data to Line Printers (E3Run) |
Link2Stub |
E3Run's thread responsible for asynchronously sending Link events |
OpcAsyncCreateServer |
OPC client's threads responsible for isolating the connection and access to an OPC server |
OpcCallback |
E3Run's or E3 Studio's thread responsible for asynchronously receiving events from OPC clients |
OpcClient |
Thread where the OPC client is executed |
OpcClientHost |
Main OPC client's thread |
OPCGroup |
Thread responsible for sending notifications from E3's OPC server (E3Run) |
OpcQueue |
Thread responsible for sending OPC client's notifications asynchronously |
PowerCADWarmUp |
Thread used to perform a PowerCAD pre-loading when opening Elipse Power Studio |
PowerHubReceive |
Thread responsible for receiving notifications from electrical studies (E3Run) |
PowerHubReceive2 |
Thread responsible for receiving notifications from electrical studies in EDB format (E3Run) |
PowerHubSend |
Thread responsible for sending updates to electrical studies (E3Run) |
PowerHubSend2 |
Thread responsible for sending updates to electrical studies in EDB format (E3Run) |
RECAppartment |
Thread used to manage the transmission of REC packets during a connection |
RECChannel |
Thread used to manage the transmission of data via network in REC connections |
RemoteDomain |
E3 Server's threads responsible for managing client connections from Remote Domains |
RemoteDomainsManager |
Thread where management of RemoteDomain sets occurs |
SafeServerSession |
Thread responsible for access or maintenance of retentive data from a Domain (E3Run) |
ServerControl |
E3 Server's threads responsible for managing a local or remote Domain server |
ServerControlCallback |
Thread responsible for sending notifications to E3 Admin (E3 Server) |
ServerControlMonitor |
E3 Server's thread responsible for automatically starting E3 Admin for logged in users |
ServerLinkManager |
E3 Server's thread implementing Link management |
ServerSubscriptionManager |
Thread responsible for managing alarm signature connections |
StandbyAlgorithm |
E3 Server's thread implementing Hot-Standby algorithm decisions |
Studio |
E3 Studio's main thread (interface) |
ThreadPool |
Reusable E3DBEngine process' thread responsible for executing queries |
UaCallback |
Thread responsible for receiving notifications from OPC UA clients (UaDriver) |
UaClient |
OPC UA client's main thread |
UaQueue |
Thread responsible for sending notifications from OPC UA clients (UaDriver) |
VideoRecorder |
Thread used to manage video recording in an E3Playback |
Viewer |
E3 Viewer's main thread (interface), allows diagnosing Screen opening time, script execution time, etc. |
•FullDB: Records operations of E3 database access' threads (generated by E3Run and E3 Server). Available modules are described on the next table.
Available modules for FullDB logs
Module |
Description |
|---|---|
DBAcquisition |
Thread that sends application-generated data to queue files (.e3i files) |
DBCallback |
Thread that sends statistics about connections and operations finished or failed for the parent process |
DBEngineHost |
E3DBEngine process' main thread |
DBExec |
Thread that removes operations from queue files (.e3o files) and executes commands on a database |
OCIThread |
OCI's (Oracle Call Interface) thread |
WatchDog |
E3DBEngine process' thread responsible for terminating this process if a lengthy operation is locked |
•FullIO: Records activities on IOServer's threads. Available modules are described on the next table.
Available modules for FullIO logs
Module |
Description |
|---|---|
CallBack |
Thread for sending data collected by a Driver to E3Run |
Driver |
Thread executing a Driver |
IOServer |
IOServer's main thread, which receives Driver configuration and requests sent by E3Run |
UaClientHost |
E3UaClient process' main thread |
WatchDog |
IOServer's thread responsible for terminating this process if any lengthy operation is locked |
•FullPower: Records detailed information on E3PowerEngine (when the electrical model file is in XPD format) or PowerEngine2 (when the electrical model file is in EDB format) threads. This log records, for example, information about performance diagnosis, in addition to detailed results of several operations. Available modules are described on the next table.
Available modules for FullPower logs
Module |
Description |
|---|---|
DistLoadModel |
Module responsible for calculations on Distribution Load Modeling Electrical Study |
External Reader |
Module responsible for calculations on External Reader Electrical Study |
LoadShedding |
Module responsible for calculations on Load Shedding Electrical Study |
PowerEngine |
Elipse Power's main module, responsible for handling Elipse Power requests |
PowerFlow |
Module responsible for calculations on Power Flow Electrical Study |
SelfHealing |
Module responsible for calculations on Self-Healing Electrical Study |
Send |
Module responsible for sending results generated by several Electrical Studies to E3 |
StateEstimator |
Module responsible for calculations on State Estimator Electrical Study |
TopologyProcessor |
Module responsible for calculations on Topology Processor Electrical Study |
Workspace |
Module responsible for centralizing values of Measurements used by Electrical Studies |
•PowerEngine: Records general information on E3PowerEngine (when the electrical model file is in XPD format) or PowerEngine2 (when the electrical model file is in EDB format) threads. Available modules are described on the next table.
Available modules for PowerEngine logs
Module |
Description |
|---|---|
DistLoadModel |
Thread with information about Distribution Load Modeling Electrical Study |
ExternalReader |
Thread with information about External Reader Electrical Study |
Input |
Thread with input information for Measurements and Measurement Sources |
LoadShed |
Thread with information about Load Shedding Electrical Study |
Output |
Thread with output information for Measurements and Measurement Sources |
PowerEngine |
Thread with global information about PowerEngine |
PowerFlow |
Thread with information about Power Flow Electrical Study |
SelfHealing |
Thread with information about Self-Healing Electrical Study |
StateEstimator |
Thread with information about State Estimator Electrical Study |
TopologyProcessor |
Thread with information about Topology Processor Electrical Study |
Workspace |
Thread with information about Measurement values used by Electrical Studies |
NOTE |
Module configuration only has precedence over Section configuration. |