Tweet
i recently got everything up and running but i'm having an issue with the interface randomly not giving vertical or horizontal launch angles. it happens maybe once in every 25 to 30 shots. the interface will show "calculated" for both. when it happens, i go to the camera settings page and in the result window in the top right, it shows a good clear ball streak but no red line. i then right click and select"(re)analyse" and it will then show the red line correctly (i don't make any changes to the settings before clicking on re-analyse). i have the latest 3.05L installed and my hitting mat is connected via serial port. should i try the previous version of the protee interface?
-
-
There is a timeout system on the cameras. If for some reason the analysis takes too long, the analysis will jump into fallback mode and will use the relative club loft as launch angle (VCAM) and sensor data for ball direction (HCAM). Once every 20/30 shots means 3 times per round.
This is implemented to prevent long delays (waiting for camera analysis) and to prevent launch failures (no launch at all).
We would not recommend to try an older version. In stead have a close look at your PC configuration first:
1] Make sure the energy scheme can not disable USB ports.
2] Disable firewalls and real time virus scanners.
3] Make sure no other programs are running/running in the background.
4] Make sure you are not exhausting system resources by pushing TGC resolution and details to the max.
5] Make sure both cameras are connected to different internal USB hubs.
In the settings file (ALT-E) you will also find a setting called number of iterations. This is set to 25. You can set this higher, which might help as well. -
1] Make sure the energy scheme can not disable USB ports.
-was already set to off
2] Disable firewalls and real time virus scanners.
-firewall was already set to off, no virus scanner software running either
3] Make sure no other programs are running/running in the background.
-no other programs running
4] Make sure you are not exhausting system resources by pushing TGC resolution and details to the max.
-i typically run with around 15-20% system idle with golf.exe and the protee interface eating up the rest but occasionally i see it spike into the 90's so maybe on occasion if the two programs peg the cpu, this would cause my problem. i will try running at a lower resolution and see that resolves the problem.
5] Make sure both cameras are connected to different internal USB hubs.
-please look at the attached picture of what usbview tells me about my computer. i have 4 ports and 3 headers on my motherboard. the headers give me 6 additional ports. it doesn't seem to matter where i plug the cameras. they always end up on the "standard enhanced pci to usb host controller". it does appear that they are on different hubs but i've read that they should be on different controllers. when i had the protee sensors plugged in to a usb to serial adapter, i would sometimes see the cameras do a crazy split screen and i'd have to unplug and replug the cameras to resolve it but since i switched to serial, i've had no issues.
I had number of iterations set to 35 already. If i set it higher, will there be more chance of launch failures? i get launch failures occasionally but that usually happens on a badly hit ball.
Comment
-
The camera split screen will happen when the CPU is unable to keep up with the image processing. This usually happens when the cameras are set into a 640x480 (or higher) resolution and/or when the cameras are NOT set to Format7 compression. A split screen will cause a detection problem. When you then go into the preview screen, the camera will re-initialize and when you do a re-analyze everything might look OK, but in fact it was not.
Try plugging 1 camera in the back of the PC and 1 on the front. Usually these ports are separated on different internal HUBS. Just to test.
Make sure Format7 - Mode 1 compression is on and use a 320x240 resolution.Comment
Comment