 Re: Viewing logged data in Engine Data (not Data Viewer) |
| So here's the deal. I have the v1 box. One of the issues with that box is how the COM ports get assigned. For whatever reason a COM port got assigned all the time and was active. So when I tried to open up the engine data screen it was looking for a COM port to talk to the box. Since there wasn't a box hooked up it searched for it until it timed out without finding it. Went to device manager in my laptop and disabled the active COM port and that took care of my problem.
I'd like to thank Anthony at WRT for his quick support and helping me figure out what "wasn't" wrong.
With the v2 and up boxes this doesn't happen. |
| |
| Re: Viewing logged data in Engine Data (not Data Viewer) |
| So what I have come up with so far is there is an issue opening up the engine data part of the program with something on my computer.
Anthony took some of my logged files and was able to view them in the engine data on his computer. I uninstalled WRT and reinstalled it on my laptop and still had the same issue. I installed WRT on another computer and the engine data viewing worked fine.
So for some reason my laptop has something that was loaded on it or updated that is causing a problem with the the engine data part.
Open to ideas |
| |
| Viewing logged data in Engine Data (not Data Viewer) |
| I use to use the engine data as a "real time" viewer when I finished a run.
When I try to open the data viewer it will semaphore timeout period has expired.
If you try and open a log file the program will crash and shut the Woolich program down.
Before you could open Engine Data, open a logged run and watch the the run.
It was great to be able to see the "tach needle" bounce when you lost traction.
The Data Viewer doesn't capture that. |
| |
| |
| View Topic on the Woolich Racing Forums |