Remote admin session
-- In a MeshCore client that supplies the sender timestamp, sync and - then verify: -
-clock sync
-clocktempradio command
+ Before sending it, run get radio and save the result.
+ No clock setup is needed. Your saved settings return automatically.
+
- The test will include bridges. If the Puget Sound area experiences a - widespread power outage or loss of cellular service, we will end the - test early. A stock node's one-minute temporary test profile then ends - on that node's own saved radio settings. -
-
- Run get radio and record the saved primary tuple. Both
- primary TempRadio methods return to that saved tuple; they do not store
- a return tuple inside the temporary command. On a Companion, also run
- get radio2 and get radio2.cross so you can restore
- any non-default secondary-profile setup.
-
- The primary tempradioat and Companion
- tempradioat2 schedulers use UTC Unix time. Run
- clock on every node that will be scheduled and compare it
- with the browser UTC time below. It should agree to within about a minute.
- A wrong clock can start late, start immediately, or cause the schedule to
- be rejected.
-
Send this command to return to your saved radio settings in one minute:
+- No node-clock correction is applied. Scheduled commands use the normal UTC epochs. -
- -
- This changes only the absolute tempradioat and
- tempradioat2 epochs shown on this page; it does not issue a
- clock-setting command. The correction is for this node and this open page
- only: it is never added to generated URLs, and is cleared on reload. If
- the node clock later syncs or jumps, delete and queue the schedule again.
-
- In a MeshCore client that supplies the sender timestamp, sync and - then verify: -
-clock sync
-clockCopy this fresh, run it immediately, and then verify with clock:
time 0
-clock
- If setting the correct time returns ERR: clock cannot go backwards,
- run the command below. It resets the clock to an older fallback date and
- reboots the node immediately, so it sends no reply. After the node reconnects,
- copy and run the fresh local clock command above, verify with clock,
- and then add the Companion tempradioat2 schedule again. The
- reboot clears any pending scheduled entries.
-
- If resetting or correcting this remote node's clock is not safe, leave - it unchanged and use the optional node-clock conversion above instead. -
-clkreboot- The Companion schedule must be queued while both its start and end are - in the future and within the firmware's roughly 24-day scheduling - horizon. Scheduled entries are held in RAM and disappear if the node - reboots. -
- - -- The immediate commands become available one hour before the official - start. Their timeout shrinks so every node still returns at the same end - time. Before that setup window, the command text and copy controls stay - unavailable. -
- -
- rxtx permits transmission on the second profile;
- radio2.cross on copies ordinary Companion traffic across
- the primary and temporary profiles.
-
- A Simple Repeater build can schedule its primary radio with
- tempradioat. A Companion can instead schedule its second
- profile with tempradioat2. Both commands use the exact UTC
- epochs below, switch at the common start, and restore saved settings at
- the common end. A node-clock conversion above replaces only those command
- epochs with its per-node translated values. Room-server and sensor roles
- use Option 1 instead.
-
- Use the immediate tempradio command in Option 1 after
- its setup window opens.
-
- This is available only on a Simple Repeater build with primary
- scheduled-radio support. It changes the primary tuple at the start
- and restores the saved tuple at the end. If get tempradioat
- returns Error: unsupported, use Option 1 instead.
-
- Crossing is saved independently and remains on after the
- temporary second profile ends. Restore its previous value after the
- test; auto is the normal default.
-
- A stock node can leave an active test as shown below. For a primary or
- Companion schedule, the all form removes every temporary
- schedule in that family. To preserve another schedule, first run the
- corresponding get command and replace all with
- its displayed entry number.
-
- Stock MeshCore has no normalradio command. This starts a
- one-minute temporary session on this page's test profile without
- saving over the node's configuration. When that minute ends, the node
- restores whatever primary radio settings it had saved.
-
- This replaces the current temporary timeout with 30 minutes, then - restores the saved primary tuple automatically. -
-- Before the start, this removes the queued temporary schedule. While - it is running, it also restores the saved primary tuple after the - command reply drains. -
-
- If get radio2.cross was not auto before the
- test, restore that recorded value instead.
-
- These commands clear any absolute second-profile schedule and give
- the test profile a fresh 30-minute lease. The saved second profile
- returns at expiry, but crossing remains on; afterward,
- restore the value you recorded before the test (auto is
- the normal default).
-
- Primary tempradioat scheduling is implemented by the Simple
- Repeater role; room-server and sensor roles use their immediate
- tempradio command during the setup window. The Companion
- scheduling commands require current full-parser firmware, and
- tempradio2 and tempradioat2 require a build with
- dual-radio-profile support. If a node reports an unknown command, use only
- a method that its installed firmware documents.
+ Use these only if your firmware supports the listed commands or you need
+ dual-radio operation, scheduling, or clock correction.
Firmware schedule epochs:
+ The test will include bridges. If the Puget Sound area experiences a + widespread power outage or loss of cellular service, we will end the + test early. A stock node's one-minute temporary test profile then ends + on that node's own saved radio settings. +
+
+ Run get radio and record the saved primary tuple. Both
+ primary TempRadio methods return to that saved tuple; they do not store
+ a return tuple inside the temporary command. On a Companion, also run
+ get radio2 and get radio2.cross so you can restore
+ any non-default secondary-profile setup.
+
+ The primary tempradioat and Companion
+ tempradioat2 schedulers use UTC Unix time. Run
+ clock on every node that will be scheduled and compare it
+ with the browser UTC time below. It should agree to within about a minute.
+ A wrong clock can start late, start immediately, or cause the schedule to
+ be rejected.
+
+ No node-clock correction is applied. Scheduled commands use the normal UTC epochs. +
+ +
+ This changes only the absolute tempradioat and
+ tempradioat2 epochs shown on this page; it does not issue a
+ clock-setting command. The correction is for this node and this open page
+ only: it is never added to generated URLs, and is cleared on reload. If
+ the node clock later syncs or jumps, delete and queue the schedule again.
+
+ In a MeshCore client that supplies the sender timestamp, sync and + then verify: +
+clock sync
+clockCopy this fresh, run it immediately, and then verify with clock:
time 0
+clock
+ If setting the correct time returns ERR: clock cannot go backwards,
+ run the command below. It resets the clock to an older fallback date and
+ reboots the node immediately, so it sends no reply. After the node reconnects,
+ copy and run the fresh local clock command above, verify with clock,
+ and then add the Companion tempradioat2 schedule again. The
+ reboot clears any pending scheduled entries.
+
+ If resetting or correcting this remote node's clock is not safe, leave + it unchanged and use the optional node-clock conversion above instead. +
+clkreboot+ The Companion schedule must be queued while both its start and end are + in the future and within the firmware's roughly 24-day scheduling + horizon. Scheduled entries are held in RAM and disappear if the node + reboots. +
++ These commands become available one hour before the official start. + Their timeout shrinks so the Companion returns at the same end time. +
+ +
+ rxtx permits transmission on the second profile;
+ radio2.cross on copies ordinary Companion traffic across
+ the primary and temporary profiles.
+
+ A Simple Repeater build can schedule its primary radio with
+ tempradioat. A Companion can instead schedule its second
+ profile with tempradioat2. Both commands use the exact UTC
+ epochs below, switch at the common start, and restore saved settings at
+ the common end. A node-clock conversion above replaces only those command
+ epochs with its per-node translated values. Room-server and sensor roles
+ use the stock join command above instead.
+
+ Use the stock tempradio command above after
+ its setup window opens.
+
+ This is available only on a Simple Repeater build with primary
+ scheduled-radio support. It changes the primary tuple at the start
+ and restores the saved tuple at the end. If get tempradioat
+ returns Error: unsupported, use the stock join command
+ above instead.
+
+ Crossing is saved independently and remains on after the
+ temporary second profile ends. Restore its previous value after the
+ test; auto is the normal default.
+
+ For a primary or Companion schedule, the all form removes every temporary
+ schedule in that family. To preserve another schedule, first run the
+ corresponding get command and replace all with
+ its displayed entry number.
+
+ This replaces the current temporary timeout with 30 minutes, then + restores the saved primary tuple automatically. +
++ Before the start, this removes the queued temporary schedule. While + it is running, it also restores the saved primary tuple after the + command reply drains. +
+
+ If get radio2.cross was not auto before the
+ test, restore that recorded value instead.
+
+ These commands clear any absolute second-profile schedule and give
+ the test profile a fresh 30-minute lease. The saved second profile
+ returns at expiry, but crossing remains on; afterward,
+ restore the value you recorded before the test (auto is
+ the normal default).
+
+ Primary scheduling requires a Simple Repeater build. Companion
+ tempradio2 and tempradioat2 require dual-profile
+ firmware. If a command is unknown, use only the method your installed
+ firmware supports.
+