Watch App : HRV

Former Member
Former Member
HRV app. Discussion, report bugs, suggested features, etc...

HRV
Get the app.

Graphing.
The design currently only saves to 1 location per day. The timestamp is taken when the test starts, so autostart will take the timestamp at the scheduled time. This means that any saved test will overwrite any previous test of that same day. A day is calculated from the local timezone, so travelling won't disrupt the storage so long as you have updated the timezone before starting the test. The averages are a 30 day mean average.

Description & Explanation
Wouldn't that be nice. Will happen, but might take a while.
This page could be useful.

Notes
- Your device must have firmware that supports Connect IQ Apps.
- You can save the results by creating a log file. To do this you must work out which name has been applied to the HRV app file. The apps are in the /GARMIN/APPS folder. It will be a name something like A6227C9B.PRG. You then create a log file with the same name, e.g /GARMIN/APPS/LOGS/A6227C9B.TXT. Each reading you save will output a result formatted as ISO8601 date & time, hrv, avg pulse, 30 day hrv avg, 30 day pulse avg.
  • Former Member
    Former Member over 10 years ago
    A note to all users. I believe I have tracked down the last cause of the crashes. It is related to a CIQ function for saving the settings & results. To avoid a crash simply exit the app after a test, or after changing a setting. If you navigate through the pages after either of these the app will soon crash.
  • Is it possible to save the actual R-R interval to the log file?
  • Former Member
    Former Member over 10 years ago
    Yes it's possible, but I have not put too much thought into it at the moment. I see the logging I have implemented as a temporary measure, especially since I am unable to give the file a user friendly name. I will look into the possibilities after I have released the alpha version. On a plus note I have removed all the bugs I have been able to discover, and the alpha release should be in the next few days. What do you intend to use them for? What format would you like to see them in?
  • Keeps rebooting watch

    I have The 2.60 Firmware for the Vivoactive and the 0.9.9 beta HRV. Every time I load it and touch the screen, the watch reboots.
  • Yes it's possible, but I have not put too much thought into it at the moment. I see the logging I have implemented as a temporary measure, especially since I am unable to give the file a user friendly name. I will look into the possibilities after I have released the alpha version. On a plus note I have removed all the bugs I have been able to discover, and the alpha release should be in the next few days. What do you intend to use them for? What format would you like to see them in?


    that would be great. And I think just the raw R-R interval would suffice, perhaps in CSV format? The main advantage I can see is that it then can be used for people(like me) who're interested in more than just the RMSSD, to import the data into app like Kubios to do more comprehensive time & frequency domain analysis. Anything extra could be shown in the app would be a welcome bonus of course but I'm not sure how much processing power is available from just the watch.

    This would make pretty cool, accurate & most compact form of HRV logging that I know of...
  • Former Member
    Former Member over 10 years ago
    I have The 2.60 Firmware for the Vivoactive and the 0.9.9 beta HRV. Every time I load it and touch the screen, the watch reboots.
    I'm sorry about that. Is this the first version you have used? I believe I may have let slip an error that will not allow the recent versions to create a new result. I got a bit muddled trying to address other issues, and sadly traded 1 problem for another it seems. The release in the next couple of days will not have this problem.
  • Former Member
    Former Member over 10 years ago
    that would be great. And I think just the raw R-R interval would suffice, perhaps in CSV format? The main advantage I can see is that it then can be used for people(like me) who're interested in more than just the RMSSD, to import the data into app like Kubios to do more comprehensive time & frequency domain analysis. Anything extra could be shown in the app would be a welcome bonus of course but I'm not sure how much processing power is available from just the watch.

    This would make pretty cool, accurate & most compact form of HRV logging that I know of...
    Being that I first started out with Kubios I know where you're coming from. I started out in HRV by creating an app with the FIT SDK to extract the information from a fit file into Kubios readable data. As previously alluded the logging system is not ideal for creating specific files, over consecutive readings the file would quickly grow, and start creating new files when the first is full. This is slightly problematic, in that you may have to extract the data from multiple locations and piece it together. While that in itself is not a particularly hard process, and is one that I would happily do myself, it is not the sort of process I want to release to all users. I suppose I could create an extra item in the menu, that when checked gave you an additional step to enable at the start of each test. I will keep it in mind. Cross your fingers and you might (no promises) see it in the next few days.
  • that would be prefect!
    And yes I agree that probably not every user wants this.
  • Former Member
    Former Member over 10 years ago
    Hrv 1.0 released :)
  • Former Member
    Former Member over 10 years ago
    No Kubios option yet Shinew :(