1. Applicable products
- RCbenchmark Series 1520 Thrust Stand
- RCbenchmark Series 1580 Thrust Stand and Dynamometer
- RCbenchmark Series 1585 Thrust Stand and Dynamometer
- RCbenchmark Series 1780 Thrust Stand and Dynamometer
2. What describes your problem?
Please find within the following table which describes your problem. Once selected, mark down the troubleshooting points to follow.
3. Problem specific troubleshooting
3.1 I observed fluctuating sampling rate in my CSV file.
When opening the output CSV file, you may sometimes find the data fluctuating. In this problem specified troubleshooting, we only provide solutions to the sampling rate that varies. If you observe other parameters being fluctuating, please refer to section 4.1.
- Please understand that the sampling rate in an output CSV file may not be consistent due to the COM port limitation.
- If you observe the sampling rate fluctuating from 37 Hz to 40 Hz, this is normal with the thrust stand. This is the product’s limit and cannot be resolved.
- If you observe the sampling rate fluctuating from 40 Hz down to 8 Hz and then come back, you may continue following this guideline to troubleshoot.
- Try to use another USB cable to connect the circuit / mainboard to the PC.
- Try to use another USB port on your PC.
- Disable all the real-time plots in the GUI, and close all other windows such as Chrome, IE, or other memory consuming softwares. Run with only the RCbenchmark GUI.
- Run again to see the problem persists, if yes, continue to:
- Open the RCbenchmark GUI, go to Setub tab and check the box to activate the debug mode:
- Go to Debug tab and check the connectivity report of the GUI.
- Copy the connectivity report:
- We may suggest using a more powerful computer and unplug all unused COM ports and close all other software during the test.
- Send your support request to firstname.lastname@example.org and please include:
- Subject: CSV output sampling rate fluctuation
- The connectivity report from the Debug mode
- The version of circuit / mainboard of your product
- The processes, memory usage and performance report from your OS, for example, task manager if you are using Windows. A screenshot of your real time performance
3.2 I observed missing measurements in my CSV file.
This guideline is dedicated for the cases where you open a CSV file and find there are missing measurements, e.g. thrust, torque, and some derived values while other parameters are being measured properly.
- Please make sure that you download the most up-to-date software.
- Open the RCbenchmark GUI and go to the Setup tab
- In the Working Directory, please make sure the output file will be saved in a local directory but NOT on the cloud:
- If necessary to change the working directory, clock on the … to setup the directory.
- Now run the manual control with continuous recording, or run the automatic script that you made for the tests.
- Open the output CSV file and double check if there is still missing measurement
- Please understand, if you are user of the Series 1580, the load cell sampling rate is limited to 8 Hz, thus there will be measurement points where the stand measure the voltage, current but no torque.
- If you problem persists, please send an email to email@example.com and include:
- Subject: CSV output missing measurement
- The output CSV file of a manual test from 0% to 60% throttle (at least 30 seconds)
- Your product: Series 1520 / 1580 / 1585 / 1780
- Version of your product, on the Series 15 circuit or the Series 17 main board
4. Problems persist?
We support all issues related to the measurement tools itself, and we can provide limited support regarding your test setup and power-train selection. If you need extended support for your specific tests, manufacturing facility or UAV, contact us at firstname.lastname@example.org. We offer extended support contracts including phone and video conferences at affordable rates.
To obtain a solution to your problem faster, please indicate which troubleshooting steps you have already done. Also, include the debug log from the software. If relevant, please also include screenshot or pictures of the issue.
4.1 Cross-reference to other types of problem
- SGGSAR: understanding the limit of the sampling rate of our product
- SITESC: all measurement fluctuating may be caused by the ESC