Table of content

Supported Setup

The CLI Flasher is designed to work over Ethernet in a point-to-point connection and

• not in network with office PC (requests from the office PC to the netX can disturb the CLI Flasher communication) and
• without any switch / hub inbetween.

A supported setup could look like this:

We continue to improve the stability for the point-to-point connection.

Discovered issues

We discovered the following issue during internal tests. There maybe other issues as well, if the connection is NOT a point-to-point connection or other traffic is generated via the used Ethernet adapter.

Simultainously started CLI Flasher commands can fail

A CLI Flasher instance can fail to detect a netX over Ethernet, if multiple CLI Flasher instances are running at the same time.

Maybe the netX not react to all detection requests, if multiple are sent by the PC at the same time. 

The issue can reliably be seen with the following setup:

Four netX 90 are connected to the Ethernet port of a test PC via a switch.

On the test PC there are four CLI Flasher instances running at the same time, each attempting to access a specific netX 90 on the Ethernet connection.

If the CLI Flasher instances all execute a detect_netx or list_interfaces command at the same time, a netX might not respond to one of the detection requests sent by the CLI Flashers.

This issue can occur when starting any command which interacts with a netX in this manner as all execute a list_interfaces first. This detection handling is done internally in the CLI Flasher and required before accessing a netX hardware.

Workaround

Introducing a slight delay (>0.1 seconds) between CLI Flasher commands will prevent this issue.

Use the WFP command to reduce the number of CLI Flasher start sequences. (Anschauen Freddy)