Support Forums
Data compression

Hi All,

Here's a quick question... I am looking into using some satellite telemetry to send a large bunch of data daily and want to minimize transmission time to cut costs, one sure way is to reduce the file size being sent.

The data being a csv file should be able to be "zipped" substantially before being sent - is it possible to implement some form of data compression in the DT80? If not presently available maybe the R+D department could look into the possibilities for future storage/transmission benefits?

Kind regards,
Bill

Hi All, Here's a quick question... I am looking into using some satellite telemetry to send a large bunch of data daily and want to minimize transmission time to cut costs, one sure way is to reduce the file size being sent. The data being a csv file should be able to be "zipped" substantially before being sent - is it possible to implement some form of data compression in the DT80? If not presently available maybe the R+D department could look into the possibilities for future storage/transmission benefits? Kind regards, Bill

Maybe check the size of an original .dbd binary file against an unloaded text file for the same stored data and see if the binary file is any smaller (don't know if it actually is as I have never specifically done this).

Then if it is, implement the command line DUMP utility from Datataker back on wherever the data is being sent to unpack it. Also maybe look at running two schedules to give you 'bare bones' data for regular transmission and more detailed data for manual unload or transfer when required.

You could also run a polled schedule via ALARMS to only log when the data has actually changed, make the program a bit more complex but will reduce the data volume.

Far as I know the best way to have a smaller data file is to have less data.

Maybe check the size of an original .dbd binary file against an unloaded text file for the same stored data and see if the binary file is any smaller (don't know if it actually is as I have never specifically done this). Then if it is, implement the command line DUMP utility from Datataker back on wherever the data is being sent to unpack it. Also maybe look at running two schedules to give you 'bare bones' data for regular transmission and more detailed data for manual unload or transfer when required. You could also run a polled schedule via ALARMS to only log when the data has actually changed, make the program a bit more complex but will reduce the data volume. Far as I know the best way to have a smaller data file is to have less data.
25
1
1
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft