that was a nerf gun. 108fps is correct.
https://drive.google.com/drive/folders/1...drive_link
anyways, stripped the sdk down to bare bones so my google drive folder should have everything needed minus instructions. you need to have java to run. i will fix it up a little later, but needs to run in ISE, and the path needs to be the same as where the script lives in the terminal.
*edit* and I think i fixed the way it should run.
download folder, extract all somewhere - right click the Garmin_CSV_Converter_To_USA.ps1 file - run in powershell (you might need to open the file, add a # or something at the end then save to get around execution level warning/error because I wrote this today so its not signed) When prompted with a file explorer prompt, point to the FIT files either on the device or anywhere else if you offload them (it will copy to the fit_temp folder as a backup anyways and work from there rather than on the device)
There will be a summary displayed on the screen with a prompt for "Session Name" - Now is the time to name the session. The session name will be the name of the text file, spaces are ok.
The TXT file results appear in the "Results" folder as does the unmodified CSV file and can be opened with anything, its a text file.
So why bother doing this? If you notice, you can select multiple files at once and it processes them in a batch. It will display a summary and prompt to name for each one. I dont think Garmin or whatever that other software is allows for this functionality and I kinda of really need it if I am doing a OCW test.
I'll add ES and SD as well, but not right now. it was a headache enough to get the user interaction as minimal as possible. The bones are built, now can add features and fix minor bugs
https://drive.google.com/drive/folders/1...drive_link
anyways, stripped the sdk down to bare bones so my google drive folder should have everything needed minus instructions. you need to have java to run. i will fix it up a little later, but needs to run in ISE, and the path needs to be the same as where the script lives in the terminal.
*edit* and I think i fixed the way it should run.
download folder, extract all somewhere - right click the Garmin_CSV_Converter_To_USA.ps1 file - run in powershell (you might need to open the file, add a # or something at the end then save to get around execution level warning/error because I wrote this today so its not signed) When prompted with a file explorer prompt, point to the FIT files either on the device or anywhere else if you offload them (it will copy to the fit_temp folder as a backup anyways and work from there rather than on the device)
There will be a summary displayed on the screen with a prompt for "Session Name" - Now is the time to name the session. The session name will be the name of the text file, spaces are ok.
The TXT file results appear in the "Results" folder as does the unmodified CSV file and can be opened with anything, its a text file.
So why bother doing this? If you notice, you can select multiple files at once and it processes them in a batch. It will display a summary and prompt to name for each one. I dont think Garmin or whatever that other software is allows for this functionality and I kinda of really need it if I am doing a OCW test.
I'll add ES and SD as well, but not right now. it was a headache enough to get the user interaction as minimal as possible. The bones are built, now can add features and fix minor bugs