AnsweredAssumed Answered

81150A LAN remote control problem

Question asked by llemish on Nov 12, 2017
Latest reply on Nov 13, 2017 by hognala

We are using LAN remote control of the 81150A and a few other Keysight devices. There is a local network and socket is used for 81150A control.

While we were using Windows 7 and socket implementation for Python3, response time for the 81150A was around 0.2-0.5 sec. Nowadays we has changed OS from Windows 7 to Linux Mint, and the response time is increased to 3.5 sec.

Problem analyze showed that increase only the time before first command apply. If there are a few commands that were sent one by one to the 81150A we can see around 3 sec delay only before fist command apply, time of reaction on other commands from the list are the same like it was during Windows 7 using.

Except Linux Mint, Raspbian were tried with the same result.

 

Update1:

The problem is 2-3 seconds delay before the first command start to work, when I use LAN remote control of the waveform generator 81150A from Linux PC. There is no such problem if to use Windows PC, neither for remote control of PNA-L and PXI instruments using  Linux. For communication i use Python 3 with socket library.
I use tcpdump for analyze net behavior, and results show, that the delay is a problem of the opening the connection.
Lower there is a log of tcpdump, there Linux PC has IP: 192.168.0.2, and the 81150A IP: 192.168.0.98
12:28:41.631956 IP 192.168.0.2.45680 > 192.168.0.98.5025: Flags [S], seq 95620863, win 29200, options [mss 1460,sackOK,TS val 4768440 ecr 0,nop,wscale 7], length 0
12:28:41.632239 IP 192.168.0.98.5025 > 192.168.0.2.45680: Flags [S.], seq 138345035, ack 95620864, win 33580, options [mss 1460,nop,wscale 0,nop,nop,TS val 0 ecr 0,nop,nop,sackOK], length 0
12:28:41.632302 IP 192.168.0.2.45680 > 192.168.0.98.5025: Flags [.], ack 1, win 229, options [nop,nop,TS val 4768440 ecr 0], length 0
12:28:41.637438 IP 192.168.0.2.45680 > 192.168.0.98.5025: Flags [F.], seq 1, ack 1, win 229, options [nop,nop,TS val 4768442 ecr 0], length 0
12:28:41.637622 IP 192.168.0.98.5025 > 192.168.0.2.45680: Flags [.], ack 2, win 33580, options [nop,nop,TS val 193608 ecr 4768442], length 0
12:28:41.651694 IP 192.168.0.98.1211 > 192.168.0.2.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; UNICAST
12:28:41.651730 IP 192.168.0.2 > 192.168.0.98: ICMP 192.168.0.2 udp port netbios-ns unreachable, length 86
12:28:43.651667 IP 192.168.0.98.1212 > 192.168.0.2.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; UNICAST
12:28:43.651731 IP 192.168.0.2 > 192.168.0.98: ICMP 192.168.0.2 udp port netbios-ns unreachable, length 86
12:28:45.660490 IP 192.168.0.98.5025 > 192.168.0.2.45680: Flags [F.], seq 1, ack 2, win 33580, options [nop,nop,TS val 193647 ecr 4768442], length 0
12:28:45.660547 IP 192.168.0.2.45680 > 192.168.0.98.5025: Flags [.], ack 2, win 229, options [nop,nop,TS val 4769447 ecr 193647], length 0
So base on timing, the delay appears after the waveform generator sends UDP NetBIOS request. As i could find, NetBIOS is the specifically Windows protocol, and by default is not supported by Linux.
I checked traces of another Keysight instruments, what we use in laboratory, and none form other devices has the NetBIOS request.
Is it possible somehow to switch the NetBIOS query off for 81150A?

 

 

Thank you for help.

Outcomes