Hi, please find another PC and use HTerm to check whether the EVK can work properly or not at first, I think maybe something wrong with the USB 2 Serial port driver on your PC, you can check and reinstall it.

Hi @dilip_msec,

1. OpenIMU series of products are parts of opened platform, we recommend user to develop self-defined applications and algorithms, as well as messages. Here is a sample "https://openimu.readthedocs.io/en/latest/tutorial/OpenIMU_Core/SerialMessaging.html?highlight=serial#testing-using-serial-terminal-emulator" of how to construct “s1” package which you have received with coolterm, you can find how to parse s1 message on this webpage.

2. On this webpage you also can find how to set "userPacketRate" to 10Hz.
   If you don't want to modify source code, you can change it to 10 Hz on ANS https://developers.aceinna.com/devices/connect.

3. We don't have OpenIMU300Za ROS driver, so I think you need to write code to receive and parse OpenIMU300Za data via serial port or SPI, and package data to sensor_msgs/Imu Message format, then use it in your system.http://docs.ros.org/api/sensor_msgs/html/msg/Imu.html

Hi @dilip_msec ,
For Ubuntu machine, please follow "ST-LINK Install for Ubuntu" part on https://openimu.readthedocs.io/en/latest/install.html?highlight=ubuntu#pc-tools-installation to install libusb and Stlink Tools firstly.

Hi @YaoHan404 ,
Connect the Micro USB interface shown in above picture to your computer, you will find a new serial port device in your device list, then you can operate this unit via serial port.

hi @YaoHan404 ,

I'm assuming that you communicate with IMU via UART.
We have an openimu driver which can be downloaded from https://github.com/Aceinna/python-openimu.git
You will find how to parse IMU data in function parse_buffer() in openimu.py file.
"z1" packet is the IMU 9 DOF data you are looking for, function parse_buffer() can parse "z1", and you can find detailed description of "z1" in "app_config/IMU/openimu.json".

@sharat said in OPENIMU300ZA sensor (without EVK) output through serial cable:

ART

Yes, pin 7 is a selector to enable UART or SPI.

Then you can use cool term to receive data via your TTL to USB converter. Correct data is stat with "0X55 55" ( HEX format ), like the picture which Mr @cek mentioned above.

Except for using cool term, you also could use the executable file which can automatically match the correct baud rate and connect with IMU, besides, this executable file is also running as a web server, you will find Aceinna navigation studio connect with IMU now.

Please feel free to let us know if you have any questions.

@sharat
The user can select the serial interface used with the unit by controlling the logic level on connector pin 7 at system startup. If the connector pin 7 is grounded then the unit is configured for low-level UART output on pins 3 and 4.
About the connector pins definition, please refer to online manual: https://openimu.readthedocs.io/en/latest/300ZA/pinout.html
Hope this is helpful for you, have a nice day~

@david

OPENIMU300RI / Mtlt305D are always used in vehicles such as cars and tractors via CAN interface, so the RS-232 messages are QUIET by default.

Nav-view software can help you configure unit to send messages via RS-232 interface:

1. Connec unit and PC with a RS-232 to USB cable.
2. Open Nav-view, it can scan all available COM ports and try some usual baudrate, then connect unit automatically. If the bottom of GUI become green, it means Nav-view has connected with unit successfully, rather, if it is red as below picture, it means hasn't connected. You can try to replug usb port or re-open Nav-view.
3. After the unit connect with Nav-view successfully, you can configure the output rate in configuration sheet.
   

If the unit can't connect with Nav-view:

1. Could you please tell me which sample code or application bin you downloaded to unit, it is better to provide a screenshot.
2. Could you please try to receive messages via CAN? Unit outputs messages all the time. So we can make sure the unit is still alive after you upload bin/firmware last time.

Thanks.