Home My Devices Jupiter settings
DashboardTrackingLive Device InfoGeneral SettingsOutput ConfigArming & SafetyRules & AutomationsExpansion & AccessoriesCalibrationLoggingSIM & CellularAdvanced FeaturesCustom DatasetsBlack BoxSettings Queue & History
···
Checking arm state…
Jupiter3640···
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.
Jupiter3640
General Settings
Identity
Flight detection
m1 to 200
s0 to 999
s60 to 99999
Sensors
1 to 50
1 to 50
After changing this setting the fusion can take 5-10 seconds to settle, so restarting the device is the safest option.
Apogee prediction
g1 to 100000
0 to 5
mm21 to 1000000
J/kgK200 to 400
Power
mV1000 to 20000
mV1000 to 20000
Super capacitor i
System
min-720 to 840
After-landing tracking
How often the device reports its position once it has landed. Slower saves power and keeps it findable for longer; faster finds it sooner but flattens the pack.
No battery pack set on the power card? Then there is no state of charge to work from, so the device walks these same four intervals on time instead: the first for 30 minutes, the second for 1 hour, the third for 2 hours, then the last one from then on.
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.