Sniffer on OSX - revisited

RE: Sniffer on OSX - revisited

kalauffenburger — Wed, 11 Jul 2018 14:27:32 GMT

Ok, I tried all three of the above suggestions. So far no luck.

The last thing I tried was reverting the Wireshark version back to v2.0.x, as recommended in the "OS X Sniffer for BTLE" link. In all cases, the nRF Sniffer capture interface does not show up in the interfaces list. Also, there is not an interface toolbar available under the View menu as described in the v2.1 User Guide. See the attached screenshot of the Wireshark window.

Also, I have verified using minicom that packet data is arriving on the /dev/tty.usbmodem1411 interface from the pca10040 board.

RE: Sniffer on OSX - revisited

David Elvig — Mon, 07 May 2018 00:43:36 GMT

I've verified the fix by running through a use case from Mohammad Afeneh's Bluetooth LE eBook for using the sniffer with Wireshark. All looks good.

WireShark "sees" the nrf_sniffer on start-up, and the subsequent steps in Mohamad's tutorial, and in the nRF_Sniffer_User_Guide_v2.1.pdf work as expected.

Now I have the WireShark learning curve... and am thankful to get on to it.

Thanks to those that helped, particularly Richard and David Edwin in this thread!

The fix is a bit of a hack, it seems, and I'll look forward to staying in touch on how to standardize the setup - either by explicit documentation of this work-around in the nRF_Sniffer_User_Guide_v2.X.pdf, or in a update that allows "latest versions" default installation options for required software.

Thanks again!

RE: Sniffer on OSX - revisited

David Elvig — Sat, 05 May 2018 17:12:41 GMT

Python version

Davids-MacBook-Pro-2:~ davidelvig$ python --version
Python 2.7.14

Which
Davids-MacBook-Pro-2:~ davidelvig$ which python
/Library/Frameworks/Python.framework/Versions/2.7/bin/python

In that ...\bin directory is:

lrwxr-xr-x  1 root        admin     6B Mar 15 12:41 2to3 -> 2to3-2
lrwxr-xr-x  1 root        admin     8B Mar 15 12:41 2to3-2 -> 2to3-2.7
-rwxrwxr-x  1 root        admin   140B Sep 16  2017 2to3-2.7
-rwxrwxr-x  1 root        admin   310B Mar 15 12:42 easy_install
-rwxrwxr-x  1 root        admin   310B Mar 15 12:42 easy_install-2.7
lrwxr-xr-x  1 root        admin     5B Mar 15 12:41 idle -> idle2
lrwxr-xr-x  1 root        admin     7B Mar 15 12:41 idle2 -> idle2.7
-rwxrwxr-x  1 root        admin   138B Sep 16  2017 idle2.7
-rwxr-xr-x  1 davidelvig  admin    33K Mar 23 21:57 miniterm.py
-rw-r--r--  1 davidelvig  admin    37K Mar 23 21:57 miniterm.pyc
-rwxr-xr-x  1 davidelvig  admin   282B Mar 23 21:57 pip
-rwxr-xr-x  1 davidelvig  admin   282B Mar 23 21:57 pip2
-rwxr-xr-x  1 davidelvig  admin   282B Mar 23 21:57 pip2.7
lrwxr-xr-x  1 root        admin     6B Mar 15 12:41 pydoc -> pydoc2
lrwxr-xr-x  1 root        admin     8B Mar 15 12:41 pydoc2 -> pydoc2.7
-rwxrwxr-x  1 root        admin   123B Sep 16  2017 pydoc2.7
lrwxr-xr-x  1 root        admin     7B Mar 15 12:41 python -> python2
lrwxr-xr-x  1 root        admin    10B Mar 15 12:41 python-32 -> python2-32
lrwxr-xr-x  1 root        admin    14B Mar 15 12:41 python-config -> python2-config
lrwxr-xr-x  1 root        admin     9B Mar 15 12:41 python2 -> python2.7
lrwxr-xr-x  1 root        admin    12B Mar 15 12:41 python2-32 -> python2.7-32
lrwxr-xr-x  1 root        admin    16B Mar 15 12:41 python2-config -> python2.7-config
-rwxrwxr-x  1 root        admin    25K Sep 16  2017 python2.7
-rwxrwxr-x  1 root        admin    14K Sep 16  2017 python2.7-32
-rwxrwxr-x  1 root        admin   1.7K Sep 16  2017 python2.7-config
lrwxr-xr-x  1 root        admin     8B Mar 15 12:41 pythonw -> pythonw2
lrwxr-xr-x  1 root        admin    11B Mar 15 12:41 pythonw-32 -> pythonw2-32
lrwxr-xr-x  1 root        admin    10B Mar 15 12:41 pythonw2 -> pythonw2.7
lrwxr-xr-x  1 root        admin    13B Mar 15 12:41 pythonw2-32 -> pythonw2.7-32
-rwxrwxr-x  1 root        admin    25K Sep 16  2017 pythonw2.7
-rwxrwxr-x  1 root        admin    14K Sep 16  2017 pythonw2.7-32
lrwxr-xr-x  1 root        admin     9B Mar 15 12:41 smtpd.py -> smtpd2.py
-rwxrwxr-x  1 root        admin    18K Sep 16  2017 smtpd2.7.py
lrwxr-xr-x  1 root        admin    11B Mar 15 12:41 smtpd2.py -> smtpd2.7.py

After my latest edit, the top of the nrf_sniffer.py looks like this

#!/usr/local/bin/python2
#####!/usr/bin/env python

# Copyright (c) 2017, Nordic Semiconductor ASA
#
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without

A listing of /usr/local/bin is as follows:

lrwxr-xr-x  1 root        wheel    66B Mar 15 12:41 2to3 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/2to3 wheel    68B Mar 15 12:41 2to3-2 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/2to3-2 wheel    70B Mar 15 12:41 2to3-2.7 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/2to3-2.7 wheel    47B Apr  2 09:59 JFlashLite -> /Applications/SEGGER/JLink_V630j/JFlashLite.app wheel    47B Apr  2 09:59 JFlashLite.app -> /Applications/SEGGER/JLink_V630j/JFlashLite.app wheel    42B Apr  6 12:47 JFlashSPI -> /Applications/SEGGER/JLink_V616c/JFlashSPI wheel    41B Apr  6 12:47 JLinkExe -> /Applications/SEGGER/JLink_V616c/JLinkExe wheel    47B Apr  6 12:47 JLinkGDBServer -> /Applications/SEGGER/JLink_V616c/JLinkGDBServer wheel    51B Apr  2 09:59 JLinkGDBServer.app -> /Applications/SEGGER/JLink_V630j/JLinkGDBServer.app wheel    52B Apr  2 09:59 JLinkGDBServerCL -> /Applications/SEGGER/JLink_V630j/JLinkGDBServerCLExe wheel    56B Apr  6 12:47 JLinkLicenseManager.app -> /Applications/SEGGER/JLink_V616c/JLinkLicenseManager.app wheel    47B Apr  6 12:47 JLinkRTTClient -> /Applications/SEGGER/JLink_V616c/JLinkRTTClient wheel    47B Apr  6 12:47 JLinkRTTLogger -> /Applications/SEGGER/JLink_V616c/JLinkRTTLogger wheel    54B Apr  6 12:47 JLinkRegistration.app -> /Applications/SEGGER/JLink_V616c/JLinkRegistration.app wheel    50B Apr  6 12:47 JLinkRemoteServer -> /Applications/SEGGER/JLink_V616c/JLinkRemoteServer wheel    54B Apr  2 09:59 JLinkRemoteServer.app -> /Applications/SEGGER/JLink_V630j/JLinkRemoteServer.app wheel    55B Apr  2 09:59 JLinkRemoteServerCLExe -> /Applications/SEGGER/JLink_V630j/JLinkRemoteServerCLExe wheel    43B Apr  6 12:47 JLinkSTM32 -> /Applications/SEGGER/JLink_V616c/JLinkSTM32 wheel    47B Apr  6 12:47 JLinkSWOViewer -> /Applications/SEGGER/JLink_V616c/JLinkSWOViewer wheel    44B Apr  6 12:47 JTAGLoadExe -> /Applications/SEGGER/JLink_V616c/JTAGLoadExe 1 davidelvig  admin    28B Feb 22 20:20 brew -> /usr/local/Homebrew/bin/brew admin    11B Mar 23 22:45 capinfos -> ./wireshark admin    11B Mar 23 22:45 dftest -> ./wireshark admin    11B Mar 23 22:45 dumpcap -> ./wireshark admin    74B Mar 15 12:42 easy_install -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/easy_install admin    78B Mar 15 12:42 easy_install-2.7 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/easy_install-2.7 admin    11B Mar 23 22:45 editcap -> ./wireshark 1 davidelvig  admin    33B Feb 22 20:42 ffmpeg -> ../Cellar/ffmpeg/3.4.2/bin/ffmpeg 1 davidelvig  admin    34B Feb 22 20:42 ffprobe -> ../Cellar/ffmpeg/3.4.2/bin/ffprobe 1 davidelvig  admin    35B Feb 22 20:42 ffserver -> ../Cellar/ffmpeg/3.4.2/bin/ffserver wheel    66B Mar 15 12:41 idle -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/idle wheel    67B Mar 15 12:41 idle2 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/idle2 wheel    69B Mar 15 12:41 idle2.7 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/idle2.7 1 davidelvig  admin    29B Feb 22 20:42 lame -> ../Cellar/lame/3.100/bin/lame admin    11B Mar 23 22:45 mergecap -> ./wireshark 1 davidelvig  admin    29M Aug  1  2017 node staff    38B Aug  4  2017 npm -> ../lib/node_modules/npm/bin/npm-cli.js admin    65B Mar 15 12:42 pip -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/pip admin    66B Mar 15 12:42 pip2 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/pip2 admin    68B Mar 15 12:42 pip2.7 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/pip2.7 wheel    67B Mar 15 12:41 pydoc -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/pydoc wheel    68B Mar 15 12:41 pydoc2 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/pydoc2 wheel    70B Mar 15 12:41 pydoc2.7 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/pydoc2.7 wheel    68B Mar 15 12:41 python -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/python wheel    71B Mar 15 12:41 python-32 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/python-32 wheel    75B Mar 15 12:41 python-config -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/python-config wheel    69B Mar 15 12:41 python2 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/python2 wheel    72B Mar 15 12:41 python2-32 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/python2-32 wheel    76B Mar 15 12:41 python2-config -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/python2-config wheel    71B Mar 15 12:41 python2.7 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 wheel    74B Mar 15 12:41 python2.7-32 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7-32 wheel    78B Mar 15 12:41 python2.7-config -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7-config wheel    69B Mar 15 12:41 pythonw -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/pythonw wheel    72B Mar 15 12:41 pythonw-32 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/pythonw-32 wheel    70B Mar 15 12:41 pythonw2 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/pythonw2 wheel    73B Mar 15 12:41 pythonw2-32 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/pythonw2-32 wheel    72B Mar 15 12:41 pythonw2.7 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/pythonw2.7 wheel    75B Mar 15 12:41 pythonw2.7-32 -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/pythonw2.7-32 admin    11B Mar 23 22:45 randpkt -> ./wireshark admin    11B Mar 23 22:45 rawshark -> ./wireshark wheel    70B Mar 15 12:41 smtpd.py -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/smtpd.py wheel    73B Mar 15 12:41 smtpd2.7.py -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/smtpd2.7.py wheel    71B Mar 15 12:41 smtpd2.py -> ../../../Library/Frameworks/Python.framework/Versions/2.7/bin/smtpd2.py admin    11B Mar 23 22:45 text2pcap -> ./wireshark admin    11B Mar 23 22:45 tshark -> ./wireshark wheel   833B Feb 23 14:00 wireshark 1 davidelvig  admin    29B Feb 22 20:42 x264 -> ../Cellar/x264/r2854/bin/x264

RE: Sniffer on OSX - revisited

David Edwin — Sat, 05 May 2018 16:19:53 GMT

Can you also provide the output of "which python" ?

RE: Sniffer on OSX - revisited

David Elvig — Sat, 05 May 2018 14:09:01 GMT

My python version is (and has been throughout) 2.7.14 as display now below:

Davids-MacBook-Pro-2:~ davidelvig$ python --version
Python 2.7.14

I posted that step way back ups in this thread.

The only change I made recently, based on the post by @Richard was to edit the top of nrf_sniffer.py

I've been delayed in my end-to-end testing, but still plan to do that in the coming days

Thanks, all for your posts!

RE: Sniffer on OSX - revisited

David Edwin — Fri, 04 May 2018 07:41:03 GMT

Would this have been caught if the the "python --version" as requested in nRF Sniffer User guide v2.1 was verified ?

Install nRF Sniffer Step 6.

C:>python --version
Python 2.7.x

RE: Sniffer on OSX - revisited

David Elvig — Thu, 03 May 2018 19:47:18 GMT

Wow! This appears to be the magic bullet. With that one change to the nrf_sniffer.py file, I now see this when launching Wireshark.

I'll check this more thoroughly tomorrow, end-to-end, and with the otherwise-default installation options.

Thanks a million! I'll validate the answer after that checking.

RE: Sniffer on OSX - revisited

Richard — Thu, 03 May 2018 16:30:27 GMT

I was having issues with Wireshark not showing the extcap interface in it's UI on Mac OS X 10.13.5, even though the files were in the correct location, inside the .app /Applications/Wireshark.app/Contents/MacOS/extcap/

While trying to debug the issue, i decided to run wireshark directly from my shell to see any possible output via /Applications/Wireshark.app/Contents/MacOS/Wireshark

Turns out, this was enough to get nrf_sniffer.py to load, so if you've been having trouble getting it to load, it might be worth running the executable directly from Terminal.app

I suspect it has something to do with environment variables that Wireshark inherits from the shell, but haven't debugged further.

EDIT: Turns out, the best way to fix this so regular app launches work was to change the shebang at the top of nrf_sniffer.py to point directly to your local python2 instance. For me, this was #!/usr/local/bin/python2

RE: Sniffer on OSX - revisited

David Elvig — Tue, 01 May 2018 16:19:54 GMT

OK, I've run the above with no luck on either board.

I'm wondering where to go next.

I've been through the steps many times.

Are others experiencing this problem?
Is so, what is your environment?

RE: Sniffer on OSX - revisited

David Elvig — Tue, 01 May 2018 03:15:57 GMT

OK. I'll try that tomorrow (Tuesday US Central time) with:
- Python 2.7.14
- pyserial (3.2.1)
- SEGGER J-Link Commander V6.16c (Compiled Jun 16 2017 18:19:39)
DLL version V6.16c, compiled Jun 16 2017 18:19:20
- WireShark Mac OS Version 2.4.5

In separate sessions, I'll use each device (nRF dongle-PCA10031 and DK-PCA10040) and flash them using the appropriate parameters in JLINKEXE to "erase..." as in the Sniffer 2.1 User Guide.

Then in OSX Terminal, I'll run "screen <port> 460800"
and report the results.

Have I got it?

Thanks

RE: Sniffer on OSX - revisited

David Edwin — Mon, 30 Apr 2018 14:17:30 GMT

Can you try the screen option on all the the DKs that you have, I see that a PCA10031 and a PCA10040 were mentioned.

RE: Sniffer on OSX - revisited

David Elvig — Thu, 26 Apr 2018 16:07:35 GMT

Thanks for working on this, David Edwin!

I've copied the contents of your new code into the ...\extcap folder
no change in visibility of the interface in WireShark.

I ran through the "Troubleshooting" steps in nRF_Sniffer_User_Guide_v2.1.
All steps gave appropriate success results, except "screen port 460800" (same blank, unresponsive screen) and WireShark - with no evidence of the interface.

I'm still open for a screen-share - 24/7.

Thanks again!

Dave

RE: Sniffer on OSX - revisited

David Edwin — Thu, 26 Apr 2018 13:09:27 GMT

David Elvig

I have placed a patched sniffer python fileset that could fix this for you in my original answer. Can you try it and let me know if this is fixed.

RE: Sniffer on OSX - revisited

David Edwin — Mon, 23 Apr 2018 13:37:13 GMT

Can you also ensure that you have an advertiser running in the neighbourhood ? You can get the advertiser running using nRF connect or some other BTLE application on the phone.

RE: Sniffer on OSX - revisited

David Elvig — Fri, 20 Apr 2018 14:21:11 GMT

I have run the MSDDisable command (and alternatively MSDEnable) on both OSX and Windows 7, getting "Probe Configured Successfully" in all cases.

I do see that the USB drive representing the dongle goes away after the MSDDisable and reappears with MSDEnable.

After running MSDDisable, I get the same non-response from the terminal apps:

On OSX using "screen cu.usbmodem1461 460800" I get a screen window with no characters as before

On Windows using puTTY, connecting to "COM18"- the JLink USB serial port at 460800, I get a similar result... a blank terminal window with no response to typing and no characters displayed (and no apparent way to exit the terminal session)

RE: Sniffer on OSX - revisited

David Edwin — Fri, 20 Apr 2018 09:38:34 GMT

We need to see some characters on the screen when connecting to the board from OS X.

"screen <port> 460800"

If that does not happen then

Action 1:
we need to do this in addition (we will attempt to disable the mass storage device to see if this improves the situation.

Action 2:

We attempt to see the characters when connecting to the board on windows. In addition can you connect to the board in Windows using termite or other terminal application at 460800 to verify that the port is accessible and that characters are coming out of it.

RE: Sniffer on OSX - revisited

Kristian Sylwander — Fri, 20 Apr 2018 07:59:31 GMT

I tried this with a Windows machine as well. Worked on the first try. So there's something strange with the OSX version.

OS Version: Windows 10 Pro 64 bit
Wireshark version: 2.4.2
Python version: 2.7.14
Pyserial version: 3.4

Segger jlink version on PC: 6.16c
Segger jlink version or build date on the jlink emulator on nRF5x-DK: ??????

PCA board number:
- PCA10040 (Dev Kit)

RE: Sniffer on OSX - revisited

Kristian Sylwander — Thu, 19 Apr 2018 06:03:06 GMT

I've manage to get hold off an old macbook pro in order to mimic the settings David Edwin suggested.

OS X 10.11.6
Wireshark : 2.4.1 (also tried 2.4.2 and the latest 2.4.6)
python 2.7.14 (installed with brew, could not find a way to install 2.7.10 using brew.)
pyserial 3.2.1
nRF Sniffer v2 Beta 1

PCA10040

Segger jlink 6.16c

Still the interface does not pop up in Wireshark. This is starting to be a bit frustrating now.

RE: Sniffer on OSX - revisited

David Elvig — Fri, 13 Apr 2018 00:31:43 GMT

I've done all but the minicom step. I ran the Windows j-Link Configurator and it shows this screen

as in the sniffer 2.0 documentation

I ran j-Link Commander and with exec invalidatefw I get this

I said "no" since I think we're trying to stay on older builds... That said, I'm typing commands that I don't fully understand (I don't understand all of the layers involved)

I expect my hardware is working (both the dongle (PCA10031) and the Dev Kit (PCA10040)). I can use the dongle without trouble using nRFConnect on the Mac, and the DK works well with example SDK apps, and my own MIDI BLE app.

I've stayed on the 6.16c version throughout (on Mac and Win)

I did not easily find how to install minicom on the Mac.

I did flash the Dev Kit board using the nRF52832_XXAA parameter to "erase"

No difference in Wireshark visibility.

Is there a chance of a screen-share where you could look over my shoulder, @David Edwin?

I expect it's a missed step on my part... I have two hardware options to try, and access to all of the various permutations of j-link, segger and Wireshark.

I'm available any time around the clock to make that happen (and have WebEx available for screen-sharing)

RE: Sniffer on OSX - revisited

David Edwin — Wed, 11 Apr 2018 07:11:44 GMT

That is a problem, can you try with other terminal programs like minicom and open the port at 460800. You need to see something on the UART. Turn on the hardware flow control if possible.

Actions:

1. Can you verify that the board is indeed working by flashing some example program like ble_app_uart and running those examples.

2, Can you also try with a different board

3. Specify the board PCA10040 and the PCA10031 version numbers ?

4. Please stay on jlink 6.16c on the jlink emulator for all the experiments and actions.

Edit: Additional Action:

I checked if the jlink 6.16c for OS X and Windows are bundling the identical version of the jlink emulator firmware they are NOT. If you have a windows PC can you install jlink 6.16c and use the exec invalidatefw to set the jlink emulator firmware to what was bundled with jlink 6.16c for windows. Then use the board with OS X. Let me know if this is possible for you.

Edit : ping

RE: Sniffer on OSX - revisited

David Elvig — Tue, 10 Apr 2018 13:58:16 GMT

Thanks for your patience.

I get the same result as above with

"screen cu.usbmodem1461 460800"

Dave

RE: Sniffer on OSX - revisited

David Edwin — Tue, 10 Apr 2018 06:13:05 GMT

The baud rate I suggested was 460800 (not 46800 as I see in your screen shot).
Please connect to the port at 460800 and see if you are getting characters on the "screen".

Thanks

RE: Sniffer on OSX - revisited

David Elvig — Mon, 09 Apr 2018 15:39:14 GMT

I've done the following:
- Identified the serial port with this partial ls from \dev:

cu.Bluetooth-Incoming-Port	ttyv0
cu.LGHBS760-CSRGAIA		ttyv1
cu.MALS				ttyv2
cu.SOC				ttyv3
cu.usbmodem1451061		ttyv4
cu.usbmodem1461			ttyv5
disk0				ttyv6
disk0s1				ttyv7

It is the "cu.usbmodem1461" entry that appear/disappears with plugging/unplugging the dongle

I typed the following into Terminal:
screen cu.usbmodem1461 46800

...resulting in:

No typed keystrokes show, and it responds only to the Ctrl-a-Ctrl-k command to quit.

RE: Sniffer on OSX - revisited

David Edwin — Mon, 09 Apr 2018 08:48:15 GMT

did you actually give the right path to the UART, it is usually in /dev .

Verify that by using the "screen <port> 460800", you should see some characters on the screen.

RE: Sniffer on OSX - revisited

David Elvig — Fri, 06 Apr 2018 17:52:30 GMT

Davids-MacBook-Pro-2:extcap davidelvig$ ./nrf_sniffer.py --extcap-interfaces
extcap {version=2.0.0}{display=nRF Sniffer}{help=http://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF-Sniffer#Downloads}
control {number=0}{type=selector}{display=Device}{tooltip=Device list}
control {number=1}{type=string}{display=Passkey / OOB key}{tooltip=6 digit temporary key or 16 byte Out-of-band (OOB) key in hexadecimal starting with '0x', big endian format. If the entered key is shorter than 16 bytes, it will be zero-padded in front'}{validation=\b^(([0-9]{6})|(0x[0-9a-fA-F]{1,32}))$\b}
control {number=2}{type=string}{display=Adv Hop}{default=37,38,39}{tooltip=Advertising channel hop sequence. Change the order in which the siffer switches advertising channels. Valid channels are 37, 38 and 39 separated by comma.}{validation=^\s*((37|38|39)\s*,\s*){0,2}(37|38|39){1}\s*$}{required=true}
control {number=3}{type=button}{role=help}{display=Help}{tooltip=Access user guide (launches browser)}
control {number=4}{type=button}{role=restore}{display=Defaults}{tooltip=Resets the user interface and clears the log file}
control {number=5}{type=button}{role=logger}{display=Log}{tooltip=Log per interface}
value {control=0}{value= }{display=All advertising devices}{default=true}
Davids-MacBook-Pro-2:extcap davidelvig$