Currently, reg stream CSV files have a fixed name. Would be helpful to allow customization of the name (label files without having to do it after the capture)

In the product datasheets, such as the ADIS16497, the *_LOW registers represent the lower 16bits of the inertial data, while in the software, they seem to represent the entire 32-bit number. Personally, I like the way that this works, but I am wondering if this could create confusion, in some customers. I really like the idea of representing the full 32-bit number, in the data log, but am wondering if we should consider including 16-bit or 32-bit naming in what the customers will selection.

Should we consider some form of notification, when customers select the _LOW, to let them know what they can expect? Or, should we consider listing 16-bit or 32-bit with these selections?

For a cleaner user experience, the GUI should be packaged into a one-click installer

Could we consider accommodating a time input OR a total number of samples input, with respect to how customers will establish total record time?

Also, should the Burst mode have the same options as the Register Logging?

If the FX3 is disconnected, the custom personality currently loaded (if any) cannot be saved to the custom_personality.csv file because the personality settings are sourced from the active FX3 object

When one FX3 is connected and streaming data, connecting a second FX3 to your PC and loading the application firmware causes a brief interruption in the data streaming process for the first FX3. This can be avoided by ensuring that all FX3s are connected before starting any data streams.

Dear @juchong and @ajn96
I bought MEMS IMU Adis-16505 together with Eval-adis-fx3. I make the sensor vibrate through a shaker in the X direction with a constant frequency and amplitude. This is an experiment to read the output of x, y, z from the accelerometer. What is important to me is the amplitude and frequency in the time domain. The frequency domain simulation is successful, but the time domain simulation is not clear. When I simulate the time domain I don't get the correct frequency and amplitude. Maybe it has to do with the sample rate? I do not know. Please let me know if you want csv files for more information to help me out.

I still tried to read the frequency domain of X, Y, Z ACCL_OUT in matlab, it worked, but the time domain is still not clear to me. Can you help me to read the amplitude and frequency of the time domain in matlab or on the Eval-adis-fx3 app v2.9.4.0.

Originally posted by @mokhtarpakazizi in https://github.com/analogdevicesinc/iSensor-FX3-API/issues/9#issuecomment-822215128

When plotting different data types (eg xl vs gyro) it can be helpful to have the data in two separate plot windows, allowing for independent axis scaling and less visual clutter.

Currently, if you open an ADcmXL stream GUI and stream data everything works as expected. However, if you close that form, and open a new one, the invoke call which updates the form labels after the completion of a stream throws an exception (trying to invoke on a control which does not exist). This is not related to the FX3 API.

After manually loading a register map file into the GUI, the scale data check can remain selected, even though the register values are read in hex:

Placing the show help button on the bottom of the form will make it easier for people to find (as opposed to the advanced access tab)

Blue FX3 (Cypress Eval board + breakout) does not have the hardware to control the power supply. Personality file routines should be made aware of this.

Currently the user must save a plot as an image, then load it to whatever application they are using. Would be easier if you could simply right click in the form, copy the image, then paste it anywhere which supports image pasting (word, outlook, etc).

Should be easy, see
https://docs.microsoft.com/en-us/dotnet/api/system.windows.forms.clipboard.setimage?view=windowsdesktop-6.0

Currently have three different GPIO forms:
General read/write and pulse drive form
PWM setup form
Resistor setup form

Would be better for it to be an all-in-one pin interfacing form

The Burst Data Capture Window is Force Closing, after clicking start and then selecting folder to save the data. Same behavior happened on Advanced, Burst Mode Test window.
Tested on ADIS16480 connected. Other register readings works okay.
ERROR_LOG.csv

The ADcmXL GUI allows users to perform multiple streams with a trigger between them. The trigger can be a timer or an external pin. If two streams are completed within a second of each other (for example, timer trigger of 250ms with only 1 real time stream frame captured), the data for the second stream will be appended to the first file, because the target file name is the same.

The measure DR check box on the main form uses a separate thread to measure the DR freq at a fixed interval. If this is kept running while a continuous data log is executed, an application lockup can occur.

On first time setup, the form forces you to select a DUT from the drop down menu prior to the welcome guide being accessible.

Some of the functionality of the FX3 eval application is designed to enable firmware development work. These functions can be confusing, and are not part of a typical customer evaluation workflow. They should be moved to a "developer options" tab, which can be enabled via the settings screen.

could you check the reference to the iSensor-FX3-API? Thank you!

Built-in winforms installer is probably fine. An installer will provide a cleaner user experience compared to a standalone executable.

If the EVAL-ADIS-FX3 settings are changed after selecting a device from the DUT selection drop down menu, the loaded DUT personality becomes "Custom". The next time the drop down menu is loaded, the selected device is the first in the list, not the most recently selected.

The workflow for most use cases would be simpler if the GUI remembered the most recently selected device (when using a custom personality) and went to that device in the drop down by default.

Application images are somewhat out of date (v2.5.0.0). Either should update the app guide to have latest images, or point users towards the ADI wiki entry for the EVAL-ADIS-FX3. Leaning towards having all documentation in wiki.

Running an FFT plot and time domain plot at the same time causes unstable GUI behavior. This is due to the fairly heavy resource utilization on the FX3 by the FFT plot GUI (has to capture continuous, data ready synchronized data) conflicting with the data plot GUI. This can be avoided by stopping any time domain data plot before running an FFT plot, and vice versa.

This may eventually be fixed via re-work of the resource protection scheme in use on the FX3 API. The stream mutex approach currently implemented isn't perfect.

Once -3dB point lines are added, the plot must be re-started to remove lines. This is inconvenient, especially if the plot data represents a long data capture (large NFFT or FFT averages)

When using a custom DUT personality file, the data ready pin can be assigned to DIO2 if the application crashes. This is likely due to the FX3Connection attributes being reset to their default values (for the connected sensor type) when an error occurs during firmware load.

Need to do more investigation as to the root cause. The application uses several threads to perform the data capture and FFT calculation - probably an issue with one of them not being stopped properly, and invoking an event on the form after it is closed.

It's sometimes useful to enable/disable DRActive when using the Data Plotting form.

Would be nice to add the following features:

• Setting the freq and magnitude plot limits
• Allowing for zooming in on the plot (while maintaining label/save shot feature)
• Allowing for copying image to clipboard

Make the burst GUI set/clear the burst 32-bit in MSC_CTRL for the IMUs which have that feature (and only show option for IMUs with configurable burst). Could do something similar for delta output vs inertial for burst.

This will require significant changes to burst data logging form, but would increase ease of use.

Adding an option to zero-mean each FFT data set will improve the practical usability of the FFT plotter

Would be nice to be able to set a plot title in the time domain plotter (similar to the FFT plotter). This will make plot images exported easier to use.

It's unclear whether "Sample Frequency" refers to the IMU sample frequency (decimation setting) or the Windows form update rate. Maybe we can change it to "Plot Update Rate"?

Scale can be set by user for the plotting forms, or manually adjusted in the regmap. Would be easier if there were default scales already set.

For IMU families with multiple ranges, will have to use judgement regarding what to set the scale values too. Could potentially break out each part in the personality file list - might get cluttered though.

Currently the register logging application logs signed data only, which must be post processed to meaningful units. Would be useful to have a single button which allows for automatic scaling.