Horrible Functionality for RFD and Endurance
RFD test: gives completely random results and the only thing I've learned after an hour of testing is that you should never pull when it says pull. Why can't it just continuously listen and measure RFD 2080 and the best Time Interval when the user chooses to pull. Same goes for endurance. Why can't the function be that it registers the best f.ex 5 second average if that's the endurance interval I choose. Countdown makes the testing so much more like a sprint where it matters a lot how good you are initiating the pull... Seriously disappointed, but luckily this is programmatic issue that hopefully can be dealt with.
