I was able to let it work.
It was a jumper position issue.
I can't figure out why I can't connect anymore to imu. When I run openimu command in vscode It find tne connected device (openimu 330ZI EVK) but can't connect to it.
With the previous installation of Ubuntu I had no problems.
When a couple of days ago I had to reinstall Ubuntu 16.04 no way to connect to imu.
I followed all insttrucions to get it work.
Download and install vscode.
Built from source python-openimu from Aceinna repo of github
I also gave rights to USB.
Moreover I rebuild factory data on EEPROM with ST-link following the tutorial on readthedocs (Warnign before starting development).
I'm starting to think that It could be a python issue. Can anyone explain me steps to follow and wich python version I need?
In the file Userconfiguration.c is set to NMEA protocol and 115200 gpsbaudrate.
In ucenter i've disabled all msg other then the three NMEA that i need. My target is to let them communicate via UART1 so in ucenter i have activated the UART1 and USB (just to see if i can see message on serial monitor) in port configuration.
Maybe this could be a problem?
Anyway in the manual is said that if i want to use header P2 (where i have actually connected rx out and tx in of the GPS) the header on 5-6 of P1 should be off. For example if Serial Channel 1 used for connection with some external device (GPS or other).
But this is in contrast with the photo of pin connection that i have found where is clear that every jumper on P1 is ON.
i want to run the INS APP but most of the times the NMEA messages are not seen by the openimu and so there isn't position available.
I have the openimu 300ZI eval kit, u-blox zed-f9p and pc running ubuntu 18.04 with u-center 20.01 and vscode.
My procedure is the following: