Where to buy Firmware updater USB WiFi config Log uploader Guides
HomeMy DevicesJupiter settings
DashboardTrackingLive Device InfoGeneral SettingsOutput ConfigArming & SafetyRules & AutomationsExpansion & AccessoriesCalibrationLogging & sensorsSIM & CellularAdvanced FeaturesCustom DatasetsBlack BoxSettings Queue & History
···
Checking arm state…
Jupiter9506···
connecting…
- -
—
CPU 20s— 3m—
View all device info →
Position
Sats-  -
hAcc-m
HDOP
-
AssistNow
-
GNSS alt
-
Pressure alt
-
Power
Batt-V
Cap-V
4V24.2V-V
CPU 20s100%-%
CPU 3m100%-%
Buck boost mode
-
Exp power
-
Signal
CSQ-/31
Net--
RSRP
-
RSRQ
-
Reconn
-
Expansion
EXP1Not connected
EXP2Not connected
EXP3Not connected
EXP4Not connected
Magnetic orientation
Heading
-
Declination
-
Field (µT)
-
Attitude
Roll
-
Pitch
-
Yaw
-
Tilt
-
Thermal
MBoard
-°
DBoard
-°
CPU
-°
Outputs
OUT1-
OUT2-
OUT3-
System
Disk-MB
RAM free
—
Uptime
—
Light (lux)
-
Device
Firmware
-
Boots
-
Last reset
-
Read-only view. This is a shared demo Jupiter, so you can look around every page but nothing can be changed or sent to the device.
Jupiter9506
Arming & Safety
Manual arming methods
Deliberate ways to arm the system. Any enabled method can arm it (they combine with OR).
Audio arming tones
Hold your phone to the Jupiter's microphone and play, or download the .wav. Encodes a 2 s 3 kHz preamble, 21 FSK bits (2 kHz=0 / 4 kHz=1, 75 ms each: 4-bit command + your 17-bit code), then a 500 ms 3 kHz end.
ArmDownload .wav
DisarmDownload .wav
Automatic arming methods
When enabled, the system arms itself once every threshold below is satisfied.
Before relying on automatic arming: make sure your motor's burn actually meets the thrust threshold settings below (magnitude, duration and window), or the launch will not be detected and the outputs will never be enabled. Always wait at least the minimum time since power-on before you launch.
s1 to 100
m50 to 1000
s30 to 1800
Required motor thrust i
These three combine into one check: the acceleration must stay above the magnitude for at least 95% of the duration, and that must have happened within the window.
s30 to 1000
ms100 to 2000
mG2000 to 20000
General arming options
Behaviour and coverage that applies however the system is armed.
Expand arming to cover these:
s20 to 1800
Automatic disarm
Optional timers that return the outputs to a safe, disarmed state after a flight. All independent; any one that elapses disarms.
Each timer disarms the system and drives the outputs safe once it elapses. Set a timer to 0:00 to turn it off. Leave the landing and recording timers off if a rule needs the outputs to stay armed after touchdown (for example a locator siren or a recovery task).
mins0 = off
mins0 = off
mins0 = off
mins0 = off
Remote arm / disarm
Arm or disarm over the cellular link while the device is online. Each action asks for a one-time confirm code.
Live safety status
Connecting to your device. Live signals stream here every 2 seconds while this page is open.
Arm / disarm history
Arm and disarm events recorded on the server, newest first.
Disarmedvia cellular26 Sep 02:17:50
Armedvia cellular26 Sep 02:17:18
Disarmedvia reboot31 Aug 14:13:07
Armedvia magnet27 Aug 19:04:23
Disarmedvia landing27 Jul 14:23:14
Armedvia magnet27 Jul 14:22:31
Disarmedvia magnet26 Jul 10:17:51
Armedvia magnet26 Jul 10:17:35
Disarmedvia magnet24 Jul 17:52:17
Armedvia magnet24 Jul 17:52:01
Disarmedvia reboot24 Jul 17:46:55
Armedvia magnet24 Jul 17:46:42
Jupiter settings
Settings sync

We’ll check the device’s settings hash against the website’s copy. These should always be in sync, and this confirms they absolutely are.

Type the code above to confirm.