Unico / LSM6DSOX - From decision tree to .ucf (.h) by hand, understanding how .ucf works

[ladislas]

Hi there!

We've used Unico a lot and find it really cumbersome to create new `.ucf` files: you need to juggle between apps, you can't go back during configuration, if you've made a mistake you have to start from scratch. And it's not possible to automate the process...

We've studied the `.ucf` and `.h` files and are wondering how we could generate them without using Unico. Or at least juste use the "copy past the decision tree and generate the files" instead of having to do everything each time.

It is possible and if so, where can we find documentation?

Unico is great for evaluation but for our product and use case, it's really not that great.​

Thanks a lot!

Ladislas

[ladislas]

To be a little more precise:

When reading a .ucf file, one can quickly notice that the most part is composed of the following commands/registers:

• 02h - PAGE_SEL
• 08h - PAGE_ADDRESS
• 09h - PAGE_VALUE

For example here, in 4_LSM6DSOX_configuration.ucf:

Ac 02 11
Ac 08 EE
Ac 09 00
Ac 02 11
Ac 08 EF
Ac 09 00
Ac 02 11
Ac 08 F0
Ac 09 0A

We'd like to understand the mapping of the decision tree:

F3_VAR_on_ACC_V <= 0.00293
|   F1_MEAN_on_ACC_Z <= -0.844238: face_down (66.0)
|   F1_MEAN_on_ACC_Z > -0.844238: face_up (73.0)
F3_VAR_on_ACC_V > 0.00293: shaking (51.0)

To the .ucf.

We can't seem to find it in the documentation.

[ladislas]

We still haven't found an answer, any help would be greatly appreciated 🙂