This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Python scripting with master emulator to make sniffer

Hello,

I would like to build a tool in Python that allows sniffing/interaction with BLE traffic between nRFgo modules (nRF51822) and a Mac via the master emulator. I am looking for an alternative to using an iOS device simulator all the time. I want something like this:

code.google.com/.../

I am guessing that the Master Emulator looks like a virtual com port? Is the source code available to help me do this? I would just need to know what needs to be sent along the VCOM between Mac and emulator and I can use pySerial to do the rest.

I see the dlls in C:\Program Files\Nordic Semiconductor\Master Emulator\2.1.6.8098, but am looking for the source. Guessing from code in nRFUart, perhaps knowing about the MasterEmulator object would be enough?

Thanks,

Shane

Parents
  • It is not possible to build a sniffer based on the Master Emulator API, as that is purely made for connecting to devices and doing GATT operations. Making a sniffer would require a completely different radio strategy, so if you need this, the only option is currently to write your own firmware, without using any softdevice or similar.

    Be aware that this is not a trivial task, although most definitely possible.

    Edit: If I miunderstood you, and you actually want to look at the HCI traffic going between the MCP and the dongle, you can take a look at the log file you can find from MCP's File -> Log file menu. It is just a text file, but does include all commands and events sent and received from the dongle.

Reply
  • It is not possible to build a sniffer based on the Master Emulator API, as that is purely made for connecting to devices and doing GATT operations. Making a sniffer would require a completely different radio strategy, so if you need this, the only option is currently to write your own firmware, without using any softdevice or similar.

    Be aware that this is not a trivial task, although most definitely possible.

    Edit: If I miunderstood you, and you actually want to look at the HCI traffic going between the MCP and the dongle, you can take a look at the log file you can find from MCP's File -> Log file menu. It is just a text file, but does include all commands and events sent and received from the dongle.

Children
No Data
Related