Posts made by soundwave

Which IMU example you want to programed?

The one I mentioned in my first message: the "IMU" example (with annotation "An IMU provide calibrated inertial sensor data to the user") downloaded via Aceinna's OpenIMU Platform plug-in for VSCode.

For the EXE, pls check whether it works well or not.

What is this software? (I can't try it right now, shall only be able next week)

We doubt COM20 may be not right port which connect to user port of IMU

The COM port doesn't change, because I don't plug the device's serial interface in or out while I program the firmware back and forth via ST-Link. Besides, commands.py scans all available COM ports.

Device SN: 1808400503

Error message from python-openimu/commands.py (Python 3.6.1, Windows 10 Pro):

could not open port 'COM20': PermissionError(13, 'Access is denied.', None, 5)

It works with default firmware, then I just program the IMU example firmware (via ST-Link) and that's the error which I have as a result. No other process actually holds COM20; same result when running with administrator provileges. Merely returning the default firmware makes it work again.

Hello. I downloaded the IMU example via Custom IMU Examples interface within the Aceinna's OpenIMU Platform plug-in for VSCode. I expected the IMU example to work similar to the firmware which is shipped with the device. However, it doesn't seem the case.

The shipped firmware does reply to the Memsic's UART commands from Memsic's NAV-VIEW program, while the IMU example firmware does not.

The shipped firmware does reply to the python-openimu/commands.py requests, while the IMU example firmware does not.

My questions are:

1. Was I right or wrong expecting the IMU example to work similar to the firmware which is shipped with the device?

2. Do the OpenIMU300ZA devices undergo any individual calibrations before shipping?

3. If yes, then are the individual calibration parameters stored in the area which is not erased during uploading of IMU example firmware via ST-Link programmer? (so that IMU example firmware could pick them up)

Hello. We used the Memsic IMU380ZA modules in SPI mode and now consider to switch to OpenIMU300ZA modules.
This causes several questions.

1. Is OpenIMU300ZA expected to support the SPI protocol of Memsic IMU380ZA?

2. Out of the box OpenIMU300ZA doesn't respond to Memsic's SPI commands (pin 7 is configured to enable SPI).
   Is it because the default firmware doesn't support SPI?
   Will rebulding and uploading to device of the IMU example with platformSetUnitCommunicationType(SPI_COMM) solve the issue?

3. When do you plan to publish the SPI protocol description in the Documentation?
   Currently it merely says "SPI Interface Details - To Be Provided"
   (https://buildmedia.readthedocs.org/media/pdf/openimu/latest/openimu.pdf)