npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@b1naryth1ef/svag-telemetry-format

v1.13.0

Published

Telemetry data format for the Svag application

Readme

Svag Telemetry Format (STF)

This repository contains a very simple protobuf based file format for telemetry data recorded by the Svag app, a third party application for the Stark Varg series of electric motorcycles. This format is designed to record samples of all the relevant telemetry data produced by the VCU.

Format Details

The format mostly replicates the data available via the Bluetooth interface, and the units also directly match the data received via this interface. This can produce unexpected results as different fields may use different units depending on Stark's internal design.

Power Usage

One very common question when processing a STF file would be calculating the instantaneous motor power. This can be done with two fields, the battery_dc_bus and battery_current. First you must divide battery_dc_bus by 10 to convert it into volts. Next we can simply do the standard electrical calculation of voltage * current, or in our case: (battery_dc_bus / 10) * battery_current.

To calculate the HP from the KW used in the motor we must know the motors power factor. For at least the Varg EX and probably the MX this value is 0.0011. Multiplying the motor wattage by this value produces the instantaneous HP used.

Battery Cell Voltages

While not all recordings may include this data as its very verbose, the battery cell voltages include a value for all 100 cell groups. One half of the pack is indexes 0-49 and the other half is 50-99. Cell voltages are recorded in 1/10000 of a volt, not millivolts.

GPS Data

GPS data from the VCU is not available so these fields are intended for the recording device to fill in. This data is intended to be contextual rather than authoritative.