The Automation logs contain all the information flowing from the application to the several devices controlled by it. They also keep track of the commands the Automation application sends to the other Etere modules. The Automation log files can be found in the local directory of the workstation where the application runs (Ex. ...\Etere\Log\). The log name is exe.module.user.pcname.XXXXXX(workstation system id).log. Example: au.etereau.001.onairmain.onair.log. The log captures the date and time in dd/mm/yyyy hh:mm:ss:ms format.
Moreover, all the log file names ending in "OLD" indicate the log files created when the main log file exceeds a specific size (settable). They represent a backup of the older log files.
The Automation log files can be divided into the following categories:
Startup Log
Log name: AU.ETEREAU.001.PCNAME.STARTUP-XXXXXX.LOG
This log file is written during the application's startup. It contains the following information:
•Startup: application's date, hour and path
•About: network name, software version and system-id
•System: it contains a list of all the different paths
•Params: it shows the local copy of the following .ini files (Param.ini, Global.ini)
•Resources: it shows the local copy of the folder containing the configuration of all the resources
•Device List: it shows a list of all the devices controlled by the application
•Devices: it shows the initialization of all the devices controlled by the application
ONAIR Log
Log name: AU.ETEREAU.001.PCNAME.ONAIR.LOG
It's the main log file of the application. It contains the following information:
•data flow from the application to the videoserver
• application's high-level activity (attachments, video router switches, master control switches, received commands, etc.…)
• user's activity (commands sent from the application's interface)
•Hexadecimal commands (Imagine protocol)
The information is ordered by hour (HH:mm: ss. ms). This log file can be beneficial to detect errors. The error messages are written in the log file. The following example shows information about the failed attaching of a clip contained in a log file:
18:32:51.105 118695.19 2 1 oatAtPdr | Attaching "0EVS NDJEPROG ", MarkIn=0, MarkOut=419 {a}
18:32:52.127 118696.20 6 4 oavExec | Extern async event: OnNotExecuted from 0x1 {Ref. 0x00000001}
18:32:52.127 118696.20 2 4 oatAtPdr | Error: Attach failed {Ref. 0x00000001}
Device Controller Log
Log name: AU.ETEREAU.001.PCNAME.DEVS.LOG
This log file contains the information about the controller of all the devices: GPI input boards, Titlers, Dsk, etc…It shows the commands sent to the devices, but it's not the device's log itself.
The VTR device type has a separate log file (AU.ETEREAU.001.PCNAME.VTR.LOG). The information is ordered by date (dd/mm/yyyy) and hour (HH:mm: ss.ms).
The following example shows a list of commands sent to a Titler device
31/01/2002 15:10:41.789 223841.18 000A Titler 3 : Status=1 Jumped genCtrl
31/01/2002 15:10:41.789 223841.18 000A Titler 3 : Status=2 Jumped genCtrl
31/01/2002 15:10:41.789 223841.18 000A Titler 3: Change Status to 3 at 0 msec genCtrl
31/01/2002 15:10:41.789 223841.18 000A Titler 3 : Task is "{0|000| | |0|0|}" genCtrl
31/01/2002 15:10:41.789 223841.18 000A Titler 3: Dsk TakeOff
31/01/2002 15:10:41.806 223841.18 000A Titler 3 : Logo Preset&Take (0,000)
Onair Database Log
Log name: AU.ETEREAU.001.PCNAME.DBF.LOG
This log file contains all the operations completed in the on-air database (play, stop, skip commands, hour synchronization…). The log file tracks all the procedures during the scheduled play. Therefore, it keeps track of the local file Tpalxxxx. dbf (xxxx indicates the onair month and day), the daily on-air archive.
The information is ordered by date (dd/mm/yyyy) and hour (HH:mm: ss.ms).
The following example shows the transcription of a schedule update
31/01/2002 15:05:00.416 223500.12 000A |DttxUpd | +-----------------------------------------------
31/01/2002 15:05:00.416 223500.12 000A |DttxUpd | | Schedule Update
31/01/2002 15:05:00.416 223500.12 000A |DttxUpd | | -----------+---
31/01/2002 15:05:00.416 223500.12 000A |DttxUpd | | Date/Time | 31/01/2002 15:05:00
31/01/2002 15:05:00.416 223500.12 000A |DttxUpd | | Duration | 00:00:00
31/01/2002 15:05:00.416 223500.12 000A |DttxUpd | | From Pos | 95 To Pos 95
31/01/2002 15:05:00.416 223500.12 000A |DttxUpd | | Play Pos | Yes
31/01/2002 15:05:00.416 223500.12 000A |DttxUpd | | Forced | Yes
31/01/2002 15:05:00.416 223500.12 000A |DttxUpd | +-----------------------------------------------
31/01/2002 15:05:00.416 223500.12 000A |DttxUpd | | ---> TPAL0131.DBF <---
Udp Log
Log name: AU.ETEREAU.001.PCNAME.UDPSERVER.LOG (Udp Server)
Log name: AU.ETEREAU.001.PCNAME.UDPCLIENT.LOG (Udp Client)
Several Etere applications use the UDP protocol to communicate. The Udp log file shows the commands an application (Udp Server) sends to another (Udp Client). All the controls are ordered by date (dd/mm/yyyy) and hour (HH:mm: ss.ms).
The following examples show the commands sent (Udp Server) and the same commands after being received (Udp Client)
Udp Server:
31/01/2002 15:29:03.999 52143.23 2774 | -> | Command 10 Start Send to 10.101.1.31:10100
31/01/2002 15:29:03.999 52143.23 2774 | >> |>.10100>:0110<.<: To 10.101.1.31:10100
Udp Client:
31/01/2002 15:29:04.099 52144.00 126AF2 | << |013E0200000003T000091A7000000FF000023F800000248000F2F0800000000 01111100000111100 37287,64519000008000000103 RETE 40000000000019 r4-m1111333113000000 From 127.0.0.1:10101
31/01/2002 15:29:04.099 52144.00 126AF2 | c | | -> Received Request: Cmd 3E
31/01/2002 15:29:04.099 52144.00 126AF2 | c | | <- Answer: , {1207165421}Answer not required
Device Log
Log name: AU.ETEREAU.001.PCNAME.1BMC-ID1.LOG (Videoserver)
AU.ETEREAU.001.PCNAME.1LOGO.LOG (Generatore di Logo)
AU.ETEREAU.001.PCNAME.1MAST.LOG (Master Control)
This log file regards the drivers of the several devices controlled by the Automation application. Every device has its log file, with a different name for every single type of device. In this log file is written all the commands received by the application (they must be the same commands written in the ONAIR and the DEVS log files), the serial or network communication.
The commands sent to the videoserver device are in hexadecimal form and are in Imagine protocol. All the commands are ordered by date (dd/mm) and hour (HH:mm: ss.ms).
The following example shows the command sent by the application to the videoserver.
31/01 15:40:31.360[09] 000052831360 0000 *** Status check TEtereAncestorImagineServer
31/01 15:40:31.440[11] 000052831440 0000 ... PORT STATUS 0x0F TEtereImagine
31/01 15:40:31.440[11] 000052831440 0000 Tx: 02 03 30 05 0F BC TEtereAncestorImagineServer
31/01 15:40:31.440[11] 000052831440 0000 Rx: 02 0A 30 85 0F 84 01 00 00 00 00 18 9F TEtereAncestorImagineServer
Initialization parameters
Log name - Global.ini
This log file is the initialization file regarding all the Etere modules.
Initialization parameters
Log name - AuRemote.ini
This log file is the initialization file regarding the Automation application. The file contains the following information:
IDENTIFICATION - Workstation identification data (IP address, system ID, port and u_number)
ROUTER - Video router configuration data
TITLER - Titler configuration data
VIDEOSERVER - Video server configuration data
OTHER - Devices configuration data (VTR, Logo, Dsk, Gpi input boards)
Initialization parameters
Log name - Param.ini
This log file is the initialization file where all the user (channel) parameters are saved.
Initialization parameters
Log name - 15653437.ini
This log file is the initialization file where all the workstation parameters are saved. The number is variable.
As RunLog
Starting from version 14.2.24.304 in Etere Automation, a new log file is available, which logs only the events broadcasted and the most important ones.
Technical Details:
The log file name is au.eterau.xxx.pcname.asrun.log
The logs are structured as follows (see attached example):
[TYPE] [DATEHOUR] MESSAGE
TYPE
APP: important events
EVENT event's star time
DATEHOUR
TYPE = APP: date/hour when the event was broadcasted
TYPE = EVENT: date/hour when the event started
MESSAGE
TYPE=APP – it's displayed for each significant event; the messages that could appear are the following
FATAL ERROR -> critical error, block
AUTOMATION IS ONAIR -> automation startup
AUTOMATION STOP -> When automation is stopped
AUTOMATION RESET -> When automation is reset
PLAYOUT DECLARED OFFAIR -> when automation is put off-line
PLAYOUT DECLARED ONAIR -> When automation comes back online
PLAYOUT IS NOW IN EMERGENCY LIVE -> when an emergency live broadcast starts
PLAYOUT IS GOING TO EXIT EMERGENCY LIVE -> when an emergency live broadcast ends
TYPE = EVENT: it appears every time a new event starts; the fields listed in the message are the following ones (fixed size, separated by commas)
STATUS -> on air, error
EVENTID -> event number referred to tpalinse
CODE
SUPPORT
DESCRIPTION
EVENT_TYPE
MARKIN -> in HH:MM: SS.FF
MARKOUT -> in HH:MM: SS.FF
EVENT TYPE -> manual/variable/...
DURATION -> in HH:MM: SS.FF
[- ] 17/05 12:38:40.469 | |Log Started [APP ][2004-05-17 12:38:40.14] AUTOMATION RESET [APP ][2004-05-17 12:39:00.03] AUTOMATION IS ONAIR [CLIP][2004-05-17 12:38:57.00] Y, 214611531001, SAMI04, 0BMC INT_CAR , prova IOMs - 1, T, 00:00:00.00, 00:01:00.00, [CLIP][2004-05-17 12:39:02.00] Y, 214612274439, SAMI04, 0BMC INT_CAR , prova IOMs - 1, T, 00:00:00.00, 00:01:00.00, [CLIP][2004-05-17 12:39:05.01] Y, 214612279091, SAMI04, 0BMC INT_CAR , prova IOMs - 1, T, 00:00:00.00, 00:01:00.00, [CLIP][2004-05-17 12:39:07.21] X, 214612281341, SAMI04, , prova IOMs – 1 , T, 00:00:00.00, 00:01:00.00, [CLIP][2004-05-17 12:39:10.00] Y, 214612283989, SAMI04, 0BMC INT_CAR , prova IOMs - 1, T, 00:00:00.00, 00:01:00.00, [CLIP][2004-05-17 12:39:12.02] Y, 159366535592, C-6BD93730@clip25.sh, 0BMC ENG_BILL , M, 00:00:00.00, 00:01:00.00, [APP ][2004-05-17 12:39:14.08] AUTOMATION STOP
Au64 Logs
Au64 logs are dedicated to the Automation 64-bit version of Etere, characterized by the suffix "Au64.*.log". They are composed of the same structure as the previous automation, with some exceptions:
- driver logs substituted with "*.ETXServer_Au0xx.log" (where "xx" is the station code)
Example code
24/06/2021 23:48:27.758 |debg|[ EVENT ] Tx: <ETXServerEvent><Event Id="SIGNAL_EVENT" ChannelId="ETXServerReply" EventName="command_completed" EventParam="<ETXServer><Reply Handle="32057793" Value="7" ErrorCode="0" Description="Success" CommandHandle="53" Id="QUEUE_APPEND" /></ETXServer>" EventTime="20210624214827751" Handle="0" /></ETXServerEvent> [EventsClient_OnTransmitted]
24/06/2021 23:48:27.758 |debg| Transmit signaled [EtereETXEventsCommunicationProtocol.SignalEvent]
- MPtoNDI*.log files, which describe the NDI output processes.
Example code
19/06/2021 03:08:19.303 |info|Done [Start]
19/06/2021 03:08:19.314 |info|mp link available: ETXMC-Au001-MPSwitcher-02DE72D6-mixer-020702D9 [WaitMPLink]
19/06/2021 03:08:19.321 |info|mp link playing: mp://ETXMC-Au001-MPSwitcher-02DE72D6-mixer-020702D9 [WaitMPLink]
19/06/2021 03:08:19.321 |info|Setting renderer... [WaitMPLink]
19/06/2021 03:08:19.322 |info|Renderer set: NDI Renderer [WaitMPLink]
19/06/2021 03:08:19.323 |info|Renderer line out set: 01ETX0061N [WaitMPLink]
- NDItoMP*.log files, which describe the input processes from external sources.
Example code
24/06/2021 16:55:20.089 |info|Process start [Start]
24/06/2021 16:55:20.090 |debg|Starting thread: SuicideThreadCheckProcess [StartSuicideThread]
24/06/2021 16:55:20.090 |debg|Done [StartSuicideThread]
24/06/2021 16:55:20.090 |info|Initalizing live input... [Start]
24/06/2021 16:55:20.091 |info|live.ObjectNameSet(ETXMC-Au001-live-51810644) [Start]
24/06/2021 16:55:20.578 |info|live.DeviceSet(video,NDI Receiver,null) [Start]
24/06/2021 16:55:20.578 |info|live.DeviceSet(video::line-in,VMC-R1 (MIX 1),null) [Start]
24/06/2021 16:55:20.578 |info|live.PropsSet(device::ndi_bandwidth,highest) [Start]
24/06/2021 16:55:20.578 |info|live.DeviceSet(ext_audio,<No External Audio>,null) [Start]
24/06/2021 16:55:20.579 |info|live.PropsSet(device::capture_cc,true) [Start]
24/06/2021 16:55:20.579 |info|live.PropsSet(object::mdelay.enabled,true) [Start]
24/06/2021 16:55:20.579 |info|live.PropsSet(object::mdelay.time,0.000) [Start]
24/06/2021 16:55:20.579 |info|live.PropsSet(object::mdelay.delete_on_close,true) [Start]
24/06/2021 16:55:20.579 |info|live.PropsSet(object::mdelay.buffer_duration,0) [Start]
24/06/2021 16:55:20.579 |info|live.PropsSet(object::mdelay.buffer_size_mem,200M) [Start]
Further information
Further helpful information for reading Etere logs can be consulted in the following chapters:
•Automation commands
•Used constants