RE: nRF52840 dongle serial hex for interaction with interactive pyaci

Hieu — Thu, 01 Aug 2024 21:38:55 GMT

Hi zanluka,

Our apologies for the late follow up.

As Maria said, it would be hard for us to deep dive into your project to find what is wrong. A big part of the reason is that the PyACI script is a part of the nRF5 SDK solution, which is in maintenance mode. See the note in the first page of the SDK documentation: https://infocenter.nordicsemi.com/topic/struct_sdk/struct/sdk_mesh_latest.html.

I personally haven't touched the PyACI script for many months. Our current solution for a BT Mesh - PC kind of bridge is Mesh Shell on the nRF Connect SDK. It provides a human-operable shell interface, which can be over UART or USB CDC ACM.

Firstly, I would like to ask: How much effort has you put into the current project? Is it possible for you to switch to Mesh Shell now?

Next. I see that your PDF documents describe the process for a demo. To do this demo, must you use the PyACI script? You could easily provision the mesh devices with the nRF Mesh mobile app.

Finally, if I recall correctly, the PyACI script just provides you an interactive interface. It should connect with a COM port directly and not require any user configurations. Am I right to understand that you had to modify the script? Why is that?

For reference, this is the log from my last time working with it, where I provisioned a few devices and bound an app key to them. I reached this point following the documentation in nrf5sdkformeshv500src\scripts\interactive_pyaci\doc and online documentation.

db = MeshDB("database/example_database.json")

p = Provisioner(device, db)
p.scan_start()
p.scan_stop()
p.provision("b9ed5250206146188612adafdf9e29e7", 0, "Sensor", 0, 0)
p.provision("f1f09dbd97e649818e0f62426819e67e", 0, "Observer", 0, 0)

cc = ConfigurationClient(db)
device.model_add(cc)

cc.publish_set(8, 0)
cc.composition_data_get()
cc.appkey_add(0)


cc.model_app_bind(db.nodes[0].unicast_address, 0, mt.ModelId(0x1100))
cc.model_publication_set(db.nodes[0].unicast_address, mt.ModelId(0x1100), mt.Publish(db.nodes[1].unicast_address, index=0, ttl=2, period=3000))
cc.model_publication_get(db.nodes[0].unicast_address, mt.ModelId(0x1100))


cc.model_app_bind(db.nodes[0].unicast_address, 0, mt.ModelId(0x1101))
cc.model_subscription_add(db.nodes[0].unicast_address, db.groups[0].address, mt.ModelId(0x1101))
cc.model_subscription_get(db.nodes[0].unicast_address, mt.ModelId(0x1101))



cc.publish_set(9, 1)
cc.composition_data_get()
cc.appkey_add(0)

cc.model_app_bind(db.nodes[1].unicast_address, 0, mt.ModelId(0x1102))

cc.model_subscription_add(db.nodes[1].unicast_address, db.groups[0].address, mt.ModelId(0x1102))
cc.model_subscription_get(db.nodes[1].unicast_address, mt.ModelId(0x1102))
cc.model_publication_set(db.nodes[1].unicast_address, mt.ModelId(0x1102), mt.Publish(db.nodes[1].unicast_address, index=0, ttl=2))
cc.model_publication_get(db.nodes[1].unicast_address, mt.ModelId(0x1102))

Hieu

RE: nRF52840 dongle serial hex for interaction with interactive pyaci

Maria Gilje — Thu, 25 Jul 2024 12:51:43 GMT

Hello zanluka,

I will begin by setting some expectations. Us Nordic support engineers will most likely not be able to deeply research your project, but we are able to help you with specific issues.

Since your support ticket is public to the rest of the DevZone community anyone with insights on this are encouraged to help out.

I will have a closer look on your ticket contents and a quick look through your project within the next couple of days.

Best regards,

Maria