Log files, written by Etere Sarvaj, hold traces of all the commands sent and received by the software, to the running of the commutation, managed through the protocol UDP. Sarvaji logs are saved in local in the directory
C:\(or in another local drive)\Program Files\Etere\Logs and they can be compressed, whit the appropriate function Save Logs (the zip file is saved in the same directory).
To interpret logs, created by Etere Sarvaj, it is important to set the logs files generation in ASCII characters, rather than hexadecimal, to make the contents of the logs less cryptic.
When we have done that, we have to see how to interpret the logs:
In Sarvaj log, if the device sends an answer to the controller, to one controller command correspond 5 or more lines on the log:
.Type A lines: show the communication start between controller and device: hold something like UdpReceive from <IP address> <IP port> <Sarvaj channel> and show at the same time that Sarvaji has received one string, from the controller, at the address and Com indicated on one of the its 16 reception Udp channels.
.Type B lines: follow type A, hold Rx: and finish with ip address and one number: show that sarvaj received a string from the controller, with the said ip address and the said Com.
.Type C lines: follow type B, hold Tx; and finish with COM x: show the string sent to the said com (to which the device is connected) from Sarvaj.
.Type D lines: present only when the device sends an answer; follow the type C, hold Rx: and finish with COMx: show the string received on the com in question from Sarvaj.
.Type E lines: present only when the device sends an answer; follow the Type D, hold Tx: and finish with an ip address and a Com: show the string sent to Sarvaj to the controller, with the IP address and the Com.
If the device answer is too long, on the log you can find something like this:
A
B
C
D
E
D
E
...
D
E
- The strings which start with Tx and finish with COM...(They are the strings sent to Sarvaj on the serial, then sent to the device). Clearly the contents of these strings depend on the protocol. With this protocol the device checked by Sarvaj is then checked.
In this situation, the device is a Leitch with Pass through protocol
- In the situation with the protocol in question
. if the strings hold sub strings type @ P:L/D,S [0D] [0A] these sub strings recognize a preset command : L is the level in hex (0-F), D is the out channel out (in hex and numbered from 0), and S is the in channel (in hex and numbered from 0). Then a string like:
@ B:C [0D] [0A] @ P:0/0044,003B [0D] [0A] @ P:1/0044,003B [0D] [0A] @ P:2/0044,003B [0D] [0A] @ P:3/0044,003B [0D] [0A] @ P:4/0044,003B [0D] [0A] @ P:5/0044,003B [0D] [0A] @ P:6/0044,003B [0D] [0A] @ P:7/0044,003B [0D] [0A]
recognize the preset on levels 0 to 7 of the entrance 44 (=68) on the exit 3B (=59)
. if the strings hold @ B:E [0D] [0A] recognize a Take of the preset previously planned out