Portable Power: Check Device Start Overlap on a Timeline

To check whether device starts overlap, put each documented start interval and steady-running interval on the same timeline, then total the demand within each interval. Compare that total with the exact station's applicable output limits. Staggering can remove overlapping starts, but it does not resolve an excessive steady load or missing startup evidence. If the shared limit or the relevant transient demand is unknown, mark simultaneous operation unresolved.

This worksheet is for households planning non-critical devices whose individual power paths have already been verified. It uses existing documentation and observations from supported ordinary operation. It is not a procedure for finding a station's overload threshold, and the illustrative numbers below are not FlashFish test results.

Separate the timing question from the energy question

A daily watt-hour budget asks how much energy tasks consume over time. An overlap timeline asks how much output is required at the same moment. A modest daily energy total can still include a demanding start interval. Conversely, moving a start later can reduce overlap without reducing the energy that the tasks ultimately use.

Keep two records: the energy plan and the concurrent-power plan. A larger Wh figure cannot establish startup capability. Nor does a successful individual start establish that another device can start while the first one is running.

Gather evidence before drawing the timeline

For each device, record its exact identity, the approved adapter or cable, and the station output used. Distinguish power measured at a device from power measured at the station's output; those values do not necessarily describe the same boundary. Put all values used in a combined sum on a consistent boundary.

Record what the startup evidence actually captures: the interval duration, the observed demand, and the source or instrument's limitations. A slow display reading or a single maximum with no timestamp does not establish when a brief event occurred. If the evidence cannot locate or bound the start interval, leave that part of the timeline open rather than choosing an arbitrary delay.

Copy this evidence sheet for each already verified device path
Device and path	Start interval	Start-demand evidence	Steady interval and demand	Overlap sum	Unresolved limit
Exact device, adapter, station port	Start and end on one common clock	Documented value or bound, source, capture limitations	Start/end and supported output-boundary W	Sum of demands active in that interval	Per-port, shared-group, AC or whole-unit restriction
Next device, with its own verified path	Proposed start and end	Unknown if not documented	Known value or unknown	Unresolved if a required term is missing	Exact manual clause still needed

Split the schedule wherever a device changes state

Choose a common time origin, such as the start of the planned session. Mark each start, transition to steady operation, and shutdown.
Divide the timeline at every marked event. Within each resulting segment, list all active device states.
Add supported demand values or conservative documented bounds for that segment. Keep unknown terms visible.
Check each applicable limit separately. An AC-only sum cannot stand in for a mixed AC-and-USB whole-unit check.
Move a proposed start only if the revised schedule removes the relevant overlap. Recalculate later segments, including the period when both devices run steadily.

A candidate window passes this worksheet's numerical screening only when every relevant segment and limit is supported. That is not a guarantee of operation: device modes, timing variation, measurement uncertainty, and the original instructions still matter. A schedule resting exactly on a limit leaves no demonstrated allowance for those unknowns.

Three illustrative timeline decisions

The following cases use invented low-risk device loads and a hypothetical 100 W continuous screening limit. They are arithmetic examples, not recommendations for a particular station, device, or delay. Assume the stated demands are complete bounds at the same output boundary and all other applicable limits have been checked.

Example 1: Moving one start creates a candidate window

Device A's documented start interval is 0–5 seconds at 70 W, followed by 25 W steady demand. Device B needs 50 W during its 2-second start, then 20 W steadily. Starting both at second 0 produces 120 W during seconds 0–2, above the assumed limit. Starting B at second 8 instead produces 70 W, then 25 W, then 75 W during seconds 8–10, then 45 W. That revised timeline fits the hypothetical screen, subject to evidence covering timing variation.

Example 2: Removing start overlap does not fix steady demand

Suppose A settles at 60 W and B settles at 50 W. Even if their starts are completely separated, their shared steady interval totals 110 W. A delayed start cannot solve that segment. The plan needs non-overlapping operating periods or a separately verified alternative, not a longer guessed pause.

Example 3: Missing timing evidence leaves the answer open

A's steady demand is documented at 25 W. B has a recorded 50 W maximum, but the record supplies neither a start duration nor evidence that it captured the transient. Writing “wait 10 seconds” adds no missing information. Record the proposed window as unresolved and request documentation that can bound B's start before claiming an overlap result.

Where FlashFish E103 and T300Pro fit

FlashFish E103 is specified at 179.2 Wh, 300 W rated pure-sine AC output, and a USB-C output up to 60 W. Its cited manual is a 230V version; those details do not identify the AC configuration of an individual U.S. unit. Confirm that unit's regional instructions before applying any AC comparison.

FlashFish T300PRO (also called T300Pro or TELLUS-T300Pro) is specified at 230 Wh and 300 W continuous pure-sine AC output with two 120V outlets. Two outlets do not establish 300 W per outlet. These headline specifications do not provide the complete shared-limit documentation and device traces needed to approve the mixed-output schedule in this article.

Use either model as a candidate only after matching its exact ports and regional variant to the existing device plan. Check the original instructions for your unit before relying on a disputed output arrangement.

FAQ

How long should I wait between starts?

There is no universal delay. Use the documented end of the first start interval and evidence about timing variation, then check the second start against every device still running. If you cannot bound those intervals, a specific number of seconds would be a guess.

Can I add the watt ratings printed on adapters?

Only if the values describe a suitable, consistent bound for the states and measurement boundary you are checking. A label does not automatically supply a time-resolved startup trace. Record its meaning and any missing evidence instead of treating every printed number as an observed demand.

Does enough battery capacity mean the simultaneous load fits?

No. Wh addresses energy; W addresses power at a moment. The timeline still needs the applicable continuous and transient restrictions, output-group limits, and device evidence. Neither nominal capacity nor an individual successful start answers all of those questions.

Finish with one supported decision

Save the proposed timing window, its largest supported segment demand, the limits checked, and any missing evidence. If the window is unresolved, identify the exact manual clause or startup record needed next. Once that question is resolved, compare the matching FlashFish model's documented output paths with the worksheet before choosing a station.

Next step: Compare FlashFish E103 specifications with your equipment list.