ANDi Frequently Asked Questions

Error recognizing CRC signal
Fire_event function misbehavior
The function "start_capture", the Traffic Viewer and the PCAP Player aren't able to read pcap files
Channels configuration lost
Start capture in scripting environment does nothing
Receive and receive_list methods doesn't work
How to import external python modules?
Newly plugged adapter is not detected by ANDi
ANDi is not transmitting frames using Vector devices
ANDi decodes TCP based messages twice
ANDi crashes after script's execution
The script's execution leads to memory leak
Packet loss detected
WinPcap is not working properly
Adapters cannot be configured
Blue screen

Error recognizing CRC signal 

User could do as first check a database review to be sure that the signal exists and have the CRC flag.

Fire_event function misbehavior 

Fire Event/Field requires a correct subscription between ECUs:
- The service has an Event Group
- The Event/Field in question explicitly belongs to an Event Group
- A SOME/IP-SD "Subscribe Event Group ACK" took place for the Event Group
- The subscription has not expired (subscription time + TTL < now)

The function "start_capture", the Traffic Viewer and the PCAP Player aren't able to read pcap files 

ANDi supports pcap files but not pcapng. Changing the extension is not changing the format.
Please save *.pcapng as *.pcap by Wireshark.

Channels configuration lost 

Channels configuration is not saved in the ATP, it's saved in tmp/project_name.

Start capture in scripting environment does nothing 

The on_message_received handler attribution should be done before the start capture call as follows:

# create call back function
def callback_function(msg):
        print(msg)

# Set the handler
message.on_message_received += callback_function

# Start the capture
message.start_capture()

Receive and receive_list methods doesn't work 

Please check the IP addresses and ports numbers.

How to import external python modules?

import sys
# Specify the directory that contains the python module file
sys.path.append(some_directory_path)

Newly plugged adapter is not detected by ANDi 

The new adapter needs to be registered in the WinPcap driver, a restart of the driver (or the entire PC) is required.
To restart the WinPcap driver:
- Close all instances of ANDi and Wireshark.
- Run below commands from command line as administrator:
  net stop npf net start npf
If restarting the WinPcap driver does not work, restart the PC.

ANDi is not transmitting frames using Vector devices 

This behavior happens when making loop-back with Vector hardware between two channels and using only one channel for sending and receiving can messages.
Sender and receiver should use different channels.

ANDi decodes TCP based messages twice 

Just remove message.start_capture() and message.stop_capture() from _send_diag_command. There is no need for start_capture() when using connect().

ANDi crashes after script's execution 

Please do not use recursive calls that leads to stack overflow exception:

# create recursive method
def myfucntion():
        myfucntion()
        return

# call the recursive method
myfucntion()

The script's execution leads to memory leak 

See Writing clean scripts

Packet loss detected 

This is coming from an automatic ANDi thread, that monitor the running adapters for packet loss. The packet loss is usually detected by the WinPcap driver itself.
A bit of explanation:
- The WinPcap driver captures raw packets passing through a network interface. The packets have to be parsed and filtered, and that takes some time, so incoming packets have to be buffered (queued) for processing.
- Sometimes there are too many packets, they are saved to a buffer, but they are saved faster than processed, so eventually the buffer runs out of space, so the kernel drops all further packets until there is some free space in the buffer.
Usual Reasons:
- You are sending packets faster than what the adapter/driver could process
- Some adapter models/drivers are faulty and cause the problem to happen more often that it should. (example: using the slower USB 2.0 connector for a stress test)
- Duplex mismatch
- The problem simply could not be avoided, Windows is not a real time OS, and it gives equal chances to all threads to run. This usually does not happen often if the hardware/CPU is fast enough.
- Some other software on the server (Firewall or CPU intensive application) is delaying the packets processing.
This can be avoided when it is caused by a packet length which is higher than MTU. In that case, user needs to configure sender and receiver to support Jumbo Frames as detailed below :
- Change the MTU using this command line
  netsh interface ipv4 set subinterface "Your Interface Name" mtu=1550 store=persistent
- Activate Jumbo Frames in the Device Manager

WinPcap is not working properly 

Adapters cannot be configured 

Blue screen 

These problems may, most likely, occur from Npcap. In fact, since Npcap is not officially supported by ANDi, we strongly recommend not to install it while using ANDi Tools.
Unless you have to, try to install Npcap 0.996 or prior versions and make sure to check the option
- Install Npcap in WinPcap API-compatible Mode

Please take into consideration that Npcap can cause other problems. You can find, in link below, bugs caused by Npcap: https://github.com/nmap/nmap/issues?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug.

If needed, you can install WinPcap from https://files.technica-engineering.de/ANDi/Redistributables/.