2020-01-13 02:29 PM
Hi,
I have been trying to connect UNICO PC software to a Nuclieo L476RG and a X-NUCLEO-IKSO1A2 and a STEVAL-MKI159V1 with a LSM9DS1 MEMS on it. But so far this has not worked. I see in ST.COM videos they are using a completely different processor board called STEVAL-MKL109V2.
My question, is it possible to use what I have so that I can graphically see the accelerometer, gyroscope & magnetometer of the LSM9DS1 using the GUI in UNICO?
Or do I have to get yet more HW (this STEVAL-MKI109V2) to do this?
-thanks.
2020-01-14 01:23 AM
Hi @Rstua.1 , please note that there is the following correspondence between the SW and the HW ST evaluation tools for MEMS and sensors:
If you are using the X-NUCLEO-IKSO1A2 you have to interface it with the UNICLEO GUI.
Regards
2020-01-14 08:57 AM
Thank you @Eleon BORLINI . I did not know about UNICO verses UNICLEO. It appears UNICLEO is what I want to use.
My next difficulty: Our product contains a LSM9DS. I have one on a STEVAL-MKI159V1 board. However, I can not find instructions to switch from the IKS01SA2 sensors to the LSM9DS1 sensor on the STEVAL-MKI159V1 board.
-thanks.
2020-01-15 01:42 AM
Hi @Rstua.1 , unfortunately the Unicleo-GUI package doesn't support the LSM9DS1 sensor :( Here below the screenshot of the supported sensors, from the tutorial video:
This because the LSM9DS1 sensor has two different interfaces (acc+gyro and mag), and the IKS tool can manage only one at HW level. You can of course start from scratch, "bypassing" the Unicleo-GUI and directly wiring the adapter to the Nucleo board... If you want a ready-to-go interface, it's better to switch to the Unico-GUI...
Regards
2020-01-15 11:29 AM
Thank you @Eleon BORLINI for your answer. I started looking at the STM32L4xx-Nucleo-ECompass demonstration code with the intention of re-coding it for the LSM9DS1. In almost every case, a structure of an array of type uint8_t is used to pass hundreds of bytes of data between functions. Is there an explanation of what each byte means? Right now I only know what some of the bytes might be used for by examining what the example source code (only the source code as the Middle Ware code is only giving out as an ST.COM library) is doing to the bytes in this array.
-thanks
2020-02-07 05:05 AM
Just a follow up. The above mentioned structure is used at the end of the Cube-MEMS program to send the data to the STMicro's PC based UNICLEO GUI. It may be used internally to pass data between the different methods. But its ultimate purpose is to supply data to the PC for graphical presentation.