RE: Problems about mesh

Hung Bui — Mon, 23 Apr 2018 09:05:37 GMT

Hi Herry,

We have updated the interactive py aci in Mesh SDK v2.0. I would suggest you to test with the new SDK and let us know if you still see the issue.

RE: Problems about mesh

herrychiu — Wed, 18 Apr 2018 06:07:00 GMT

Hi Petter,

I got the same result when I followed the Provisioning example of Interactive PyACI page.

From the log, it seems the provision sequence can not be completed.

Could you give me some comment how to debug this issue ? Thanks.

Microsoft Windows [版本 10.0.16299.371]
(c) 2017 Microsoft Corporation. 著作權所有，並保留一切權利。

C:\NORDIC\nrf5_SDK_for_Mesh_v1.0.1_src\scripts\interactive_pyaci

C:\\NORDIC\nrf5_SDK_for_Mesh_v1.0.1_src\scripts\interactive_pyaci>python interactive_pyaci.py -d COM12 COM13

    To control your device, use d[x], where x is the device index.
    Devices are indexed based on the order of the COM ports specified by the -d option.
    The first device, d[0], can also be accessed using device.

    Type d[x]. and hit tab to see the available methods.

2018-04-18 13:07:04,777 - ERROR - COM12: Exception in pkt handler <bound method Interactive.__event_handler of <__main__.Interactive object at 0x05709270>>
2018-04-18 13:07:04,780 - ERROR - COM12: traceback: Traceback (most recent call last):
  File "C:\NORDIC\nrf5_SDK_for_Mesh_v1.0.1_src\scripts\interactive_pyaci\aci\aci_uart.py", line 88, in process_packet
    fun(packet)
  File "interactive_pyaci.py", line 152, in __event_handler
    if self._event_filter_enabled and event._opcode in self._event_filter:
AttributeError: 'Interactive' object has no attribute '_event_filter_enabled'

2018-04-18 13:07:04,781 - ERROR - COM13: Exception in pkt handler <bound method Interactive.__event_handler of <__main__.Interactive object at 0x05526F50>>
2018-04-18 13:07:04,786 - ERROR - COM13: traceback: Traceback (most recent call last):
  File "C:\NORDIC\nrf5_SDK_for_Mesh_v1.0.1_src\scripts\interactive_pyaci\aci\aci_uart.py", line 88, in process_packet
    fun(packet)
  File "interactive_pyaci.py", line 152, in __event_handler
    if self._event_filter_enabled and event._opcode in self._event_filter:
AttributeError: 'Interactive' object has no attribute '_event_filter_enabled'

Activating auto-logging. Current session state plus future input saved.
Filename       : interactive_session_18-108-13-7.log
Mode           : backup
Output logging : False
Raw input log  : False
Timestamping   : False
State          : active
Python 3.6.5 (v3.6.5:f59c0932b4, Mar 28 2018, 16:07:46) [MSC v.1900 32 bit (Intel)]
Type 'copyright', 'credits' or 'license' for more information
IPython 6.3.1 -- An enhanced Interactive Python. Type '?' for help.

In [1]: p = Provisioner(d[0])

I2018-04-18 13:10:38,722 - INFO - COM12: Successn [
2]:2018-04-18 13:10:38,728 - INFO - COM12: Success 2018-04-18 13:10:38,730 - INFO - COM12: SubnetAdd: {'subnet_handle': 0}
In [2]:

In [2]: a = Provisionee(d[1])

In2018-04-18 13:10:52,677 - INFO - COM13: Success [
3]:2018-04-18 13:10:52,684 - INFO - COM13: In [3]:

In [3]: p.scan_start()

2018-04-18 13:11:02,681 - INFO - COM12: Success
In [4]:

In [4]: a.listen()

2018-04-18 13:11:13,590 - INFO - COM13: Success
In [5]: 2018-04-18 13:11:14,946 - INFO - COM12: Received UUID B32DE29E978FC2181368C92FFD5B5DEB with RSSI: -231 dB
In [5]:

In [5]: p.provision()

I2018-04-18 13:11:25,533 - INFO - COM12: Provision: {'context': 0}n
[6]:    2018-04-18 13:11:25,550 - INFO - COM13: Link established
2018-04-18 13:11:25,562 - INFO - COM12: Link established
2018-04-18 13:11:25,607 - INFO - COM12: Received capabilities
2018-04-18 13:11:25,608 - INFO - COM12: Number of elements: 2
2018-04-18 13:11:25,612 - INFO - COM12: OobUse: {'context': 0}
2018-04-18 13:11:27,771 - INFO - COM12: ECDH request received
2018-04-18 13:11:27,784 - INFO - COM12: EcdhSecret: {'context': 0}
2018-04-18 13:11:27,791 - INFO - COM13: ECDH request received
2018-04-18 13:11:27,804 - INFO - COM13: EcdhSecret: {'context': 0}
2018-04-18 13:12:27,802 - INFO - COM12: Provisioning link closed
2018-04-18 13:12:27,877 - INFO - COM13: Provisioning link closed

RE: Problems about mesh

Petter Myhre — Tue, 20 Feb 2018 08:41:35 GMT

Sorry for the late reply, Hung has been travelling. Is this still a problem? Could you try with Mesh SDK v1.0.1? Are you following example here? Your logs doesn't look the same.

RE: Problems about mesh

Beike — Mon, 05 Feb 2018 11:07:35 GMT

The probability of occurrence is 30%

RE: Problems about mesh

Beike — Mon, 05 Feb 2018 11:06:20 GMT

firmware :S132_5.0.0

the log:

client:
2018-01-31 17:17:10,179 - INFO - COM7: Provision: {'context': 0}
2018-01-31 17:17:10,234 - INFO - COM7: Link established
2018-01-31 17:17:10,274 - INFO - COM7: Received capabilities
2018-01-31 17:17:10,275 - INFO - COM7: Number of elements: 2
2018-01-31 17:17:10,277 - INFO - COM7: OobUse: {'context': 0}
2018-01-31 17:17:12,445 - INFO - COM7: ECDH request received
2018-01-31 17:17:12,450 - INFO - COM7: EcdhSecret: {'context': 0}
2018-01-31 17:18:12,474 - INFO - COM7: Provisioning link closed





server:
2018-01-31 17:17:10,214 - INFO - COM9: Link established
2018-01-31 17:17:12,453 - INFO - COM9: ECDH request received
2018-01-31 17:17:12,458 - INFO - COM9: EcdhSecret: {'context': 0}
2018-01-31 17:18:12,539 - INFO - COM9: Provisioning link closed

RE: Problems about mesh

Hung Bui — Wed, 31 Jan 2018 13:39:17 GMT

Hi Beike,

Which firmware you run on the provisionee ? Could you post the full log ?

How often do you see the issue ?