Logging and the Arena SDK  

If you request assistance from the LUCID support team regarding your Arena SDK application, you may be asked to provide logs. This knowledge base describes how to retrieve and/or create these logs. 

Lucid Lightweight Filter log 

This log stores the information that the Lucid Lightweight Filter sees. To initiate logging, run the following executable file, which is available in the folder c:\Program Files\LUCID Vision Labs\Arena SDK\x64Release. You can copy this file to your Arena SDK application folder. 

DumpDriverLog_v140.exe output.log 

Logging for libraries and GenTL  

To add logging at the library level and GenTL level, add a file called lucid_log.conf located in the ArenaView installation location (default location is C:\ProgramData\LUCID Vision Labs\ArenaView) to your Arena SDK application folder. This configuration file is the same one used to configure logging for ArenaView. 

Wireshark logs 

You may be asked for Wireshark logs by the LUCID support team. Wireshark is an open-source packet detection tool. For the purposes of logging, however, we use Wireshark to display packet logs captured by other network analysis tools. 

• In Windows, we use Packet Monitor (pktmon). 
• In Linux, we use tcpdump. 

How capture network traffic in Windows using pktmon:  

1. List the components used on your machine using the following command in command prompt:

   pktmon comp list  

2. From the resulting list, determine the ID of the Ethernet adapter that is connected to your camera. 
3. Start pktmon using the ID that you found using the following command (12 in the example below):

   pktmon start --etw --pkt-size 256 --comp 12

   Note: The pkt-size switch configures how many bytes to capture. The default is 128 bytes. 

4. Use ArenaView or your Arena SDK application to capture images, video, etc. from the camera. 
5. Stop logging using the following command:

   pktmon stop

   This command causes pktmon to stop capturing packets and places the information about the packets in an etl file (PktMon.etl by default). 

6. Convert the etl file to a Wireshark-readable format using the command below.

   pktmon pcapng PktMon.etl -o PktMon.etl.pcapng 

You can send this file (PktMon.etl.pcapng) to the LUCID Team. 

How to capture network traffic in Linux: 

• To use the tcpdump tool to obtain packet logs in Linux the interface enp4s0, use the following command:

  sudo tcpdump -i enp4s0 -w output.pcap 

• To do the same as the previous step but specify the number of bytes captured in the packet, use this command:

  sudo tcpdump -i enp4s0 -s 256 -w output.pcap

  Note: By default,  tcpdump captures 68 bytes for IPv4 packets and 96 bytes for IPv6 packets. 

• To stop recording, press Ctrl-C. 

To open the log file in Wireshark: 

The methods used above result in a pcap file or pcapng file that can be opened and viewed in Wireshark. Double-click on the pcap/pcapng file to open it. Wireshark opens showing the history of communication with the camera. 

You will notice that most of the packets are of the type GVSP (GigE Vision Streaming Protocol) or GVCP (GigE Vision Control Protocol). 

• GVCP packets: These packets deal with the SDK controlling the camera. Usually, they are changes to the camera registry followed by an acknowledgement from the camera. 
• GVSP packets: These packets contain image data. Each image corresponds to 1 block. Each block is made up of a leader, multiple packets, and a trailer. These packets should be in roughly sequential order. Any gaps in the packets indicate there is a problem.   

If you capture packets from a video stream, you will notice it is made up of multiple sequentially numbered blocks (images).