- 60
- darqpassenger
Overview of GT7 Telemetry Software
- Thread starter snimat
- 182 comments
- 61,381 views
- 60
- darqpassenger
- 60
- darqpassenger
I also tried cmd. But then I get this
C:\Users\Downloads\gt7telemetry-main\gt7telemetry-main>python3 gt7telemetry.py 192.168.3.14
'python3' is not recognized as an internal or external command,
operable program or batch file.
But I have installed python3
Update, I got this. But I have Installed salsa20
Traceback (most recent call last):
File "C:\Users\Downloads\gt7telemetry-main\gt7telemetry.py", line 8, in <module>
from salsa20 import Salsa20_xor
ModuleNotFoundError: No module named 'salsa20'
Last edited:
- 60
- darqpassenger
telemetry is working thanksHmmm.... ah
Try "python" rather than "python3".
The Python installer add the location to my %PATH% environment so its in the search path.
C:\Users\Behrens\Downloads\gt7telemetry-main\gt7telemetry-main>python .\gt7telemetry.py 192.168.1.20
Have Fun!
Nevermind. I got the telemetry to work, but I was wondering about the dashboard. The first app listed by the OP
Last edited:
- 60
- darqpassenger
- 60
- darqpassenger
Thank you! I was able to download car list and inserted this "set GT7_PLAYSTATION_IP=192.168.3.14 bokeh serve"
Now, i get this:
C:\Users\Downloads\gt7>python .\main.py
INFO:root:No connection to 192.168.3.14 bokeh serve:33739: [Errno 11001] getaddrinfo failed
Ip is correct.
Update: I also disabled firewall and allowed UDP conenction for ports listed on the description.
Last edited:
- 60
- darqpassenger
- 60
- darqpassenger
OMG it worked! Thank you so much. The instructions should be updated? Cause those commands were not working!Please take notice about the "dot" which means current location.
Than open your browser and point it to the url which you see in the output.
Got it "working"
View attachment 1254324
Regards,
Joerg
- 60
- darqpassenger
I can select a reference lap, but can I change de last lap information?
- 50
- Germany
No. Currently last lap will always be your last lap.
The commands work for MacOS and Linux. I will add the commands for Windows to the Readme.
To be fair, the whole setup process is currently made for more experienced users. I will gladly add any other helping information.
Edit:
I added run.bat and run.sh files which may help users with no experience of the command line and Python.
Last edited:
- 60
- darqpassenger
I want to thank you for that, this is such a underrated app on the community. It gives us a lot of rich information, I am enjoying it a lot! I just have two questions about the manual when it says:
Both are slower?
And..
Index number of the map is different from the index number on the graph table for me.
Also Speed Deviation (Spd. Dev.) graph is blank for me, nothing shows up.
- 60
- darqpassenger
Thank you for sharing this telemetry @snimat; it has been helping me better understand the brake modulation that replay pilots use. However, I came across the following situation. I'm comparing my lap with the replay lap, where my line is represented by the blue trace and the reference line by the purple one. Notice that I brake earlier, but the speed graph reduces the speed later compared to the reference. Is this a bug? I noticed this because when I try to replicate the replay's braking, I never manage to make the turn; I always end up running wide on the exit. Could it be related to tire temperature as well?
Attachments
- 4
- Brazil
- TeixeiraMauro92
Help
Collecting six>=1.5 (from python-dateutil>=2.8.1->pandas~=1.5.3->-r requirements.txt (line 4))
Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Building wheels for collected packages: salsa20
Building wheel for salsa20 (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for salsa20 (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [1 lines of output]
error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for salsa20
Failed to build salsa20
ERROR: Could not build wheels for salsa20, which is required to install pyproject.toml-based projects
Collecting six>=1.5 (from python-dateutil>=2.8.1->pandas~=1.5.3->-r requirements.txt (line 4))
Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Building wheels for collected packages: salsa20
Building wheel for salsa20 (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for salsa20 (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [1 lines of output]
error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for salsa20
Failed to build salsa20
ERROR: Could not build wheels for salsa20, which is required to install pyproject.toml-based projects
- 4
- Brazil
- TeixeiraMauro92
- 4
- Brazil
- TeixeiraMauro92
I installed the latest version and it showed a new error.
Building wheels for collected packages: salsa20
Building wheel for salsa20 (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for salsa20 (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [7 lines of output]
core_hsalsa20.c
core_salsa20.c
stream_salsa20.c
stream_xsalsa20.c
salsa20.c
LINK : fatal error LNK1104: nÆo ‚ poss¡vel abrir o arquivo 'MSVCRT.lib'
error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio\\2022\\BuildTools\\VC\\Tools\\MSVC\\14.35.32215\\bin\\HostX86\\x86\\link.exe' failed with exit code 1104
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for salsa20
Failed to build salsa20
ERROR: Could not build wheels for salsa20, which is required to install pyproject.toml-based projects
- 50
- Germany
Creator here. This is related to salsa20 needing compiled libraries. There is a pure python salsa20 implementation I am currently evaluating. It is way slower than the compiled salsa20 but it could be sufficient for our use case. This should solve this problem. In the mean time you should probably try installing MSVCRT.lib whatever this is. I do not have Windows, so I cannot try. Others seem not to have the same problem.
- 332
- Denmark
I observed the same behaviour with my own GT-to-Motec telemetry logger (and wrote about it here); for some reason the brake signal is filtered in replays making it look like the ghost brakes way later. I have no idea why PD programmed it that way (to make the replays look more 'impressive,' maybe? "Just look at how late they brake, bro!")
Here's a comparison I made - the coloured traces are from a track session captured live, the overlaid white traces are from the corresponding replay capture. Observe how the throttle traces are virtually identical, while the brake traces aren't:
(There's another example in the post mentioned above.)
If you want to check braking points from a replay capture, look at the longitudinal G forces instead.
Last edited:
- 60
- darqpassenger
The best way to see braking points is looking for the speed and throttle graphs. Brake is out of sync. But when you track a ghost in front of you, the braking points are clearly before from what the telemetry says. By the way, how did you get data in Motec?I observed the same behaviour with my own GT-to-Motec telemetry logger (and wrote about it here); for some reason the brake signal is filtered in replays making it look like the ghost brakes way later. I have no idea why PD programmed it that way (to make the replays look more 'impressive,' maybe? "Just look at how late they brake, bro!")
Here's a comparison I made - the coloured traces are from a track session captured live, the overlaid white traces are from the corresponding replay capture. Observe how the throttle traces are virtually identical, while the brake traces aren't:
(There's another example in the post mentioned above.)
If you want to check braking points from a replay capture, look at the longitudinal G forces instead.
- 60
- darqpassenger
Can you share this workspace? I am not able to see braking pedal and the map. Thanks!I observed the same behaviour with my own GT-to-Motec telemetry logger (and wrote about it here); for some reason the brake signal is filtered in replays making it look like the ghost brakes way later. I have no idea why PD programmed it that way (to make the replays look more 'impressive,' maybe? "Just look at how late they brake, bro!")
Here's a comparison I made - the coloured traces are from a track session captured live, the overlaid white traces are from the corresponding replay capture. Observe how the throttle traces are virtually identical, while the brake traces aren't:
(There's another example in the post mentioned above.)
If you want to check braking points from a replay capture, look at the longitudinal G forces instead.
Edit: nevermind, I was able to import from the channel list.
Last edited:
- 4
- Brazil
- TeixeiraMauro92
