{"id":9775,"date":"2026-07-28T06:51:00","date_gmt":"2026-07-28T06:51:00","guid":{"rendered":"https:\/\/www.herewinpower.com\/?p=9775"},"modified":"2026-07-28T06:51:00","modified_gmt":"2026-07-28T06:51:00","slug":"battery-protocol-compatibility-smart-drone-bms","status":"publish","type":"post","link":"https:\/\/www.herewinpower.com\/ru\/blog\/battery-protocol-compatibility-smart-drone-bms\/","title":{"rendered":"Drone Battery Communication Compatibility: The Procurement Risk Most Teams Miss"},"content":{"rendered":"<figure class=\"wp-block-image aligncenter size-large\"><img fetchpriority=\"high\" decoding=\"async\" width=\"1264\" height=\"843\" src=\"https:\/\/www.herewinpower.com\/wp-content\/uploads\/2026\/07\/e17df0d5-348e-4127-b0c2-2d099dddd2ed.jpeg\" alt=\"Smart drone battery communication protocol compatibility diagram for procurement and integration\" class=\"wp-image-9774\" srcset=\"https:\/\/www.herewinpower.com\/wp-content\/uploads\/2026\/07\/e17df0d5-348e-4127-b0c2-2d099dddd2ed.jpeg 1264w, https:\/\/www.herewinpower.com\/wp-content\/uploads\/2026\/07\/e17df0d5-348e-4127-b0c2-2d099dddd2ed-768x512.jpeg 768w, https:\/\/www.herewinpower.com\/wp-content\/uploads\/2026\/07\/e17df0d5-348e-4127-b0c2-2d099dddd2ed-18x12.jpeg 18w\" sizes=\"(max-width: 1264px) 100vw, 1264px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Industrial drones are getting smarter\u2014and battery selection has quietly become an integration decision, not just a spec-sheet decision.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On paper, procurement can still look simple: Select battery \u2192 Install battery \u2192 Test flight<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">But in modern platforms, the first integration loop often looks like this:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Select battery \u2192 Connect BMS \u2192 Flight controller misreads telemetry \u2192 SOC mismatch \/ false warnings \u2192 Test delays \u2192 Firmware tuning or redesign<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">OEM teams usually start with the specs that are easy to compare:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p>Voltage<\/p><\/li><li><p>Capacity<\/p><\/li><li><p>Weight<\/p><\/li><li><p>C-rate<\/p><\/li><li><p>Energy density<\/p><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Those matter. But they don\u2019t answer the question that protects your schedule:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Can the aircraft interpret the battery\u2019s data reliably\u2014every flight, in every corner case?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For smart drone systems, compatibility isn\u2019t only electrical. It\u2019s also system communication compatibility.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Why Electrical Compatibility Is No Longer Enough for Intelligent Drone Batteries<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An \u201cintelligent drone battery\u201d isn\u2019t defined by chemistry alone. It\u2019s defined by whether the pack can publish trustworthy telemetry into the aircraft\u2019s decision loop.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A battery can hit the correct nominal voltage and still derail a program.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That\u2019s because, in many industrial UAV architectures, the battery is no longer only a power source. It\u2019s also a data-producing subsystem.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At minimum, the aircraft needs a reliable path for telemetry to move through the stack:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Battery \u2192 BMS \u2192 Flight controller \u2192 Ground station (and sometimes ESC \/ power-management ECU)<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When that path is missing\u2014or worse, present but semantically wrong\u2014you get an integration failure that doesn\u2019t look like a battery defect. It looks like \u201csoftware instability,\u201d \u201crandom warnings,\u201d or \u201cunreliable flight time.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is why procurement teams get surprised: the pack meets the electrical datasheet, yet integration still fails.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p>If your flight controller can\u2019t trust SOC and fault status, it can\u2019t make deterministic safety decisions\u2014no matter how good the cells are.<\/p><\/blockquote>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">How Battery Communication Affects Drone System Integration<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Communication compatibility has two layers:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><p><strong>Interface\/protocol fit<\/strong>: can the battery talk to the flight stack on the right physical\/data interface?<\/p><\/li><li><p><strong>Data semantics fit<\/strong>: does the aircraft interpret the fields correctly (units, scaling, IDs, thresholds, validity flags)?<\/p><\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">If either fails, the integration timeline expands.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u201cBattery protocol compatibility\u201d is a major part of drone battery compatibility, and it often becomes the hidden blocker in UAV battery integration programs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">CAN, UART, and SMBus: Different Protocols, Different Integration Requirements<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">This isn\u2019t about which protocol is \u201cbest.\u201d It\u2019s about what your aircraft is designed to ingest\u2014and whether the battery speaks that language.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p><strong>CAN (often DroneCAN\/UAVCAN in UAV ecosystems)<\/strong><\/p><ul><li><p><strong>Strengths<\/strong>: robust in noisy environments, supports multi-node networks, good fit for industrial harnesses.<\/p><\/li><li><p><strong>Integration reality<\/strong>: CAN-based battery integration requires alignment on communication settings, message definitions, and system configuration.<\/p><\/li><li><p>This is where UAV battery CAN communication becomes an integration gate.<\/p><\/li><\/ul><\/li><li><p><strong>UART (often used as a MAVLink data path)<\/strong><\/p><ul><li><p><strong>Strengths<\/strong>: simple point-to-point link, straightforward bring-up.<\/p><\/li><li><p><strong>Integration reality<\/strong>: you still need consistent link settings and a verified message definition so the aircraft interprets values correctly.<\/p><\/li><\/ul><\/li><li><p><strong>SMBus \/ I2C smart battery interfaces<\/strong><\/p><ul><li><p><strong>Strengths<\/strong>: widely used for \u201csmart battery\u201d style data exchange.<\/p><\/li><li><p><strong>Integration reality<\/strong>: compatibility depends on whether your flight stack supports the monitor mode and data fields you need.<\/p><\/li><\/ul><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If your platform is built around one interface but the battery ships with another\u2014or ships with proprietary message definitions\u2014you\u2019ve created a translation project.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That translation work is rarely planned in procurement timelines.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">BMS Telemetry and Data Semantics Are More Than Monitoring<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A modern BMS is expected to output more than pack voltage.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typical telemetry fields include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p>SOC (State of Charge)<\/p><\/li><li><p>SOH (State of Health)<\/p><\/li><li><p>Pack voltage and current<\/p><\/li><li><p>Temperatures (pack \/ cell groups)<\/p><\/li><li><p>Fault codes \/ status flags (over-current, over-temp, under-voltage, etc.)<\/p><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This is the core of drone battery BMS communication: the aircraft isn\u2019t just \u201creading a battery,\u201d it\u2019s ingesting a stream of operational inputs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">These fields drive real system logic:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p><strong>Flight-time estimation<\/strong>: If SOC is wrong, your \u201cminutes remaining\u201d model collapses.<\/p><\/li><li><p><strong>Warning thresholds<\/strong>: A pack can be electrically fine while the system throws a low-battery warning because the data stream says so.<\/p><\/li><li><p><strong>Maintenance and fleet diagnostics<\/strong>: Without readable fault logs and consistent SOH reporting, you can\u2019t manage reliability at scale.<\/p><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If you want a deeper overview of how BMS capabilities impact safety and lifespan, see Herewin\u2019s explainer on <a target=\"_self\" rel=\"follow\" class=\"link\" href=\"https:\/\/www.herewinpower.com\/drone-battery\/bms-role-in-drone-battery-performance-safety-and-lifespan\/\">advanced BMS functions for UAV safety and lifespan<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Incorrect Battery Data Can Create Operational Risks<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Most teams recognize the risk of an electrical mismatch.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Fewer teams account for <strong>data mismatch<\/strong>, which can be just as operationally dangerous.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Example: SOC mismatch<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p>Actual pack SOC (based on energy removed): ~40%<\/p><\/li><li><p>SOC reported to the aircraft: ~15%<\/p><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Even if the pack can still deliver the power, the aircraft logic may:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p>trigger premature Return-to-Launch \/ auto-land behavior<\/p><\/li><li><p>enforce power limits earlier than necessary<\/p><\/li><li><p>force conservative mission planning that reduces productivity<\/p><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The inverse is worse:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p>Actual SOC: low<\/p><\/li><li><p>Reported SOC: high<\/p><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Now your reserve margin is fiction.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Example: fault semantics mismatch<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the BMS flags an event as \u201ccritical\u201d but the flight controller treats it as \u201cinformational\u201d (or vice versa), you get either nuisance aborts or unsafe continuation.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Hidden Costs of Battery Protocol Incompatibility<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Protocol incompatibility rarely shows up as \u201cbattery failure.\u201d It shows up as <strong>engineering time<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Longer Integration and Validation Cycles<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">When a battery doesn\u2019t match the flight stack\u2019s expected interface and data mapping, the fix is usually software work:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p>message field mapping (units, scaling, IDs)<\/p><\/li><li><p>parameter tuning (warning thresholds, failsafe timers)<\/p><\/li><li><p>gateway\/translator development (CAN &#x2194; UART &#x2194; SMBus bridges)<\/p><\/li><li><p>repeated bench + flight validation loops<\/p><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">That consumes the scarcest resource in drone OEM programs: engineering hours during EVT\/DVT.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Poor Diagnostics Increase Maintenance Difficulty<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Even if you \u201cmake it work,\u201d poor data accessibility turns into a long-term reliability tax.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If your maintenance team can\u2019t:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p>read BMS event logs<\/p><\/li><li><p>interpret fault codes consistently<\/p><\/li><li><p>correlate battery events with flight logs<\/p><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Then field issues become slower and more expensive to resolve.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is where \u201cprotocol compatibility\u201d becomes \u201cmaintainability.\u201d<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">A simple TCO lens: what protocol mismatch actually costs<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You don\u2019t need a full financial model to see exposure. Track three indicators that show up in every program:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p><strong>Engineering hours<\/strong> spent on mapping\/debug and edge-case handling<\/p><\/li><li><p><strong>Validation cycles<\/strong> added (bench re-tests + flight re-tests after firmware changes)<\/p><\/li><li><p><strong>Field diagnostic cost<\/strong> (time to isolate battery-related issues when logs\/fault semantics aren\u2019t consistent)<\/p><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If you can\u2019t estimate these early, it\u2019s hard to defend a battery choice internally.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">What OEMs Should Confirm Before Selecting a Smart Drone Battery Supplier<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Below is a procurement checklist designed for drone OEM electrical engineers. Every item is intentionally binary.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1) Communication interface and protocol fit<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p>Does the battery support the interface our flight stack expects (CAN \/ UART \/ SMBus)?<\/p><\/li><li><p>If CAN is used, are the message definitions documented (e.g., DBC\/register map), and are IDs stable across firmware versions?<\/p><\/li><li><p>Is there a defined plan for gateways\/translators if the interface doesn\u2019t match natively?<\/p><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">2) Data mapping (units, scaling, validity)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p>Can the supplier provide a field map for SOC\/SOH\/voltage\/current\/temperature\/fault flags?<\/p><\/li><li><p>Are there validity flags (e.g., SOC-valid) or quality indicators to avoid acting on bad data?<\/p><\/li><li><p>Have you validated that the ground station display matches the BMS raw values (no scaling errors)?<\/p><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">3) SOC accuracy expectations (under dynamic load)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p>Has SOC behavior been validated under mission-like load profiles (takeoff peaks, steady hover\/cruise, reserve margin)?<\/p><\/li><li><p>Is the SOC estimation method documented at a high level (coulomb counting + correction vs voltage-only heuristics)?<\/p><\/li><li><p>Do you have a defined acceptance criterion for SOC error at key points (e.g., at 30% and 15%)?<\/p><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">4) Fault codes and aircraft response<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p>Is there a fault dictionary (definition, threshold, hysteresis, reset condition) for each fault flag?<\/p><\/li><li><p>Is the mapping between BMS faults and aircraft actions explicitly defined (warning vs critical vs immediate land)?<\/p><\/li><li><p>Have you tested fault injection (or simulated faults) to verify the aircraft response?<\/p><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">5) Communication loss behavior<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p>If telemetry drops out, does the aircraft enter a defined safe mode (voltage-based fallback, conservative thresholds, mission abort rules)?<\/p><\/li><li><p>Have you tested communication loss on the bench and verified logs show the event clearly?<\/p><\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">6) Flight controller configuration evidence<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">This is where many \u201ccompatible on paper\u201d batteries turn into integration work\u2014because the battery monitor mode and field mapping have to match what the flight stack expects.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p>Does your integration plan include explicit flight stack parameters and verification steps?<\/p><\/li><li><p>Have you confirmed your stack\u2019s expected smart battery mode and bus settings?<\/p><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Most flight stacks require battery monitor configuration and validation steps before deployment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">7) Firmware support and change control<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p>Will the supplier commit to firmware support during EVT\/DVT (response time, versioning discipline)?<\/p><\/li><li><p>Is there a change-control process for protocol changes (IDs\/fields) to prevent silent regressions?<\/p><\/li><li><p>Can the supplier provide anonymized logs from prior integrations as evidence of maturity?<\/p><\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">A Short Integration Case Example<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A drone OEM selected a battery with matching voltage and capacity. Integration looked fine in early bench checks\u2014until flight test.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What showed up:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p>SOC drifted under dynamic load<\/p><\/li><li><p>Warning messages were inconsistent<\/p><\/li><li><p>Part of the battery status couldn\u2019t be interpreted reliably<\/p><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The pack wasn\u2019t \u201cbad.\u201d The interface was.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Result:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p>extra firmware\/debug cycles<\/p><\/li><li><p>delayed flight testing<\/p><\/li><li><p>unplanned effort to build and validate a mapping layer<\/p><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">That\u2019s the hidden risk: you can buy a pack that meets the datasheet and still miss your schedule.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">The Best Smart Drone Battery Must Communicate Reliably<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For smart drone platforms, the \u201cbest\u201d battery is not just one that delivers power.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It\u2019s one that:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><p>communicates on an interface your aircraft is designed to ingest<\/p><\/li><li><p>outputs telemetry your flight controller can interpret correctly<\/p><\/li><li><p>behaves predictably under faults and communication loss<\/p><\/li><li><p>supports maintainable diagnostics across the fleet lifecycle<\/p><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If you want to reduce integration risk early, treat battery selection as a system interface decision\u2014not a component purchase.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For OEM programs requiring customized battery communication, an experienced ODM\/OEM partner should be able to provide protocol documentation, integration support, and validation assistance.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Herewin supports industrial UAV battery programs with customized BMS communication, pack design, and system validation support. If you\u2019d like to discuss an integration approach for your platform, you can <a target=\"\" rel=\"noopener noreferrer nofollow\" class=\"link\" href=\"https:\/\/www.herewinpower.com\/\">contact<\/a> the Herewin team.<\/p>","protected":false},"excerpt":{"rendered":"<p>Why smart drone batteries fail integration: BMS protocol\/data mapping issues, hidden costs, and an OEM checklist to validate compatibility.<\/p>","protected":false},"author":3,"featured_media":9774,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[1,83],"tags":[],"class_list":["post-9775","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","category-drone-battery"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.herewinpower.com\/ru\/wp-json\/wp\/v2\/posts\/9775","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.herewinpower.com\/ru\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.herewinpower.com\/ru\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.herewinpower.com\/ru\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.herewinpower.com\/ru\/wp-json\/wp\/v2\/comments?post=9775"}],"version-history":[{"count":1,"href":"https:\/\/www.herewinpower.com\/ru\/wp-json\/wp\/v2\/posts\/9775\/revisions"}],"predecessor-version":[{"id":9786,"href":"https:\/\/www.herewinpower.com\/ru\/wp-json\/wp\/v2\/posts\/9775\/revisions\/9786"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.herewinpower.com\/ru\/wp-json\/wp\/v2\/media\/9774"}],"wp:attachment":[{"href":"https:\/\/www.herewinpower.com\/ru\/wp-json\/wp\/v2\/media?parent=9775"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.herewinpower.com\/ru\/wp-json\/wp\/v2\/categories?post=9775"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.herewinpower.com\/ru\/wp-json\/wp\/v2\/tags?post=9775"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}