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
Output Config
Fetching data
Requesting from device
Each output has an igniter continuity window and a power-good handling mode. The igniter reads as good when its measured resistance sits between the low and high values: below the low value suggests a short, and above the high value suggests an open circuit or no igniter fitted.
Output 1
Igniter resistance (Ω)i
LOWGOODHIGH
Power-good handlingi
Live resistance-
Loading…
Output 2
Igniter resistance (Ω)i
LOWGOODHIGH
Power-good handlingi
Live resistance-
Loading…
Output 3
Igniter resistance (Ω)i
LOWGOODHIGH
Power-good handlingi
Live resistance-
Loading…
To set up expansion ports as outputs, use the Expansion & Accessories page.
Expansion & Accessories →
To choose when each output fires, use the Rules & Automations page.
Rules & Automations →
Test fire trace
No trace fetched yet
The board keeps its last five test fires on its own flash, each recorded at 50 Hz from half a second before the output came on. Fetch them to chart what the rails did.
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.