How to Do FOTA Remote Firmware Upgrades? Batch Update Device Firmware

Once construction IoT devices are deployed across sites, firmware upgrade becomes a major pain — traditionally either send engineers on-site (huge travel cost) or ship back to factory (downtime loss). FOTA (Firmware Over The Air) lets devices be reflashed remotely after deployment — a core ops capability of any IoT system. This guide details how to use JGY FOTA.

What FOTA Solves

Without FOTA you hit scenes like:

• Protocol change: The OEM upgrades CAN; old devices can't read new fields.
• Bug fix: A T-BOX bug causes intermittent drops or data corruption.
• Security patch: A vulnerability needs an urgent patch.
• New feature: New geofence algorithm, fuel-identification logic.

The traditional way: send engineers to each site; thousands of devices nationwide means millions in travel and downtime.

With FOTA: one click from the platform, devices auto-upgrade when idle — no site visit, no downtime.

Prerequisites for FOTA

Not every device can FOTA:

1. T-BOX supports FOTA: All three JGY models (YOOAI-GC-DT-CTF, CAN, CL) support it.
2. Device online: T-BOX must connect to the platform (4G signal reachable) during upgrade.
3. Stable power: Power loss during upgrade may brick the device.
4. Firmware uploaded: The new firmware package must be uploaded to the platform.
5. Model match: Different T-BOX models use different firmware — never flash the wrong one.

FOTA Upgrade Flow

Step 1: Upload Firmware

1. Go to the JGY platform Device Management → Firmware Management.
2. Click "Upload Firmware," pick the package (.bin or .hex).
3. Fill in:
   • Version (e.g., v2.3.1)
   • Applicable models (CTF/CAN/CL)
   • Release notes (what's fixed, what's new)
4. Upload completes; firmware enters "pending release."

Step 2: Select Target Devices

1. On the firmware detail page, click "Push Upgrade."
2. Select targets:
   • By model: Auto-lists all devices of that model.
   • By customer: Upgrade some customers first as a canary.
   • By region: Push region by region to reduce risk.
   • Manual multi-select: Pinpoint devices.
3. Confirm the list.

Step 3: Configure Upgrade Strategy

• Immediate: Execute on dispatch (for urgent patches, but ensure stable power).
• Scheduled: Run at a set time (e.g., 2–4 a.m., device idle, no business impact).
• Forced: Ignore current device state, force execution.
• Allow defer: Device picks its own timing (better compatibility).

Recommended: Scheduled (early morning) + allow defer — balances timeliness and stability.

Step 4: Execute and Monitor

1. Confirm strategy, click "Start Upgrade."
2. The platform dispatches in batch; the T-BOX downloads the package.
3. Download → MD5 verify → write to Flash → reboot.
4. The platform shows each device's status in real time:
   • Pending / Downloading / Verifying / Upgrading / Done / Failed
5. On completion, export the upgrade report.

The whole process typically takes 5–15 minutes (depending on firmware size and signal).

Canary Strategy for Batch Upgrades

Pushing all thousands at once is extremely risky — a shared bug bricks everything. Recommended canary strategy:

Three-Stage Canary

1. Stage 1 (5%): Pick a few "test devices" (internal, friendly customers); observe 24–48 hours.
2. Stage 2 (30%): After confirming no issues, expand to 30%; observe 24 hours.
3. Stage 3 (100%): Full push.

Canary Metrics

• Upgrade failure rate
• Post-upgrade drop rate
• Post-upgrade data-report anomaly rate
• Customer feedback

Any anomaly → pause subsequent pushes and investigate.

Rollback and Safety

Rollback

Bricking is the worst fear. JGY FOTA provides:

• Dual-bank firmware: A/B banks inside the T-BOX; new firmware writes to bank B; boot failure auto-rolls back to bank A.
• Manual rollback: The platform can issue "rollback to previous version," batch restore.
• Checksums: MD5/SHA256 verification; corrupted packages are rejected.

Security

• Firmware signing: Digitally signed packages, tamper-proof.
• Encrypted transport: Firmware download over HTTPS, MITM-proof.
• Permission control: Only authorized accounts can upload/push.
• Audit logs: All operations logged and traceable.

Best Practices to Avoid Bricking

1. Always canary first: Even urgent patches — at least 5%.
2. Avoid peak hours: Pick idle times (early morning, lunch).
3. Ensure stable power: Confirm charging/running state; avoid low battery.
4. Signal threshold: Mark weak-signal devices separately; upgrade when signal improves.
5. Prepare rollback: Before each upgrade, ensure the previous firmware is still on the platform for rollback.
6. Notify customers: For important upgrades, notify in advance ("devices will reboot briefly tonight around 2 a.m., about 5 minutes").

Common Issues

Q: What if the device drops during upgrade? A: The T-BOX caches upgrade state and resumes on reconnect. Dual-bank design prevents bricking even if interrupted.

Q: How to troubleshoot upgrade failure? A: Check the device upgrade log (Device Detail → Log Query). Common causes: insufficient storage, corrupted package, model mismatch, power loss.

Q: Can I upgrade the equipment controller (e.g., PLC) firmware? A: Yes. JGY T-BOX can FOTA some equipment controllers via CAN, but OEM protocol support is required.

Q: Does upgrade interrupt data reporting? A: Yes, but only for the few minutes of reboot. Scheduling in troughs makes impact negligible.

FOTA Upgrade Configuration Checklist

• Firmware uploaded, version/model/notes complete
• Targets filtered by canary strategy (5% → 30% → 100%)
• Strategy: scheduled (early morning) + allow defer
• Dual-bank firmware confirmed (anti-brick)
• Rollback ready (previous firmware available)
• Canary metric dashboard queryable
• Customer notification sent (important upgrades)

Follow this checklist and firmware upgrades across thousands of devices proceed reliably. For more FOTA and device-ops tactics, see device management or contact us.