Skip to content

samples: add sat-pass-prediction Zephyr sample#253

Open
buckleypaul wants to merge 1 commit into
HubbleNetwork:mainfrom
buckleypaul:samples/sat-pass-prediction
Open

samples: add sat-pass-prediction Zephyr sample#253
buckleypaul wants to merge 1 commit into
HubbleNetwork:mainfrom
buckleypaul:samples/sat-pass-prediction

Conversation

@buckleypaul

Copy link
Copy Markdown
Collaborator

A sample application that uses satellite pass prediction to time transmissions. The main loop computes the next pass above the device location, sleeps until it opens, then broadcasts a packet.

An optional shell interface exposes runtime state, and a companion tool fetches orbital parameters from the Hubble ephemeris API.

A sample application that uses satellite pass prediction to time
transmissions. The main loop computes the next pass above the device
location, sleeps until it opens, then broadcasts a packet.

An optional shell interface exposes runtime state, and a companion tool
fetches orbital parameters from the Hubble ephemeris API.

Signed-off-by: Paul Buckley <paul@hubble.com>
uint64_t now = hubble_time_get() / 1000ULL;
int64_t wait;

err = hubble_sat_next_pass_get(now, &device_pos, &pass);

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we put in the doc that device uptime must never be used for pass prediction, I'm not sure if having this sample is a good idea since we're going against our recommendation.

The issue is that hubble_sat_next_pass_get account for retries for TDR, with device uptime as counter source, the call to hubble_internal_time_drift_get() will returns 0 anyway since time is not synced. So time drift is not accounted for regardless of whatever value CONFIG_HUBBLE_SAT_NETWORK_DEVICE_TDR is set to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants