Odometer readings for different required vehicle speeds
We are completing a vehicle test using a 10Hz Locosys GPS. We have to complete a certain distances at different speeds, in a specific order. Once we have completed the first distance at a certain speed, we then have to complete the next distance at a different speed. The test procedure is as follows:
1) 3km at a speed over 50km/h, then;
2) 22 @ 50km/h, finally;
3) [email protected]/h
Is it possible to set this up in DEWESoft using three separate odometers for each of the test parts (IF functions)? With the second odometer (22km @50m/h) only starting to record once the first part (3km over 50km/h) has been completed? Following [email protected]/h, odometer three should then start recording for [email protected]/h?
Thanks in advance.
I've created a similar setup then before, just with a few added calculations. The Odometers should start running after the test before them has been completed, and if their speed conditions are met. I've attached a demo example with the speed slider, which allows you to test out the system.
For your second and third conditions (50 km/h and 25 km/h), I've added a tolerance channel called "Speed tolerance". You can enter any value, which will act as a number of km/h by which the speed can be off (positive or negative), and still contribute to the distance calculation. It will be hard for the GPS to read exactly 50 or 25 km/h, so you can configure the tolerance in any way you like to still make the correct calculations.
The demo setup is tested and works correctly, but I haven't tested the real setup very much, so I'd recommend that you double check all of the calculations to make sure that everything is right.
The only things that's a bit of at the moment, is that the odometer will continue to run even after the target distance has been reached, if the initial condition is still satisfied. This can't be easily changed, because the conditions start to loop. If this bothers you, maybe we can reconfigure the setup to stop each odometer after it's reached the target value.
Thanks for the help, I will be testing this setup asap.
Although not critical, I would be interested to know how to make the odometer stop after reaching the target distance?
the "velocity conversion" channels needed to be passed through another channel. I've now configured the math so that the odometer will display the calculated distance while it is lower then the target distance, but when it reaches it's goal, it will simply switch to display the actual target distance. While experimenting with the setup, I've also added a manual on/off switch for each odometer. It's automatically set to be turned on, but you can switch it off at any time, and the calculations will not contribute to the odometer. I thought this might be a good feature to have in the setup. Again, I must stress that the setup was only tested in demo mode.
This setups work well, it is much appreciated.
Can these functions be applied to data already collected (in post-processing)? I tried using the 'distance travelled at a target speed' formula on some existing data, but the calculation seemingly failed.
Thanks for your help.
yes, you can use these formulas in post processing, you just have to adjust them a little. For example, you won't be able to use user inputs (control channels) in already recorded data, since they require live interaction, so you'll have to remove the conditions that use these channels from the formulas. I've tested the first odometer function myself on a random data set that includes a moving car, and the displays/formulas worked as they should. If you have any specific trouble with adjusting the formulas, please let me know and I'll help you out.