Page 1 of 1

Where to see OW memory content?

Posted: Tue Oct 26, 2021 11:21 am
by skinnykaen
Hi everyone! https://www.bitcraze.io/documentation/r ... ry_format/. There is sample content here for the led ring deck. But where can you find content for other decks? For example, for optical flow. I tried using wireshark but no success.

Re: Where to see OW memory content?

Posted: Wed Oct 27, 2021 7:53 am
by arnaud
You can read the onewire memory using this example python script: https://github.com/bitcraze/crazyflie-l ... read-ow.py. There is also an example to write memories in the same folder if you want to program your own decks.

Re: Where to see OW memory content?

Posted: Wed Oct 27, 2021 10:03 am
by skinnykaen
arnaud wrote: Wed Oct 27, 2021 7:53 am You can read the onewire memory using this example python script: https://github.com/bitcraze/crazyflie-l ... read-ow.py. There is also an example to write memories in the same folder if you want to program your own decks.
Thank you very much. Just one more question. What is Updating id? I have 2 flow v2. They have different Updating id. How can I change it? I tried the line mems [0] .id = 4, but the script did not finish its execution.

Re: Where to see OW memory content?

Posted: Fri Oct 29, 2021 7:43 am
by arnaud
I am not sure what you are after, what is your goal?

This ID is the Crazyflie firmware internal ID for the memory, it is an implementation details: this ID is used in radio packet to select the onewire memory. So this is not data that is part of the memory and you should not touch it (it likely happened that by modifying it you made the lib unable to access the memory).

The boards ID, recognized by the deck drivers, are VID and PID. The best during development of a new deck is to set VID:PID to 0:0 and then set a name for the board. This will make the Crazyflie firmware select the deck driver by name instead of by vid:pid.

If you have multiple decks, the ordering of the ID will depends of the deck memory address. The deck memory address can be considered random so the ordering will change between decks, but we are never looking a the memory or id but only at the content of the memory so this is not a problem.